From owner-freebsd-current@freebsd.org Sun Jan 14 02:10:07 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 503E5E6E8CF for ; Sun, 14 Jan 2018 02:10:07 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 23C8783F9B for ; Sun, 14 Jan 2018 02:10:07 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-io0-x235.google.com with SMTP id w188so9752212iod.10 for ; Sat, 13 Jan 2018 18:10:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=5cgqyc6XjOyTyaNf6rcjg+ISpEGrrzsxFJULUYI3DZU=; b=iqvL53CU+WZvheF6uOHqC8S77DcrAwgixa6NPq2ZYKO3FylkQ7h4OTMs0GgFLDwrbe gE5Qm+Q2ZLwczfyZQTOsAGSrFlIWN6pewd5jJBMdqVGNt9A3HY7yPqNpIhwrQ8lL26zj fjklfNxUZ4wQysl/+mvOgcyv79kcKGiZBn2YwFJwoJlFDgKo9QfgMM0k5BPvaGe+t4Oc FJYQyaT3fWlhsocSUx14Hc9IdUzHovCSkOqF/MRVImFcwz5L6837gB7W969t8MXGZTDr xflyLDpc5M+jXqGVDhe4cfnYU2k2uCPAckPrNUd9cvYCsemW5zBJ0rpZEAyZw3KiGYfk 4hlw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=5cgqyc6XjOyTyaNf6rcjg+ISpEGrrzsxFJULUYI3DZU=; b=pGHEUiXV2Bq2EWewhBJHQDSjSG5BorQfK2DZnEtuTXLKRlpPNZyKloslK7HMXn0yHj 7JTFpe5RBDaz5IosqHe5jhgtnZTvI7aSaalwLmzYoAh9ikkCVriGIxiRlVKM6F4P7vWk PgG//BjxcoB7flHAVGsXXDDBe05W7sUycTJGTIUXqtZNwfPvi1GSVpsWRSbbIE38xVQG 9rxoDEYdzeBHjQIzRUmAIU/5Jzq/JWhtqwGCcnVGLCs5VEfNNrZsPTiTAvNxpa9ihel0 a7N7I0gM/i05UHnzdHchCsl47sShy5tWsh/Wi7YeA030jdvVB17GgWpRVajVAfien+LB 4klQ== X-Gm-Message-State: AKwxytc6qOjUFLyEqBkGlpCVu9XWpBYvjnMLzqVP5Rtzj8kydo3sNlSw uWQBeCvHCWGk1KNDmyTwwSjtr5bIjYHpj4O3otjzeRkX X-Google-Smtp-Source: ACJfBoux+sXhd955cwyJf2yW0qGauHjzHqxDJB07WYrArE5d3nP2Hc4aqCd6RVEId0sooVLfeEo55wpBs1amxPaJaXs= X-Received: by 10.107.16.8 with SMTP id y8mr9461505ioi.213.1515895806306; Sat, 13 Jan 2018 18:10:06 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.164.193 with HTTP; Sat, 13 Jan 2018 18:10:05 -0800 (PST) From: blubee blubeeme Date: Sun, 14 Jan 2018 10:10:05 +0800 Message-ID: Subject: msdosfs_iconv To: FreeBSD current 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: Sun, 14 Jan 2018 02:10:07 -0000 This is a repost from freebsd-question; Hoping to get more exposure and help here. I am trying to run mount_msdosfs with the option to set locale like this: mount_msdosfs -L en_US.UTF-8 /dev/da0s1 $HOME/usb This returns operation not permitted. usrmount is set to 1 and everything mounts as expected w/o root if I remove the locale option. The problem here is that my document filenames are garbled and I can't actually open the files. kiconvtool: https://wiki.freebsd.org/DmitryMarakasov/kiconvtool is said to work but it does not, after installing it I still get the exact same error. Is there a way to set locale when using mount_msdosfs without sudo? From owner-freebsd-current@freebsd.org Sun Jan 14 03:44:02 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 98D0EE76232 for ; Sun, 14 Jan 2018 03:44:02 +0000 (UTC) (envelope-from jroberson@jroberson.net) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 73B51682DE for ; Sun, 14 Jan 2018 03:44:02 +0000 (UTC) (envelope-from jroberson@jroberson.net) Received: by mailman.ysv.freebsd.org (Postfix) id 73081E76231; Sun, 14 Jan 2018 03:44:02 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 729C0E76230 for ; Sun, 14 Jan 2018 03:44:02 +0000 (UTC) (envelope-from jroberson@jroberson.net) 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 420B4682DD for ; Sun, 14 Jan 2018 03:44:02 +0000 (UTC) (envelope-from jroberson@jroberson.net) Received: by mail-pg0-x229.google.com with SMTP id m20so6553351pgc.11 for ; Sat, 13 Jan 2018 19:44:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jroberson-net.20150623.gappssmtp.com; s=20150623; h=date:from:to:subject:in-reply-to:message-id:references:user-agent :mime-version; bh=aPOz1ueFWfYdLjV9xLywibQgFsj9yPYZ1V5xrtYWnoQ=; b=tY2E2YJfeS950AcM8aG+ZKA8jUpQ2FLPdAljnz5YYFx9cDxEUt2fJUX5ZxH6r/YWlJ zHjq01VGo0rAqLTQrvqNhV9Yn2WO3g/ZVkoyr+fuj0dGtNQE3Kxi6HtnRuSQEWY+JZYZ A7bXHrn9yQkwQ9QeNVbiPa3C1gHqwd5/FcpjToPBIM922gmDXOAxkJRb7FMPsPIP1J97 IQ05ryisOCJ/twfqX43jouzPH06H3a1YbobFup1b53ssAtf1qRqwGf0DpPl6DKSDplk3 oWFuUNJdAInFn+4q1i3ufyB1M9JHwP/BJbSorLn0WpP4WS5nwchyVs+Brl90r28z0kZx 51bw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:in-reply-to:message-id :references:user-agent:mime-version; bh=aPOz1ueFWfYdLjV9xLywibQgFsj9yPYZ1V5xrtYWnoQ=; b=ooL0qaSRxQnyrRHTGah4Gt3QpJKblk/6kKxsgitydl3TwqN4JbWKNFCqcPz8pcwsl3 Mwr2uQjMuvOXyJTEJUvOUD7VZUlxEJT22S3Aap6QzS88gaYfwDWkaBRMgw8JWcDeMuYA JTfUxlGWIeDLe4kSl/BcOa0uxoLlbugAjuR7hrGygrfa9S6RjRfmbJrzFDnzn2SfVlIF N0UJNBcgZIHvgklNvsr8vD8+Ygowg6Rd/GOcZ+tKDitCqgOA+3rgpsQ9NvISgLSXUZAk l9OKgtLZPqx9wShKHRUCPstydJavFOfN6XrfJA/0eLQeZLEEpXJjpYDAN8FWyfRAyUAu kt/A== X-Gm-Message-State: AKwxytdO5BOpddEm2lrfBFCYVSFWwjbhfOSrZvoyUbhCUmGvpc66VVDY +hacRAfYdSw7PJyvmCZC8679q/nr X-Google-Smtp-Source: ACJfBosPYi+UfjdPrFf/UEm3O2QHd4XcBkgRK6cQM0WE5G1lIaDllL9GXjC0B0vdKPUM64kyOWsGrw== X-Received: by 10.101.73.71 with SMTP id q7mr2035228pgs.66.1515901441486; Sat, 13 Jan 2018 19:44:01 -0800 (PST) Received: from rrcs-66-91-135-210.west.biz.rr.com (rrcs-66-91-135-210.west.biz.rr.com. [66.91.135.210]) by smtp.gmail.com with ESMTPSA id s65sm55905474pfk.7.2018.01.13.19.44.00 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 13 Jan 2018 19:44:00 -0800 (PST) Date: Sat, 13 Jan 2018 17:39:49 -1000 (HST) From: Jeff Roberson X-X-Sender: jroberson@desktop To: current@freebsd.org Subject: Re: New NUMA support coming to CURRENT In-Reply-To: Message-ID: References: User-Agent: Alpine 2.21 (BSF 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed 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, 14 Jan 2018 03:44:02 -0000 Hello, This work has been committed. It is governed by a new 'NUMA' config option and 'DEVICE_NUMA' and 'VM_NUMA_ALLOC' have both been retired. This option is fairly light weight and I will likely enable it in GENERIC before 12.0 release. I have heard reports that switching from a default policy of first-touch to round-robin has caused some performance regression. You can change the default policy at runtime by doing the following: cpuset -s 1 -n first-touch:all This is the default set that all others inherit from. You can query the current default with: cpuset -g -s 1 I will be investigating the regression and tweaking the default policy based on performance feedback from multiple workloads. This may take some time. numactl is still functional but deprecated. Man pages will be updated soonish. Thank you for your patience as I work on refining this somewhat involved feature. Thanks, Jeff On Tue, 9 Jan 2018, Jeff Roberson wrote: > Hello folks, > > I am working on merging improved NUMA support with policy implemented by > cpuset(2) over the next week. This work has been supported by Dell/EMC's > Isilon product division and Netflix. You can see some discussion of these > changes here: > > https://reviews.freebsd.org/D13403 > https://reviews.freebsd.org/D13289 > https://reviews.freebsd.org/D13545 > > The work has been done in user/jeff/numa if you want to look at svn history > or experiment with the branch. It has been tested by Peter Holm on i386 and > amd64 and it has been verified to work on arm at various points. > > We are working towards compatibility with libnuma and linux mbind. These > commits will bring in improved support for NUMA in the kernel. There are new > domain specific allocation functions available to kernel for UMA, malloc, > kmem_, and vm_page*. busdmamem consumers will automatically be placed in the > correct domain, bringing automatic improvements to some device performance. > > cpuset will be able to constrains processes, groups of processes, jails, etc. > to subsets of the system memory domains, just as it can with sets of cpus. > It can set default policy for any of the above. Threads can use cpusets to > set policy that specifies a subset of their visible domains. > > Available policies are first-touch (local in linux terms), round-robin > (similar to linux interleave), and preferred. For now, the default is > round-robin. You can achieve a fixed domain policy by using round-robin with > a bitmask of a single domain. As the scheduler and VM become more > sophisticated we may switch the default to first-touch as linux does. > > Currently these features are enabled with VM_NUMA_ALLOC and MAXMEMDOM. It > will eventually be NUMA/MAXMEMDOM to match SMP/MAXCPU. The current NUMA > syscalls and VM_NUMA_ALLOC code was 'experimental' and will be deprecated. > numactl will continue to be supported although cpuset should be preferred > going forward as it supports the full feature set of the new API. > > Thank you for your patience as I deal with the inevitable fallout of such > sweeping changes. If you do have bugs, please file them in bugzilla, or > reach out to me directly. I don't always have time to catch up on all of my > mailing list mail and regretfully things slip through the cracks when they > are not addressed directly to me. > > Thanks, > Jeff > From owner-freebsd-current@freebsd.org Sun Jan 14 03:54:31 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C3297E76CBB for ; Sun, 14 Jan 2018 03:54:31 +0000 (UTC) (envelope-from henry.hu.sh@gmail.com) Received: from mail-ua0-x22e.google.com (mail-ua0-x22e.google.com [IPv6:2607:f8b0:400c:c08::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 75C9F68B39 for ; Sun, 14 Jan 2018 03:54:31 +0000 (UTC) (envelope-from henry.hu.sh@gmail.com) Received: by mail-ua0-x22e.google.com with SMTP id l35so6533684uad.4 for ; Sat, 13 Jan 2018 19:54:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=uuAHCHqKu0GxwrzoSyXi918u2QMlXqLLVXCRKP7XyDw=; b=kkip8u4HTBp28cTiXPuSBK3Pcseb/51MLXCJzmjWuFZkCGdwNNqnslutnTJbEjoAhq /M1zpnr6V5oY0vSWjYI+DajSV9jqoMsb1mOi1J6IEKUhm3eq5b+TI34rIOCdii8dkIRg 9fqKlgqvQmq0LbhmE5dP/QuNi1ScPOEl0Mw7W6eiT8whm0LGhrPbd08EFJpKRo1gE7PV dH2pHFIxrIle0BbzcY+ycAOYHKxSknuIz0WaVAlMuEVP2v/xG1o7fl8/j8nwT39l37vq jR1XMUrZ+W83kxU1VymkO5qGhmjWhpLyWTj5Xogcuyvw9Ox1Sx7knTvct+/blsc6i6li OuEg== 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=uuAHCHqKu0GxwrzoSyXi918u2QMlXqLLVXCRKP7XyDw=; b=HKPMz/HI6LISIcRDMvuWx7kDvVs6Qsrpmj2J91n7gruPmHLHre8ePgf8GZYPb4IXsD 5EpDCNn2vdkXUQjVsfTxo5TbCfqgcGMgIqfDS5aXGJCUAa/1QBCuWFOZBkUq3C7RjHai XZXrOLDm/80QauBgO6zm3mRd2h1/I7yrIcANjC7e/C9wSkBxhBfD3x6cF5PJIx0RkxgR sAYSTytcNcgHjw2kRev0JblmIz5uOqIcBGYsf9+ZcmWeXlaelCnWX+UDdzA0W20RAoM7 ySM6QVjGYqB4Ww7U0o7gzjFpazG+9qGEMdIEEX4XMDL1XAaO8IetMbkFAz0O+EbKU3w0 jS4Q== X-Gm-Message-State: AKwxytdCT5cUS+aXHVeGmsizlBEdCBtYhi24kFFPHC0yjuIKIfI/sHL3 qtuMLJPe7XoWIi36nLShrgomnUAD/ZST3ryZqqo= X-Google-Smtp-Source: ACJfBovPmdhTbROsOqfBYjgwBe+Y/rRgKvJzc+Fiefs7HGyuaIDeoQwYRggfXihdzxHI8+1Qj01JI7bMLGiDa4vy3+I= X-Received: by 10.176.78.147 with SMTP id l19mr23486447uah.96.1515902070270; Sat, 13 Jan 2018 19:54:30 -0800 (PST) MIME-Version: 1.0 Received: by 10.103.131.149 with HTTP; Sat, 13 Jan 2018 19:53:49 -0800 (PST) In-Reply-To: References: From: Henry Hu Date: Sat, 13 Jan 2018 22:53:49 -0500 Message-ID: Subject: Re: msdosfs_iconv To: blubee blubeeme Cc: FreeBSD current 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: Sun, 14 Jan 2018 03:54:31 -0000 On Sat, Jan 13, 2018 at 9:10 PM, blubee blubeeme wrote: > This is a repost from freebsd-question; Hoping to get more exposure and > help here. > > I am trying to run mount_msdosfs with the option to set locale like this: > mount_msdosfs -L en_US.UTF-8 /dev/da0s1 $HOME/usb > > This returns operation not permitted. > > usrmount is set to 1 and everything mounts as expected w/o root if I remove > the locale option. The problem here is that my document filenames are > garbled and I can't actually open the files. > > kiconvtool: https://wiki.freebsd.org/DmitryMarakasov/kiconvtool > is said to work but it does not, after installing it I still get the exact > same error. > > Have you tried to kldload msdosfs_iconv first? Is there a way to set locale when using mount_msdosfs without sudo? > _______________________________________________ > 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" > -- Cheers, Henry From owner-freebsd-current@freebsd.org Sun Jan 14 03:56:44 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D75DBE76F33 for ; Sun, 14 Jan 2018 03:56:44 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-io0-x244.google.com (mail-io0-x244.google.com [IPv6:2607:f8b0:4001:c06::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 94F8468D04 for ; Sun, 14 Jan 2018 03:56:44 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-io0-x244.google.com with SMTP id b198so7186746iof.6 for ; Sat, 13 Jan 2018 19:56:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=dEftnzownYVYXYR1NhSKSB4zYlhh7DPneq5XcbzVGX8=; b=ReFIaG4L38ZtsoI8enMJE1eB8zSaFrGCM7I0dr8t2fP5qEcuIV2I+Pm/Qt06o4tVEu jLnXKM0JYX/SkO1WaWz/3aJm0JfmMU60BfyNpR2pnQ/w6EoHWXi1kXzIau35MOX2HGQN MLW5a/ta5gjMZlz15U+88+FqpNjCUWpFCjd+An/FSn35WuEPSWHrsddK2HHFp5JgKqUp UaNtTxpiQ+xyIZmmwZZD8xeW2eGk7/OighEMN480PLDYdS7hF3nzVtTrjFta1I0lws// B+WkHk8IkTc3Y4UFH4mpLwVcWHiLfErcN7s+SgS60tAPU0nFE3NRfF6WtDDHLyWE+3dF hBwA== 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=dEftnzownYVYXYR1NhSKSB4zYlhh7DPneq5XcbzVGX8=; b=dNJIXV1bSviFbkuA6jaVCYBu/4LjLn8o4mcUBqAO74DrsB1LXL0B7IA5bFN5vxIKiG lC4VKG/blxHd/kwXhaWNIpZRSmNLtGF4f4eNI3j1LakOwmY7oYDfeBlcxvcYHAkFFemR pK7i7xBomhat+LiGxKBSKm8nKIzUfVHMUe/REtyIdSDSNkNn4ACJ1YP2TbXnrawLoQMN la0pxfMJIw2JrnE/Dxstuie+ywuRUlglJcB6pAnFHXdycdHxqevXxYtBKIxT2JG1amLJ YcVxV1Y9OKCFiNfw+HhO7hZZeG7F1J/ie1yrThXk/Myu+Gyj/rdN10gPhCxJUAIQQJFX JOEg== X-Gm-Message-State: AKwxyteXA5fPRdeDxxn33LNMUiSvT3LydMdnJiRd1rmthl1XUrr4iZEq oU+jJV3ZgzU0ooIGeqfumZKVii+JSkI4iZYyyGA= X-Google-Smtp-Source: ACJfBovN+6CihZnlMxoptwQqXhA99TM++mp79iMCznnQZ1GwkMgi8lyid3CRnXzQSIJQ96bQOUwKajwgyk3vjmr9SQM= X-Received: by 10.107.17.226 with SMTP id 95mr45178ior.296.1515902203914; Sat, 13 Jan 2018 19:56:43 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.164.193 with HTTP; Sat, 13 Jan 2018 19:56:43 -0800 (PST) In-Reply-To: References: From: blubee blubeeme Date: Sun, 14 Jan 2018 11:56:43 +0800 Message-ID: Subject: Re: msdosfs_iconv To: Henry Hu Cc: FreeBSD current 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: Sun, 14 Jan 2018 03:56:44 -0000 On Sun, Jan 14, 2018 at 11:53 AM, Henry Hu wrote: > > > On Sat, Jan 13, 2018 at 9:10 PM, blubee blubeeme > wrote: > >> This is a repost from freebsd-question; Hoping to get more exposure and >> help here. >> >> I am trying to run mount_msdosfs with the option to set locale like this: >> mount_msdosfs -L en_US.UTF-8 /dev/da0s1 $HOME/usb >> >> This returns operation not permitted. >> >> usrmount is set to 1 and everything mounts as expected w/o root if I >> remove >> the locale option. The problem here is that my document filenames are >> garbled and I can't actually open the files. >> >> kiconvtool: https://wiki.freebsd.org/DmitryMarakasov/kiconvtool >> is said to work but it does not, after installing it I still get the exact >> same error. >> >> Have you tried to kldload msdosfs_iconv first? > > Is there a way to set locale when using mount_msdosfs without sudo? >> _______________________________________________ >> 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 >> " >> > > > > -- > Cheers, > Henry > Yes, /etc/rc.conf has this line: kld_list="nvidia-modeset msdosfs_iconv" From owner-freebsd-current@freebsd.org Sun Jan 14 04:16:56 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5F8BCE780D9 for ; Sun, 14 Jan 2018 04:16:56 +0000 (UTC) (envelope-from henry.hu.sh@gmail.com) Received: from mail-ua0-x244.google.com (mail-ua0-x244.google.com [IPv6:2607:f8b0:400c:c08::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 16120698FF for ; Sun, 14 Jan 2018 04:16:56 +0000 (UTC) (envelope-from henry.hu.sh@gmail.com) Received: by mail-ua0-x244.google.com with SMTP id x10so6554876ual.8 for ; Sat, 13 Jan 2018 20:16:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=p+z4H7PBtd+PgP4YCLy3P8D7YvqZrqLbPOZeFA6zYdU=; b=Orcr3aW9RxdaEM4NRMRZoLskUCkstZg3oNRz+8gqiSN8VdNm98WwWzEf0YLLuS+CjI fCJHWxp1AJpu4ad1Pob0t2K1D5upRSJigF0mELGGTZTUeLzJ7xFbZvp1VUtydT46WE3G bB8vhNWnrxyjwtnuFabjRl/iN61pMpcktbLinI7kSZY04ZEcYJF6e29tUQLmHbznrYsB lxRVu3WEUw4GZz1IczH7DgQFAL3hfQrpmEjIaWp0Wv1FLG6VYxx7nUAUpsdXBOczB/JR bWiTP+xd1zvqkfafYj9jgaEwAkLkdUJ6snZfU/ZSKeqLg67Vta4VOnHC9jAIoNgDzgQL 987w== 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=p+z4H7PBtd+PgP4YCLy3P8D7YvqZrqLbPOZeFA6zYdU=; b=q7EXg61hH9EG2QDZLM+JtIAZeRAqD8gzrgDzFCCZ5J/joBTGtI+KiBilfdUPNuBQDQ Bh5JB3qoMteO2CchrskYktrywOeLJY5e7EFcCtK48zw4FSK02tRVi95FBthP6AWkhDzB GBYUWIF87aLy8LSYnuoAOCIPIgaA9t2Go0vJSzA+lLq5NW8eW56/tAHxnCvG0bBJSmRw aZYtv1WNBMTq9MjpJDTMdc5O4qUjqQnRvQtvy1CldPfk8zlAhrbGD88glYECXV4ZNJ54 lMwwYcnGwomFg68zYcIq9SHVocfuMpXy2o5MNfxT5Ij2R/Rsds6M3UnBmnUuO4601CvF 6SrQ== X-Gm-Message-State: AKwxytdhq7M4XnmD9S0FIbN1U5vLSnKCFtvNcq88suBV7shsZWluYzo6 I2caBuRvh27PNWoZ24vh8V1pv8cdINiyLrBo164= X-Google-Smtp-Source: ACJfBouF8IU5Xc+Z+FuuteMOKq3wRVpd7x/HB2WjbKjmxDeRYgNQqf4cOLcHVaIZgUezM3kIfHoGHtnr+wm/o0tWmIU= X-Received: by 10.176.89.210 with SMTP id k18mr2092359uad.28.1515903414871; Sat, 13 Jan 2018 20:16:54 -0800 (PST) MIME-Version: 1.0 Received: by 10.103.131.149 with HTTP; Sat, 13 Jan 2018 20:16:14 -0800 (PST) In-Reply-To: References: From: Henry Hu Date: Sat, 13 Jan 2018 23:16:14 -0500 Message-ID: Subject: Re: msdosfs_iconv To: blubee blubeeme Cc: FreeBSD current 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: Sun, 14 Jan 2018 04:16:56 -0000 On Sat, Jan 13, 2018 at 10:56 PM, blubee blubeeme wrote: > > > On Sun, Jan 14, 2018 at 11:53 AM, Henry Hu wrote: > >> >> >> On Sat, Jan 13, 2018 at 9:10 PM, blubee blubeeme >> wrote: >> >>> This is a repost from freebsd-question; Hoping to get more exposure and >>> help here. >>> >>> I am trying to run mount_msdosfs with the option to set locale like this: >>> mount_msdosfs -L en_US.UTF-8 /dev/da0s1 $HOME/usb >>> >>> This returns operation not permitted. >>> >>> usrmount is set to 1 and everything mounts as expected w/o root if I >>> remove >>> the locale option. The problem here is that my document filenames are >>> garbled and I can't actually open the files. >>> >>> kiconvtool: https://wiki.freebsd.org/DmitryMarakasov/kiconvtool >>> is said to work but it does not, after installing it I still get the >>> exact >>> same error. >>> >>> Have you tried to kldload msdosfs_iconv first? >> >> Is there a way to set locale when using mount_msdosfs without sudo? >>> _______________________________________________ >>> freebsd-current@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@f >>> reebsd.org" >>> >> >> >> >> -- >> Cheers, >> Henry >> > Yes, /etc/rc.conf has this line: > kld_list="nvidia-modeset msdosfs_iconv" > > I just tried that and it works. I can create filenames in Chinese on the mounted drive. The command I used: > mount_msdosfs -L zh_CN.UTF-8 /dev/da1p1 /tmp/y kernel modules: > kldstat | grep iconv 30 3 0xffffffff8506e000 458f libiconv.ko 33 1 0xffffffff8507a000 801 msdosfs_iconv.ko But I'm using 11.1-STABLE. Maybe something changed? -- Cheers, Henry From owner-freebsd-current@freebsd.org Sun Jan 14 05:21:00 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7D311E7B7C4 for ; Sun, 14 Jan 2018 05:21:00 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4238C6C0D7 for ; Sun, 14 Jan 2018 05:21:00 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-it0-x231.google.com with SMTP id b5so13381985itc.3 for ; Sat, 13 Jan 2018 21:21:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=cEbjof5qpluhvyprnkXyQTOPwusG0TyD86EetKQCZh8=; b=dQb+KaO8sjLQpwjh4ihcCTVnZuGkMmug7K9CBfdO2XkrwMv1WCzKsFmF9qE28Lw9z9 Ny4uE3ClBPRYZmc6rfi7UNqRAHuTQTTOvg3EJaVty4aLpto9a0Q1O0MR/h/7urh8cS/O 9ZeMFxBtgOFFMrQDnMrcI6Ip2FVJbIDpLyZ/Pbvur23uP6mgUYqfqfKWbW8xGmXJzlGz C7Xro7WhI/9UERQM1uyMN9MKRD+CmXh5rW5e1Uv1nR7DxgrhMpzykw0dJ9iseXwpRaBD ndbxCKcNrPAzHO7+9xvFhfm86UzyN/2eGQf172wI/z4giTGa3euvB4O17K9WsOK0Q6f8 sYZg== 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=cEbjof5qpluhvyprnkXyQTOPwusG0TyD86EetKQCZh8=; b=LRHcw0ZMxbMMTnHQxEmkvO4SKAT3wBGbDFX4WrmFgvHRcOdbMB8cqBtzTWTAcs2DeX SpEHf8pKJAFhsy561gzT+nCSj7XaLuTLZH6gJX/FPos8OhAhmS1jgAnMYG90myiBthZE yFVhjFFyqlchMIWOoGnTFV2FsUH99oDg8tpwgBsRJZ+OlzE+qS5n4YtEDohdYwe3X7M2 xnLt916CHyN24f8raj5JXwQokRRVMFaBEup8fH99jbb5tRkry6v+Qu0bm23B8bYWf5FD 9cqDvHCv9a3lkXwjLxMrtoSnKvniN7WU1ptSxsYfFgO8VvrzohbWeO+ftEcnJKWVo8ti Qyog== X-Gm-Message-State: AKwxytdhJGUbHhKJ7dv7NVM/x8nmNOM7VZ2anUN9qDZN+utrL0J9yNja QiangcrM0lm8km57MLxHkO2cx8oMm+MR+ZlYnX4= X-Google-Smtp-Source: ACJfBovrHd0vkx22fijt0vokFCc4W4CTmVvv0nQ46GbT43UtFaMvbzeBrCpkpNJ4ecSyHkPNGA7dGCVbT1h2T3X+tlg= X-Received: by 10.36.50.73 with SMTP id j70mr9715651ita.149.1515907259482; Sat, 13 Jan 2018 21:20:59 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.164.193 with HTTP; Sat, 13 Jan 2018 21:20:58 -0800 (PST) In-Reply-To: References: From: blubee blubeeme Date: Sun, 14 Jan 2018 13:20:58 +0800 Message-ID: Subject: Re: msdosfs_iconv To: Henry Hu Cc: FreeBSD current 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: Sun, 14 Jan 2018 05:21:00 -0000 On Sun, Jan 14, 2018 at 12:16 PM, Henry Hu wrote: > > > On Sat, Jan 13, 2018 at 10:56 PM, blubee blubeeme > wrote: > >> >> >> On Sun, Jan 14, 2018 at 11:53 AM, Henry Hu wrote: >> >>> >>> >>> On Sat, Jan 13, 2018 at 9:10 PM, blubee blubeeme >>> wrote: >>> >>>> This is a repost from freebsd-question; Hoping to get more exposure and >>>> help here. >>>> >>>> I am trying to run mount_msdosfs with the option to set locale like >>>> this: >>>> mount_msdosfs -L en_US.UTF-8 /dev/da0s1 $HOME/usb >>>> >>>> This returns operation not permitted. >>>> >>>> usrmount is set to 1 and everything mounts as expected w/o root if I >>>> remove >>>> the locale option. The problem here is that my document filenames are >>>> garbled and I can't actually open the files. >>>> >>>> kiconvtool: https://wiki.freebsd.org/DmitryMarakasov/kiconvtool >>>> is said to work but it does not, after installing it I still get the >>>> exact >>>> same error. >>>> >>>> Have you tried to kldload msdosfs_iconv first? >>> >>> Is there a way to set locale when using mount_msdosfs without sudo? >>>> _______________________________________________ >>>> freebsd-current@freebsd.org mailing list >>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@f >>>> reebsd.org" >>>> >>> >>> >>> >>> -- >>> Cheers, >>> Henry >>> >> Yes, /etc/rc.conf has this line: >> kld_list="nvidia-modeset msdosfs_iconv" >> >> > I just tried that and it works. I can create filenames in Chinese on the > mounted drive. > The command I used: > > > mount_msdosfs -L zh_CN.UTF-8 /dev/da1p1 /tmp/y > > kernel modules: > > > kldstat | grep iconv > 30 3 0xffffffff8506e000 458f libiconv.ko > 33 1 0xffffffff8507a000 801 msdosfs_iconv.ko > > But I'm using 11.1-STABLE. Maybe something changed? > > -- > Cheers, > Henry > I am running: FreeBSD blubee 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r326056: Tue Nov 21 14:54:55 UTC 2017 root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 kldstats 10 1 0xffffffff85e89000 806 msdosfs_iconv.ko 11 1 0xffffffff85e8a000 4633 libiconv.ko Can you list out the steps that you followed? I know that if I first run the mount command as root; I can then mount and unmount as regular user. If I try to mount with that -L flag msdosfs_iconv complains at me. From owner-freebsd-current@freebsd.org Sun Jan 14 05:40:39 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DEC0AE7C79A for ; Sun, 14 Jan 2018 05:40:39 +0000 (UTC) (envelope-from henry.hu.sh@gmail.com) Received: from mail-ua0-x22f.google.com (mail-ua0-x22f.google.com [IPv6:2607:f8b0:400c:c08::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 92B716CBB6 for ; Sun, 14 Jan 2018 05:40:39 +0000 (UTC) (envelope-from henry.hu.sh@gmail.com) Received: by mail-ua0-x22f.google.com with SMTP id e19so6585254uam.6 for ; Sat, 13 Jan 2018 21:40:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=2/Jdy09Ngzrc9H+McTN0HQX8j+dtB6gdsKHqTfkZZIg=; b=lsY7CAGUupNav89GtwOOl9es9VTrE45AEOEE3gdsQpAMV1Jlc5KO6886OaE3boXFmC V4GgFp5BsnoH90IY2xWm6vLSGMSl5eMYpWJ4I1LPKtHn/50zkAN0tvJKaRs8kyCwfD8S v2VjcVeKLmjEQrSExC+zoBVcMiuDgMAbuOrPIWXuVxkSpIRmCFNBAU4dOqMAPfS6wXqM tSL3ezmcfbc05jJrrFA/Q7hex3GKVDmKp0kcJVafbAliV00nOd5YapWxOH01OJpARihS NpDIuF2cq3pL3iovJ1+i7iSO62u3bSsIxvVefTbWIuAC9I1aPgJnvzQriHpvKIa0W4Sg zeqA== 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=2/Jdy09Ngzrc9H+McTN0HQX8j+dtB6gdsKHqTfkZZIg=; b=T3rbmwSocUi5GS4qLTO6JyIty4AIpTYw/cWUYQBxKk4nuv3xZAoau8MwXirpgpWaQ5 hTva/wJUqym7GQRYVdlSBax8ZqJaH//uuSGz+PT0MM9OfnXlkzkbKeHae+o9fYlwcCM4 jpJ/hrn7YMzgHT7h5ZyOWbQVUni36hhSxBl0TT2GC92TJ4EhS18eFlekpVLDgWXuanYu Y+fCQeogV6xrU0ddw2ykaK1xa15OFTGo1m7i8NGQP1IsHLXOYzZ5j0fqIfZoBvsUyUAh 7VYq/3Jo3WKZ9AyooJZ2gmdSD3+iShIb3bd06JJOYHMNsL4kLYhuoxfZbVPdw/iXsO3u wcyQ== X-Gm-Message-State: AKwxyteLXavtnHqt+3+cneAQUe1xNU+HER+KDFRyRje1ZmvoqWn4HqjR fWIXPuLG4CKR5HsPF7GgiGcop0tV6TXEoFwiRLdeGw== X-Google-Smtp-Source: ACJfBoucjObdlBM5imhtOWh5EEd3XyviguU7ZnO6WXl+LcvXSixk3tVy5tXog9iVM9Gaid0a7p6cAa7S4SnvvertNZ8= X-Received: by 10.176.78.147 with SMTP id l19mr23605188uah.96.1515908438387; Sat, 13 Jan 2018 21:40:38 -0800 (PST) MIME-Version: 1.0 Received: by 10.103.131.149 with HTTP; Sat, 13 Jan 2018 21:39:57 -0800 (PST) In-Reply-To: References: From: Henry Hu Date: Sun, 14 Jan 2018 00:39:57 -0500 Message-ID: Subject: Re: msdosfs_iconv To: blubee blubeeme Cc: FreeBSD current 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: Sun, 14 Jan 2018 05:40:40 -0000 On Sun, Jan 14, 2018 at 12:20 AM, blubee blubeeme wrote: > > > On Sun, Jan 14, 2018 at 12:16 PM, Henry Hu wrote: > >> >> >> On Sat, Jan 13, 2018 at 10:56 PM, blubee blubeeme >> wrote: >> >>> >>> >>> On Sun, Jan 14, 2018 at 11:53 AM, Henry Hu >>> wrote: >>> >>>> >>>> >>>> On Sat, Jan 13, 2018 at 9:10 PM, blubee blubeeme >>>> wrote: >>>> >>>>> This is a repost from freebsd-question; Hoping to get more exposure and >>>>> help here. >>>>> >>>>> I am trying to run mount_msdosfs with the option to set locale like >>>>> this: >>>>> mount_msdosfs -L en_US.UTF-8 /dev/da0s1 $HOME/usb >>>>> >>>>> This returns operation not permitted. >>>>> >>>>> usrmount is set to 1 and everything mounts as expected w/o root if I >>>>> remove >>>>> the locale option. The problem here is that my document filenames are >>>>> garbled and I can't actually open the files. >>>>> >>>>> kiconvtool: https://wiki.freebsd.org/DmitryMarakasov/kiconvtool >>>>> is said to work but it does not, after installing it I still get the >>>>> exact >>>>> same error. >>>>> >>>>> Have you tried to kldload msdosfs_iconv first? >>>> >>>> Is there a way to set locale when using mount_msdosfs without sudo? >>>>> _______________________________________________ >>>>> freebsd-current@freebsd.org mailing list >>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >>>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@f >>>>> reebsd.org" >>>>> >>>> >>>> >>>> >>>> -- >>>> Cheers, >>>> Henry >>>> >>> Yes, /etc/rc.conf has this line: >>> kld_list="nvidia-modeset msdosfs_iconv" >>> >>> >> I just tried that and it works. I can create filenames in Chinese on the >> mounted drive. >> The command I used: >> >> > mount_msdosfs -L zh_CN.UTF-8 /dev/da1p1 /tmp/y >> >> kernel modules: >> >> > kldstat | grep iconv >> 30 3 0xffffffff8506e000 458f libiconv.ko >> 33 1 0xffffffff8507a000 801 msdosfs_iconv.ko >> >> But I'm using 11.1-STABLE. Maybe something changed? >> >> -- >> Cheers, >> Henry >> > I am running: > FreeBSD blubee 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r326056: Tue Nov 21 > 14:54:55 UTC 2017 root@releng3.nyi.freebsd.org: > /usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 > > kldstats > 10 1 0xffffffff85e89000 806 msdosfs_iconv.ko > 11 1 0xffffffff85e8a000 4633 libiconv.ko > > Can you list out the steps that you followed? > > I know that if I first run the mount command as root; I can then mount and > unmount as regular user. > > If I try to mount with that -L flag > msdosfs_iconv complains at me. > I just inserted a USB drive, and created /tmp/y for testing, which is owned by my user. I can access /dev/da1p1 as my user. Do you mean that if you have mounted & unmounted as root once, you can mount as regular user? Maybe that changes something, like loaded a kernel module? Maybe you can compare kldstat output? -- Cheers, Henry From owner-freebsd-current@freebsd.org Sun Jan 14 05:50:58 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D5BF7E7CF01 for ; Sun, 14 Jan 2018 05:50:58 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 934A26D003 for ; Sun, 14 Jan 2018 05:50:58 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-it0-x236.google.com with SMTP id f143so13675745itb.0 for ; Sat, 13 Jan 2018 21:50:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=eELoivh9nvjM84b//b3c2dCGJ25Cb8TixSctkirDhOU=; b=qpZiZOumyK+2nWOj5Z3IUUODt8QZES0KQzD4zYgPatkSVTttGcfHHxyEI05BhPMWZY iD4fN6ohQjMHxMxghGVG2zsefQFZpm6fSoozqLIqBXWA4h5GjOaF2ukIGVj5pPYLiMmS AtzhhZdUjrXvBtgmyaK9u4ZvvZZmppB6QSGl6zw1hHWbn2egv/9MvLcBRDmEeln3wYh/ tecq+A2k1bTB9l3NySKscRtVW1eRz3dRbV8s0+rqc9oOX5k0YNBlL0+P7x4HHIrv3VtR sIVNYsamaMlkGpf7QGAyc9TYrVCFZSeDIwkHRdtwVfaORcrA0e0lGXRnOeQYdlmghr/L BaZg== 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=eELoivh9nvjM84b//b3c2dCGJ25Cb8TixSctkirDhOU=; b=lfWgBC7BrZsJ/FJSKuy5icunMPQ/uDwwP/klvbEC2QqxW7Zb1bWfndFYIXSVsUQjZ4 cLLuuhyRkds+P4ZL5XAv4x5W4pIZlJ7Zwfj5DYqpph53vHivsXY2zwnnC/o5W0SgPE5F 32TnusUgXS68ABvrD+dryRtPnnJOlkYnzRzUbBRIOtyqt9a1kVtw8uh7YHCdWFL1EsuP KPnShpdc+LEUbUOP7zRU3Yk8tY2c8c6wnXfxtUEVQESF5qVC3wuWZWimc6Vj7tk0riIM rGNU1D3jo1joozPandPJf1MxlhKw/bZNZa1EiNL84IU9IXeBuexOfN1jU9gNv6jIVH0t UHCQ== X-Gm-Message-State: AKwxytcPQWiQiGYxocHm5O/XNTzuRTGb3ivGI7d4FZ6kh2pNPbghKCps x3XsVbSf5wweZuOzlkmXEg8CdcqiZL39/be/PBE= X-Google-Smtp-Source: ACJfBotqUVx0OYs1cRIs5lj7djmAVTXr1x6acfV0JZy+D7SSScDVXVifS0optRHNPLfG0f7lRT6N7kRIJuKIH0k0Fa8= X-Received: by 10.36.110.71 with SMTP id w68mr9445802itc.119.1515909057934; Sat, 13 Jan 2018 21:50:57 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.164.193 with HTTP; Sat, 13 Jan 2018 21:50:57 -0800 (PST) In-Reply-To: References: From: blubee blubeeme Date: Sun, 14 Jan 2018 13:50:57 +0800 Message-ID: Subject: Re: msdosfs_iconv To: Henry Hu Cc: FreeBSD current 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: Sun, 14 Jan 2018 05:50:58 -0000 On Sun, Jan 14, 2018 at 1:39 PM, Henry Hu wrote: > > > On Sun, Jan 14, 2018 at 12:20 AM, blubee blubeeme > wrote: > >> >> >> On Sun, Jan 14, 2018 at 12:16 PM, Henry Hu wrote: >> >>> >>> >>> On Sat, Jan 13, 2018 at 10:56 PM, blubee blubeeme >>> wrote: >>> >>>> >>>> >>>> On Sun, Jan 14, 2018 at 11:53 AM, Henry Hu >>>> wrote: >>>> >>>>> >>>>> >>>>> On Sat, Jan 13, 2018 at 9:10 PM, blubee blubeeme >>>>> wrote: >>>>> >>>>>> This is a repost from freebsd-question; Hoping to get more exposure >>>>>> and >>>>>> help here. >>>>>> >>>>>> I am trying to run mount_msdosfs with the option to set locale like >>>>>> this: >>>>>> mount_msdosfs -L en_US.UTF-8 /dev/da0s1 $HOME/usb >>>>>> >>>>>> This returns operation not permitted. >>>>>> >>>>>> usrmount is set to 1 and everything mounts as expected w/o root if I >>>>>> remove >>>>>> the locale option. The problem here is that my document filenames are >>>>>> garbled and I can't actually open the files. >>>>>> >>>>>> kiconvtool: https://wiki.freebsd.org/DmitryMarakasov/kiconvtool >>>>>> is said to work but it does not, after installing it I still get the >>>>>> exact >>>>>> same error. >>>>>> >>>>>> Have you tried to kldload msdosfs_iconv first? >>>>> >>>>> Is there a way to set locale when using mount_msdosfs without sudo? >>>>>> _______________________________________________ >>>>>> freebsd-current@freebsd.org mailing list >>>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >>>>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@f >>>>>> reebsd.org" >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Cheers, >>>>> Henry >>>>> >>>> Yes, /etc/rc.conf has this line: >>>> kld_list="nvidia-modeset msdosfs_iconv" >>>> >>>> >>> I just tried that and it works. I can create filenames in Chinese on the >>> mounted drive. >>> The command I used: >>> >>> > mount_msdosfs -L zh_CN.UTF-8 /dev/da1p1 /tmp/y >>> >>> kernel modules: >>> >>> > kldstat | grep iconv >>> 30 3 0xffffffff8506e000 458f libiconv.ko >>> 33 1 0xffffffff8507a000 801 msdosfs_iconv.ko >>> >>> But I'm using 11.1-STABLE. Maybe something changed? >>> >>> -- >>> Cheers, >>> Henry >>> >> I am running: >> FreeBSD blubee 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r326056: Tue Nov 21 >> 14:54:55 UTC 2017 root@releng3.nyi.freebsd.org: >> /usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 >> >> kldstats >> 10 1 0xffffffff85e89000 806 msdosfs_iconv.ko >> 11 1 0xffffffff85e8a000 4633 libiconv.ko >> >> Can you list out the steps that you followed? >> >> I know that if I first run the mount command as root; I can then mount >> and unmount as regular user. >> >> If I try to mount with that -L flag >> msdosfs_iconv complains at me. >> > > I just inserted a USB drive, and created /tmp/y for testing, which is > owned by my user. I can access /dev/da1p1 as my user. > > Do you mean that if you have mounted & unmounted as root once, you can > mount as regular user? > Maybe that changes something, like loaded a kernel module? Maybe you can > compare kldstat output? > > -- > Cheers, > Henry > if you first run the mount_msdosfs command as root, it'll load the locale settings just fine. If you logout or reboot and try to call mount_msdosfs -L [locale] as a regular user; The command will fail. From owner-freebsd-current@freebsd.org Sun Jan 14 11:10:20 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 31944E62DE8 for ; Sun, 14 Jan 2018 11:10:20 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A395377168 for ; Sun, 14 Jan 2018 11:10:19 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from hermann.intern.walstatt.dynvpn.de ([85.182.8.155]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0LfSyv-1fBsbx3v7x-00p2D7 for ; Sun, 14 Jan 2018 12:10:17 +0100 Date: Sun, 14 Jan 2018 12:10:15 +0100 From: "Hartmann, O." To: FreeBSD CURRENT Subject: /lib/casper: read error: Invalid argument Message-ID: <20180114121011.56204f3f@hermann.intern.walstatt.dynvpn.de> Organization: walstatt.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:315Nj6kOhywFqCl5El1mFTlSphCyCSvm8gJVZBsGND+iBzA4+rW YpDpCfQo96/ZmOK2MF9b+wADZ4a7Nvrjc4kMf0pKvo2D/d3wkgszJOSbBnhJ9uNs+FqAguw 84nHHHT54udXRVjKihCuDXCIdJBUct5l07hgA6hrM8hMhk6mnmyRfBoAIa44mDIytvzz2Pf 9q4aTyXVgbkyBVZO3fqaw== X-UI-Out-Filterresults: notjunk:1;V01:K0:ZHyeK2ttgIk=:2PSrbncQMphzxBI+L0IOS9 IDnwr4l1pWTam+l7YBn8TKitCuQWD6UzozAh4+TahVhF2w1TJazfPs9mG5bBq38QIPuU8DF5P eCdEltXIx1w+OinNfzPIVVlBgzjOYnC851sq1fWU5U4vkgneNQ95Hlik7N+QYvZzy/yo1ujuS bmmhHQuj4uD/d99Nb37ueKnMYPj1zEfz/L0b1UuD2DF5ZU5EFIuHa1OD9fwxMtuSZlYgkXI0o xoBxiplL2qvIAlxWFQxbYu2cZAmTavbvaF2pgOeJz8d+iFQ3//n8tBIWDIY9dmy8CwXUDtbdP XVtZXHgk7j5loypG7koHljR3YWng1f9ugx4wIE5LznElZ3K2NS43M0A0S7XGedawNrCFwjcO7 cHZbbnVe7zGAoJDXYokurn3bY97nn7DLwcO4nMkYPqsiMkUuAz+B61sjnozmQ3nOogCXy7Lng HVDab97+xLok+OQ3u3KYpme4u6z5zMAfH9o5ZIivzWKyTa5om3WWJKutZSC2Iv5hdkZYX4gdq /6GEydm/WCGrzW7pkcBDhDj1IBDilpeUFkCMugTsrNrgUW1oYhtu2DeSe63LGHJ7TTFmjk+FR HRzVsXIcQBM3Pze1R+f/Jw6p/w7uDOd3PlBLr4jSq69AWeUtdKWKhdGC5aTPql0JwMf1sBt1c xi8MSeNCApVediyheTE4pNcAsiJx/xsqjP3D3dw+HiI4cjVTaZ8f5C8UUssL/iShqWgnKzbwL GZlYOrYTIAkmFB3Cs+NnGIxH7p35s+31tD8gLbQbmSHnRxHA9Ld7OLfEdzu8M0IHolbknn4lb VxQXhg5Wj47ppMT2P0NSWssGO+47l0ksb+zvS34uUleUxE1euM= 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, 14 Jan 2018 11:10:20 -0000 Again, I ran into a havoc update of CURRENT last night. While booting a freshly installed kernel and performing "make -j4 installworld", the box suddenly rebooted - out of the blue. With the wrecked CURRENT left behind (r327866), I'm not able to boot even into single user mode. The box halts with a starnge BTX loader message indicating BTX halted followed by a set of register dumps. I saw this weird behaviour last year around November, when the boot chain has been corrupted. Well, when the strange "BTX halted" message doesn't appear, some other strange message occurs claiming that there is no /boot/loader. I tried to investigate with the USB image created 10th January 2018 from ISO downloads and it showed, that /boot/ was obviously intact, but files in /usr/sbin, /usr/bin were zero in size, also some libs in /usr/lib and /lib. While /boot/ seemingly being already installed while other portions failed, I knew from the past that I had to replace all /boot, /bin, /sbin, /usr/sbin, /usr/bin, /lib, /usr/lib , /usr/libexec and /libexec from the recent USB image. I did so via "pax -v -rw -pe", but I had to "chflags noschg" some files/libraries on the target to get them overwritten. I simply did a chflags noschg * to every folder/subfolder and "pax'ed" the destination then. So far. I'm able to boot into single user again, but when it comes to the shell and /bin/sh is supposed to be executed, I get the strange message: /lib/casper/: read error: Invalid argument and the prompt is jumping back to ensure the PASSWORD (console is password protected). So, when using /rescue/sh (which is a remaining from the broken update procedure), I'm able to have a shell in single user mode. But I have no chance to repair the system by using the fully intact /usr/src and /usr/obj infrastructure! Why? Again, when typing "make buildworld", I'm bothered with /lib/casper/: read error: Invalid argument and make: "/usr/src/share/mk/bsd.compiler.mk" line 142: warning: "cc --version|| echo 0.0.0" returned non-zero status and a following line complaining about line 155: Unable to determin compiler type for CC=cc. Consider setting COMPILER_TYPE. Something is hindering to start the compiler somehow and it is related to /lib/casper/: read error: Invalid argument? What is wrong here? How to fix this? Again, the useless, minimalistic USB iamges provided by the FreeBSD.org site without compiler infrastructure are useless for desaster recovery, since I can not simply boot into the image and performing a DESTDIR-delegated installworld of an existing precompiled world! How can I use the ISO image to rescue the system? I do not find anything in recent docs. A couple of years ago such a task was possible until some people started to get rid of the compiler/installation infrastructure necessary to installworld. Thanks in advance for the help, kind regards, oh From owner-freebsd-current@freebsd.org Sun Jan 14 11:57:45 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A6593E654AC for ; Sun, 14 Jan 2018 11:57:45 +0000 (UTC) (envelope-from ml@vishwin.info) Received: from varun.vishwin.info (varun.vishwin.info [46.101.93.59]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "varun.vishwin.info", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3B01E78AF0 for ; Sun, 14 Jan 2018 11:57:44 +0000 (UTC) (envelope-from ml@vishwin.info) Received: from varun.vishwin.info (fd35:9eae:7575::2 [IPv6:fd35:9eae:7575::2]) by varun.vishwin.info (OpenSMTPD) with ESMTP id cbb4f159 for ; Sun, 14 Jan 2018 06:57:39 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=vishwin.info; h=subject :references:to:from:message-id:date:mime-version:in-reply-to :content-type:content-transfer-encoding; s=fuccboi12; bh=AeeFdhh cat/JSs+ohpOJDrAFpWJAUpHY5G9SRK6je6M=; b=scDk1U6sfOYCgapRcTK29jo +Jan93eTsIrXa+Crt05gi5ahGFK8v/LGYHwlu1eVLf3lPrzF/lpyf+j3tYOgbzBy z/3/VdSyDQho7oF53+Gx1igU84OlMiJK0Dh7joJyPX7Hcb1G3NrMjKuYo3Rg4Gk+ yhVhsfGKzcaOqtA8v0D1PFgkNOb9KcLIDY1s/oL1PQyF3bhR23YFMrbf/Y3OMGEW GfJ09e/SA42tLJSCg490ROSCSZzEufDn+xbtbsA2gBEjE1n8KOG6As8JA5d9fXca 8WfNdmTuyUHXVVaHVg2gQM3weExzeH+vP9qEE+Ngi4u9etyphUyJCr2vPoHoy/g= = Received: from [IPv6:2001:470:8:6ca:cad7:19ff:fec0:a06d] (2001:470:8:6ca:cad7:19ff:fec0:a06d [IPv6:2001:470:8:6ca:cad7:19ff:fec0:a06d]) by varun.vishwin.info (OpenSMTPD) with ESMTPSA id 4a9f7e63 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO for ; Sun, 14 Jan 2018 06:57:39 -0500 (EST) Subject: Re: /lib/casper: read error: Invalid argument References: <20180114121011.56204f3f@hermann.intern.walstatt.dynvpn.de> To: freebsd-current@freebsd.org From: Charlie Li Message-ID: <73025813-0fb8-d9a6-2b10-ad65589a6865@vishwin.info> Date: Sun, 14 Jan 2018 06:57:38 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <20180114121011.56204f3f@hermann.intern.walstatt.dynvpn.de> Content-Type: text/plain; charset=utf-8 Content-Language: en-GB-large 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, 14 Jan 2018 11:57:45 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 14/01/2018 06:10, Hartmann, O. wrote: > I tried to investigate with the USB image created 10th January > 2018 from ISO downloads and it showed, that /boot/ was obviously > intact, but files in /usr/sbin, /usr/bin were zero in size, also > some libs in /usr/lib and /lib. While /boot/ seemingly being > already installed while other portions failed, I knew from the past > that I had to replace all /boot, /bin, /sbin, /usr/sbin, /usr/bin, > /lib, /usr/lib , /usr/libexec and /libexec from the recent USB > image. I did so via "pax -v -rw -pe", but I had to "chflags noschg" > some files/libraries on the target to get them overwritten. I > simply did a > > chflags noschg * > > to every folder/subfolder and "pax'ed" the destination then. So > far. I'm able to boot into single user again, but when it comes to > the shell and /bin/sh is supposed to be executed, I get the > strange message: > > /lib/casper/: read error: Invalid argument > > and the prompt is jumping back to ensure the PASSWORD (console is > password protected). > Something like this happened to me once, albeit a libc.so symbol mismatch after a hard crash that corrupted that and some more system files. So far you're on the right track with copying files off the image, though I extracted the relevant files/directory structures from the base.txz that bsdinstall uses. > Something is hindering to start the compiler somehow and it is > related to /lib/casper/: read error: Invalid argument? > > What is wrong here? How to fix this? > Don't reboot out of the USB image. Stay there and chroot into your mounted root filesystem, then run make installworld. - -- Charlie Li Can't think of a witty .sigline today… (This email address is for mailing list use only; replace local-part with vishwin for off-list communication) -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIzBAEBCgAdFiEE/RdyC3Asy49czZEGtQ4IJhNZSS0FAlpbRZ0ACgkQtQ4IJhNZ SS0aAxAAplLJ9NCLgttDDRLANK+ql15E5AE6pV1Y8jdLM7CunUzgMsyg/1hhy8ZK 2TG/0mEE7+jsxYjW5Wu9uBjsGaRuwY4dAO7TNdkbn3DMzJsrbBCfkXKGjeFKHwQu CB2fZRwfH6hdR0CxMeth9ftPHn8mbEqwl5YC4SLXBzixgi8Hpjj5J2Gne2nIur7q yhXdChon+k50zl+WxAeCNXTkKK7QKEANh56D/6VgTEyR1POFJqKBywLKm07tePUC 4Yqo4IPQsJsfQFCJ5V7o87PWqIpfsb/gPJkEsT81MKT0/XWRHXtHvzA0Ero7dMDS WbGFblyPg7GRzNRC7FLfqPmcOW6Qc3JFr2KA6b5IVoV3IhCor1o+mEV8tkZY2iPz scCImjPqr+QWoSt2Hv0QUc8i3L40pc4OAxslC8lCOKZrePA/nIowfRS8oJmhgKrL 9gJDQxPQGAn0fYKoY3n+oI95YfIn9MBE6hmpUKfXSRqh+s6xX5sMnf2tqm7Swiul Tjp05MbhBQn/Yxmwxa8Lnk6U3jtumza8qS8SXX3b039+8ADd4Y9L6l0IVk7+cG2i uNXxbl9o5jqoUyRgEvGAGzohGGUzzpz4k/wHht1gWeEmww4WJ2VN6eL8FFepWi2v o5rOeFbnuSzqOOslA6rQ6mkwDKPRoIVNFWEkQO1FR9MjyhKk7+4= =YOoR -----END PGP SIGNATURE----- From owner-freebsd-current@freebsd.org Sun Jan 14 13:00:42 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 22855E6E4D5 for ; Sun, 14 Jan 2018 13:00:42 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 956807ACC2 for ; Sun, 14 Jan 2018 13:00:40 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([85.182.8.155]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0LgISa-1fFYUN3vC0-00negW; Sun, 14 Jan 2018 14:00:32 +0100 Date: Sun, 14 Jan 2018 13:59:57 +0100 From: "O. Hartmann" To: Charlie Li Cc: freebsd-current@freebsd.org Subject: Re: /lib/casper: read error: Invalid argument Message-ID: <20180114140024.0a4c7e62@thor.intern.walstatt.dynvpn.de> In-Reply-To: <73025813-0fb8-d9a6-2b10-ad65589a6865@vishwin.info> References: <20180114121011.56204f3f@hermann.intern.walstatt.dynvpn.de> <73025813-0fb8-d9a6-2b10-ad65589a6865@vishwin.info> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/0Jlk.O6lo6/M=bUI4ZQeg_/"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:KR1vGkS9vmMRCJVmjBq0yOZQ1rco9NobylQz4SERPuyIdTplzI1 v0zEQr8hVIjMI/cn+E7BqAcKj+qOfkrM4wtemNE+DYvsFTT3qOAOovdBApaw6LM2f4DcXen wdMK2P9Q7WHhZIP5N2+4iCbcIi4pxpym0TaV9YBs07nV0GvnlA/Hb6+ZIbqYEpAhOVyARg1 DSIXliS0vtBbS79ymPSHw== X-UI-Out-Filterresults: notjunk:1;V01:K0:1ejrn9mxrrc=:7wLLJ/S7XbggVlI6ejeqAN /tFugHqVw8wjRVhmLoZy1DMFbV1XKv/Durn+QLnba+I0yx7A8vrwQ7+aBLKR1ss31D7za758p kemUtjihF+LMF6dibh+rgJslJom9Sa1Xs+FlytoKgMrVKvFJvNi5Ayt9oi/AUX1HMarlvBMW7 nRCuXosL4QnYFLniHwx0IZLwBMtMjNKz//dCwDHkjpPn78Wx2o1QlFxH/swVeivgERBIrYtY6 ZPeGMSIkpk6sRnmoHhT0DxmsHHW8fTI4J4advMIG4rJSTFS0OC7419yy2/qmscARuJXQ3v4xt a8MZhWLXzGwVbmdKnKFnJj8v870nrGGFMbyxDo6b2V9Jgmf0zNEhlZ/TgMV9M0MkRQDmXuNxO hdjzeVezaXw+NCCCYJCQYQRHDnC0al0AzFBxnvJ1wa5jD7J0aROXsepNci1NZV4ePvxWIw69a IpWlxPOq/mhub5vjuH0SgIJgOsUrIsI0IXW0kP3bfgreU4D9wJe1Qlh94GAh4Wt2Ccf5TlPY3 p5PZtyMJOJY9Q637NO9b8w3hLHpEktE6Esbf3TmnGNryRrC/gRd8ZeBnzeVT3LbxOr5tlU83J Ykfuxl0jaiYZATNSOhV9J1qlqThhekAJ1fRRZBIu7te1af1/JSnFj+AvOgAJ4HWPWO8oXcsd3 NMo6OmfG1wEoOX/dhUgiRW6cRmLhVYuNZiIYcWOoGstHT5fKATD0aPcku/uQOJU+0qsVYW5jE bYEKBfjuhMzkdKE7i/jssArw61eyf7eqy+5dkIaE9mAsYC/rF723OaEa6dZC5QCUDVlZuNSIR Q7lkPXoZoPtiqJtpniJKRV5VqdJ+A== 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, 14 Jan 2018 13:00:42 -0000 --Sig_/0Jlk.O6lo6/M=bUI4ZQeg_/ Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Am Sun, 14 Jan 2018 06:57:38 -0500 Charlie Li schrieb: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 >=20 > On 14/01/2018 06:10, Hartmann, O. wrote: > > I tried to investigate with the USB image created 10th January > > 2018 from ISO downloads and it showed, that /boot/ was obviously > > intact, but files in /usr/sbin, /usr/bin were zero in size, also > > some libs in /usr/lib and /lib. While /boot/ seemingly being > > already installed while other portions failed, I knew from the past > > that I had to replace all /boot, /bin, /sbin, /usr/sbin, /usr/bin, > > /lib, /usr/lib , /usr/libexec and /libexec from the recent USB > > image. I did so via "pax -v -rw -pe", but I had to "chflags noschg" > > some files/libraries on the target to get them overwritten. I > > simply did a > >=20 > > chflags noschg * > >=20 > > to every folder/subfolder and "pax'ed" the destination then. So > > far. I'm able to boot into single user again, but when it comes to > > the shell and /bin/sh is supposed to be executed, I get the > > strange message: > >=20 > > /lib/casper/: read error: Invalid argument > >=20 > > and the prompt is jumping back to ensure the PASSWORD (console is=20 > > password protected). > > =20 > Something like this happened to me once, albeit a libc.so symbol > mismatch after a hard crash that corrupted that and some more system > files. >=20 > So far you're on the right track with copying files off the image, > though I extracted the relevant files/directory structures from the > base.txz that bsdinstall uses. > > Something is hindering to start the compiler somehow and it is > > related to /lib/casper/: read error: Invalid argument? > >=20 > > What is wrong here? How to fix this? > > =20 > Don't reboot out of the USB image. Stay there and chroot into your > mounted root filesystem, then run make installworld. >=20 > - --=20 > Charlie Li > Can't think of a witty .sigline today=E2=80=A6 >=20 > (This email address is for mailing list use only; > replace local-part with vishwin for off-list communication) > -----BEGIN PGP SIGNATURE----- > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ >=20 > iQIzBAEBCgAdFiEE/RdyC3Asy49czZEGtQ4IJhNZSS0FAlpbRZ0ACgkQtQ4IJhNZ > SS0aAxAAplLJ9NCLgttDDRLANK+ql15E5AE6pV1Y8jdLM7CunUzgMsyg/1hhy8ZK > 2TG/0mEE7+jsxYjW5Wu9uBjsGaRuwY4dAO7TNdkbn3DMzJsrbBCfkXKGjeFKHwQu > CB2fZRwfH6hdR0CxMeth9ftPHn8mbEqwl5YC4SLXBzixgi8Hpjj5J2Gne2nIur7q > yhXdChon+k50zl+WxAeCNXTkKK7QKEANh56D/6VgTEyR1POFJqKBywLKm07tePUC > 4Yqo4IPQsJsfQFCJ5V7o87PWqIpfsb/gPJkEsT81MKT0/XWRHXtHvzA0Ero7dMDS > WbGFblyPg7GRzNRC7FLfqPmcOW6Qc3JFr2KA6b5IVoV3IhCor1o+mEV8tkZY2iPz > scCImjPqr+QWoSt2Hv0QUc8i3L40pc4OAxslC8lCOKZrePA/nIowfRS8oJmhgKrL > 9gJDQxPQGAn0fYKoY3n+oI95YfIn9MBE6hmpUKfXSRqh+s6xX5sMnf2tqm7Swiul > Tjp05MbhBQn/Yxmwxa8Lnk6U3jtumza8qS8SXX3b039+8ADd4Y9L6l0IVk7+cG2i > uNXxbl9o5jqoUyRgEvGAGzohGGUzzpz4k/wHht1gWeEmww4WJ2VN6eL8FFepWi2v > o5rOeFbnuSzqOOslA6rQ6mkwDKPRoIVNFWEkQO1FR9MjyhKk7+4=3D > =3DYOoR > -----END PGP SIGNATURE----- > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" I was afraid of using bsdinstall or just tar'ing the base.txz into the moun= ted partition, since I know that several issues existed in the past with overwriting crucu= ial files. /etc/ is always backuped, but /var/db holds other files, like from O= penLDAP. And it seems FreeBSD didn't take care of those. Somehow I "bravely" extracted base.txz - successfully.=20 I wasn't able to isolate the /lib/casper/ issue - which is really a pity si= nce it would have been important for desaster-recovery analysis. Another point is that FreeBSD's kernel is quiet when it fails to boot into = multiuser mode. The phenomenon with the broken installation was, that the kernel stop= ped issuing anything after USB subsystem has been started. Pluggin and unplugging was r= eported, but the boot didn't proceed. Somehow this is annoying. Also, with CURRENT FreeBSD 12.0-CURRENT #75 r327948: Sat Jan 13 23:00:08 C= ET 2018 amd64 up and running again, there are some strange leftovers in /usr/lib: find ./ -ctime +5 -a -name "*.a" -exec ls -l {} \; -r--r--r-- 1 root wheel 173698 Dec 23 23:02 ./libmlx5.a -r--r--r-- 1 root wheel 75698 Dec 23 23:02 ./libibnetdisc.a -r--r--r-- 1 root wheel 43516 Dec 25 03:49 ./libcxgb4.a -r--r--r-- 1 root wheel 6044 Dec 23 23:02 ./libnandfs.a -r--r--r-- 1 root wheel 6580 Dec 23 23:02 ./libnandfs_p.a -r--r--r-- 1 root wheel 86580 Dec 25 03:49 ./libosmcomp.a -r--r--r-- 1 root wheel 22104 Oct 31 13:33 ./libibcommon.a -r--r--r-- 1 root wheel 69812 Dec 23 23:02 ./libibumad.a -r--r--r-- 1 root wheel 105084 Dec 25 03:49 ./libibverbs.a -r--r--r-- 1 root wheel 182118 Dec 23 23:02 ./libibmad.a -r--r--r-- 1 root wheel 67548 Dec 23 23:02 ./libmlx4.a -r--r--r-- 1 root wheel 51190 Oct 16 22:31 ./libmthca.a -r--r--r-- 1 root wheel 125960 Dec 23 23:02 ./libopensm.a -r--r--r-- 1 root wheel 39574 Dec 23 23:02 ./libosmvendor.a -r--r--r-- 1 root wheel 17466 Dec 23 23:02 ./libibcm.a -r--r--r-- 1 root wheel 62058 Dec 23 23:02 ./librdmacm.a -r--r--r-- 1 root wheel 112430 Oct 31 13:33 ./libibsdp.a Those files aren't addressed by "make delete-old-libs" and some of them see= m to belong to outdated or switched off portions of the tree. Regards, Oliver --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/0Jlk.O6lo6/M=bUI4ZQeg_/ Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWltUaAAKCRDS528fyFhY lHE4Af0UJEELRgjL992Juqo3CJkfXrKxbd41r47WcLeCWpyDOcar1Hj41WYNXMFy l3DNJMeR2VLQpHcPw+NAunHBvPwuAf91/h9xFgwGN4czmOjIj7qeTJzmO+ZeElWY osT055vBgOISDe6uSLBMWN++7vO1TkGMH3E1l/ZSUFZ0HtgH8x7o =7nXb -----END PGP SIGNATURE----- --Sig_/0Jlk.O6lo6/M=bUI4ZQeg_/-- From owner-freebsd-current@freebsd.org Sun Jan 14 16:36:02 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E7887E79431 for ; Sun, 14 Jan 2018 16:36:02 +0000 (UTC) (envelope-from cejkar@fit.vutbr.cz) Received: from kazi.fit.vutbr.cz (kazi6.fit.vutbr.cz [IPv6:2001:67c:1220:808::93e5:80c]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "kazi.fit.vutbr.cz", Issuer "Brno University of Technology CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 865EE829A0 for ; Sun, 14 Jan 2018 16:36:02 +0000 (UTC) (envelope-from cejkar@fit.vutbr.cz) Received: from kazi.fit.vutbr.cz (localhost [127.0.0.1]) by kazi.fit.vutbr.cz (8.15.2/8.15.2) with ESMTPS id w0EGZxMl056476 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 14 Jan 2018 17:35:59 +0100 (CET) Received: (from cejkar@localhost) by kazi.fit.vutbr.cz (8.15.2/8.15.1/Submit) id w0EGZxtr056475; Sun, 14 Jan 2018 17:35:59 +0100 (CET) (envelope-from cejkar@fit.vutbr.cz) X-Authentication-Warning: kazi.fit.vutbr.cz: cejkar set sender to cejkar@fit.vutbr.cz using -f Date: Sun, 14 Jan 2018 17:35:59 +0100 From: Cejka Rudolf To: blubee blubeeme Cc: Henry Hu , FreeBSD current Subject: Re: msdosfs_iconv Message-ID: <20180114163559.GA55347@fit.vutbr.cz> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.2 (2017-12-15) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fit.vutbr.cz; h=date:from:to:cc:subject:message-id:references:mime-version:content-type:in-reply-to; s=mx1; bh=xTZdDdQ3cMKi3/xJoe64+xk3j9amJg1wdUY2DN9suAU=; b=MzJj6jwt+gvyTOFAj48x65NK7U36I8E7gM5QUYk1XwDCTbXb1edUSi4wmn0aTQLdouICtk1pmypxojv5TZunThMM6Ui2dqt0Cf4jk/gpYenfyun7+WDADiU4OLuXA3ckA4QsBHs4a5TZzBk0BW8TpAjCBaOTdt2qTiS27jupmSg= X-Scanned-By: MIMEDefang 2.78 on 147.229.8.12 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, 14 Jan 2018 16:36:03 -0000 blubee blubeeme wrote (2018/01/14): > if you first run the mount_msdosfs command as root, it'll load the locale > settings just fine. > If you logout or reboot and try to call mount_msdosfs -L [locale] as a > regular user; > The command will fail. If you have kiconvtool already installed and usermount set to 1, did you set also kiconv_preload="YES" kiconv_local_charsets="..." kiconv_foreign_charsets="..." in your /etc/rc.conf? Please look at EXAMPLES in man kiconvtool. -- Rudolf Cejka http://www.fit.vutbr.cz/~cejkar Brno University of Technology, Faculty of Information Technology Bozetechova 2, 612 66 Brno, Czech Republic From owner-freebsd-current@freebsd.org Mon Jan 15 00:10:08 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 589B9E68D1E for ; Mon, 15 Jan 2018 00:10:08 +0000 (UTC) (envelope-from jakub_lach@mailplus.pl) Received: from n6.nabble.com (n6.nabble.com [162.255.23.37]) by mx1.freebsd.org (Postfix) with ESMTP id 3667D7463C for ; Mon, 15 Jan 2018 00:10:07 +0000 (UTC) (envelope-from jakub_lach@mailplus.pl) Received: from n6.nabble.com (localhost [127.0.0.1]) by n6.nabble.com (Postfix) with ESMTP id D6143407D847 for ; Sun, 14 Jan 2018 17:01:22 -0700 (MST) Date: Sun, 14 Jan 2018 17:01:22 -0700 (MST) From: Jakub Lach To: freebsd-current@freebsd.org Message-ID: <1515974482874-0.post@n6.nabble.com> In-Reply-To: References: <1075465a-ffef-95c7-7750-2d50d7b8a15c@sentex.net> <3ea937fe-bbb1-7f6f-f2e1-8a7d94e7feef@freebsd.org> Subject: Re: [CFT] AMD cpu microcode update port sysutils/devcpu-data D13832 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jan 2018 00:10:08 -0000 How far it's supposed to support legacy CPUs on FreeBSD? x86info Found 2 identical CPUs Extended Family: 0 Extended Model: 1 Family: 6 Model: 23 Stepping: 10 Type: 0 (Original OEM) CPU Model (x86info's best guess): Unknown model. Processor name string (BIOS programmed): Intel(R) Core(TM)2 Duo CPU P9700 @ 2.80GHz from README "Features: - SMP support. - Recognition of all Intel/AMD/Centaur/Cyrix/VIA CPUs." -- Sent from: http://freebsd.1045724.x6.nabble.com/freebsd-current-f3875308.html From owner-freebsd-current@freebsd.org Mon Jan 15 06:43:10 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D11D3EB2C1B for ; Mon, 15 Jan 2018 06:43:10 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F833823B0 for ; Mon, 15 Jan 2018 06:43:09 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from freyja.zeit4.iv.bundesimmobilien.de ([87.138.105.249]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MexFh-1eCzPg2aO9-00OY1A for ; Mon, 15 Jan 2018 07:43:01 +0100 Date: Mon, 15 Jan 2018 07:42:50 +0100 From: "O. Hartmann" To: freebsd-current Subject: CURRENT: can't buildworld; /usr/bin/ld: error: cannot open crt1.o: Message-ID: <20180115074244.72264055@freyja.zeit4.iv.bundesimmobilien.de> Organization: Walstatt MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:4G/I59pYfOFE57I2P9zSUFCw3eXOCEQkVLg3zyTn7QXURXtM8yo Nm20YS4Gv4F3RtNO6z9xdOIY9BQ8IKBk0NHN+6RUw4T8nllEEd1Xb4YYF/Ud3BwPxGUMkH9 HE1glXIRsPxiaGjL6/kot5I1c1KPlevXIkH6UeRS5uWoaCb86+z5XNZF2zrCjIzcEn1zzRd KT1dGptTMzOEIbtQzqTxA== X-UI-Out-Filterresults: notjunk:1;V01:K0:IffBKX7bs1c=:109EeK/UeduNPvzilOTHWA 7gulyaegSPInYrl8NRSl9M8pBQouKDrfGMKkaDkMpYQhniK22xlwTwV4S+j0eD211mMXnhXOX SK58/hNCHW540sQCVcQXev8GWe3gxevRI9vm/lTL2MhfLzrnfG7VscB5pvMEp63VOuOGtznoI kcEAkDkiOZFEVxIk9T24nll+4//mYcsGbxQ5oaH49XfX9uTJONj0rodzWk2/HFxjL5dTgwPyB 2reHbHI/OmBuFHwzC0KmFF5crc/UYbOICLVOoOJt2+Kr3dBolt+apMHRGpIZOfNNGEjCGLLjq jqNkc3Sq6rhXSg2/cBiHJ8I2tsCPVlSYvhvDcDQHP/JrKqq9ZPOGgL7xaBm/uymblsk765wSa syYnmyo91hpGWEgq/mOTYFQZ1gv2WRPmigAl5ar1qVMYdI/YoVJN3c+Phuu72z2/ZM/vhLZFK eoOHlY1obFXbeMnqMB6OcFBAmtF+GopXDw0SUtBstniKfmJ9ak9gpWOUiX0Iik7fV0oVS6tMP lUsLORvWyh0y4CJtXFvD9JTStDPH5dbu8q/J2VydDgSk4KvT9qsxccWuEdoGDgfIDbMnsHg5X 19vNTvs4ipanlhD4wDGXYTJk9OsqYjBM2gvSewww1bCO5oxdsKNp5uF8M8ovcu8SR5ol95qD1 I3zqkoFGb02BCo6S9CL+IOrCoLwPl37/YXO6j4Dg4S8UuEQNkUFUqRpgSuiIE3htWbmPPZhzm I0Aha0v1qq6OqBqlKcmDLhSpJK7epb0Mv2hwA/6LncY/F7AhI7BGMGZe6GjTflSVt83BYctAx Pk+5szromAhceS3dbmpJ2vP7Hl3J+KMXMU89omupBwTOhNeIqk= 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, 15 Jan 2018 06:43:10 -0000 One of our CURRENT boxes is repeateadly disobeying to build "buildworld" (make buildkernel seems to work as I did several kernels right now). The hosts's world is as of Wednesday, 10th January, the kernel's revison is FreeBSD 12.0-CURRENT #0 r327871: Fri Jan 12 12:18:19 CET 2018 amd64. I did, as a test, Friday, 12th Jan, as you can see, the last kernel build. The host in question also carries a variety of release, package an jail builds in separate source trees (CURRENT in most cases, to keep them away from the host's source tree). Those separate source trees also reject to build. After performing a "make cleanworld" to startover (even this morning, when I watched LLVM/CLANG 6.0.0 has slipped in), I face still the same error: /usr/bin/ld: error: cannot open crt1.o: No such file or directory More details see below. The last installation of the system was performed with WITH_LLD_IS_LD and WITH_BOOTSTRAP_LLD set, if this is of importance. I still have WITH_LLD_IS_LD=YES set in /usr/src.conf. An we use WITH_META_MODE, just for the record. I have other machines which didn't get updated on Wednesday, 10th January and they perform well and without problems (with the same settings in /etc/src.conf and also WITH_META_MODE). Can someone give me some hints? How to fix the problem? Thanks ins advance, Oliver [...] -------------------------------------------------------------- >>> stage 1.1: legacy release compatibility shims -------------------------------------------------------------- cd /usr/src; INSTALL="sh /usr/src/tools/install.sh" TOOLS_PREFIX=/usr/obj/usr/src/amd64.amd64/tmp PATH=/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/bin:/sbin:/bin:/usr/sbin:/usr/bin WORLDTMP=/usr/obj/usr/src/amd64.amd64/tmp MAKEFLAGS="-m /usr/src/tools/build/mk -m /usr/src/share/mk" make -f Makefile.inc1 DESTDIR= OBJTOP='/usr/obj/usr/src/amd64.amd64/tmp/obj-tools' OBJROOT='${OBJTOP}/' MAKEOBJDIRPREFIX= BOOTSTRAPPING=1200055 BWPHASE=legacy SSP_CFLAGS= MK_HTML=no NO_LINT=yes MK_MAN=no -DNO_PIC MK_PROFILE=no -DNO_SHARED -DNO_CPU_CFLAGS MK_WARNS=no MK_CTF=no MK_CLANG_EXTRAS=no MK_CLANG_FULL=no MK_LLDB=no MK_TESTS=no MK_LLD=yes MK_INCLUDES=yes legacy ===> tools/build (obj,includes,all,install) Building /usr/obj/usr/src/amd64.amd64/tmp/obj-tools/tools/build/_libinstall -------------------------------------------------------------- >>> stage 1.2: bootstrap tools -------------------------------------------------------------- cd /usr/src; INSTALL="sh /usr/src/tools/install.sh" TOOLS_PREFIX=/usr/obj/usr/src/amd64.amd64/tmp PATH=/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/bin:/sbin:/bin:/usr/sbin:/usr/bin WORLDTMP=/usr/obj/usr/src/amd64.amd64/tmp MAKEFLAGS="-m /usr/src/tools/build/mk -m /usr/src/share/mk" make -f Makefile.inc1 DESTDIR= OBJTOP='/usr/obj/usr/src/amd64.amd64/tmp/obj-tools' OBJROOT='${OBJTOP}/' MAKEOBJDIRPREFIX= BOOTSTRAPPING=1200055 BWPHASE=bootstrap-tools SSP_CFLAGS= MK_HTML=no NO_LINT=yes MK_MAN=no -DNO_PIC MK_PROFILE=no -DNO_SHARED -DNO_CPU_CFLAGS MK_WARNS=no MK_CTF=no MK_CLANG_EXTRAS=no MK_CLANG_FULL=no MK_LLDB=no MK_TESTS=no MK_LLD=yes MK_INCLUDES=yes bootstrap-tools ===> lib/clang/libllvmminimal (obj,all,install) Building /usr/obj/usr/src/amd64.amd64/tmp/obj-tools/lib/clang/libllvmminimal/Support/ConvertUTFWrapper.o Building /usr/obj/usr/src/amd64.amd64/tmp/obj-tools/lib/clang/libllvmminimal/Support/Debug.o [...] Building /usr/obj/usr/src/amd64.amd64/tmp/obj-tools/usr.bin/clang/llvm-tblgen/X86RecognizableInstr.o Building /usr/obj/usr/src/amd64.amd64/tmp/obj-tools/usr.bin/clang/llvm-tblgen/llvm-tblgen /usr/bin/ld: error: cannot open crt1.o: No such file or directory c++: error: linker command failed with exit code 1 (use -v to see invocation) *** Error code 1 Stop. make[3]: stopped in /usr/src/usr.bin/clang/llvm-tblgen .ERROR_TARGET='llvm-tblgen' .ERROR_META_FILE='/usr/obj/usr/src/amd64.amd64/tmp/obj-tools/usr.bin/clang/llvm-tblgen/llvm-tblgen.meta' .MAKE.LEVEL='3' MAKEFILE='' .MAKE.MODE='meta missing-filemon=yes missing-meta=yes silent=yes verbose' _ERROR_CMD='c++ -O2 -pipe -O3 -I/usr/obj/usr/src/amd64.amd64/tmp/obj-tools/lib/clang/libllvm -I/usr/src/lib/clang/include -I/usr/src/contrib/llvm/include -DLLVM_BUILD_GLOBAL_ISEL -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DLLVM_DEFAULT_TARGET_TRIPLE=\"x86_64-unknown-freebsd12.0\" -DLLVM_HOST_TRIPLE=\"x86_64-unknown-freebsd12.0\" -DDEFAULT_SYSROOT=\"/usr/obj/usr/src/amd64.amd64/tmp\" -ffunction-sections -fdata-sections -DNDEBUG -Qunused-arguments -I/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/include -std=c++11 -fno-exceptions -fno-rtti -stdlib=libc++ -Wno-c++11-extensions -Wl,--gc-sections -static -L/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/lib -o llvm-tblgen AsmMatcherEmitter.o AsmWriterEmitter.o AsmWriterInst.o Attributes.o CTagsEmitter.o CallingConvEmitter.o CodeEmitterGen.o CodeGenDAGPatterns.o CodeGenHwModes.o CodeGenInstruction.o CodeGenMapTable.o CodeGenRegisters.o CodeGenSchedule.o CodeGenTarget.o DAGISelEmitter.o DAGISelMatcher.o DAGISelMatcherEmitter.o DAGISelMatcherGen.o DAGISelMatcherOpt.o DFAPacketizerEmitter.o DisassemblerEmitter.o FastISelEmitter.o FixedLenDecoderEmitter.o GlobalISelEmitter.o InfoByHwMode.o InstrDocsEmitter.o InstrInfoEmitter.o IntrinsicEmitter.o OptParserEmitter.o PseudoLoweringEmitter.o RegisterBankEmitter.o RegisterInfoEmitter.o SDNodeProperties.o SearchableTableEmitter.o SubtargetEmitter.o SubtargetFeatureInfo.o TableGen.o Types.o X86DisassemblerTables.o X86EVEX2VEXTablesEmitter.o X86FoldTablesEmitter.o X86ModRMFilters.o X86RecognizableInstr.o /usr/obj/usr/src/amd64.amd64/tmp/obj-tools/lib/clang/libllvmminimal/libllvmminimal.a -L/usr/obj/usr/src/amd64.amd64/tmp/obj-tools/lib/ncurses/ncursesw -lncursesw -L/usr/obj/usr/src/amd64.amd64/tmp/obj-tools/lib/libthr -lpthread -legacy;' .CURDIR='/usr/src/usr.bin/clang/llvm-tblgen' .MAKE='make' .OBJDIR='/usr/obj/usr/src/amd64.amd64/tmp/obj-tools/usr.bin/clang/llvm-tblgen' .TARGETS='all' DESTDIR='' LD_LIBRARY_PATH='' MACHINE='amd64' MACHINE_ARCH='amd64' MAKEOBJDIRPREFIX='' MAKESYSPATH='/usr/src/share/mk' MAKE_VERSION='20171028' PATH='/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/bin:/sbin:/bin:/usr/sbin:/usr/bin' SRCTOP='/usr/src' OBJTOP='/usr/obj/usr/src/amd64.amd64/tmp/obj-tools' .MAKE.MAKEFILES='/usr/src/share/mk/sys.mk /usr/src/share/mk/local.sys.env.mk /usr/src/share/mk/src.sys.env.mk /etc/src-env.conf /usr/src/share/mk/bsd.mkopt.mk /usr/src/share/mk/src.sys.obj.mk /usr/src/share/mk/auto.obj.mk /usr/src/share/mk/bsd.suffixes.mk /etc/make.conf /usr/local/etc/ports.conf /usr/src/share/mk/local.sys.mk /usr/src/share/mk/src.sys.mk /etc/src.conf /usr/src/usr.bin/clang/llvm-tblgen/Makefile /usr/src/usr.bin/clang/llvm.prog.mk /usr/src/lib/clang/llvm.pre.mk /usr/src/lib/clang/llvm.build.mk /usr/src/tools/build/mk/bsd.prog.mk /usr/src/share/mk/bsd.prog.mk /usr/src/share/mk/bsd.init.mk /usr/src/share/mk/bsd.opts.mk /usr/src/share/mk/bsd.cpu.mk /usr/src/share/mk/local.init.mk /usr/src/share/mk/src.init.mk /usr/src/usr.bin/clang/llvm-tblgen/../Makefile.inc /usr/src/share/mk/bsd.compiler.mk /usr/src/share/mk/bsd.linker.mk /usr/src/usr.bin/clang/llvm-tblgen/../../Makefile.inc /usr/src/share/mk/bsd.own.mk /usr/src/share /mk/bsd.libnames.mk /usr/src/share/mk/src.libnames.mk /usr/src/share/mk/src.opts.mk /usr/src/share/mk/bsd.nls.mk /usr/src/share/mk/bsd.confs.mk /usr/src/share/mk/bsd.files.mk /usr/src/share/mk/bsd.incs.mk /usr/src/share/mk/bsd.links.mk /usr/src/share/mk/bsd.dep.mk /usr/src/share/mk/bsd.clang-analyze.mk /usr/src/share/mk/bsd.obj.mk /usr/src/share/mk/bsd.subdir.mk /usr/src/share/mk/bsd.sys.mk /usr/src/tools/build/mk/Makefile.boot' .PATH='. /usr/src/usr.bin/clang/llvm-tblgen /usr/src/contrib/llvm/utils/TableGen' *** Error code 1 From owner-freebsd-current@freebsd.org Mon Jan 15 07:21:17 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 534ECEB4D3F for ; Mon, 15 Jan 2018 07:21:17 +0000 (UTC) (envelope-from ultima1252@gmail.com) Received: from mail-yb0-x244.google.com (mail-yb0-x244.google.com [IPv6:2607:f8b0:4002:c09::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0DD9583C74 for ; Mon, 15 Jan 2018 07:21:17 +0000 (UTC) (envelope-from ultima1252@gmail.com) Received: by mail-yb0-x244.google.com with SMTP id h62so4087394ybi.11 for ; Sun, 14 Jan 2018 23:21:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=kAnGwFMVCWko3GRC4826wrFHpU/uLH1b40EU+1G7+Gs=; b=TOuvZlGQYCg355vTxVG+1JU3zxj8pAtKmJMHXbHIgo23BegJOSJFf7HnTbUR3gbw9c m8037vc27AABxG+jZPqa7FKxNnMjxG7XRdRhBq902zYwIew6Nak2mFNXpbF30o4Iwt67 sHQ2lYaheC+uqlrCG1KNM6H5ksBb7v4ekWLmvaHvOS4auAnCwuZgnW6Ahz49gayiI6xA P/2rq90oScTiFIiV58v155lQsTYJbhAV3FMNzXFmms+xIQ8HgIUQHYNtflBalXVgYZqg RvV2MNcZTE+5jcdMnjNCnOGU1RTf/VXdxb3kVcNQ86LimaSQ+gzxUE7FBBFUOokZfa2D oPDg== 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=kAnGwFMVCWko3GRC4826wrFHpU/uLH1b40EU+1G7+Gs=; b=dqwTmr3Bjg0gzNv5V1kcEokDUtxW7WYLm4fdkTsO/zBhN3TmunRCaGeC+1Koa4Zl00 ifuhjyT02Wyi4L3xcOfQn3gN3bUFH62ikDDz5uvQ7nrG6TfmwhjnM5zd5Eejke+9CI1I qkcG5OFqThw0FOT9Cv/DFsZy+UbbiPD8pyJvsQ1bkoJzyc8m3AmKITdLBdlQ9rCFWjsf Z+dnUZwe9iI+ibv9Fwk+s7Y+wyrQ/sCJasoukhyWETlnH8UVq7A6t/9cD3sEio6pjhT7 CY4NOnIZ9q78ELeo0x+YiH/gtCxo5QCw7ewY5xm/Np3MrO55vt5GYQRF+2Ec2dijFXk1 7a9A== X-Gm-Message-State: AKwxytdbJ+ZJESoN84bnQamKFEbp/6D97gsn2bv11AD6CYoLVvAaPEpR xPdwn0AHYPVzHWwuAl0uML+r2gq3wCnilw/Pld8I77cd X-Google-Smtp-Source: ACJfBouI2Z69r5BupIo8yGNDNkXjB9h/QTttoTCj42yhqjpj52Ms0Err3jAeVen9hRfVLypHnNK1njM7bNOdK8e8wxE= X-Received: by 10.37.130.143 with SMTP id r15mr2131654ybk.261.1516000875840; Sun, 14 Jan 2018 23:21:15 -0800 (PST) MIME-Version: 1.0 Received: by 10.129.74.214 with HTTP; Sun, 14 Jan 2018 23:21:15 -0800 (PST) In-Reply-To: <20180115074244.72264055@freyja.zeit4.iv.bundesimmobilien.de> References: <20180115074244.72264055@freyja.zeit4.iv.bundesimmobilien.de> From: Ultima Date: Sun, 14 Jan 2018 23:21:15 -0800 Message-ID: Subject: Re: CURRENT: can't buildworld; /usr/bin/ld: error: cannot open crt1.o: To: "O. Hartmann" Cc: freebsd-current 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: Mon, 15 Jan 2018 07:21:17 -0000 Try updating? just upgraded to r327991 and it was smooth sailing. On Sun, Jan 14, 2018 at 10:42 PM, O. Hartmann wrote: > One of our CURRENT boxes is repeateadly disobeying to build "buildworld" > (make > buildkernel seems to work as I did several kernels right now). > > The hosts's world is as of Wednesday, 10th January, the kernel's revison is > > FreeBSD 12.0-CURRENT #0 r327871: Fri Jan 12 12:18:19 CET 2018 amd64. > > I did, as a test, Friday, 12th Jan, as you can see, the last kernel build. > > The host in question also carries a variety of release, package an jail > builds > in separate source trees (CURRENT in most cases, to keep them away from the > host's source tree). Those separate source trees also reject to build. > > After performing a "make cleanworld" to startover (even this morning, when > I > watched LLVM/CLANG 6.0.0 has slipped in), I face still the same error: > > /usr/bin/ld: error: cannot open crt1.o: No such file or directory > > More details see below. > > The last installation of the system was performed with WITH_LLD_IS_LD and > WITH_BOOTSTRAP_LLD set, if this is of importance. I still have > WITH_LLD_IS_LD=YES set in /usr/src.conf. > > An we use WITH_META_MODE, just for the record. > > I have other machines which didn't get updated on Wednesday, 10th January > and > they perform well and without problems (with the same settings in > /etc/src.conf > and also WITH_META_MODE). > > Can someone give me some hints? How to fix the problem? > > Thanks ins advance, > > Oliver > > [...] > -------------------------------------------------------------- > >>> stage 1.1: legacy release compatibility shims > -------------------------------------------------------------- > cd /usr/src; INSTALL="sh /usr/src/tools/install.sh" > TOOLS_PREFIX=/usr/obj/usr/src/amd64.amd64/tmp > PATH=/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/ > usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/usr/obj/ > usr/src/amd64.amd64/tmp/legacy/bin:/sbin:/bin:/usr/sbin:/usr/bin > WORLDTMP=/usr/obj/usr/src/amd64.amd64/tmp > MAKEFLAGS="-m /usr/src/tools/build/mk -m /usr/src/share/mk" make -f > Makefile.inc1 DESTDIR= OBJTOP='/usr/obj/usr/src/ > amd64.amd64/tmp/obj-tools' > OBJROOT='${OBJTOP}/' MAKEOBJDIRPREFIX= BOOTSTRAPPING=1200055 > BWPHASE=legacy > SSP_CFLAGS= MK_HTML=no NO_LINT=yes MK_MAN=no -DNO_PIC MK_PROFILE=no > -DNO_SHARED -DNO_CPU_CFLAGS MK_WARNS=no MK_CTF=no MK_CLANG_EXTRAS=no > MK_CLANG_FULL=no MK_LLDB=no MK_TESTS=no MK_LLD=yes MK_INCLUDES=yes > legacy > ===> tools/build (obj,includes,all,install) > Building /usr/obj/usr/src/amd64.amd64/tmp/obj-tools/tools/build/_ > libinstall > > -------------------------------------------------------------- > >>> stage 1.2: bootstrap tools > -------------------------------------------------------------- > cd /usr/src; INSTALL="sh /usr/src/tools/install.sh" > TOOLS_PREFIX=/usr/obj/usr/src/amd64.amd64/tmp > PATH=/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/ > usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/usr/obj/ > usr/src/amd64.amd64/tmp/legacy/bin:/sbin:/bin:/usr/sbin:/usr/bin > WORLDTMP=/usr/obj/usr/src/amd64.amd64/tmp > MAKEFLAGS="-m /usr/src/tools/build/mk -m /usr/src/share/mk" make -f > Makefile.inc1 DESTDIR= OBJTOP='/usr/obj/usr/src/ > amd64.amd64/tmp/obj-tools' > OBJROOT='${OBJTOP}/' MAKEOBJDIRPREFIX= BOOTSTRAPPING=1200055 > BWPHASE=bootstrap-tools SSP_CFLAGS= MK_HTML=no NO_LINT=yes MK_MAN=no > -DNO_PIC MK_PROFILE=no -DNO_SHARED -DNO_CPU_CFLAGS MK_WARNS=no MK_CTF=no > MK_CLANG_EXTRAS=no MK_CLANG_FULL=no MK_LLDB=no MK_TESTS=no MK_LLD=yes > MK_INCLUDES=yes bootstrap-tools ===> lib/clang/libllvmminimal > (obj,all,install) > Building /usr/obj/usr/src/amd64.amd64/tmp/obj-tools/lib/clang/ > libllvmminimal/Support/ConvertUTFWrapper.o > Building /usr/obj/usr/src/amd64.amd64/tmp/obj-tools/lib/clang/ > libllvmminimal/Support/Debug.o > > [...] > > Building /usr/obj/usr/src/amd64.amd64/tmp/obj-tools/usr.bin/clang/ > llvm-tblgen/X86RecognizableInstr.o > Building /usr/obj/usr/src/amd64.amd64/tmp/obj-tools/usr.bin/clang/ > llvm-tblgen/llvm-tblgen > /usr/bin/ld: error: cannot open crt1.o: No such file or directory > c++: error: linker command failed with exit code 1 (use -v to see > invocation) > *** Error code 1 > > Stop. > make[3]: stopped in /usr/src/usr.bin/clang/llvm-tblgen > .ERROR_TARGET='llvm-tblgen' > .ERROR_META_FILE='/usr/obj/usr/src/amd64.amd64/tmp/obj- > tools/usr.bin/clang/llvm-tblgen/llvm-tblgen.meta' > .MAKE.LEVEL='3' > MAKEFILE='' > .MAKE.MODE='meta missing-filemon=yes missing-meta=yes silent=yes verbose' > _ERROR_CMD='c++ -O2 -pipe -O3 > -I/usr/obj/usr/src/amd64.amd64/tmp/obj-tools/lib/clang/libllvm > -I/usr/src/lib/clang/include -I/usr/src/contrib/llvm/include > -DLLVM_BUILD_GLOBAL_ISEL -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS > -DLLVM_DEFAULT_TARGET_TRIPLE=\"x86_64-unknown-freebsd12.0\" > -DLLVM_HOST_TRIPLE=\"x86_64-unknown-freebsd12.0\" > -DDEFAULT_SYSROOT=\"/usr/obj/usr/src/amd64.amd64/tmp\" -ffunction-sections > -fdata-sections -DNDEBUG -Qunused-arguments > -I/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/include -std=c++11 > -fno-exceptions -fno-rtti -stdlib=libc++ -Wno-c++11-extensions > -Wl,--gc-sections -static -L/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/lib > -o > llvm-tblgen AsmMatcherEmitter.o AsmWriterEmitter.o AsmWriterInst.o > Attributes.o CTagsEmitter.o CallingConvEmitter.o CodeEmitterGen.o > CodeGenDAGPatterns.o CodeGenHwModes.o CodeGenInstruction.o > CodeGenMapTable.o > CodeGenRegisters.o CodeGenSchedule.o CodeGenTarget.o DAGISelEmitter.o > DAGISelMatcher.o DAGISelMatcherEmitter.o DAGISelMatcherGen.o > DAGISelMatcherOpt.o DFAPacketizerEmitter.o DisassemblerEmitter.o > FastISelEmitter.o FixedLenDecoderEmitter.o GlobalISelEmitter.o > InfoByHwMode.o > InstrDocsEmitter.o InstrInfoEmitter.o IntrinsicEmitter.o OptParserEmitter.o > PseudoLoweringEmitter.o RegisterBankEmitter.o RegisterInfoEmitter.o > SDNodeProperties.o SearchableTableEmitter.o SubtargetEmitter.o > SubtargetFeatureInfo.o TableGen.o Types.o X86DisassemblerTables.o > X86EVEX2VEXTablesEmitter.o X86FoldTablesEmitter.o X86ModRMFilters.o > X86RecognizableInstr.o /usr/obj/usr/src/amd64.amd64/ > tmp/obj-tools/lib/clang/libllvmminimal/libllvmminimal.a > -L/usr/obj/usr/src/amd64.amd64/tmp/obj-tools/lib/ncurses/ncursesw > -lncursesw > -L/usr/obj/usr/src/amd64.amd64/tmp/obj-tools/lib/libthr -lpthread > -legacy;' .CURDIR='/usr/src/usr.bin/clang/llvm-tblgen' .MAKE='make' > .OBJDIR='/usr/obj/usr/src/amd64.amd64/tmp/obj-tools/usr.bin/clang/llvm-tblgen' > .TARGETS='all' > DESTDIR='' LD_LIBRARY_PATH='' MACHINE='amd64' MACHINE_ARCH='amd64' > MAKEOBJDIRPREFIX='' MAKESYSPATH='/usr/src/share/mk' > MAKE_VERSION='20171028' > PATH='/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/ > usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/usr/obj/ > usr/src/amd64.amd64/tmp/legacy/bin:/sbin:/bin:/usr/sbin:/usr/bin' > SRCTOP='/usr/src' > OBJTOP='/usr/obj/usr/src/amd64.amd64/tmp/obj-tools' > .MAKE.MAKEFILES='/usr/src/share/mk/sys.mk /usr/src/share/mk/local.sys. > env.mk /usr/src/share/mk/src.sys.env.mk /etc/src-env.conf > /usr/src/share/mk/bsd.mkopt.mk /usr/src/share/mk/src.sys.obj.mk > /usr/src/share/mk/auto.obj.mk /usr/src/share/mk/bsd.suffixes.mk > /etc/make.conf /usr/local/etc/ports.conf /usr/src/share/mk/local.sys.mk > /usr/src/share/mk/src.sys.mk /etc/src.conf /usr/src/usr.bin/clang/llvm-tblgen/Makefile > /usr/src/usr.bin/clang/llvm.prog.mk /usr/src/lib/clang/llvm.pre.mk > /usr/src/lib/clang/llvm.build.mk /usr/src/tools/build/mk/bsd.prog.mk > /usr/src/share/mk/bsd.prog.mk /usr/src/share/mk/bsd.init.mk > /usr/src/share/mk/bsd.opts.mk /usr/src/share/mk/bsd.cpu.mk > /usr/src/share/mk/local.init.mk /usr/src/share/mk/src.init.mk > /usr/src/usr.bin/clang/llvm-tblgen/../Makefile.inc /usr/src/share/mk/bsd. > compiler.mk /usr/src/share/mk/bsd.linker.mk /usr/src/usr.bin/clang/llvm-tblgen/../../Makefile.inc > /usr/src/share/mk/bsd.own.mk /usr/src/share > /mk/bsd.libnames.mk /usr/src/share/mk/src.libnames.mk /usr/src/share/mk/ > src.opts.mk /usr/src/share/mk/bsd.nls.mk /usr/src/share/mk/bsd.confs.mk > /usr/src/share/mk/bsd.files.mk /usr/src/share/mk/bsd.incs.mk > /usr/src/share/mk/bsd.links.mk /usr/src/share/mk/bsd.dep.mk > /usr/src/share/mk/bsd.clang-analyze.mk /usr/src/share/mk/bsd.obj.mk > /usr/src/share/mk/bsd.subdir.mk /usr/src/share/mk/bsd.sys.mk > /usr/src/tools/build/mk/Makefile.boot' .PATH='. > /usr/src/usr.bin/clang/llvm-tblgen /usr/src/contrib/llvm/utils/TableGen' > *** Error code 1 > _______________________________________________ > 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 Jan 15 07:46:04 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DC183EB6388 for ; Mon, 15 Jan 2018 07:46:04 +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 9F30FE6B for ; Mon, 15 Jan 2018 07:46:04 +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 4CBF047335; Mon, 15 Jan 2018 08:45:56 +0100 (CET) From: Dimitry Andric Message-Id: <1C404258-502F-43D4-B88A-45BE6A90681F@FreeBSD.org> Content-Type: multipart/signed; boundary="Apple-Mail=_CFBE0B21-3E5E-4F31-8A19-218C9849668A"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: CURRENT: can't buildworld; /usr/bin/ld: error: cannot open crt1.o: Date: Mon, 15 Jan 2018 08:45:56 +0100 In-Reply-To: <20180115074244.72264055@freyja.zeit4.iv.bundesimmobilien.de> Cc: freebsd-current To: "O. Hartmann" References: <20180115074244.72264055@freyja.zeit4.iv.bundesimmobilien.de> X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jan 2018 07:46:05 -0000 --Apple-Mail=_CFBE0B21-3E5E-4F31-8A19-218C9849668A Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 15 Jan 2018, at 07:42, O. Hartmann wrote: >=20 > One of our CURRENT boxes is repeateadly disobeying to build = "buildworld" (make > buildkernel seems to work as I did several kernels right now). >=20 > The hosts's world is as of Wednesday, 10th January, the kernel's = revison is >=20 > FreeBSD 12.0-CURRENT #0 r327871: Fri Jan 12 12:18:19 CET 2018 amd64. >=20 > I did, as a test, Friday, 12th Jan, as you can see, the last kernel = build. >=20 > The host in question also carries a variety of release, package an = jail builds > in separate source trees (CURRENT in most cases, to keep them away = from the > host's source tree). Those separate source trees also reject to build. >=20 > After performing a "make cleanworld" to startover (even this morning, = when I > watched LLVM/CLANG 6.0.0 has slipped in), I face still the same error: ... > -------------------------------------------------------------- >>>> stage 1.2: bootstrap tools > -------------------------------------------------------------- ... > Building = /usr/obj/usr/src/amd64.amd64/tmp/obj-tools/usr.bin/clang/llvm-tblgen/llvm-= tblgen > /usr/bin/ld: error: cannot open crt1.o: No such file or directory > c++: error: linker command failed with exit code 1 (use -v to see = invocation) If this happens during bootstrap-tools, the toolchain on your host system is busted. Do you have the following .o files in /usr/lib? Scrt1.o crt1.o crtbegin.o crtbeginS.o crtbeginT.o crtend.o crtendS.o crti.o crtn.o gcrt1.o If these are missing, restore them from a backup, or extract them from an installation image. -Dimitry --Apple-Mail=_CFBE0B21-3E5E-4F31-8A19-218C9849668A 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 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCWlxcNAAKCRCwXqMKLiCW o0FjAJ98e6HFFZq31m0f7Ju9JXl9xHy9kQCePTPeioMdCEb3h41jQnet57MljVk= =yJQR -----END PGP SIGNATURE----- --Apple-Mail=_CFBE0B21-3E5E-4F31-8A19-218C9849668A-- From owner-freebsd-current@freebsd.org Mon Jan 15 10:44:12 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AE90CE72739; Mon, 15 Jan 2018 10:44:12 +0000 (UTC) (envelope-from luca.pizzamiglio@gmail.com) Received: from mail-io0-f171.google.com (mail-io0-f171.google.com [209.85.223.171]) (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 7A0A26CB5C; Mon, 15 Jan 2018 10:44:11 +0000 (UTC) (envelope-from luca.pizzamiglio@gmail.com) Received: by mail-io0-f171.google.com with SMTP id t22so418762ioa.7; Mon, 15 Jan 2018 02:44:11 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Z+IQFhOHn2AZC+mGbXwmbFTbmATtkUjwKlVVb/WWCec=; b=rVzxsAJt2bfrz8g795bSasdkfudf3eJmigGt8K4biv2rftw/uVx4Vfx5CmVkEMZKbY UyozjZHcSxTWIvJuRJmOvli+5KZg82+yVqIqps1NegiDXvf10JfnZqQi1IjNXNxxTsQ+ VYOH8QjFsnJXcDA5aIXUK8mVvsumXwrOCMhED00Hey/KINNBHmu96/RDFwFAcw90QYZs MrFsp/VgkkyCGuea35LTUHoY/+dVqxAHMxGyQSLYMIuKEsOgc3VjlLYRDz2Zqg8FTdbT SJ5bDW/6VONUylZJKZEJa36+z8/DoLHcdx8P3QgJd8HJqmhPXPSBPpoeK9pl5zameF+E ImSQ== X-Gm-Message-State: AKwxyteKw6twtpuvkYiH6AOD+k0GpdYVnnjaDun29YiWNxC+rVpmwwV2 gKldn/3ZmHfKpPfOzHLh9ZWj4/Cv X-Google-Smtp-Source: ACJfBotx14+t+bAFQ+9qKKJsjT0CUjQtg4ip6fKUjsERQI7qfh8apFLFf2Zdb1MOGftHf9Si3VCuZw== X-Received: by 10.107.82.15 with SMTP id g15mr1689600iob.157.1516013045540; Mon, 15 Jan 2018 02:44:05 -0800 (PST) Received: from mail-io0-f182.google.com (mail-io0-f182.google.com. [209.85.223.182]) by smtp.gmail.com with ESMTPSA id t4sm5027013ita.27.2018.01.15.02.44.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 15 Jan 2018 02:44:05 -0800 (PST) Received: by mail-io0-f182.google.com with SMTP id c17so12634418iod.1; Mon, 15 Jan 2018 02:44:05 -0800 (PST) X-Received: by 10.107.51.149 with SMTP id z143mr489121ioz.287.1516013045069; Mon, 15 Jan 2018 02:44:05 -0800 (PST) MIME-Version: 1.0 Received: by 10.2.169.12 with HTTP; Mon, 15 Jan 2018 02:43:44 -0800 (PST) From: Luca Pizzamiglio Date: Mon, 15 Jan 2018 11:43:44 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: atomic in i386 Current after CLANG 6 upgrade To: FreeBSD Current , freebsd-ports@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: Mon, 15 Jan 2018 10:44:12 -0000 Hy all, I've already received a couple of messages from pkg-fallout about build failure on head-i386-default [1] [2] both pointing to the same errors, about missing intrinsic symbols related to __atomic_* The clang documentation about C11 atomic builtins [3] stats that __atomic_* are GCC extension and Clang provides them. It seems to me that this specific GCC-compatible builtin are enabled on amd64, but not on i386. Is there a way to enable GCC compatible __atomic_ builtin also on i386? Or should I provide patches to adopt _c11_atomic_* instead of __atomic_* for every ports that need it ? Thanks in advance! Best regards, pizzamg [1] http://beefy11.nyi.freebsd.org/data/head-i386-default/p458948_s327953/logs/librdkafka-0.11.3.log [2] http://beefy11.nyi.freebsd.org/data/head-i386-default/p458948_s327953/logs/stress-ng-0.09.09.log [3] https://clang.llvm.org/docs/LanguageExtensions.html#langext-c11-atomic From owner-freebsd-current@freebsd.org Mon Jan 15 11:27:08 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A6B8BE75CB4 for ; Mon, 15 Jan 2018 11:27:08 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 9252D6EE50 for ; Mon, 15 Jan 2018 11:27:08 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: by mailman.ysv.freebsd.org (Postfix) id 91A88E75CB3; Mon, 15 Jan 2018 11:27:08 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 914C7E75CB1 for ; Mon, 15 Jan 2018 11:27:08 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 573D36EE4F for ; Mon, 15 Jan 2018 11:27:07 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id 7679A2739D for ; Mon, 15 Jan 2018 11:27:06 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTPS id w0FBQo2b007205 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Mon, 15 Jan 2018 11:26:51 GMT (envelope-from phk@critter.freebsd.dk) Received: (from phk@localhost) by critter.freebsd.dk (8.15.2/8.15.2/Submit) id w0FBQoo7007204; Mon, 15 Jan 2018 11:26:50 GMT (envelope-from phk) To: current@freebsd.org Subject: Hooking RPi PWM driver into tree From: Poul-Henning Kamp MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <7202.1516015610.1@critter.freebsd.dk> Date: Mon, 15 Jan 2018 11:26:50 +0000 Message-ID: <7203.1516015610@critter.freebsd.dk> 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, 15 Jan 2018 11:27:08 -0000 I wrote a device driver for PWM on the RPi's, but I have not yet hooked it into the tree, because I'm unsure how we would want that. I personally think by default it should be a module which is only compiled for RPi kernels, but how does one do that ? (Needless to say, it should also be possible to compile it into the kernel for an RPi, but I know how to do that :-) And do we want it to live in sys/modules/rpi_pwm or sys/modules/rpi/pwm ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@freebsd.org Mon Jan 15 11:58:01 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 96217E77823; Mon, 15 Jan 2018 11:58:01 +0000 (UTC) (envelope-from tijl@freebsd.org) Received: from mailrelay106.isp.belgacom.be (mailrelay106.isp.belgacom.be [195.238.20.133]) (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 BF4087054A; Mon, 15 Jan 2018 11:58:00 +0000 (UTC) (envelope-from tijl@freebsd.org) X-Belgacom-Dynamic: yes IronPort-PHdr: =?us-ascii?q?9a23=3A5zIf5BJ/oCa/vLYM89mcpTZWNBhigK39O0sv0rFi?= =?us-ascii?q?tYgfLfzxwZ3uMQTl6Ol3ixeRBMOHs6sC07KempujcFRI2YyGvnEGfc4EfD4+ou?= =?us-ascii?q?JSoTYdBtWYA1bwNv/gYn9yNs1DUFh44yPzahANS47xaFLIv3K98yMZFAnhOgpp?= =?us-ascii?q?POT1HZPZg9iq2+yo9JDffxhEiCChbb9uMR67sRjfus4KjIV4N60/0AHJonxGe+?= =?us-ascii?q?RXwWNnO1eelAvi68mz4ZBu7T1et+ou+MBcX6r6eb84TaFDAzQ9L281/szrugLd?= =?us-ascii?q?QgaJ+3ART38ZkhtMAwjC8RH6QpL8uTb0u+ZhxCWXO9D9QKsqUjq+8ahkVB7oiD?= =?us-ascii?q?8GNzEn9mHXltdwh79frB64uhBz35LYbISTOfFjfK3SYMkaSHJPUMhRSSJPH4Cy?= =?us-ascii?q?YIkBD+UOIelWoJLwp0cMoBeiGQWgGP/jxiFOi3Tr3aM6yeMhEQTe0QI+HtIOsn?= =?us-ascii?q?DUp8jrOacVVuC117fHzTDZYPNQwjf29Y/FcgwgofGOWbJ9asrfyVMxGAzbk1ie?= =?us-ascii?q?tILrMymS1uQXvGiW9uxtXv+hhW4grgF+uDmvxsE0h4nHnIIa1E7L+j5iwIkoP9?= =?us-ascii?q?G4T1R7YdG8HJtUsyGaKY52TtklQ2FytyY3zKANt52jfCUSy5kr2gTTZ+KIfoWJ?= =?us-ascii?q?+B7vSeicLDliiH54dr+yiBC/+lW6xOLmTMm7ylNKozJAktnLq38CyQTe6tOCSv?= =?us-ascii?q?th5keh3iuP1xzL5uFEP080ka3bJoYiwrEqkpoTsEHDETHsmEXxlqOWakQk+uqs?= =?us-ascii?q?6+j9frrmoZicN5RqhQH7KKsunNe/Df4/MggUUGiX4eW81Lv98k3lWLhHjeA6nr?= =?us-ascii?q?PHvJ3VJMkXvLO1DgFb34o59hqyATir3MwdnXYdLVJFfByHj5LuO1HLOP34Efa/?= =?us-ascii?q?g1aokDpwyfDGJKPuDYvWIXjYjbjtZ7F961RTyAYr19BQ+4pUCq0dIPL0QkLxus?= =?us-ascii?q?bYAQEnPAOv2OboFcxx1psZWWKVHq+ZK7jfsVGS5u0xPeaDf5QVtyvnJ/gi/f7u?= =?us-ascii?q?gmczmUUBcqmxwZsXdHe4E+xoI0WDf3XjnMwOEXwXsQYnUOPqlUeCUSRNaHa0Q6?= =?us-ascii?q?Ix/T87CJi4AojdXY+tm6GO0D28Hp1MaWBMEkqMHmvwd4WYR/cMbzqfItdgkj0F?= =?us-ascii?q?VLmuUYoh1RChtALhxbpnNPTb9TMDupL4ydd5/erTlQs99W88M8PI93yGRilMn3?= =?us-ascii?q?EaTjo306R+pgQp0laRw6F9gvNwG8Ze6vlSXkE9L5GKnMJgDNWnZgPDep+iT1G9?= =?us-ascii?q?T9CvByp5Gs4wwdsmTVxwFv+ZolbExSX8UOxdrKCCGJFhqvGU5HP2Pcsoji+ejK?= =?us-ascii?q?Q=3D?= X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2AqAwDalVxa/4aF9lFdGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYNBVhB0FBOPK41oAQGCATIBmQ8vhRYChExDFQEBAQEBAQEBAQF?= =?us-ascii?q?qKII4JAGCRwEFOhwjEAsOCgklDyoeBhOKNwytFIozAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEhhDyFVYMugy8Eh2sFo2SIDI0ygQCCDZEQjT6LIzUjgVBMMAiCZwmET0A3AQE?= =?us-ascii?q?BAYw3AQEB?= X-IPAS-Result: =?us-ascii?q?A2AqAwDalVxa/4aF9lFdGQEBAQEBAQEBAQEBAQcBAQEBAYN?= =?us-ascii?q?BVhB0FBOPK41oAQGCATIBmQ8vhRYChExDFQEBAQEBAQEBAQFqKII4JAGCRwEFO?= =?us-ascii?q?hwjEAsOCgklDyoeBhOKNwytFIozAQEBAQEBAQEBAQEBAQEBAQEhhDyFVYMugy8?= =?us-ascii?q?Eh2sFo2SIDI0ygQCCDZEQjT6LIzUjgVBMMAiCZwmET0A3AQEBAYw3AQEB?= Received: from 134.133-246-81.adsl-dyn.isp.belgacom.be (HELO kalimero.tijl.coosemans.org) ([81.246.133.134]) by relay.skynet.be with ESMTP; 15 Jan 2018 12:57:56 +0100 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 w0FBvujt077981; Mon, 15 Jan 2018 12:57:56 +0100 (CET) (envelope-from tijl@FreeBSD.org) Date: Mon, 15 Jan 2018 12:57:56 +0100 From: Tijl Coosemans To: Luca Pizzamiglio Cc: FreeBSD Current , freebsd-ports@freebsd.org Subject: Re: atomic in i386 Current after CLANG 6 upgrade Message-ID: <20180115125756.37b803ba@kalimero.tijl.coosemans.org> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jan 2018 11:58:01 -0000 On Mon, 15 Jan 2018 11:43:44 +0100 Luca Pizzamiglio wrote: > I've already received a couple of messages from pkg-fallout about build > failure on head-i386-default [1] [2] both pointing to the same errors, > about missing intrinsic symbols related to __atomic_* > > The clang documentation about C11 atomic builtins [3] stats that __atomic_* > are GCC extension and Clang provides them. > > It seems to me that this specific GCC-compatible builtin are enabled on > amd64, but not on i386. > Is there a way to enable GCC compatible __atomic_ builtin also on i386? > Or should I provide patches to adopt _c11_atomic_* instead of __atomic_* > for every ports that need it ? > > [1] > http://beefy11.nyi.freebsd.org/data/head-i386-default/p458948_s327953/logs/librdkafka-0.11.3.log > [2] > http://beefy11.nyi.freebsd.org/data/head-i386-default/p458948_s327953/logs/stress-ng-0.09.09.log > [3] https://clang.llvm.org/docs/LanguageExtensions.html#langext-c11-atomic 8 byte atomics requires at least i586. So either find a way to disable the use of these atomics in these ports or add something like this to the port Makefile. .if ${ARCH} == i386 && ! ${MACHINE_CPU:Mi586} CFLAGS+= -march=i586 .endif From owner-freebsd-current@freebsd.org Mon Jan 15 12:21:33 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 70E8EE799DE for ; Mon, 15 Jan 2018 12:21:33 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E1C2771F24; Mon, 15 Jan 2018 12:21:31 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from freyja.zeit4.iv.bundesimmobilien.de ([87.138.105.249]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LzbXq-1exYfp1xje-014gzL; Mon, 15 Jan 2018 13:21:23 +0100 Date: Mon, 15 Jan 2018 13:21:22 +0100 From: "O. Hartmann" To: Dimitry Andric Cc: "O. Hartmann" , freebsd-current Subject: Re: CURRENT: can't buildworld; /usr/bin/ld: error: cannot open crt1.o: Message-ID: <20180115132116.0960cdfb@freyja.zeit4.iv.bundesimmobilien.de> In-Reply-To: <1C404258-502F-43D4-B88A-45BE6A90681F@FreeBSD.org> References: <20180115074244.72264055@freyja.zeit4.iv.bundesimmobilien.de> <1C404258-502F-43D4-B88A-45BE6A90681F@FreeBSD.org> Organization: Walstatt MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:SQmS6AljoOgrDE9qjGIvp6dvvY2c3Q+Zd+nVb6CIyUfGxNnZXYD MxB1YUedVqoheWv8ZB5v+9XOJSprgHTjuVDmkzK+IsUcjxnkrloSlH3LckJDBvwEBv0Qdga xsgKf65QJlTGr91XKKe9WglSYXEjjHCVWXgucX9K3DC6rp7nu96U6o9zPqWwAiLNrTjjgqr BB5GjNQvG8rdoYpOAH4eg== X-UI-Out-Filterresults: notjunk:1;V01:K0:59l0dV04kOI=:frljoNaG19tsBbagZzuHgC LM59tPincT/HOeFtaqG7BumXLKbue5nl0dwfoUP/nmdLtnuYeBLwnuFYz2uPtO6rGySSsYoFg 2WjRMyO7+B7vJyEd3Wcp+vkZLo6CSWzcBmHJEoAq2tiA9nLaYUUdl6uBppzergMHs6/+T5zWH 5V6qeqKNwU5yEz2VHLEV9k3tMXISbroEJStyemDulmWVqlMq6IMUgPoQEnuKnpzd8kGpHGqsE ZhsaXWgFujfXveDH3UTgqR+yIKIRJe3mNYx+UdIcyVMA56F/3MTlzfNKlfYbxczkNDZ1NsQul 1RjbUGgWhJedV4wreWgYnajNmKyN3/AijdLatrC97T3YBgpFKR1jLtuxP+5VKAP3mUREIqVDG tJsy7EoyME9GO+zUiNneXnHQlpCY3YzaxEOFkBGe3aFKd1AHIJDw9K9R7CVCuJP8Gwb20K4g+ mX197uW/qhbGCVkATZ0tghWzGklB756MPmwNrsZ1ceF4KeESQtCET4VmE7RgjutNfL5BMc8IP NBNURLvChY0q7FcRXjZvGnuvn5AZtt9ZBOE06YlrAAxHDQQpggA/miB2QTrHm/dIiKl8/BqCV nXC0GXWScKehqbVJLoUT+NqtXAda+CjDWh097sNvze+5Ce/Q1t2gKoQ/alv62fe1VA7KXwkCa McP71uteWgAFz48VMy3kzQKTIUb36Lz3a75wAXZGBUQQzgD+WIOFnkDpouf4bMfU3sLCs6pce b3RMkK6srbd0otm2/pZgrcVpZJVPb54Rlv8pEn5WvkirX1zNw8IcwlSne79r1GLphlXgHi1K1 uqBgrMPlpY2Ba8qNblk31pTGzScg32I2bPt9uh4Vdw0tRhahkY= X-Mailman-Approved-At: Mon, 15 Jan 2018 12:27:13 +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: Mon, 15 Jan 2018 12:21:33 -0000 On Mon, 15 Jan 2018 08:45:56 +0100 Dimitry Andric wrote: > On 15 Jan 2018, at 07:42, O. Hartmann wrote: > > > > One of our CURRENT boxes is repeateadly disobeying to build > > "buildworld" (make buildkernel seems to work as I did several kernels right > > now). > > > > The hosts's world is as of Wednesday, 10th January, the kernel's revison is > > > > FreeBSD 12.0-CURRENT #0 r327871: Fri Jan 12 12:18:19 CET 2018 amd64. > > > > I did, as a test, Friday, 12th Jan, as you can see, the last kernel build. > > > > The host in question also carries a variety of release, package an jail > > builds in separate source trees (CURRENT in most cases, to keep them away > > from the host's source tree). Those separate source trees also reject to > > build. > > > > After performing a "make cleanworld" to startover (even this morning, when I > > watched LLVM/CLANG 6.0.0 has slipped in), I face still the same error: > ... > > -------------------------------------------------------------- > >>>> stage 1.2: bootstrap tools > > -------------------------------------------------------------- > ... > > Building /usr/obj/usr/src/amd64.amd64/tmp/obj-tools/usr.bin/clang/llvm-tblgen/llvm-tblgen > > /usr/bin/ld: error: cannot open crt1.o: No such file or directory > > c++: error: linker command failed with exit code 1 (use -v to see > > invocation) > > If this happens during bootstrap-tools, the toolchain on your host > system is busted. Do you have the following .o files in /usr/lib? > > Scrt1.o > crt1.o > crtbegin.o > crtbeginS.o > crtbeginT.o > crtend.o > crtendS.o > crti.o > crtn.o > gcrt1.o > > If these are missing, restore them from a backup, or extract them from > an installation image. > > -Dimitry > # ll /usr/lib/Scrt1* /usr/lib/crt* /usr/lib/gcrt1.* 160561 -r--r--r-- 1 root wheel - 3.2K 10 Jan. 16:14 /usr/lib/Scrt1.o 161693 -r--r--r-- 1 root wheel - 2.2K 10 Jan. 16:14 /usr/lib/crtbegin.o 161696 -r--r--r-- 1 root wheel - 2.3K 10 Jan. 16:14 /usr/lib/crtbeginS.o 161695 -r--r--r-- 1 root wheel - 2.7K 10 Jan. 16:14 /usr/lib/crtbeginT.o 161694 -r--r--r-- 1 root wheel - 1.5K 10 Jan. 16:14 /usr/lib/crtend.o 161697 -r--r--r-- 1 root wheel - 1.5K 10 Jan. 16:14 /usr/lib/crtendS.o 160518 -r--r--r-- 1 root wheel - 800B 10 Jan. 16:14 /usr/lib/crti.o 160526 -r--r--r-- 1 root wheel - 896B 10 Jan. 16:14 /usr/lib/crtn.o 160565 -r--r--r-- 1 root wheel - 3.7K 10 Jan. 16:14 /usr/lib/gcrt1.o Something went wrong :-( Thank you for the hint, I try to recover from backup/image. Oliver From owner-freebsd-current@freebsd.org Mon Jan 15 13:58:43 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E0B3BE7EA74 for ; Mon, 15 Jan 2018 13:58:43 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5F03C75F8B; Mon, 15 Jan 2018 13:58:42 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from freyja.zeit4.iv.bundesimmobilien.de ([87.138.105.249]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MWgND-1eMX7B1TT9-00Xt3T; Mon, 15 Jan 2018 14:58:34 +0100 Date: Mon, 15 Jan 2018 14:58:33 +0100 From: "O. Hartmann" To: Dimitry Andric Cc: "O. Hartmann" , freebsd-current Subject: Re: CURRENT: can't buildworld; /usr/bin/ld: error: cannot open crt1.o: Message-ID: <20180115145833.43adfa28@freyja.zeit4.iv.bundesimmobilien.de> In-Reply-To: <20180115132116.0960cdfb@freyja.zeit4.iv.bundesimmobilien.de> References: <20180115074244.72264055@freyja.zeit4.iv.bundesimmobilien.de> <1C404258-502F-43D4-B88A-45BE6A90681F@FreeBSD.org> <20180115132116.0960cdfb@freyja.zeit4.iv.bundesimmobilien.de> Organization: Walstatt MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:wrPa9+YFQhW6nkK1zcuqUZf667wSeDoHbCr0N0a10piFTbfvjZl 1qrp16gMcBpZ9st1EjYZ67s32TlhpxkZndKxGTu5t3h1fyqmCJnGGLHjbXFLXq3NTPLGWzB Mn6E8cR8WKOdvOypHNmvNYL6uxAv6lIRzAhzYr7cw86iUCIekVQepTObKcrgxtKMGCUKo16 OQsVX/RAfnKXUi9kUT0qg== X-UI-Out-Filterresults: notjunk:1;V01:K0:UFUDhiTRtHA=:ssPUiLNnTH+3K7mc1To1N6 WwZLsWHadNDOD5tYJfBgkCqQLq08aOqiql201U/uxHPJjpy3b46CkLhY46G/ZFthttBWmi3YB IN/8MPuWFUprUx9Bbz4K8wFMLN/k89D14uppbq7rZTSqB7xN6QZE6ncwRo1Zw8hysT6PgtoT/ AumWzdVnD7PfZ8yOjD0w/qsokMzZbpVMOQmO+s906qGYptb4HlDYq+bjhAcEonkhnYMWXqcJb LYIzD8UE5/BRY8cUXgc0YZtSQzMkqVdGd/YnTGO3R4BhtGuVofYDH0RNhyYo0/sdNhMxfNSYy X41RaC8f7SDEF5Oqn6Dh5rMfkMe9pXRHSXa2FoSHtiIWy7w2wRFZ5g3J+JmaQb244zWn7WOuP PuLzDXojrQUo3iHnwWVUVdyIuKVnak0wELQSX5BySjtSmz1/QEv4RqgxyQUvWLao69BJG7MLf KQmGPFO3RVOKqdo6WGr1pFRjD+bmSK8IK59OvBzwNMoTuA1NtgZHoi6xl6di4x3dxr7t6rxRK x0z1oB1foCJ+A4BmC/RPLlyOdd9rJvGoOHX4QThe5kajzTsgQ0mOJ8set33Q1OFr29orUV4wj 77gT3E2KJfZob/JUbH40TBOMUrtjFT8CJrRFOqik5gJ52aKfmK1efpBNCf1y4sZMAYbW+tlGp Htvs3vTvSdkj65DfU75yZ3ofMWL6h+cXa7Z/ZXE927zu/O9e+dMBx0PNjespdlOmt+LpAsZI/ N8P6GAchuKUEQLfIZXKC8Q8jdNKSL9vOkMXCUXNqKX+IRosQMSUXcK+uYEqLH3jQ131c1JWZh q0hDjERELXBWS9f6OiAiFDTf9uKam0QUIyslmuSA+NfZMQHFRg= 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, 15 Jan 2018 13:58:44 -0000 On Mon, 15 Jan 2018 13:21:22 +0100 "O. Hartmann" wrote: > On Mon, 15 Jan 2018 08:45:56 +0100 > Dimitry Andric wrote: > > > On 15 Jan 2018, at 07:42, O. Hartmann wrote: > > > > > > One of our CURRENT boxes is repeateadly disobeying to build > > > "buildworld" (make buildkernel seems to work as I did several kernels > > > right now). > > > > > > The hosts's world is as of Wednesday, 10th January, the kernel's revison > > > is > > > > > > FreeBSD 12.0-CURRENT #0 r327871: Fri Jan 12 12:18:19 CET 2018 amd64. > > > > > > I did, as a test, Friday, 12th Jan, as you can see, the last kernel build. > > > > > > The host in question also carries a variety of release, package an jail > > > builds in separate source trees (CURRENT in most cases, to keep them away > > > from the host's source tree). Those separate source trees also reject to > > > build. > > > > > > After performing a "make cleanworld" to startover (even this morning, > > > when I watched LLVM/CLANG 6.0.0 has slipped in), I face still the same > > > error: > > ... > > > -------------------------------------------------------------- > > >>>> stage 1.2: bootstrap tools > > > -------------------------------------------------------------- > > ... > > > Building /usr/obj/usr/src/amd64.amd64/tmp/obj-tools/usr.bin/clang/llvm-tblgen/llvm-tblgen > > > /usr/bin/ld: error: cannot open crt1.o: No such file or directory > > > c++: error: linker command failed with exit code 1 (use -v to see > > > invocation) > > > > If this happens during bootstrap-tools, the toolchain on your host > > system is busted. Do you have the following .o files in /usr/lib? > > > > Scrt1.o > > crt1.o > > crtbegin.o > > crtbeginS.o > > crtbeginT.o > > crtend.o > > crtendS.o > > crti.o > > crtn.o > > gcrt1.o > > > > If these are missing, restore them from a backup, or extract them from > > an installation image. > > > > -Dimitry > > > > > # ll /usr/lib/Scrt1* /usr/lib/crt* /usr/lib/gcrt1.* > > 160561 -r--r--r-- 1 root wheel - 3.2K 10 Jan. 16:14 /usr/lib/Scrt1.o > 161693 -r--r--r-- 1 root wheel - 2.2K 10 Jan. 16:14 /usr/lib/crtbegin.o > 161696 -r--r--r-- 1 root wheel - 2.3K 10 Jan. 16:14 /usr/lib/crtbeginS.o > 161695 -r--r--r-- 1 root wheel - 2.7K 10 Jan. 16:14 /usr/lib/crtbeginT.o > 161694 -r--r--r-- 1 root wheel - 1.5K 10 Jan. 16:14 /usr/lib/crtend.o > 161697 -r--r--r-- 1 root wheel - 1.5K 10 Jan. 16:14 /usr/lib/crtendS.o > 160518 -r--r--r-- 1 root wheel - 800B 10 Jan. 16:14 /usr/lib/crti.o > 160526 -r--r--r-- 1 root wheel - 896B 10 Jan. 16:14 /usr/lib/crtn.o > 160565 -r--r--r-- 1 root wheel - 3.7K 10 Jan. 16:14 /usr/lib/gcrt1.o > > Something went wrong :-( > > Thank you for the hint, > I try to recover from backup/image. > > Oliver > _______________________________________________ > 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" Sorry for the hurry (I was in a hurry). As my listing indicates, crt1.o was missing. CURRENT does strange things lately. The same day I've updated the base system, luckily the jail for poudriere, based on the base system, has been updated and so I was able to restore /usr/lib/crt1.o. Oliver From owner-freebsd-current@freebsd.org Mon Jan 15 14:39:23 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 68B2CEA6C65 for ; Mon, 15 Jan 2018 14:39:23 +0000 (UTC) (envelope-from yuripv@icloud.com) Received: from pv33p00im-asmtp001.mac.com (pv33p00im-asmtp001.me.com [17.142.194.250]) (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 4B78778272 for ; Mon, 15 Jan 2018 14:39:23 +0000 (UTC) (envelope-from yuripv@icloud.com) Received: from process-dkim-sign-daemon.pv33p00im-asmtp001.me.com by pv33p00im-asmtp001.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) id <0P2L00400OAG3T00@pv33p00im-asmtp001.me.com> for freebsd-current@freebsd.org; Mon, 15 Jan 2018 14:38:58 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=icloud.com; s=04042017; t=1516027138; bh=sFjLpCN0tHmgydKZ7aZMyXU3J2s59nxZGwz3Gx0dU2Y=; h=To:From:Subject:Message-id:Date:MIME-version:Content-type; b=dwdIL8X6T7BnS0CLehhxgqWQWCVQqzeyK8LOl3X4JCA0rDU4GPxTRRR+KTCKnvGCr spnxkzGeWp3wZ1Nt9g+9zCcXrOGg/jwifRp95VvkFuN2cIwmih74cK1B0BPzASDGVC tsJWxhXN4V5FdJUhaL5aeVf5Tv+SCEVOB0bXfI/TAAIrFbuMShF+utH4gFFSPrccaN umrF1vCOWOF87QYeaILkFRXoIqgV4D9AOCnEK0rfZa4n3j8SahqqwPtALA/07OWvCd RA5ro0vBEg6a2SPBrp8ledLzVULy2JH4Kab1RHJEnVSJJ62O/vw6LHsRcw5S4eWXjn VCNvJnQNViRuA== Received: from icloud.com ([127.0.0.1]) by pv33p00im-asmtp001.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) with ESMTPSA id <0P2L0087ZQ0U3T00@pv33p00im-asmtp001.me.com> for freebsd-current@freebsd.org; Mon, 15 Jan 2018 14:38:57 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2018-01-15_08:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1011 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1801150209 To: freebsd-current From: Yuri Pankov Subject: inconsistent for() and while() behavior when using floating point Message-id: <6c423dbf-cd85-3c93-41e4-3362c06dfbb7@icloud.com> Date: Mon, 15 Jan 2018 17:38:54 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-version: 1.0 Content-type: text/plain; charset=utf-8; format=flowed Content-language: en-US Content-transfer-encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.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, 15 Jan 2018 14:39:23 -0000 Hi, Looking at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217149, I noticed that it isn't a seq(1) problem per se, rather for() and while() loops behaving inconsistently while using floating point, i.e.: double i; for (i = 1; i <= 2.00; i += 0.1) printf("%g\n", i); would produce: 1 ... 1.9 but: double i; for (i = 1; i <= 2; i += 0.2) printf("%g\n", i); would correctly end with 2: 1 ... 2 $ cc -v FreeBSD clang version 6.0.0 (branches/release_60 321788) (based on LLVM 6.0.0) Target: x86_64-unknown-freebsd12.0 Thread model: posix InstalledDir: /usr/bin though gcc 4.4.4 on illumos behaves the same. Is this a known problem with loops and floating point numbers? From owner-freebsd-current@freebsd.org Mon Jan 15 14:48:44 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0FF8FEA772C for ; Mon, 15 Jan 2018 14:48:44 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CBDF278DF0 for ; Mon, 15 Jan 2018 14:48:43 +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 3894826009E; Mon, 15 Jan 2018 15:48:41 +0100 (CET) Subject: Re: inconsistent for() and while() behavior when using floating point To: Yuri Pankov , freebsd-current References: <6c423dbf-cd85-3c93-41e4-3362c06dfbb7@icloud.com> From: Hans Petter Selasky Message-ID: <379d470c-480b-96d7-819b-873cc3100fc7@selasky.org> Date: Mon, 15 Jan 2018 15:45:51 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <6c423dbf-cd85-3c93-41e4-3362c06dfbb7@icloud.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.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, 15 Jan 2018 14:48:44 -0000 On 01/15/18 15:38, Yuri Pankov wrote: > Hi, > > Looking at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217149, I > noticed that it isn't a seq(1) problem per se, rather for() and while() > loops behaving inconsistently while using floating point, i.e.: > >         double i; > >         for (i = 1; i <= 2.00; i += 0.1) >                 printf("%g\n", i); > > would produce: > >         1 >         ... >         1.9 > > but: > >         double i; > >         for (i = 1; i <= 2; i += 0.2) >                 printf("%g\n", i); > > would correctly end with 2: > >         1 >         ... >         2 > Hi, The decimal value "0.2" is the same like the fraction "1/5", which cannot be represented by a float nor double without rounding error. The more times you iterate the bigger the error becomes. When you compare an integer with a float rounding happens. Check this out: if ((int)(float)0.999999999999999999999 >= (int)1) printf("OK\n"); Sequences using floating point should technically only use steps which can be written like this: "remainder * pow(2, -shift)". --HPS From owner-freebsd-current@freebsd.org Mon Jan 15 14:52:40 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 024BCEA7E09 for ; Mon, 15 Jan 2018 14:52:40 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BA80F795D9 for ; Mon, 15 Jan 2018 14:52:39 +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 59C8626009E; Mon, 15 Jan 2018 15:52:37 +0100 (CET) Subject: Re: inconsistent for() and while() behavior when using floating point From: Hans Petter Selasky To: Yuri Pankov , freebsd-current References: <6c423dbf-cd85-3c93-41e4-3362c06dfbb7@icloud.com> <379d470c-480b-96d7-819b-873cc3100fc7@selasky.org> Message-ID: Date: Mon, 15 Jan 2018 15:49:47 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <379d470c-480b-96d7-819b-873cc3100fc7@selasky.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jan 2018 14:52:40 -0000 Hi, The "seq" utility should use two 64-bit integers to represent the 10-base decimal number instead of float/double. And then you need to step this pair of integers. --HPS From owner-freebsd-current@freebsd.org Mon Jan 15 14:55:10 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 11A92EB2196 for ; Mon, 15 Jan 2018 14:55:10 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from theravensnest.org (xvm-110-62.dc2.ghst.net [46.226.110.62]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "theravensnest.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A6DD47990E for ; Mon, 15 Jan 2018 14:55:09 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from c124.sec.cl.cam.ac.uk (c124.sec.cl.cam.ac.uk [128.232.18.124]) (authenticated bits=0) by theravensnest.org (8.15.2/8.15.2) with ESMTPSA id w0FEt0lr060099 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 15 Jan 2018 14:55:00 GMT (envelope-from theraven@FreeBSD.org) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: inconsistent for() and while() behavior when using floating point From: David Chisnall In-Reply-To: Date: Mon, 15 Jan 2018 14:54:59 +0000 Cc: Yuri Pankov , freebsd-current Content-Transfer-Encoding: quoted-printable Message-Id: <3E349DFD-046F-46B2-A80B-5C19755CC3D4@FreeBSD.org> References: <6c423dbf-cd85-3c93-41e4-3362c06dfbb7@icloud.com> <379d470c-480b-96d7-819b-873cc3100fc7@selasky.org> To: Hans Petter Selasky X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jan 2018 14:55:10 -0000 On 15 Jan 2018, at 14:49, Hans Petter Selasky wrote: >=20 > The "seq" utility should use two 64-bit integers to represent the = 10-base decimal number instead of float/double. And then you need to = step this pair of integers. As the saying goes: > Sometimes, people think 'I have a problem and I will solve it with = floating point values' and then they have 1.99999999 problems. David From owner-freebsd-current@freebsd.org Mon Jan 15 15:40:08 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AFB2BEB54B8 for ; Mon, 15 Jan 2018 15:40:08 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 867827CD37 for ; Mon, 15 Jan 2018 15:40:08 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.ysv.freebsd.org (Postfix) id 85B0CEB54B4; Mon, 15 Jan 2018 15:40:08 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 855E0EB54B3 for ; Mon, 15 Jan 2018 15:40:08 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1BAEB7CD30 for ; Mon, 15 Jan 2018 15:40:08 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-wm0-x229.google.com with SMTP id 143so2642602wma.5 for ; Mon, 15 Jan 2018 07:40:08 -0800 (PST) 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=yc/7uGXCk8Z1VSNdx1tgpd/MIkDLj8HJbPeMeCq83JM=; b=jkv1R8xKgovlkUU7cVafLZ2pxsix2limU04tbfZ9wIpN10/N4oNAlxgTWtakVXU2z/ ODUmw38dlov1OlOAyRqOcDRUnM2ZU4Yq5D5hellGp28rtot6RidxHe7X2gN2Vj3IRoxq TSpvhjZDueQClDzQX84vMJDVBq7kNNUB/b6++lUOr4CoUtRqnWh61VMHu5LJ+K/5aBWF BP7Fw8JmEUtfZPyDSptECTLZSG0czQdI4MPZruQOEkLyKBcCmDDVyKEJlFwrADdAWXpU N1qxnO1182dylOSvri/didiqn/pdd/vHvXG74t9z4z4eXpXxSt453Y9u8HNFF4TqlF8O idWw== 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=yc/7uGXCk8Z1VSNdx1tgpd/MIkDLj8HJbPeMeCq83JM=; b=aa4g/q/c5o2IukmlGZEShfZdHMfleAHiLBJqwjI4Df6i2ibbXur5FgSMDVhofDZ2WW oVZ1nXixp4mH93Gwwf4AU/iSipTrCQdNrnHedCxhF/OwtMB7mwzr31WqqlPiEGGVyhXz Xx7j7EgRirYsXyiaKGDX0Lxs4FaIEFrG1bnWOndlSnciN/8VyL8llB3pZSBv6N9UOiGd +rqXYcw6FZFc7ysyBS7DKvZFLnUWkwtWJlrGrP8L9wABfx2hLn3TJ8j6ZBK94/v89Lmh NTI4ot3e3giYH9WPONHrEkXi7IDn9hvOv8PrLOOtFhZ01PiCdD0P1wfEejWa0UEKiEJl r7ZQ== X-Gm-Message-State: AKGB3mLd2lXmY2L5xvL/FTEglipUCwlU2QoAFfSnl73yK+jOUG1EJVk8 VRB1tFYWfQ2nNFljFMRVw/kIJEd1cjsj+kS1cOM6hQ== X-Google-Smtp-Source: ACJfBos4xfwnIRkvIkfTIajKRtKmwF+uSTGE4UkKD6RYtl/1brRyouaNUwZqDYArghCOZmoGXC6xlnff93wB89BlRnI= X-Received: by 10.80.190.9 with SMTP id a9mr48810171edi.258.1516030804641; Mon, 15 Jan 2018 07:40:04 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.80.195.88 with HTTP; Mon, 15 Jan 2018 07:40:04 -0800 (PST) X-Originating-IP: [50.253.99.174] In-Reply-To: <7203.1516015610@critter.freebsd.dk> References: <7203.1516015610@critter.freebsd.dk> From: Warner Losh Date: Mon, 15 Jan 2018 08:40:04 -0700 X-Google-Sender-Auth: z3uzzf6N1AYEGxyQcg2OmQgewko Message-ID: Subject: Re: Hooking RPi PWM driver into tree To: Poul-Henning Kamp Cc: FreeBSD Current 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: Mon, 15 Jan 2018 15:40:08 -0000 On Mon, Jan 15, 2018 at 4:26 AM, Poul-Henning Kamp wrote: > I wrote a device driver for PWM on the RPi's, but I have not yet > hooked it into the tree, because I'm unsure how we would want that. > > I personally think by default it should be a module which is > only compiled for RPi kernels, but how does one do that ? > We don't. We have no idea we're building for a particular kernel, so we don't subset the modules based on the kernel UNLESS the kernel config gives a list (MODULES_OVERRIDE). Compile it for armv[67] arm64 and we're fine (since those are the archs we have it for). Even this level of subsetting has grown painful, but there's not been a good fix for that yet either (and arguably, no bad fixes, just bad hacks that have grown up and proliferated to the point Something Must Be Done, but that turns out to be non-trivial to do in a way that doesn't replace one thicket of kludge with another :() In fact, on ARM, we've been moving to not building for specific boards, but having a GENERIC kernel that can be used everywhere. I'll be augmenting that with automatic driver loading based on the "plug and play" table data that's marked in the driver. (Needless to say, it should also be possible to compile it into the > kernel for an RPi, but I know how to do that :-) > Your best bet if you are creating a tiny distribution for this is to use MODULES_OVERRIDE in the kernel config so it's a module still, but not built into the kernel so you can load / unload as need arises. > And do we want it to live in sys/modules/rpi_pwm or sys/modules/rpi/pwm ? > Neither. rpi is just a board. It's really a pwm driver for the bcm family of SoC, so it should be called bcm_pwm. Any connections / configuration for rpi is handled via FDT, right? There's work underway to enumerate the modules you need on a system so one could automate the subsetting of the drivers (as well as the loading), but I'm not quite ready to turn that on end-to-end yet. The base infrastructure is there, we can find modules for unattached devices, but the have to have their ID tables (plug and play data) decorated appropriately. And that's taking a lot of doing. My goal is to be completely deployed by BSDcan. Warner From owner-freebsd-current@freebsd.org Mon Jan 15 15:52:56 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E4678EB6544 for ; Mon, 15 Jan 2018 15:52:56 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7736D7DA60 for ; Mon, 15 Jan 2018 15:52:56 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-wm0-x22c.google.com with SMTP id r78so2940054wme.0 for ; Mon, 15 Jan 2018 07:52:56 -0800 (PST) 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=KFmRWaurjkFJMFpyNwJxmgzzu812gsUTBXIad3uqG0k=; b=t50i70Bp3B8zsoY2ibUKOMnqntaRRTbpMRuHKv708O5d4OGGpromu7yLqSlkLds9yK zFOk9bvnrKaDyJwKxFakEbczOOGbhdAh5KsinAP/SDMnIv/6vS9GQM9mFpcjloK5vvmO 5n2WuaInvIq4cteiinDE12zOmnwmLxiW8YHZ5ZCdFkv/diWyhB3Te9q+mSjUAIb93wdM 1bh9k+IX2PaohiM4JVwHnhbS2KclHva+/g4b6C/4kkIUP6SAPE3Bi1wKpDnM/925zesQ /lOaq44LTAo0D55k/leLw5ZAoLYcdeLfQBIcHvy4x4nEPrAoiR7AMELJb0Ji81iYrMPB Ospw== 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=KFmRWaurjkFJMFpyNwJxmgzzu812gsUTBXIad3uqG0k=; b=aenpM2fHf0SQQlx0vUsBZlBP9XTKraRqf9+yXN9LaU9MKY+d0daeiLGTzre4fXt9Lt siB2rY6ZVPFxKl7IwEiLcZcbIkr/9ypxn0zUDpl/4U4u5x4kNy5ObiH9VHOtxSyQ+tRw lrhVYKPMQ/Ugw6Ugbf/VpJnDJ45OI9Xv1N9DjENIfcophQwmdahOx48DesrNhGThcK0C TE6tEN9lBeQPIbbJy0EUUHUoVZ09VIzs19BrYK3MaWrOSimh0RHnIm/bXhiZzJuP+/tu bYVqQ/nOBZ4HhtjgCkuBUZ+0cYzvh98hTGAccsjubt109zhlKXqsQVTWPazkQ6kup04D H3Iw== X-Gm-Message-State: AKwxytdStOc0lUcZ1f68AG9nw3+ErCM7jRhDJxJgVjyMCid89Cldo5EO bhZ3e2Is0ZnU7t9hIptpp37vdMSHEveIH0KdsCdM6g== X-Google-Smtp-Source: ACJfBosMdNJHT9B7xSVY+EmB//G8EwckyGlZWlcPCKUw5rkNqIT0AuMD5nZWYGLnmiP809EjY+NjcB8g8ft7veCuPWk= X-Received: by 10.80.130.2 with SMTP id 2mr17063436edf.7.1516031574748; Mon, 15 Jan 2018 07:52:54 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.80.195.88 with HTTP; Mon, 15 Jan 2018 07:52:54 -0800 (PST) X-Originating-IP: [50.253.99.174] In-Reply-To: <6c423dbf-cd85-3c93-41e4-3362c06dfbb7@icloud.com> References: <6c423dbf-cd85-3c93-41e4-3362c06dfbb7@icloud.com> From: Warner Losh Date: Mon, 15 Jan 2018 08:52:54 -0700 X-Google-Sender-Auth: M0v8U0rO1IxdQHWcpyEPoWx-gwY Message-ID: Subject: Re: inconsistent for() and while() behavior when using floating point To: Yuri Pankov Cc: freebsd-current 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: Mon, 15 Jan 2018 15:52:57 -0000 On Mon, Jan 15, 2018 at 7:38 AM, Yuri Pankov wrote: > Is this a known problem with loops and floating point numbers? > Yes. Many exact fractions in base-10 aren't exact in base-2, so you get accumulation of errors based on the tiny difference and see behavior like this. This is totally expected. You have to work around the problem using a computation method that doesn't accumulate errors. Warner From owner-freebsd-current@freebsd.org Mon Jan 15 16:55:24 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 15FBCEBA35B for ; Mon, 15 Jan 2018 16:55:24 +0000 (UTC) (envelope-from yuripv@icloud.com) Received: from pv33p00im-asmtp003.me.com (pv33p00im-asmtp003.me.com [17.142.194.252]) (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 EBA1980D83; Mon, 15 Jan 2018 16:55:23 +0000 (UTC) (envelope-from yuripv@icloud.com) Received: from process-dkim-sign-daemon.pv33p00im-asmtp003.me.com by pv33p00im-asmtp003.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) id <0P2L00J00T1V9T00@pv33p00im-asmtp003.me.com>; Mon, 15 Jan 2018 15:54:58 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=icloud.com; s=04042017; t=1516031698; bh=ZYUQT3ux/rNdIwj82V1oyCIHrUOOD8ULuwsCQccfqqk=; h=Subject:To:From:Message-id:Date:MIME-version:Content-type; b=jdgOT9sKdlSv9aEo9/0AstvHvQsSvoFDbDGT1TmO1iCSajrrXL5NZobQGNVcOzN7f 3JWNIFFzWQPdMyUpS1OFw0gWMYjGweyOF3E2dcr1Jbiyot+M3V9ma2jBql1hkpqQF0 8tjySvunikk8eULDBnLv9XmWsSTczthtry93GyNONS64MzRjG9Gnzp0RqfvJMcEW7Q C2Gi6dl4xm65tvWAPn1HfUTQUsQHxhWBIZkaWxsR/78Eafi0NF2qbuzLS1VLzr65Jv pdwpiMRP3/awi54JMJDgmEHxosQj37T/2lXmuQ1k3zAt+UHQBhWP0ORyzEKuqFxBHp ZACvkBohgm5FA== Received: from icloud.com ([127.0.0.1]) by pv33p00im-asmtp003.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) with ESMTPSA id <0P2L003QLTJH7G00@pv33p00im-asmtp003.me.com>; Mon, 15 Jan 2018 15:54:57 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2018-01-15_08:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1011 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1801150227 Subject: Re: inconsistent for() and while() behavior when using floating point To: David Chisnall , Hans Petter Selasky Cc: freebsd-current References: <6c423dbf-cd85-3c93-41e4-3362c06dfbb7@icloud.com> <379d470c-480b-96d7-819b-873cc3100fc7@selasky.org> <3E349DFD-046F-46B2-A80B-5C19755CC3D4@FreeBSD.org> From: Yuri Pankov Message-id: <0b310384-819d-292c-f407-9ab73f6c4ec9@icloud.com> Date: Mon, 15 Jan 2018 18:54:54 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-version: 1.0 In-reply-to: <3E349DFD-046F-46B2-A80B-5C19755CC3D4@FreeBSD.org> Content-type: text/plain; charset=utf-8; format=flowed Content-language: en-US Content-transfer-encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jan 2018 16:55:24 -0000 On Mon, Jan 15, 2018 at 02:54:59PM +0000, David Chisnall: > On 15 Jan 2018, at 14:49, Hans Petter Selasky wrote: >> >> The "seq" utility should use two 64-bit integers to represent the 10-base decimal number instead of float/double. And then you need to step this pair of integers. Thanks for the hint! > As the saying goes: > >> Sometimes, people think 'I have a problem and I will solve it with floating point values' and then they have 1.99999999 problems. Well, seq(1) is about floating numbers, so at least initially using them internally would seem correct, though reading your replies I now understand it's not :-) From owner-freebsd-current@freebsd.org Mon Jan 15 17:00:17 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 297DFEBAC1F; Mon, 15 Jan 2018 17:00:17 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0A99F813D1; Mon, 15 Jan 2018 17:00:17 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1354) id 587838AEA; Mon, 15 Jan 2018 17:00:16 +0000 (UTC) From: Jan Beich To: Tijl Coosemans Cc: Luca Pizzamiglio , FreeBSD Current , freebsd-ports@freebsd.org Subject: Re: atomic in i386 Current after CLANG 6 upgrade References: <20180115125756.37b803ba@kalimero.tijl.coosemans.org> Date: Mon, 15 Jan 2018 18:00:11 +0100 In-Reply-To: <20180115125756.37b803ba@kalimero.tijl.coosemans.org> (Tijl Coosemans's message of "Mon, 15 Jan 2018 12:57:56 +0100") Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jan 2018 17:00:17 -0000 Tijl Coosemans writes: > On Mon, 15 Jan 2018 11:43:44 +0100 Luca Pizzamiglio wrote: > >> I've already received a couple of messages from pkg-fallout about build >> failure on head-i386-default [1] [2] both pointing to the same errors, >> about missing intrinsic symbols related to __atomic_* >> >> The clang documentation about C11 atomic builtins [3] stats that __atomic_* >> are GCC extension and Clang provides them. >> >> It seems to me that this specific GCC-compatible builtin are enabled on >> amd64, but not on i386. >> Is there a way to enable GCC compatible __atomic_ builtin also on i386? >> Or should I provide patches to adopt _c11_atomic_* instead of __atomic_* >> for every ports that need it ? >> >> [1] >> http://beefy11.nyi.freebsd.org/data/head-i386-default/p458948_s327953/logs/librdkafka-0.11.3.log >> [2] >> http://beefy11.nyi.freebsd.org/data/head-i386-default/p458948_s327953/logs/stress-ng-0.09.09.log >> [3] https://clang.llvm.org/docs/LanguageExtensions.html#langext-c11-atomic > > 8 byte atomics requires at least i586. So either find a way to disable > the use of these atomics in these ports or add something like this to > the port Makefile. > > .if ${ARCH} == i386 && ! ${MACHINE_CPU:Mi586} > CFLAGS+= -march=i586 > .endif It wouldn't help (see below). Clang 6 accidentally made __atomic* work enough to satisfy configure check but not for the port to build. I guess, it also confuses configure in net/librdkafka and net-mgmt/netdata. $ cat a.c #include typedef struct { uint64_t val64; } atomic_t; int main() { uint64_t foo; atomic_t bar; #ifdef ATOMIC_STRUCT __atomic_fetch_add(&bar.val64, 1, __ATOMIC_RELAXED); #else __atomic_fetch_add(&foo, 1, __ATOMIC_RELAXED); #endif return 0; } $ cc -m32 -march=i586 a.c $ clang50 -m32 -march=i586 a.c /tmp/a-560ad1.o: In function `main': a.c:(.text+0x46): undefined reference to `__atomic_fetch_add_8' clang-5.0: error: linker command failed with exit code 1 (use -v to see invocation) $ cc -m32 -DATOMIC_STRUCT -march=i586 a.c /usr/bin/ld: error: undefined symbol: __atomic_fetch_add_8 >>> referenced by a.c >>> /tmp/a-ad8c36.o:(main) cc: error: linker command failed with exit code 1 (use -v to see invocation) $ clang50 -m32 -DATOMIC_STRUCT -march=i586 a.c /tmp/a-0fbfd0.o: In function `main': a.c:(.text+0x46): undefined reference to `__atomic_fetch_add_8' clang-5.0: error: linker command failed with exit code 1 (use -v to see invocation) From owner-freebsd-current@freebsd.org Mon Jan 15 17:09:03 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DC7FDEBB91F; Mon, 15 Jan 2018 17:09:03 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from theravensnest.org (xvm-110-62.dc2.ghst.net [46.226.110.62]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "theravensnest.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 71AA381F6E; Mon, 15 Jan 2018 17:09:02 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from c124.sec.cl.cam.ac.uk (c124.sec.cl.cam.ac.uk [128.232.18.124]) (authenticated bits=0) by theravensnest.org (8.15.2/8.15.2) with ESMTPSA id w0FH8x7k063002 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 15 Jan 2018 17:08:59 GMT (envelope-from theraven@FreeBSD.org) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: atomic in i386 Current after CLANG 6 upgrade From: David Chisnall In-Reply-To: Date: Mon, 15 Jan 2018 17:08:58 +0000 Cc: Tijl Coosemans , Luca Pizzamiglio , FreeBSD Current , freebsd-ports@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <03DDFE7A-B5FE-4DE5-98D8-AF28EFDDFACF@FreeBSD.org> References: <20180115125756.37b803ba@kalimero.tijl.coosemans.org> To: Jan Beich , Ed Maste X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jan 2018 17:09:04 -0000 On 15 Jan 2018, at 17:00, Jan Beich wrote: >=20 > It wouldn't help (see below). Clang 6 accidentally made __atomic* work > enough to satisfy configure check but not for the port to build. I = guess, > it also confuses configure in net/librdkafka and net-mgmt/netdata. >=20 Can we (by which I probably mean emaste@) push out an EN that adds the = atomic.c from compiler-rt to our libgcc_s? That should provide all of = these helper functions. Clang assumes that they exist because both = compiler-rt and vaguely recent libgcc_s provide them. Recent GCC will = also assume that they exist and so the correct fix is probably for us to = make them to exist. If this is difficult, then we can perhaps provide a port that compiles = atomic.c into libatomic_fudge.so or similar and provides a libgcc_s.so = that=E2=80=99s a linker script that forces linking to libatomic_fudge.so = and libgcc_s.so. David From owner-freebsd-current@freebsd.org Mon Jan 15 17:11:37 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 41F9DEBBBC2 for ; Mon, 15 Jan 2018 17:11:37 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x22c.google.com (mail-it0-x22c.google.com [IPv6:2607:f8b0:4001:c0b::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AC96B82210 for ; Mon, 15 Jan 2018 17:11:36 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x22c.google.com with SMTP id b77so1657261itd.0 for ; Mon, 15 Jan 2018 09:11:36 -0800 (PST) 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=Fm+fFaeYz1VLNqbMd17nRBVrKQHy6Veqlve/VquA+HQ=; b=XHJHm8AYjnUdcCuw5O4bTM3OEBkRDlhAmPVUdUjUf1ergTU3XtX3QzuEijwR9SECpa lesSGDhopX1+4d7ovtTZpfM0GGHMYsye4f4EYUxF3K1YgNED3uMe3JK7QIiz1gk4SiTG nRBR6oTHT0aT/G3G8lpS8b5Bc4tEOvCcZAo/sXOftVzqQcnMiAXcOL8F8lf1Aqn4yG7l TV8x6IJV+gET+9gdfuX30/wOtGxmTAsuqWeQTeMvbEPNohnZ00b4AYZMCeuGkyZ/fC5w TEwETRzZpA/JdWF5IaR4DlJ2T/7OsZRVi1ZPINloNim8QepERWZhirSWpHN6zVTpnkNs wUKg== 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=Fm+fFaeYz1VLNqbMd17nRBVrKQHy6Veqlve/VquA+HQ=; b=PJOFaqfF6X4gtqXfQog+p4B9kGpg80cMPH15eV7LtJQSanGLc9cWjXnRu3jR9RmLZy Y+1jTYqWv5AyKmqLAlcYxaWw8UWbI56cv0tDCJBWJ9d3Ok5bHSiDaTk3dRNbV4XjcpiJ 7cmUz5LISQTKi1FTA6uIWC+mHywKuPgH7DXvIKpf8/PMjQEq4VDzCdW1Zk6QUR4gE0vn UrPLLu+0MoF0FEpV7TfcHihfbYjWPMiTdUaxIoZyPa2ZycsqLTLqxCRuyCDFJ/A2Pi3a RpQjr/Iu6/gO17AK8XwNRpUaRZjXYItrJHx7EHD2lYbSHXh5sdeuS8iwILx/jHEpHng2 r7zw== X-Gm-Message-State: AKwxytfQiNYCYVR3+u0jMhUdlxA5gVU+k/3ZDfn/n64ObD0tdM+btKY/ ZSghaRPgcU2lAGL8sOeU2LGCpEGDZDfjGQeCWl+DTw== X-Google-Smtp-Source: ACJfBouMrXBdhKX0qa3CtAKuWEiyM7gZvS+BP6KBLS2QWnGAasaFzYahuKD496NTQ+zRHSL8n/3KiKuSpjA/81+PQwc= X-Received: by 10.36.104.210 with SMTP id v201mr13878009itb.64.1516036295701; Mon, 15 Jan 2018 09:11:35 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.199.131 with HTTP; Mon, 15 Jan 2018 09:11:34 -0800 (PST) X-Originating-IP: [50.253.99.174] In-Reply-To: <03DDFE7A-B5FE-4DE5-98D8-AF28EFDDFACF@FreeBSD.org> References: <20180115125756.37b803ba@kalimero.tijl.coosemans.org> <03DDFE7A-B5FE-4DE5-98D8-AF28EFDDFACF@FreeBSD.org> From: Warner Losh Date: Mon, 15 Jan 2018 10:11:34 -0700 X-Google-Sender-Auth: qJg9d7K90BeEKTIKjHKgaxMwQ6w Message-ID: Subject: Re: atomic in i386 Current after CLANG 6 upgrade To: David Chisnall Cc: Jan Beich , Ed Maste , Tijl Coosemans , Luca Pizzamiglio , FreeBSD Current , FreeBSD Ports 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: Mon, 15 Jan 2018 17:11:37 -0000 On Mon, Jan 15, 2018 at 10:08 AM, David Chisnall wrote: > On 15 Jan 2018, at 17:00, Jan Beich wrote: > > > > It wouldn't help (see below). Clang 6 accidentally made __atomic* work > > enough to satisfy configure check but not for the port to build. I gues= s, > > it also confuses configure in net/librdkafka and net-mgmt/netdata. > > > > Can we (by which I probably mean emaste@) push out an EN that adds the > atomic.c from compiler-rt to our libgcc_s? That should provide all of > these helper functions. Clang assumes that they exist because both > compiler-rt and vaguely recent libgcc_s provide them. Recent GCC will al= so > assume that they exist and so the correct fix is probably for us to make > them to exist. > > If this is difficult, then we can perhaps provide a port that compiles > atomic.c into libatomic_fudge.so or similar and provides a libgcc_s.so > that=E2=80=99s a linker script that forces linking to libatomic_fudge.so = and > libgcc_s.so. > So far clang 6 is just in -current. Let's at least get them there first before we talk about ENs :) Warner From owner-freebsd-current@freebsd.org Mon Jan 15 17:26:43 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 64047EBCBA6 for ; Mon, 15 Jan 2018 17:26:43 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 35ECE83AA7 for ; Mon, 15 Jan 2018 17:26:43 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.26] (cpe-23-242-94-236.socal.res.rr.com [23.242.94.236]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 8bba2b73 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO for ; Mon, 15 Jan 2018 09:26:16 -0800 (PST) To: freebsd-current@freebsd.org From: Pete Wright Subject: Kernel Panic On Boot after r327979 Message-ID: Date: Mon, 15 Jan 2018 09:26:40 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.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, 15 Jan 2018 17:26:43 -0000 Hello, I updated an amd64 system last night to r327979 and it panics into gdb after rc attempts to mount local filesystems. The panic line is: Fatal trap 12: page fault while in kernel mode gdb states that it stopped at: Stopped at    prison_allow+0x4    movq    0x30(%rdi),%rax Is this a known issue?  This is my primary workstation - so I'm going to revert back to an older kernel, but if more info is needed I can put some cycles into debugging today. Cheers! -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Mon Jan 15 17:37:50 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7927EEBD725; Mon, 15 Jan 2018 17:37:50 +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 3AC78A5E; Mon, 15 Jan 2018 17:37:49 +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 4123147464; Mon, 15 Jan 2018 18:37:47 +0100 (CET) From: Dimitry Andric Message-Id: <85AE8E52-FC6C-4522-B5B1-7423A163DDFE@FreeBSD.org> Content-Type: multipart/signed; boundary="Apple-Mail=_27AEB962-99CF-4F1E-B6E5-78994B427340"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: atomic in i386 Current after CLANG 6 upgrade Date: Mon, 15 Jan 2018 18:37:47 +0100 In-Reply-To: Cc: FreeBSD Current , FreeBSD Ports , Ed Maste To: Luca Pizzamiglio References: X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jan 2018 17:37:50 -0000 --Apple-Mail=_27AEB962-99CF-4F1E-B6E5-78994B427340 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii On 15 Jan 2018, at 11:43, Luca Pizzamiglio wrote: > > I've already received a couple of messages from pkg-fallout about build > failure on head-i386-default [1] [2] both pointing to the same errors, > about missing intrinsic symbols related to __atomic_* > > The clang documentation about C11 atomic builtins [3] stats that __atomic_* > are GCC extension and Clang provides them. > > It seems to me that this specific GCC-compatible builtin are enabled on > amd64, but not on i386. > Is there a way to enable GCC compatible __atomic_ builtin also on i386? > Or should I provide patches to adopt _c11_atomic_* instead of __atomic_* > for every ports that need it ? There is some strangeness going on with an upstream bug fix [1], which has the unintended side effect of sometimes emitting libcalls to __atomic functions that we do not have on i386. I've commented on the upstream bug report, but I do not know an easy workaround at this point. -Dimitry [1] https://bugs.llvm.org/show_bug.cgi?id=34347 --Apple-Mail=_27AEB962-99CF-4F1E-B6E5-78994B427340 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 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCWlzm6wAKCRCwXqMKLiCW ozAWAJwME/2Ru4INV79uICryq3N6LHRnPACdF/rC1d4UyUc5q/vePu0Am4fZNpE= =Ebo4 -----END PGP SIGNATURE----- --Apple-Mail=_27AEB962-99CF-4F1E-B6E5-78994B427340-- From owner-freebsd-current@freebsd.org Mon Jan 15 17:38:16 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ADD61EBD809 for ; Mon, 15 Jan 2018 17:38:16 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-ot0-x236.google.com (mail-ot0-x236.google.com [IPv6:2607:f8b0:4003:c0f::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49448C3A for ; Mon, 15 Jan 2018 17:38:16 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: by mail-ot0-x236.google.com with SMTP id p36so3239890otd.10 for ; Mon, 15 Jan 2018 09:38:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=BGxLXkogBFNk40ia3Zsr3iWOjvITpFCi3PaSUoNjC8A=; b=fJWtv8qhyp+Dg1n2gb7SbNf3mdc44BBwU2M8pZlXAekV8XE8jvuNFXY1AEq9Mn6S8S wJodpyYWymJk8dMLOWgoKfCZjZozO6fjZJpdkzDCBxOERTzidgZ7Y0ShfkBl38+JpPR2 opZGby6gQcxw6FJdeFUM60UgCOdAFcJs4ZJT0q1hYo05C6MmWn3hX39VV4lobYHcxHdL 3Cy3Hkm5I880a2GMebSbG90Ahfn3T9b7+3T1gBsByEIKRXd7Fi31qSwWGH9oGRaARr3L NCnwyauxc1jh2+BKGmEacBw1WAXUAl/d6VyZndrLHAzKLGTlujUXB7898Gu7tay79jzs Eh4g== 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=BGxLXkogBFNk40ia3Zsr3iWOjvITpFCi3PaSUoNjC8A=; b=jTq2AKcn+c1qFEkV2LOZtAMm92OQmlUlLdk3KmAJ6N+9mtO94bk/csq/0cP1SnG/Jg KKio97JeCZcE9BnWgEvsjpBoahV24qzWc8SR2nZZKb2DX99ue9+t13EUEcVfVMOaWXOW thAjtPZPpqf915iYoXx7TD0J3QFXXEesQFl6x8wzMAA+DZh8NPnGK9mLwf5XPPxCRuWg 3TlwhjLvYJchx4ctm/Y+iskx5spDRTdgNT3InUgbKmh94Abp6W2LzQyhdeivtqgEhiyE ydvI9xp8XYuFNNN1IymLa/zw0YDCcm3fdQ/MWRfwMhPAd7AANOOrho2Qc9u8M9lgu5+U ugtg== X-Gm-Message-State: AKwxytdSpWGo4Gu7E6TM0VszhdN3+LhOk54ge3OqvZxl2eWetQ19mn/G vDGoJAuJEL8TuFCMTy/KtDiTnIzxLgLppO2kzD4= X-Google-Smtp-Source: ACJfBouFHYNPmBvOXdsMtQcwU2W5PW39ObUZ/2tD/Ye8Mf+uXFIGkC7/vr7jkonAhft8NtO6YTSgw4e2tWnCSoTjIRY= X-Received: by 10.157.82.96 with SMTP id q32mr8818724otg.376.1516037895575; Mon, 15 Jan 2018 09:38:15 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.0.2 with HTTP; Mon, 15 Jan 2018 09:38:15 -0800 (PST) In-Reply-To: <6c423dbf-cd85-3c93-41e4-3362c06dfbb7@icloud.com> References: <6c423dbf-cd85-3c93-41e4-3362c06dfbb7@icloud.com> From: Mehmet Erol Sanliturk Date: Mon, 15 Jan 2018 20:38:15 +0300 Message-ID: Subject: Re: inconsistent for() and while() behavior when using floating point To: Yuri Pankov Cc: freebsd-current 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: Mon, 15 Jan 2018 17:38:16 -0000 On Mon, Jan 15, 2018 at 5:38 PM, Yuri Pankov wrote: > Hi, > > Looking at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217149, I > noticed that it isn't a seq(1) problem per se, rather for() and while() > loops behaving inconsistently while using floating point, i.e.: > > double i; > > for (i = 1; i <= 2.00; i += 0.1) > printf("%g\n", i); > > would produce: > > 1 > ... > 1.9 > > but: > > double i; > > for (i = 1; i <= 2; i += 0.2) > printf("%g\n", i); > > would correctly end with 2: > > 1 > ... > 2 > > $ cc -v > FreeBSD clang version 6.0.0 (branches/release_60 321788) (based on LLVM > 6.0.0) > Target: x86_64-unknown-freebsd12.0 > Thread model: posix > InstalledDir: /usr/bin > > though gcc 4.4.4 on illumos behaves the same. > > Is this a known problem with loops and floating point numbers? > _______________________________________________ > When you perform floating point computations , it may be useful to remember that , the last bits of floating point numbers may be considered to be "noise" . For that reason , the same "for" or "while" loops may behave differently in different times and places . To make floating point related loops more deterministic , the useful steps may be to compute "step size" and "number of steps" , and use integer variables for counting loop steps with multiplication of "loop counter" and "step size" during loop steps : For floating point loop counter T = "integer loop counter" * "step size" . A statement like T = T + "step size" will/may produce wrong results if number of steps is sufficiently large . Computer arithmetic and theoretical arithmetic are not the same . For example , addition is not associative in computer arithmetic : a + ( b + c ) is not always equal to ( a + b ) + c . Mehmet Erol Sanliturk From owner-freebsd-current@freebsd.org Mon Jan 15 17:53:00 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2AD49EBE50F; Mon, 15 Jan 2018 17:53:00 +0000 (UTC) (envelope-from tijl@freebsd.org) Received: from mailrelay111.isp.belgacom.be (mailrelay111.isp.belgacom.be [195.238.20.138]) (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 850801C1F; Mon, 15 Jan 2018 17:52:58 +0000 (UTC) (envelope-from tijl@freebsd.org) X-Belgacom-Dynamic: yes IronPort-PHdr: =?us-ascii?q?9a23=3AfezAvhMMq/S4828L+84l6mtUPXoX/o7sNwtQ0KIM?= =?us-ascii?q?zox0K/z8p8bcNUDSrc9gkEXOFd2Cra4c0qyO6+jJYi8p2d65qncMcZhBBVcuqP?= =?us-ascii?q?49uEgeOvODElDxN/XwbiY3T4xoXV5h+GynYwAOQJ6tL1LdrWev4jEMBx7xKRR6?= =?us-ascii?q?JvjvGo7Vks+7y/2+94fcbglUmTaxe69+IAmrpgjNq8cahpdvJLwswRXTuHtIfO?= =?us-ascii?q?pWxWJsJV2Nmhv3+9m98p1+/SlOovwt78FPX7n0cKQ+VrxYES8pM3sp683xtBnM?= =?us-ascii?q?VhWA630BWWgLiBVIAgzF7BbnXpfttybxq+Rw1DWGMcDwULs5Qiqp4bt1RxD0iS?= =?us-ascii?q?cHLz85/3/Risxsl6JQvRatqwViz4LIfI2ZMfxzdb7fc9wHX2pMRshfWSxfDI2h?= =?us-ascii?q?bIUADeQBMulEoIfyvFYOsQK+CRWwCO/z1jNFhHn71rA63eQ7FgHG2RQtEcwPsH?= =?us-ascii?q?TWqNX+KbkfUeeyzKnT0zrDaulZ2THm6IPVdR0hvfCMXbB0ccfKyUcvDR3KgUuN?= =?us-ascii?q?pIL4MT2ZzOMNs3KU7+d5U++klm0pqxlprzWs28sgkJfFi40Ux1ze6Cl0zog4Kc?= =?us-ascii?q?elREN1btOpFoZbuTuAOItsWMwiRnlluCM9yrIbp5G2ZDMKyJE7xx7HbPyHbpSI?= =?us-ascii?q?7grjVOmPJTd4g2poeLGliBa28Eigz/PzVtOz0FpQsipFk9vMtnQX2xPP7ciHTe?= =?us-ascii?q?B98Vmk2TmV0QDT8ftIIUcularUM5Ihw7gwmYQPsUnbHSL6hV/6gLGZe0gl4OSk?= =?us-ascii?q?9urqb7v8qpOBOYJ5hRnyMqE0lcy+BeQ4PBIOX2+e+emkyL3j/E/5QLFRg/04iK?= =?us-ascii?q?nWro7VKt8ApqGkGQNV1Zwj6xmnAze8zNsYhWUHLE5CeB+fgYjpIU/BL+7jAvek?= =?us-ascii?q?nlugiS9rx/fcPr39GZXANXbDkK3/crlj8EFc0xc8wcpY55JOBbELOOjzVVPptN?= =?us-ascii?q?zEEh85NBS5w+j9CNpjyIwRQnmPDbKAPKzOrF+I/PgvLPeKZI8Jozv9JeIl6ODw?= =?us-ascii?q?gnAigl8SYLOl3ZwNaHC3Bv5mOVmWYWLwgtcdFmcHphI+TO3riVyDSzFTYneyX6?= =?us-ascii?q?0n6zE1EoKpE5nMSZu2gLOcxiu7GYdWZm9eAFCWDXjob5mEW+sLaC+KPMBhlyYL?= =?us-ascii?q?VaO9S4A/zhyuuhX6xKR5IeXP4S0XqIjv1N9v5+3cjRsy7yB7D9yB02GRSGF5hm?= =?us-ascii?q?EISCQo06B+vUN9ykyO0aZig/NGC9Nc/OhJXRogOZ7b1ex6BMj4WhjdcdeRVFam?= =?us-ascii?q?XtKmDCktTtIx3dAOeVxyG8u8gRDFxCeqDaUVmKKVC5Mv6aLTwmL9J8Fny3bJh+?= =?us-ascii?q?EdiAwKS9VOOSWNhq9k8QHXA8adj0WUja+0eKI08jTA+U244SyJpk4OAyBqVqCQ?= =?us-ascii?q?YXEdYgP9qtPi60bLSaTmXagmMA9p59SPJ4FxRpvul1oQF6SrA8jXf2/kwzT4Ph?= =?us-ascii?q?2P3L7ZKdOyI2g=3D?= X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2DHBABL6Vxa/4aF9lFdGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYNBVhB0FBOEE4sYjWoBAYIBMgGZDymFHAKEUEQUAQEBAQEBAQE?= =?us-ascii?q?BAWoogjgkAYJHAQUjMyMQCw4KAgIFIQICDyoeBhOKN6l+gieJSQEBAQEBBQEBA?= =?us-ascii?q?QEBI4EPjDCDLwSBb4MXgmUFo2SIDI0ygQCTHZhhNiKBUEwwCIJnCYRPQDeNDAE?= =?us-ascii?q?BAQ?= X-IPAS-Result: =?us-ascii?q?A2DHBABL6Vxa/4aF9lFdGQEBAQEBAQEBAQEBAQcBAQEBAYN?= =?us-ascii?q?BVhB0FBOEE4sYjWoBAYIBMgGZDymFHAKEUEQUAQEBAQEBAQEBAWoogjgkAYJHA?= =?us-ascii?q?QUjMyMQCw4KAgIFIQICDyoeBhOKN6l+gieJSQEBAQEBBQEBAQEBI4EPjDCDLwS?= =?us-ascii?q?Bb4MXgmUFo2SIDI0ygQCTHZhhNiKBUEwwCIJnCYRPQDeNDAEBAQ?= Received: from 134.133-246-81.adsl-dyn.isp.belgacom.be (HELO kalimero.tijl.coosemans.org) ([81.246.133.134]) by relay.skynet.be with ESMTP; 15 Jan 2018 18:51:43 +0100 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 w0FHphCG079998; Mon, 15 Jan 2018 18:51:43 +0100 (CET) (envelope-from tijl@FreeBSD.org) Date: Mon, 15 Jan 2018 18:51:43 +0100 From: Tijl Coosemans To: David Chisnall Cc: Jan Beich , Ed Maste , Luca Pizzamiglio , FreeBSD Current , freebsd-ports@freebsd.org Subject: Re: atomic in i386 Current after CLANG 6 upgrade Message-ID: <20180115185143.0ef2f67b@kalimero.tijl.coosemans.org> In-Reply-To: <03DDFE7A-B5FE-4DE5-98D8-AF28EFDDFACF@FreeBSD.org> References: <20180115125756.37b803ba@kalimero.tijl.coosemans.org> <03DDFE7A-B5FE-4DE5-98D8-AF28EFDDFACF@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jan 2018 17:53:00 -0000 On Mon, 15 Jan 2018 17:08:58 +0000 David Chisnall wr= ote: > On 15 Jan 2018, at 17:00, Jan Beich wrote: >> It wouldn't help (see below). Clang 6 accidentally made __atomic* work >> enough to satisfy configure check but not for the port to build. I guess, >> it also confuses configure in net/librdkafka and net-mgmt/netdata. >=20 > Can we (by which I probably mean emaste@) push out an EN that adds the > atomic.c from compiler-rt to our libgcc_s? That should provide all of > these helper functions. Clang assumes that they exist because both > compiler-rt and vaguely recent libgcc_s provide them. Recent GCC will > also assume that they exist and so the correct fix is probably for us > to make them to exist. >=20 > If this is difficult, then we can perhaps provide a port that compiles > atomic.c into libatomic_fudge.so or similar and provides a libgcc_s.so > that=E2=80=99s a linker script that forces linking to libatomic_fudge.so = and > libgcc_s.so. I can understand emitting function calls on i486 but according to Jan, clang is emitting function calls on i586 as well. It used to inline this which is why we never needed these functions in libgcc. Is it normal that clang emits function calls now? From owner-freebsd-current@freebsd.org Mon Jan 15 17:55:11 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 85950EBE84A for ; Mon, 15 Jan 2018 17:55:11 +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 647BC2030 for ; Mon, 15 Jan 2018 17:55:11 +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 w0FHt5Sb020657 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 15 Jan 2018 09:55:05 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id w0FHt5sI020656; Mon, 15 Jan 2018 09:55:05 -0800 (PST) (envelope-from sgk) Date: Mon, 15 Jan 2018 09:55:04 -0800 From: Steve Kargl To: Mehmet Erol Sanliturk Cc: Yuri Pankov , freebsd-current Subject: Re: inconsistent for() and while() behavior when using floating point Message-ID: <20180115175504.GA20590@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <6c423dbf-cd85-3c93-41e4-3362c06dfbb7@icloud.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.2 (2017-12-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.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, 15 Jan 2018 17:55:11 -0000 On Mon, Jan 15, 2018 at 08:38:15PM +0300, Mehmet Erol Sanliturk wrote: > > When you perform floating point computations , it may be useful > to ... read David Goldberg's paper, "What Every Computer Scientist Should Know about Floating-Point Arithmetic." http://www.validlab.com/ -- Steve From owner-freebsd-current@freebsd.org Mon Jan 15 18:14:29 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 970FFE64F2E for ; Mon, 15 Jan 2018 18:14:29 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6DCBB337A for ; Mon, 15 Jan 2018 18:14:28 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from [192.168.0.6] (67-0-236-88.albq.qwest.net [67.0.236.88]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id 9E46A1928F3 for ; Mon, 15 Jan 2018 10:08:18 +0000 (UTC) To: freebsd-current From: Sean Bruno Subject: [CFT] sysutils/devcpu-data Intel microcode migration Message-ID: <890da368-7dbf-8d4f-6731-5c6e00cfa662@freebsd.org> Date: Mon, 15 Jan 2018 11:14:18 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="w7m5jIcRHUcOzlUl6ZvxKGJeVoQN3KhRu" 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, 15 Jan 2018 18:14:29 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --w7m5jIcRHUcOzlUl6ZvxKGJeVoQN3KhRu Content-Type: multipart/mixed; boundary="hXPEDbGg3i12t7mSkA4SMXjYfslXwAsFp"; protected-headers="v1" From: Sean Bruno To: freebsd-current Message-ID: <890da368-7dbf-8d4f-6731-5c6e00cfa662@freebsd.org> Subject: [CFT] sysutils/devcpu-data Intel microcode migration --hXPEDbGg3i12t7mSkA4SMXjYfslXwAsFp Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable https://reviews.freebsd.org/D13921 In order to better absorb updates as they appear, I'm proposing that we switch from the current model of processing the "microcode.dat" legacy file to consuming the pre-digested update files. This update should not change the microcode version that you previously received, but I'd like for folks to give it a spin before we commit yet another update to this port. sean --hXPEDbGg3i12t7mSkA4SMXjYfslXwAsFp-- --w7m5jIcRHUcOzlUl6ZvxKGJeVoQN3KhRu Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEE6MTp+IA1BOHj9Lo0veT1/om1/LYFAlpc73pfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEU4 QzRFOUY4ODAzNTA0RTFFM0Y0QkEzNEJERTRGNUZFODlCNUZDQjYACgkQveT1/om1 /LYZKQf+OTAH+OpbNkS1tX9AtsNsGcGWNbdqcV4qICVIzxMTnh83RrHQtLhYwKPL m3cckptrON2eRxxYcMlLE/lID6oh29vSfe4ZsV5xh1xaOlanOqWuZQy9XFKqjNey jjUpGnNs3rMUbQWEezoGWEcXb7QHvulKHBi73W2bZiFGE1nT9Y1zf1yrp/gBQ1kN 1CfNBYwYvUbUmD0sbhAyR34HlDtdFNctyyAKnm6UN89aPxa5xZm7StxJ316+muRN X18Uox4BilA5bs6AZGwwrRiyUp25IUDppak9YkXyyt0HBcyHDQNSoQYjwPnrDm+I oT8circ5K3tkUiIA0Oypy/GsaogGJQ== =8KwH -----END PGP SIGNATURE----- --w7m5jIcRHUcOzlUl6ZvxKGJeVoQN3KhRu-- From owner-freebsd-current@freebsd.org Mon Jan 15 18:21:24 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 695CEE65A29 for ; Mon, 15 Jan 2018 18:21:24 +0000 (UTC) (envelope-from alex@xanderio.de) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4A6EF3EDE for ; Mon, 15 Jan 2018 18:21:24 +0000 (UTC) (envelope-from alex@xanderio.de) Received: by mailman.ysv.freebsd.org (Postfix) id 49BF1E65A28; Mon, 15 Jan 2018 18:21:24 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 49610E65A27 for ; Mon, 15 Jan 2018 18:21:24 +0000 (UTC) (envelope-from alex@xanderio.de) Received: from mail.xanderio.de (xanderio.de [185.194.141.122]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0007E3ED7 for ; Mon, 15 Jan 2018 18:21:22 +0000 (UTC) (envelope-from alex@xanderio.de) From: Alexander Sieg To: FreeBSD Current Subject: Building kernel with no sound Date: Mon, 15 Jan 2018 19:14:57 +0100 Message-ID: <86tvvn2dlq.fsf@xanderio.de> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=xanderio.de; s=2017; t=1516040099; h=from:subject:date:message-id:to:mime-version:content-type; bh=WjzcNI7CYKm1MgmGm214a6G03kZdlDrWuptEY+QybgA=; b=m8uzyJJqK+80XwyNyb0MlEAltz9exE+iKibavtdsm+QR1rqNSTBHVm69sRHi7xkOgznu8G HeilwSv76xgIWwtRqr3jDPaPa23ZRJ1SRbaqoEG1fHptGFjQd70y+frA19rvP8mhWx5sfP qUomfjrWkhDv3yc7ODesWzTvZnPgx31kWGWBM0qu67jr6V6lbWkPhVdoUsWWVtbQoufYDU zbuX/bweN1vQjG4vpOq2oyPbm1TPR8R1PofNM52KaYT8ShSaymn7Ix4JQ5wiBxsHIIM45J RLBxv47E73M3TXn7z54NHWTllAHNpUdiq2u27xGhj1/DOFa/lKrf2aJQMa+U6g== ARC-Seal: i=1; s=2017; d=xanderio.de; t=1516040099; a=rsa-sha256; cv=none; b=IOiBI6FuEIVDv8U2KadszEZEQcoG/leU43V3hHQ6Oi7k1fjHKoqD0PBEioaf8Xi2w2PEtZnR25aCdI27VJbN0b+ZlTGz5v5vzj23eEVnuVStL+axvNqPP9uE1VqQdz718IyIc0BreA7WbwLz1hQju6yN4xXCHip9k2ujJbH5ddZadVs/9cetTsw49Mdt8SkJSeGuAb/rGTEIsHZulDBSkk804jsB1oy/eSYdkvbkZVb+uUKbQnFiaOaqOOaPVJ9ejrjsI0/Ll7I/kZSintCSZgB/s6UoLVxouYP8Qqmkly/pRy66A1kteZ7YmZbcvlPAqBcy0o4Wc1Hx9r8Mdbzwpg== ARC-Authentication-Results: i=1; auth=pass smtp.auth=alex@xanderio.de smtp.mailfrom=alex@xanderio.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=xanderio.de; s=2017; t=1516040099; h=from:subject:date:message-id:to:mime-version:content-type; bh=WjzcNI7CYKm1MgmGm214a6G03kZdlDrWuptEY+QybgA=; b=DfD5ie9R6OEkmELGJE56UosTfYKyTM0fqRTghVL3HEYT5WJ9my2BkE5NnGBNXrF/zlirWN jYyYKSFd4V0j+a6a0cspKic171qxMR0jZ9Wp2TxNL9mnhH7/y5GOhZFk6JUnvk8+lNn3Fl EGYkqR3VyoDrAguOw9CkPXZaFmAt9sEDhCSZAE2tfMd88uuzTrDgQMPvK0VPxhFM0IX7I8 wYaRhg5LJN6zRYXFkv1y9yUG3ciU39oS0kBWMlwNiRnkh0zWPcEgCjDVrumlMFrGr0N+Ih NOhZTCgHttpVX2klKviyOLVpb6ZjvgHZ4b0p7j0GIAQO6Rbz0JbDWWBvu3ANnQ== 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, 15 Jan 2018 18:21:24 -0000 --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hey, i=C2=B4m trying to build a custom kernel with no sound support build in. This is my make.conf: MALLOC_PRODUCTION=3Dtrue KERNCONF=3DMYKERNEL #GENERIC-NODEBUG DEVELOPER=3Dyes and this is my kernel configuration: include GENERIC-NODEBUG ident MYKERNEL nodevice sound # Generic sound driver (required) nodevice snd_es137x # Ensoniq AUdioPCI ES137x nodevice snd_hda # Intel High Definition Audio nodevice snd_ich # Intel, Nvidia and other ICH AC'97 audio nodevice snd_uaudio # USB Audio nodevice snd_via8233 # VIA VT823x Audio The problem is when i try to compile it with "make buildkernel" the build process starts, but it stop with the error that it can=C2=B4t find the header file "channel_if.h". /usr/src/sys/dev/sound/pcm/channel.h:256:10: fatal error: 'channel_if.h' fi= le not found #include "channel_if.h" ^~~~~~~~~~~~~~ The intention behind the custom kernel is to try 'oss' form the ports tree. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEEedFZRxIzB9PUH6MkiRfGkdtGBUFAlpc76EACgkQkiRfGkdt GBWWQA/+M+hBmPb3lKTFKCjXSE22AxjUlvT8Cc9QV0EPI3LmbF/SHEwXKytWE0V/ P5Cn+vS+l+aqUuzGMLrMBhvdYsTHfsDdgeW3vAcPnJW3gTsskHBB5DzhRLBRhgho 8eeD47QDswP+rmkqvuiSimf6H5lvxyoyDAsBiN6+ExG9hoRhuOBap9ykoGUR721O 7ldhftzxYppA2AXFy8xI9pKg/aFBK1rFpyLKv6ounHMv7KMHmCUtWvLHP5ArqoGs qPaefoP6yuNMG/lBm4ZwSLhyqE5B+lRRMrVJxjXuQjJZ35IH7eeNNlZCjcSZsfwe 8EDG0qC9o7DVtxyKqkb6nY+GHJ85ty8ryER0nlJHq8Qh3hlw6YGaZA1xdDVvNwL0 cdtRUxleAhWgVOwBWPUS4FErtioyQJKHsct4bm7JzYLXYr5xqkvrpVc2Q9i3Q5e9 wT3iB1aOmr0LY22bRg2R3VkzbHq47GJuN//37a0XVKvz3271JPcJ2WLE5tOXJNnR t7ifZU+H+NXr55i81UW/XuqrnuFn0gKDkVpbSzBNNRDPBX/UV8/TMODGMJ1hQkv7 9JHPygt7xSHwztDlwqvKhg8+DL2BYQCSec2HxfkGlb+Gx7oYNTo1i14kSe2j65iv 1bYtPLVicApe12THYLsKXYSP/E7dXaDablv/+DJFG7w5yMbWMjA= =Ney2 -----END PGP SIGNATURE----- --=-=-=-- From owner-freebsd-current@freebsd.org Mon Jan 15 18:26:29 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EEBA3E6C1A0; Mon, 15 Jan 2018 18:26:29 +0000 (UTC) (envelope-from tijl@freebsd.org) Received: from mailrelay111.isp.belgacom.be (mailrelay111.isp.belgacom.be [195.238.20.138]) (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 CBF0F6355B; Mon, 15 Jan 2018 18:26:28 +0000 (UTC) (envelope-from tijl@freebsd.org) X-Belgacom-Dynamic: yes IronPort-PHdr: =?us-ascii?q?9a23=3AETblLRcR5zyfj3zo/6KAZpSFlGMj4u6mDksu8pMi?= =?us-ascii?q?zoh2WeGdxc26ZxON2/xhgRfzUJnB7Loc0qyK6/mmATRIyK3CmUhKSIZLWR4BhJ?= =?us-ascii?q?detC0bK+nBN3fGKuX3ZTcxBsVIWQwt1Xi6NU9IBJS2PAWK8TW94jEIBxrwKxd+?= =?us-ascii?q?KPjrFY7OlcS30P2594HObwlSizexfa5+IA+qoQnNq8IbnZZsJqEtxxXTv3BGYf?= =?us-ascii?q?5WxWRmJVKSmxbz+MK994N9/ipTpvws6ddOXb31cKokQ7NYCi8mM30u683wqRbD?= =?us-ascii?q?VwqP6WACXWgQjxFFHhLK7BD+Xpf2ryv6qu9w0zSUMMHqUbw5Xymp4rx1QxH0li?= =?us-ascii?q?gIKz858HnWisNuiqJbvAmhrAF7z4LNfY2ZKOZycqbbcNgHR2ROQ9xRWjRPDI28?= =?us-ascii?q?cYUBEukPMuRWr4byu1QAogCzBRWuCe/z1jNEmmP60bM83u88EQ/GxgsgH9cWvX?= =?us-ascii?q?rKrdX1NqMSWv2rwanPyjXDdO1Z2TLn54jOaRAqvPaBXa5xccrTzUkiDAPLjk+O?= =?us-ascii?q?poP7Ij6by+oDv3Kc7+p6WuKikmgqoBx/rDiow8cjkIjJhoQNx1DA8SV53oM1Kc?= =?us-ascii?q?e/SE5hbt6pFoZbuSKCN4ZuQc4uXntktDg1x7AHo5K3YSYHxZo9yxLCZfGKfI6F?= =?us-ascii?q?6Q/5WumLOzd3nndldaq6hxa17Eev1PXxVtKx0FZWtipFlcTMtmwV2xzT9MeHTv?= =?us-ascii?q?x981+i2TmV0wDT6+RELl4ularcMZIh3r8wlpgXsUjZAiD2n0L2jLSIeUUh4Oeo?= =?us-ascii?q?7f/nbq/hpp+GOI94kgD+MqIwlcyjGek1MRUCU3KF9emz1bDv51D1TbtEg/Esj6?= =?us-ascii?q?XUvp/XKdwepqGjAg9V1ogj6wy4DzejyNkYgXgHLFBBeB+cgYjpIU/BL+7jAvek?= =?us-ascii?q?nlugijBrx+rJPrH5GJXCMmDDkKv9fbZ680NT1g8zwspE55JIFL4MO/zzWlXvu9?= =?us-ascii?q?PGFRA5KBG7z/zgCNVn2YMUQXiPDbOBMKPOrV+I4foiI+eWZIALpjnyMOMl6OP3?= =?us-ascii?q?gX8hnl8dZ7Wp3YAMZXC2BPRpPVuWbmH3gtgcC2sKuRA+TOPygl2YTTFTf2qyX7?= =?us-ascii?q?475jwjBoKmF5nMSZ62j7yawSi3B4FZZn1cClCWD3jocZmEVuwCaCKIPMBujCcL?= =?us-ascii?q?VaO8RIM70hGurgD6waJ9LuXI4i0YqY7j1N9t6u3LlBEz9D11AN6Y02GMQGF5hW?= =?us-ascii?q?0IRyUo069hukN90UqM3bJ/g/xCGtxZ/+lJXRsiNZ7A0+x6DMj/VR/AfteMU1um?= =?us-ascii?q?TM+mDi8vQd0q2N8BflxxG9K4jhDMjGKWBOo5lrmKGIYluova02LwLI4px3fD/I?= =?us-ascii?q?c7glQMeecJMnep0P1R7Q/WUrLIkUHRvKGtbqkZ1SjWvDOfzGiKlG9CXQNaaomD?= =?us-ascii?q?WmoQMBiF5e/l71/PGuf9QY8sNRFMnIvbcvNH?= X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2DABABJ8Vxa/4aF9lFdGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYNBVhB0FBOPK41qAQGCATIBmQ8thRgChFBDFQEBAQEBAQEBAQF?= =?us-ascii?q?qKII4JAGCRwEFOhwjEAsOCgklDyoeBhOKNwysGolJAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEcBY0/gy8EGYdSBaNkiAyNMoEAkx2NPosjNSOBUEwwCIJnhFhANwGNCwEBAQ?= X-IPAS-Result: =?us-ascii?q?A2DABABJ8Vxa/4aF9lFdGQEBAQEBAQEBAQEBAQcBAQEBAYN?= =?us-ascii?q?BVhB0FBOPK41qAQGCATIBmQ8thRgChFBDFQEBAQEBAQEBAQFqKII4JAGCRwEFO?= =?us-ascii?q?hwjEAsOCgklDyoeBhOKNwysGolJAQEBAQEBAQEBAQEBAQEBAQEcBY0/gy8EGYd?= =?us-ascii?q?SBaNkiAyNMoEAkx2NPosjNSOBUEwwCIJnhFhANwGNCwEBAQ?= Received: from 134.133-246-81.adsl-dyn.isp.belgacom.be (HELO kalimero.tijl.coosemans.org) ([81.246.133.134]) by relay.skynet.be with ESMTP; 15 Jan 2018 19:26:25 +0100 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 w0FIQPCq080268; Mon, 15 Jan 2018 19:26:25 +0100 (CET) (envelope-from tijl@FreeBSD.org) Date: Mon, 15 Jan 2018 19:26:25 +0100 From: Tijl Coosemans To: Dimitry Andric Cc: Luca Pizzamiglio , FreeBSD Current , FreeBSD Ports , Ed Maste Subject: Re: atomic in i386 Current after CLANG 6 upgrade Message-ID: <20180115192625.6c3186a0@kalimero.tijl.coosemans.org> In-Reply-To: <85AE8E52-FC6C-4522-B5B1-7423A163DDFE@FreeBSD.org> References: <85AE8E52-FC6C-4522-B5B1-7423A163DDFE@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jan 2018 18:26:30 -0000 On Mon, 15 Jan 2018 18:37:47 +0100 Dimitry Andric wrote: > On 15 Jan 2018, at 11:43, Luca Pizzamiglio wrote: >> I've already received a couple of messages from pkg-fallout about build >> failure on head-i386-default [1] [2] both pointing to the same errors, >> about missing intrinsic symbols related to __atomic_* >> >> The clang documentation about C11 atomic builtins [3] stats that __atomic_* >> are GCC extension and Clang provides them. >> >> It seems to me that this specific GCC-compatible builtin are enabled on >> amd64, but not on i386. >> Is there a way to enable GCC compatible __atomic_ builtin also on i386? >> Or should I provide patches to adopt _c11_atomic_* instead of __atomic_* >> for every ports that need it ? > > There is some strangeness going on with an upstream bug fix [1], which > has the unintended side effect of sometimes emitting libcalls to > __atomic functions that we do not have on i386. I've commented on the > upstream bug report, but I do not know an easy workaround at this > point. > > [1] https://bugs.llvm.org/show_bug.cgi?id=34347 It looks to me clang is doing fewer libcalls now and more inlining, which is why the configure tests succeed now. That clang generates cmpxchg8b on i486 has always been the case. The fix for 34347 exposes this more now. From owner-freebsd-current@freebsd.org Mon Jan 15 18:33:02 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 961C9E6C9DA for ; Mon, 15 Jan 2018 18:33:02 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 72A9663B72 for ; Mon, 15 Jan 2018 18:33:02 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 720F5E6C9D7; Mon, 15 Jan 2018 18:33:02 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 71B51E6C9D4 for ; Mon, 15 Jan 2018 18:33:02 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-lf0-x22d.google.com (mail-lf0-x22d.google.com [IPv6:2a00:1450:4010:c07::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DC9F163B71 for ; Mon, 15 Jan 2018 18:33:01 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by mail-lf0-x22d.google.com with SMTP id e203so14463000lfg.3 for ; Mon, 15 Jan 2018 10:33:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=03BuKkIjmbPAQ/JMOqIqjwcMEGhSmQ2qeb7L+pA+1R4=; b=DyoHLUsLNfF+SopR+sZYnkJWwsP32ZkuehkcVAJh/K+rY0LBAe6+nVs+I1obXc3hWM EzbubC+3LZbqdFTUzQJLcIuByHRDV7XLCQtfO35oNL3/rYZhV8NCdDsh3Y1mQVFCFUVV Hp44v1CLeQWyP55kGPnj2zEFCBVOXgZsJXliZhR9ZK3rl9cepPTINnE7QIFiuXYeUkIF c+7gygAlsHGhmD26ZlJRV6fOlVSnpMzFlPjJmZPqn/akg+qi2vONa7q67U7GY4kgwk2M hIPkzYDqn5tuzTJ3uhoac+1XLfDZYujhG9gbf27Wz7gCpkh1pGp9Wb4Ge9OawpjUW/8j HZVw== 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=03BuKkIjmbPAQ/JMOqIqjwcMEGhSmQ2qeb7L+pA+1R4=; b=KXuCur1rFvX2lkPxvE9fjqCbkp/3WkXEGFiEpj+SkgWVH8E11lzOorZ4VF2VaZfvwK G7slwj3SwffRz3HTWwbpj5Tkvl3ys9fqyyWdvgqW7U4paLR16SRsP8oLNz9nzgwzYxtC a6nIlwbc66p+2hfqtmTgEBMvDn1rP9L1zKueZFAEHdSIK6iaWV+FBPOFoRiTn3LVD4Xq hD+F27JO4VBxCBc3xWiYM97EDumjz7NGCFHJ3LKC5XZ4ppdMYi8zS1lw39u+K4wZebGl DVyL82MLvA8CXe5nlUXRuixO2SL7/itohRJkXSyXrc3kXEaSsiGL2JjPPgFGtDM7o6a3 FcZA== X-Gm-Message-State: AKwxytdsgV8RidTXYVtPSoMvYnTNEC9aV48oXT1YjhrHnSiGYZxzhvxR pGdKR4TCf04NWqafDG/b1XdPnv7xWIPrKm+9rsb3nFVd X-Google-Smtp-Source: ACJfBov63Ca0ZyxxHKC6ZCwdslo3BQZv/KaZlJnkjn/rShkYqmVxioh551Z/syBci4RbEPzEOQ2el9VGmK1aE+jqNts= X-Received: by 10.46.115.16 with SMTP id o16mr13759671ljc.49.1516041178778; Mon, 15 Jan 2018 10:32:58 -0800 (PST) MIME-Version: 1.0 Received: by 10.25.163.207 with HTTP; Mon, 15 Jan 2018 10:32:58 -0800 (PST) In-Reply-To: <86tvvn2dlq.fsf@xanderio.de> References: <86tvvn2dlq.fsf@xanderio.de> From: Freddie Cash Date: Mon, 15 Jan 2018 10:32:58 -0800 Message-ID: Subject: Re: Building kernel with no sound To: Alexander Sieg Cc: 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: Mon, 15 Jan 2018 18:33:02 -0000 On Mon, Jan 15, 2018 at 10:14 AM, Alexander Sieg wrote: > Hey, > i=C2=B4m trying to build a custom kernel with no sound support build in. > > This is my make.conf: > MALLOC_PRODUCTION=3Dtrue > KERNCONF=3DMYKERNEL #GENERIC-NODEBUG > DEVELOPER=3Dyes > > and this is my kernel configuration: > include GENERIC-NODEBUG > > ident MYKERNEL > > nodevice sound # Generic sound driver (required) > nodevice snd_es137x # Ensoniq AUdioPCI ES137x > nodevice snd_hda # Intel High Definition Audio > nodevice snd_ich # Intel, Nvidia and other ICH AC'97 audio > nodevice snd_uaudio # USB Audio > nodevice snd_via8233 # VIA VT823x Audio > > > The problem is when i try to compile it with "make buildkernel" the > build process starts, but it stop with the error that it can=C2=B4t find = the > header file "channel_if.h". > > /usr/src/sys/dev/sound/pcm/channel.h:256:10: fatal error: 'channel_if.h' > file not found > #include "channel_if.h" > ^~~~~~~~~~~~~~ > > The intention behind the custom kernel is to try 'oss' form the > ports tree. > =E2=80=8BYou're missing a few of the sound drivers. Here's the section fro= m GENERIC on 11.1 for sound (it's the same for 10.4 and 12-CURRENT): =E2=80=8B# Sound support device sound # Generic sound driver (required) device snd_cmi # CMedia CMI8338/CMI8738 device snd_csa # Crystal Semiconductor CS461x/428x device snd_emu10kx # Creative SoundBlaster Live! and Audigy device snd_es137x # Ensoniq AudioPCI ES137x device snd_hda # Intel High Definition Audio device snd_ich # Intel, NVidia and other ICH AC'97 Audio device snd_via8233 # VIA VT8233x Audio =E2=80=8BSo you need to add nodevice entries for all the ones that you are = missing (snd_cmi, snd_cma, snd_emu10kx).=E2=80=8B Always check the kernel config file you are including to see what you need to exclude via nodevice. :) --=20 Freddie Cash fjwcash@gmail.com From owner-freebsd-current@freebsd.org Mon Jan 15 18:41:59 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6CC7CE6E332 for ; Mon, 15 Jan 2018 18:41:59 +0000 (UTC) (envelope-from yuripv@icloud.com) Received: from pv33p00im-asmtp002.me.com (pv33p00im-asmtp002.me.com [17.142.194.251]) (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 4F5B4685A1 for ; Mon, 15 Jan 2018 18:41:59 +0000 (UTC) (envelope-from yuripv@icloud.com) Received: from process-dkim-sign-daemon.pv33p00im-asmtp002.me.com by pv33p00im-asmtp002.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) id <0P2L00400XXFYP00@pv33p00im-asmtp002.me.com> for freebsd-current@freebsd.org; Mon, 15 Jan 2018 17:41:18 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=icloud.com; s=04042017; t=1516038078; bh=k/lkXm2hIGRg8r7Y8V9FHpxhcRiPLQ6zBe5JR1Fm19s=; h=Subject:To:From:Message-id:Date:MIME-version:Content-type; b=eIrMllrXNofNXgQIDztot8TZcfVDbsIFaPZo3SIvZL5ECNIB0XgKAG42mEI2wiaMX 50IwXDFvPAM3VmFm/8cnDdI8KWh5CZCoGR3OBFrvELNfinKmG0nb0VsTHTm5WWuhpH RNupZof7B+WxMYdQJeUe1m26nQDVrlX0AmmB3TWNDffQEQYWtQ3WI7Vpepa57CnMWp ENpqnAGEES05q+RTwgHIPZ329SGnCAb5BkVuHLcsmbVXHVOZGo4R4HWUqcSqko89ao oulb+waF5NTKGEvln31zS9uoYAPrwbFf2AA3RXskUR5QFaHb1Jsigd3iah8odTpBZy On3HK23wLFqQA== Received: from icloud.com ([127.0.0.1]) by pv33p00im-asmtp002.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) with ESMTPSA id <0P2L003PNYGP5Q20@pv33p00im-asmtp002.me.com>; Mon, 15 Jan 2018 17:41:17 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2018-01-15_08:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1011 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1801150250 Subject: Re: inconsistent for() and while() behavior when using floating point To: Mehmet Erol Sanliturk Cc: freebsd-current References: <6c423dbf-cd85-3c93-41e4-3362c06dfbb7@icloud.com> From: Yuri Pankov Message-id: Date: Mon, 15 Jan 2018 20:41:13 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-version: 1.0 In-reply-to: Content-type: text/plain; charset=utf-8; format=flowed Content-language: en-US Content-transfer-encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.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, 15 Jan 2018 18:41:59 -0000 On Mon, Jan 15, 2018 at 08:38:15PM +0300, Mehmet Erol Sanliturk: > > > On Mon, Jan 15, 2018 at 5:38 PM, Yuri Pankov > wrote: > > Hi, > > Looking at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217149 > , I > noticed that it isn't a seq(1) problem per se, rather for() and > while() loops behaving inconsistently while using floating point, i.e.: > >         double i; > >         for (i = 1; i <= 2.00; i += 0.1) >                 printf("%g\n", i); > > would produce: > >         1 >         ... >         1.9 > > but: > >         double i; > >         for (i = 1; i <= 2; i += 0.2) >                 printf("%g\n", i); > > would correctly end with 2: > >         1 >         ... >         2 > > $ cc -v > FreeBSD clang version 6.0.0 (branches/release_60 321788) (based on > LLVM 6.0.0) > Target: x86_64-unknown-freebsd12.0 > Thread model: posix > InstalledDir: /usr/bin > > though gcc 4.4.4 on illumos behaves the same. > > Is this a known problem with loops and floating point numbers? > _______________________________________________ > > > > > When you perform floating point computations , it may be useful to > remember that , the last bits of floating point numbers may be > considered to be "noise" . > For that reason , the same "for" or "while" loops may behave differently > in different times and places . > > To make floating point related loops more deterministic , the useful > steps may be to compute "step size" and "number of steps" , and use > integer variables for counting loop steps with multiplication of "loop > counter"  and "step size" during loop steps :  For floating point loop > counter T = "integer loop counter" * "step size" . Indeed, exactly as I did in a patch for that PR. > A statement  like  T = T + "step size" will/may produce wrong results if > number of steps is sufficiently large . > > > Computer arithmetic and theoretical arithmetic are not the same . > For example , addition is not associative in computer arithmetic : a + ( > b + c ) is not always equal to ( a + b ) + c . Thanks to all replies, I now clearly see the problem. From owner-freebsd-current@freebsd.org Mon Jan 15 18:52:24 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F276AE6EF31 for ; Mon, 15 Jan 2018 18:52:24 +0000 (UTC) (envelope-from karl@denninger.net) Received: from colo1.denninger.net (colo1.denninger.net [104.236.120.189]) by mx1.freebsd.org (Postfix) with ESMTP id C8A6868E99 for ; Mon, 15 Jan 2018 18:52:24 +0000 (UTC) (envelope-from karl@denninger.net) Received: from denninger.net (ip68-1-57-197.pn.at.cox.net [68.1.57.197]) by colo1.denninger.net (Postfix) with ESMTP id C2455212268 for ; Mon, 15 Jan 2018 13:44:19 -0500 (EST) Received: from [192.168.10.23] (D13.Denninger.Net [192.168.10.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by denninger.net (Postfix) with ESMTPSA id AAF6F39CB31 for ; Mon, 15 Jan 2018 12:44:18 -0600 (CST) To: freebsd-current@freebsd.org From: Karl Denninger Subject: Recent commits to -HEAD blow up cross-compile for PI3 (and possibly others) Message-ID: <89dbdd66-1ba7-15d3-d3fe-291f8e361fcb@denninger.net> Date: Mon, 15 Jan 2018 12:44:17 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-512; boundary="------------ms060309080303030309090601" 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: Mon, 15 Jan 2018 18:52:25 -0000 This is a cryptographically signed message in MIME format. --------------ms060309080303030309090601 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable There has been trouble cross-compiling for the RPI3 for a while now, which I have filed a report on with the Crochet people here: https://github.com/freebsd/crochet/issues/222 This stemmed from an older LLVM version on my 11.1 box, which I rolled forward -- and resulted in blowups claiming that there was a permission problem with posix_spawn (!) Now, having tried to roll my -HEAD repo forward it's failing *much* earlier, starting with warnings about ATOMIC_ASM: --- getarg.o --- cc=C2=A0 -O2 -pipe -I/pics/CrossBuild-Head/src/crypto/heimdal/lib/roken -= I.=C2=A0 -DHAVE_C ONFIG_H -I/pics/CrossBuild-Head/src/kerberos5/include -MD=C2=A0 -MF.depend.getarg.o - MTgetarg.o -std=3Dgnu99=C2=A0 -Qunused-arguments=C2=A0 -I/pics/Crochet-work-HEAD/obj/pics/Cr ossBuild-Head/src/arm64.aarch64/tmp/legacy/usr/include -c /pics/CrossBuild-Head/ src/crypto/heimdal/lib/roken/getarg.c -o getarg.o --- _bootstrap-tools-usr.bin/localedef --- In file included from /pics/CrossBuild-Head/src/usr.bin/localedef/collate.c:50: In file included from /pics/CrossBuild-Head/src/lib/libc/locale/collate.h:44: /pics/CrossBuild-Head/src/lib/libc/locale/xlocale_private.h:170:18: warning: pas sing 'long *' to parameter of type 'volatile u_long *' (aka 'volatile unsigned l ong *') converts between pointers to integer types with different sign [-Wpointe r-sign] =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 atomic_add_long(&(obj->retain_= count), 1); =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ^~~~~~~~~= ~~~~~~~~~~~ /usr/include/machine/atomic.h:467:1: note: passing argument to parameter 'p' her e ATOMIC_ASM(add,=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 long,=C2=A0 "addq %1,%0",=C2= =A0 "ir",=C2=A0 v); ^ /usr/include/machine/atomic.h:141:43: note: expanded from macro 'ATOMIC_A= SM' atomic_##NAME##_##TYPE(volatile u_##TYPE *p, u_##TYPE v)\ And then failing to build llvm entirely starting here: =3D=3D=3D> lib/clang/libllvm (all) llvm-tblgen -gen-dag-isel=C2=A0 -I /pics/CrossBuild-Head/src/contrib/llvm/include -I /pics/CrossBuild-Head/src/contrib/llvm/lib/Target/AArch64=C2=A0 -d AArch64GenDAGISel.inc.d -o AArch64GenDAGISel.inc=C2=A0 /pics/CrossBuild-Head/src/contrib/llvm/lib/Target/AArch64/AArch64.td FCVTZSv8f16:=C2=A0=C2=A0=C2=A0 (set V128:v16i16:$Rd, (fp_to_sint: = V128:v1f32:$Rn)) Included from /pics/CrossBuild-Head/src/contrib/llvm/lib/Target/AArch64/AArch64.td:178:= /pics/CrossBuild-Head/src/contrib/llvm/lib/Target/AArch64/AArch64InstrInf= o.td:2951:1: error: In FCVTZSv8f16: Type inference contradiction found, forcing '{v16i8:v32i8:v8i16:v16i16:v4i32:v8i32:v2i64:v4i64:nxv4i1:nxv8i1:nxv16i1:= nxv32i1:nxv32i8:nxv16i16:nxv8i32:nxv4i64}' to have same number elements as 'v1f32' defm FCVTZS : SIMDTwoVectorFPToInt<0, 1, 0b11011, "fcvtzs", fp_to_sint>; ^ Included from /pics/CrossBuild-Head/src/contrib/llvm/lib/Target/AArch64/AArch64.td:178:= Included from /pics/CrossBuild-Head/src/contrib/llvm/lib/Target/AArch64/AArch64InstrInf= o.td:337: /pics/CrossBuild-Head/src/contrib/llvm/lib/Target/AArch64/AArch64InstrFor= mats.td:5092:3: note: instantiated from multiclass =C2=A0 def v8f16 : BaseSIMDTwoSameVector<1, U, {S,1}, opc, 0b11, V128, =C2=A0 ^ FCVTZUv8f16:=C2=A0=C2=A0=C2=A0 (set V128:v16i16:$Rd, (fp_to_uint: = V128:v1f32:$Rn)) Included from /pics/CrossBuild-Head/src/contrib/llvm/lib/Target/AArch64/AArch64.td:178:= /pics/CrossBuild-Head/src/contrib/llvm/lib/Target/AArch64/AArch64InstrInf= o.td:2952:1: error: In FCVTZUv8f16: Type inference contradiction found, forcing '{v16i8:v32i8:v8i16:v16i16:v4i32:v8i32:v2i64:v4i64:nxv4i1:nxv8i1:nxv16i1:= nxv32i1:nxv32i8:nxv16i16:nxv8i32:nxv4i64}' to have same number elements as 'v1f32' defm FCVTZU : SIMDTwoVectorFPToInt<1, 1, 0b11011, "fcvtzu", fp_to_uint>; Off -HEAD revision 328011 attempting to build with: FreeBSD 11.1-STABLE #21 r327332M: Thu Dec 28 20:54:24 CST 2017=C2=A0=C2=A0= =C2=A0=C2=A0 karl@NewFS.denninger.net:/usr/obj/usr/src/sys/KSD-SMP --=20 Karl Denninger karl@denninger.net /The Market Ticker/ /[S/MIME encrypted email preferred]/ --------------ms060309080303030309090601 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgMFADCABgkqhkiG9w0BBwEAAKCC DdgwggagMIIEiKADAgECAhMA5EiKghDOXrvfxYxjITXYDdhIMA0GCSqGSIb3DQEBCwUAMIGL MQswCQYDVQQGEwJVUzEQMA4GA1UECAwHRmxvcmlkYTESMBAGA1UEBwwJTmljZXZpbGxlMRkw FwYDVQQKDBBDdWRhIFN5c3RlbXMgTExDMRgwFgYDVQQLDA9DdWRhIFN5c3RlbXMgQ0ExITAf BgNVBAMMGEN1ZGEgU3lzdGVtcyBMTEMgMjAxNyBDQTAeFw0xNzA4MTcxNjQyMTdaFw0yNzA4 MTUxNjQyMTdaMHsxCzAJBgNVBAYTAlVTMRAwDgYDVQQIDAdGbG9yaWRhMRkwFwYDVQQKDBBD dWRhIFN5c3RlbXMgTExDMRgwFgYDVQQLDA9DdWRhIFN5c3RlbXMgQ0ExJTAjBgNVBAMMHEN1 ZGEgU3lzdGVtcyBMTEMgMjAxNyBJbnQgQ0EwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAwggIK AoICAQC1aJotNUI+W4jP7xQDO8L/b4XiF4Rss9O0B+3vMH7Njk85fZ052QhZpMVlpaaO+sCI KqG3oNEbuOHzJB/NDJFnqh7ijBwhdWutdsq23Ux6TvxgakyMPpT6TRNEJzcBVQA0kpby1DVD 0EKSK/FrWWBiFmSxg7qUfmIq/mMzgE6epHktyRM3OGq3dbRdOUgfumWrqHXOrdJz06xE9NzY vc9toqZnd79FUtE/nSZVm1VS3Grq7RKV65onvX3QOW4W1ldEHwggaZxgWGNiR/D4eosAGFxn uYeWlKEC70c99Mp1giWux+7ur6hc2E+AaTGh+fGeijO5q40OGd+dNMgK8Es0nDRw81lRcl24 SWUEky9y8DArgIFlRd6d3ZYwgc1DMTWkTavx3ZpASp5TWih6yI8ACwboTvlUYeooMsPtNa9E 6UQ1nt7VEi5syjxnDltbEFoLYcXBcqhRhFETJe9CdenItAHAtOya3w5+fmC2j/xJz29og1KH YqWHlo3Kswi9G77an+zh6nWkMuHs+03DU8DaOEWzZEav3lVD4u76bKRDTbhh0bMAk4eXriGL h4MUoX3Imfcr6JoyheVrAdHDL/BixbMH1UUspeRuqQMQ5b2T6pabXP0oOB4FqldWiDgJBGRd zWLgCYG8wPGJGYgHibl5rFiI5Ix3FQncipc6SdUzOQIDAQABo4IBCjCCAQYwHQYDVR0OBBYE FF3AXsKnjdPND5+bxVECGKtc047PMIHABgNVHSMEgbgwgbWAFBu1oRhUMNEzjODolDka5k4Q EDBioYGRpIGOMIGLMQswCQYDVQQGEwJVUzEQMA4GA1UECAwHRmxvcmlkYTESMBAGA1UEBwwJ TmljZXZpbGxlMRkwFwYDVQQKDBBDdWRhIFN5c3RlbXMgTExDMRgwFgYDVQQLDA9DdWRhIFN5 c3RlbXMgQ0ExITAfBgNVBAMMGEN1ZGEgU3lzdGVtcyBMTEMgMjAxNyBDQYIJAKxAy1WBo2kY MBIGA1UdEwEB/wQIMAYBAf8CAQAwDgYDVR0PAQH/BAQDAgGGMA0GCSqGSIb3DQEBCwUAA4IC AQCB5686UCBVIT52jO3sz9pKuhxuC2npi8ZvoBwt/IH9piPA15/CGF1XeXUdu2qmhOjHkVLN gO7XB1G8CuluxofOIUce0aZGyB+vZ1ylHXlMeB0R82f5dz3/T7RQso55Y2Vog2Zb7PYTC5B9 oNy3ylsnNLzanYlcW3AAfzZcbxYuAdnuq0Im3EpGm8DoItUcf1pDezugKm/yKtNtY6sDyENj tExZ377cYA3IdIwqn1Mh4OAT/Rmh8au2rZAo0+bMYBy9C11Ex0hQ8zWcvPZBDn4v4RtO8g+K uQZQcJnO09LJNtw94W3d2mj4a7XrsKMnZKvm6W9BJIQ4Nmht4wXAtPQ1xA+QpxPTmsGAU0Cv HmqVC7XC3qxFhaOrD2dsvOAK6Sn3MEpH/YrfYCX7a7cz5zW3DsJQ6o3pYfnnQz+hnwLlz4MK 17NIA0WOdAF9IbtQqarf44+PEyUbKtz1r0KGeGLs+VGdd2FLA0e7yuzxJDYcaBTVwqaHhU2/ Fna/jGU7BhrKHtJbb/XlLeFJ24yvuiYKpYWQSSyZu1R/gvZjHeGb344jGBsZdCDrdxtQQcVA 6OxsMAPSUPMrlg9LWELEEYnVulQJerWxpUecGH92O06wwmPgykkz//UmmgjVSh7ErNvL0lUY UMfunYVO/O5hwhW+P4gviCXzBFeTtDZH259O7TCCBzAwggUYoAMCAQICEwCg0WvVwekjGFiO 62SckFwepz0wDQYJKoZIhvcNAQELBQAwezELMAkGA1UEBhMCVVMxEDAOBgNVBAgMB0Zsb3Jp ZGExGTAXBgNVBAoMEEN1ZGEgU3lzdGVtcyBMTEMxGDAWBgNVBAsMD0N1ZGEgU3lzdGVtcyBD QTElMCMGA1UEAwwcQ3VkYSBTeXN0ZW1zIExMQyAyMDE3IEludCBDQTAeFw0xNzA4MTcyMTIx MjBaFw0yMjA4MTYyMTIxMjBaMFcxCzAJBgNVBAYTAlVTMRAwDgYDVQQIDAdGbG9yaWRhMRkw FwYDVQQKDBBDdWRhIFN5c3RlbXMgTExDMRswGQYDVQQDDBJrYXJsQGRlbm5pbmdlci5uZXQw ggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAwggIKAoICAQC+HVSyxVtJhy3Ohs+PAGRuO//Dha9A 16l5FPATr6wude9zjX5f2lrkRyU8vhCXTZW7WbvWZKpcZ8r0dtZmiK9uF58Ec6hhvfkxJzbg 96WHBw5Fumd5ahZzuCJDtCAWW8R7/KN+zwzQf1+B3MVLmbaXAFBuKzySKhKMcHbK3/wjUYTg y+3UK6v2SBrowvkUBC+jxNg3Wy12GsTXcUS/8FYIXgVVPgfZZrbJJb5HWOQpvvhILpPCD3xs YJFNKEPltXKWHT7Qtc2HNqikgNwj8oqOb+PeZGMiWapsatKm8mxuOOGOEBhAoTVTwUHlMNTg 6QUCJtuWFCK38qOCyk9Haj+86lUU8RG6FkRXWgMbNQm1mWREQhw3axgGLSntjjnznJr5vsvX SYR6c+XKLd5KQZcS6LL8FHYNjqVKHBYM+hDnrTZMqa20JLAF1YagutDiMRURU23iWS7bA9tM cXcqkclTSDtFtxahRifXRI7Epq2GSKuEXe/1Tfb5CE8QsbCpGsfSwv2tZ/SpqVG08MdRiXxN 5tmZiQWo15IyWoeKOXl/hKxA9KPuDHngXX022b1ly+5ZOZbxBAZZMod4y4b4FiRUhRI97r9l CxsP/EPHuuTIZ82BYhrhbtab8HuRo2ofne2TfAWY2BlA7ExM8XShMd9bRPZrNTokPQPUCWCg CdIATQIDAQABo4IBzzCCAcswPAYIKwYBBQUHAQEEMDAuMCwGCCsGAQUFBzABhiBodHRwOi8v b2NzcC5jdWRhc3lzdGVtcy5uZXQ6ODg4ODAJBgNVHRMEAjAAMBEGCWCGSAGG+EIBAQQEAwIF oDAOBgNVHQ8BAf8EBAMCBeAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMDMGCWCG SAGG+EIBDQQmFiRPcGVuU1NMIEdlbmVyYXRlZCBDbGllbnQgQ2VydGlmaWNhdGUwHQYDVR0O BBYEFLElmNWeVgsBPe7O8NiBzjvjYnpRMIHKBgNVHSMEgcIwgb+AFF3AXsKnjdPND5+bxVEC GKtc047PoYGRpIGOMIGLMQswCQYDVQQGEwJVUzEQMA4GA1UECAwHRmxvcmlkYTESMBAGA1UE BwwJTmljZXZpbGxlMRkwFwYDVQQKDBBDdWRhIFN5c3RlbXMgTExDMRgwFgYDVQQLDA9DdWRh IFN5c3RlbXMgQ0ExITAfBgNVBAMMGEN1ZGEgU3lzdGVtcyBMTEMgMjAxNyBDQYITAORIioIQ zl6738WMYyE12A3YSDAdBgNVHREEFjAUgRJrYXJsQGRlbm5pbmdlci5uZXQwDQYJKoZIhvcN AQELBQADggIBAJXboPFBMLMtaiUt4KEtJCXlHO/3ZzIUIw/eobWFMdhe7M4+0u3te0sr77QR dcPKR0UeHffvpth2Mb3h28WfN0FmJmLwJk+pOx4u6uO3O0E1jNXoKh8fVcL4KU79oEQyYkbu 2HwbXBU9HbldPOOZDnPLi0whi/sbFHdyd4/w/NmnPgzAsQNZ2BYT9uBNr+jZw4SsluQzXG1X lFL/qCBoi1N2mqKPIepfGYF6drbr1RnXEJJsuD+NILLooTNf7PMgHPZ4VSWQXLNeFfygoOOK FiO0qfxPKpDMA+FHa8yNjAJZAgdJX5Mm1kbqipvb+r/H1UAmrzGMbhmf1gConsT5f8KU4n3Q IM2sOpTQe7BoVKlQM/fpQi6aBzu67M1iF1WtODpa5QUPvj1etaK+R3eYBzi4DIbCIWst8MdA 1+fEeKJFvMEZQONpkCwrJ+tJEuGQmjoQZgK1HeloepF0WDcviiho5FlgtAij+iBPtwMuuLiL shAXA5afMX1hYM4l11JXntle12EQFP1r6wOUkpOdxceCcMVDEJBBCHW2ZmdEaXgAm1VU+fnQ qS/wNw/S0X3RJT1qjr5uVlp2Y0auG/eG0jy6TT0KzTJeR9tLSDXprYkN2l/Qf7/nT6Q03qyE QnnKiBXWAZXveafyU/zYa7t3PTWFQGgWoC4w6XqgPo4KV44OMYIFBzCCBQMCAQEwgZIwezEL MAkGA1UEBhMCVVMxEDAOBgNVBAgMB0Zsb3JpZGExGTAXBgNVBAoMEEN1ZGEgU3lzdGVtcyBM TEMxGDAWBgNVBAsMD0N1ZGEgU3lzdGVtcyBDQTElMCMGA1UEAwwcQ3VkYSBTeXN0ZW1zIExM QyAyMDE3IEludCBDQQITAKDRa9XB6SMYWI7rZJyQXB6nPTANBglghkgBZQMEAgMFAKCCAkUw GAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTgwMTE1MTg0NDE3 WjBPBgkqhkiG9w0BCQQxQgRAZMQ1tP2xgyJljg6h8avr/0SirdhCdOlCL3K4W0t/W0zPcLTH XzoWiRyhVf3mtX2USBoz8JqvuErErdTVRPk92jBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFl AwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3 DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIGjBgkrBgEEAYI3EAQxgZUwgZIwezEL MAkGA1UEBhMCVVMxEDAOBgNVBAgMB0Zsb3JpZGExGTAXBgNVBAoMEEN1ZGEgU3lzdGVtcyBM TEMxGDAWBgNVBAsMD0N1ZGEgU3lzdGVtcyBDQTElMCMGA1UEAwwcQ3VkYSBTeXN0ZW1zIExM QyAyMDE3IEludCBDQQITAKDRa9XB6SMYWI7rZJyQXB6nPTCBpQYLKoZIhvcNAQkQAgsxgZWg gZIwezELMAkGA1UEBhMCVVMxEDAOBgNVBAgMB0Zsb3JpZGExGTAXBgNVBAoMEEN1ZGEgU3lz dGVtcyBMTEMxGDAWBgNVBAsMD0N1ZGEgU3lzdGVtcyBDQTElMCMGA1UEAwwcQ3VkYSBTeXN0 ZW1zIExMQyAyMDE3IEludCBDQQITAKDRa9XB6SMYWI7rZJyQXB6nPTANBgkqhkiG9w0BAQEF AASCAgBNPmcMrFQZ9Ijya9RVYgMVnU5zT7uGphNKFiPjg8FXibHwZBIw6mRkGNe/4BUoPsJ7 lq8myRi/iSEOnpsOz6FH86SSeMecZSpmvczAj3aMA5vHMBsMcTah5GvdaoMFx1ID+1AjHgyf oEOO6kRYtcyh1iaLRJr+pp5u2sBF0ZFeeOR87a1fLeeY7AKKrWtFgx2XaIk3WWC/SCiuFTGE b1i0ZndntNnataXTIsPO/dFFM9+ADAblswKnbGQU6mAtkRx9myXxpHc7tdL2WvBPdRWX/rhG VHVAMyIiDRvfsgpjCeWA6Dbqg3i4UnfOK8218A4bmrqubC0649YllMsjceFGKNABfwNOrE8L UchPiCwI71uxAHhfs6jk5Tk7Yu1ycyKvm4x4WzKKmH3NeEvaT0nYLB2115ZTREeKCrf2m0zG 8U4SpH5GBpauGFZFWwNFrpDNS4BWsmT004IABHU6Yp+1LcL/SIiuvAZUwFTCzx/X1Rl/VTGT uTv+KEYj4CQpx3LJU1vO4aiu2fyTbCzHyiaSui0pE+XoTi9b2XUqL+QUsYKB7Aff4ShVy/J0 mLl02fN6DlFO4MwzQ1IwEjrr+ZCMh10zX2JjPoUv3Hzpx9zzGTEz5V1PF8hPkPreH48LDl8T HZhZ/KRc+NkWs9N7sGjTuWKlfUqyIk4t8e/9zvgGHwAAAAAAAA== --------------ms060309080303030309090601-- From owner-freebsd-current@freebsd.org Mon Jan 15 20:59:22 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5CE45E764D0 for ; Mon, 15 Jan 2018 20:59:22 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 460F86D905 for ; Mon, 15 Jan 2018 20:59:22 +0000 (UTC) (envelope-from ian@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 4282CE764CF; Mon, 15 Jan 2018 20:59:22 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 421FAE764CD for ; Mon, 15 Jan 2018 20:59:22 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [52.58.109.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D80EA6D904 for ; Mon, 15 Jan 2018 20:59:21 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: cb513b7a-fa36-11e7-8dac-d32f5c2d02ef X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id cb513b7a-fa36-11e7-8dac-d32f5c2d02ef; Mon, 15 Jan 2018 20:58:11 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w0FKw6UA002197; Mon, 15 Jan 2018 13:58:06 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1516049886.11182.24.camel@freebsd.org> Subject: Re: Building kernel with no sound From: Ian Lepore To: Alexander Sieg , FreeBSD Current Date: Mon, 15 Jan 2018 13:58:06 -0700 In-Reply-To: <86tvvn2dlq.fsf@xanderio.de> References: <86tvvn2dlq.fsf@xanderio.de> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.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, 15 Jan 2018 20:59:22 -0000 On Mon, 2018-01-15 at 19:14 +0100, Alexander Sieg wrote: > Hey, > i´m trying to build a custom kernel with no sound support build in. > > This is my make.conf: > MALLOC_PRODUCTION=true > KERNCONF=MYKERNEL #GENERIC-NODEBUG > DEVELOPER=yes > > and this is my kernel configuration: > include GENERIC-NODEBUG > > ident   MYKERNEL > > nodevice sound  # Generic sound driver (required) > nodevice snd_es137x # Ensoniq AUdioPCI ES137x > nodevice snd_hda # Intel High Definition Audio > nodevice snd_ich # Intel, Nvidia and other ICH AC'97 audio > nodevice snd_uaudio # USB Audio > nodevice snd_via8233 # VIA VT823x Audio > > > The problem is when i try to compile it with "make buildkernel" the > build process starts, but it stop with the error that it can´t find the > header file "channel_if.h". > > /usr/src/sys/dev/sound/pcm/channel.h:256:10: fatal error: 'channel_if.h' file not found > #include "channel_if.h" >          ^~~~~~~~~~~~~~ > > The intention behind the custom kernel is to try 'oss' form the > ports tree. I think your nodevice list isn't quite complete.  Grepping for snd_ in i386 and amd64 GENERIC, I come up with this list:  snd_cmi      # CMedia CMI8338/CMI8738  snd_csa      # Crystal Semiconductor CS461x/428x  snd_emu10kx  # Creative SoundBlaster Live! and Audigy  snd_es137x   # Ensoniq AudioPCI ES137x  snd_hda      # Intel High Definition Audio  snd_ich      # Intel, NVidia and other ICH AC'97 Audio  snd_via8233  # VIA VT8233x Audio -- Ian From owner-freebsd-current@freebsd.org Mon Jan 15 23:19:13 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7B7C5E7E42B for ; Mon, 15 Jan 2018 23:19:13 +0000 (UTC) (envelope-from kremels@kreme.com) Received: from mail.covisp.net (mail.covisp.net [65.121.55.42]) (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 671F3754A9 for ; Mon, 15 Jan 2018 23:19:13 +0000 (UTC) (envelope-from kremels@kreme.com) Received: from mail.covisp.net (localhost [127.0.0.1]) by mail.covisp.net (Postfix) with ESMTP id 3zL8JD3x3bzxbCl; Mon, 15 Jan 2018 16:12:12 -0700 (MST) X-Virus-Scanned: amavisd-new at covisp.net Received: from mail.covisp.net ([127.0.0.1]) by mail.covisp.net (mail.covisp.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KExs00LX-d0i; Mon, 15 Jan 2018 16:12:11 -0700 (MST) From: "@lbutlr" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Copying to a new computer Message-Id: Date: Mon, 15 Jan 2018 16:12:10 -0700 To: FreeBSD Current X-Mailer: Apple Mail (2.3445.5.20) X-Mailman-Approved-At: Mon, 15 Jan 2018 23:50: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: Mon, 15 Jan 2018 23:19:13 -0000 I am replacing an old machine with a newer machine and I want to be sure = I can move the shell users to the new machine, especially since I am = mostly going too be setting up the machine as new. What are the minimal files that I need to copy over so that the users = and groups from the old machine are on the new machine and without = having to reset all the passwords? (Most the users are in sql databases, so that's not an issue, but there = are a few with shell accounts, those are the ones I'm concerned with. I was intending to stick with v11.1 at this point. --=20 We are born naked, wet and hungry; then it's all downhill. From owner-freebsd-current@freebsd.org Tue Jan 16 00:15:29 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D1A0BEA64AA for ; Tue, 16 Jan 2018 00:15:29 +0000 (UTC) (envelope-from SRS0=A9O1=EL=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (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 976F0775F3 for ; Tue, 16 Jan 2018 00:15:29 +0000 (UTC) (envelope-from SRS0=A9O1=EL=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 250BE28417; Tue, 16 Jan 2018 01:15:21 +0100 (CET) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 881462840C; Tue, 16 Jan 2018 01:15:19 +0100 (CET) Subject: Re: Copying to a new computer To: kremels@kreme.com, FreeBSD Current References: From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <5A5D4417.2020106@quip.cz> Date: Tue, 16 Jan 2018 01:15:19 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:42.0) Gecko/20100101 Firefox/42.0 SeaMonkey/2.39 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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: Tue, 16 Jan 2018 00:15:29 -0000 @lbutlr wrote on 2018/01/16 00:12: > I am replacing an old machine with a newer machine and I want to be sure I can move the shell users to the new machine, especially since I am mostly going too be setting up the machine as new. > > What are the minimal files that I need to copy over so that the users and groups from the old machine are on the new machine and without having to reset all the passwords? > > (Most the users are in sql databases, so that's not an issue, but there are a few with shell accounts, those are the ones I'm concerned with. > > I was intending to stick with v11.1 at this point. You can copy these files: /etc/group /etc/login.conf /etc/master.passwd /etc/passwd And DB files /etc/login.conf.db /etc/pwd.db /etc/spwd.db Or you can recreate them with pwd_mkdb and cap_mkdb (see their man pages) If you installed some shells like bash or zsh for users, then you must installed them too and verify /etc/shells settings. Additionally you may need a copy of /etc/profile and /etc/csh.cshrc if you modified them. Miroslav Lachman From owner-freebsd-current@freebsd.org Tue Jan 16 03:46:23 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A9220E6F676 for ; Tue, 16 Jan 2018 03:46:23 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 92CA8828F8 for ; Tue, 16 Jan 2018 03:46:23 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.26] (cpe-23-242-94-236.socal.res.rr.com [23.242.94.236]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 0ee6acad TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO for ; Mon, 15 Jan 2018 19:45:57 -0800 (PST) Subject: [SOLVED] Re: Kernel Panic On Boot after r327979 From: Pete Wright To: freebsd-current@freebsd.org References: Message-ID: <76287df0-9f92-d23b-dac7-97daeb11d584@nomadlogic.org> Date: Mon, 15 Jan 2018 19:46:22 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jan 2018 03:46:23 -0000 On 01/15/2018 09:26, Pete Wright wrote: > Hello, > > I updated an amd64 system last night to r327979 and it panics into gdb > after rc attempts to mount local filesystems. > > The panic line is: > Fatal trap 12: page fault while in kernel mode > > gdb states that it stopped at: > Stopped at    prison_allow+0x4    movq    0x30(%rdi),%rax > > > Is this a known issue?  This is my primary workstation - so I'm going > to revert back to an older kernel, but if more info is needed I can > put some cycles into debugging today. > closing the loop on this.  it looks like the panic was due to debugfs being mounted on my system.  debugfs is part of the drm-next-kmod port which enables i915 gfx on recent intel GPU's, and debugfs doesn't *need* to be mounted but is quite useful and fun to play with. anywho - the fix on my end is to: - remove the drm-next-kmod port/pkg - build and install latest kernel+world - reboot and build/install the drm-next-kmod port/pkg - reboot and enjoy i915 graphics i'm kinda interested in what prison_allow does now as i haven't run across it before.  is this part of the jails infrastrucutre? cheers, -p -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Tue Jan 16 20:24:03 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E84FEEB6421 for ; Tue, 16 Jan 2018 20:24:03 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: from mail-it0-f51.google.com (mail-it0-f51.google.com [209.85.214.51]) (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 B92466B69F for ; Tue, 16 Jan 2018 20:24:03 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: by mail-it0-f51.google.com with SMTP id x42so6400213ita.4 for ; Tue, 16 Jan 2018 12:24:03 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=W0VVKUcDu/GTByYdF44xv9uC/yYbKZSX4R+ias8mEqc=; b=n5pryevBFDFxe/98wc2E/FPfWlVUuN5iAFmDeprkcyYzDcgJ70lcTK1qve/cIHvfBd oTW7UU12TrjlynQEzyfYzjuFIcCk+8cvznBO63qBkGu3nK2UpFtKruYbtSwpd2SzwXbX a/ZmCblAabvZeVX4kQQtFtC1w6HNSzERaNO7fLHH6MOy4TcvMtICTaFcCD0u4UdYdb/D oUIDY1EaIse4T9Ze0uQ0k3GEdXbANRU/cnWXkdoS/jW9wUMwPh6Dak+E6KWmxWMOXluY 5CPYSK2faNVLm3WMpEl4IWTvouN1mL9XNzY2nXjH+MosC9M4FQFTuHwdi3bnXVRhZS0G nc1g== X-Gm-Message-State: AKwxytcrgOfDRDhXRX7RijxH5b+shu2+y8jU2y4fE1fhJK9mzSOXWGh8 MrOVEwDt616fBsMwu3Z2FhVaJTZ/ X-Google-Smtp-Source: ACJfBot/HXpYd/ahOiDT2VCmmtWM5+IX86lngQ31djvZZ7nlsjmnzEZU4NyVTyXj/UtEygb29N+cWA== X-Received: by 10.36.166.13 with SMTP id q13mr19016913ite.37.1516133736035; Tue, 16 Jan 2018 12:15:36 -0800 (PST) Received: from mail-io0-f177.google.com (mail-io0-f177.google.com. [209.85.223.177]) by smtp.gmail.com with ESMTPSA id r186sm1491146itb.13.2018.01.16.12.15.35 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 16 Jan 2018 12:15:35 -0800 (PST) Received: by mail-io0-f177.google.com with SMTP id b198so15520700iof.6 for ; Tue, 16 Jan 2018 12:15:35 -0800 (PST) X-Received: by 10.107.20.200 with SMTP id 191mr2543887iou.239.1516133735216; Tue, 16 Jan 2018 12:15:35 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.149.147 with HTTP; Tue, 16 Jan 2018 12:15:14 -0800 (PST) In-Reply-To: <2738677.q6K2ErXNlp@gizmo.my.domain> References: <2738677.q6K2ErXNlp@gizmo.my.domain> From: Kyle Evans Date: Tue, 16 Jan 2018 14:15:14 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: r328032 broke service To: Oleg Ginzburg Cc: freebsd-current@freebsd.org, dor.bsd@xm0.uk Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jan 2018 20:24:04 -0000 On Tue, Jan 16, 2018 at 5:00 PM, Oleg Ginzburg wrote: > Looks like https://svnweb.freebsd.org/base?view=revision&revision=r328032 > breaks any other arguments except '-j' for service(8) Apologies, fixed in r328060 =( From owner-freebsd-current@freebsd.org Tue Jan 16 19:58:21 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0324DEB4EAF for ; Tue, 16 Jan 2018 19:58:21 +0000 (UTC) (envelope-from olevole@olevole.ru) Received: from mail-lf0-x22b.google.com (mail-lf0-x22b.google.com [IPv6:2a00:1450:4010:c07::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 9EF0C6A60F for ; Tue, 16 Jan 2018 19:58:20 +0000 (UTC) (envelope-from olevole@olevole.ru) Received: by mail-lf0-x22b.google.com with SMTP id q17so8748994lfa.9 for ; Tue, 16 Jan 2018 11:58:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=olevole-ru.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:user-agent:mime-version :content-transfer-encoding; bh=JmtApXf8QeGVgGSH4GU08s3iqPXzGcUZgb9qFtSIGjA=; b=JQ0KakMsSvTM2+97EiKpYD8cGGNu920UW2OraIoWErWgjo0NO8uRbK7Ij70H/Uw6vv RSRS7uxr/Igx19I/iiGWWHu36AMqhfMwE2Fyix984r74ztUyiydbLpNJm2ICLvwC6FsF 0e0+h/DNOBECqYOb+cMoWJRbQXZ29kNin9F7IgqhUK+K6dDLvICNVhFSvc7olRj1TKms NGYjqgXfy1NNLwcYyNfMk7nIsGI6bbrWAkydkcDGvy3sCvjv0pNCaaRW5v/lWV9MPuc/ x5sk+HgyjIi2Y3pzf/0R9t81cWjmDyv5O3LF+8h76F0ZPr4MwNRXg4MC6Rv7T0K4rL8/ PAXA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:user-agent :mime-version:content-transfer-encoding; bh=JmtApXf8QeGVgGSH4GU08s3iqPXzGcUZgb9qFtSIGjA=; b=Ss7QiKLP4ocbw6JJD9cq0jiJ/lFZ9Zq3b4UfdgD1s13IG9+0QkjEF50xSfc8pDRgpz OBTEMcolVHc4ZSK2RVzGh3gjAWpuzbrnE+W89QmkUoVNqB0OrWCDLhwIkGfgQLpvUGsv oAScyBswj2XZSjRXestl/vA7X9LuddvBfYnSx65dDbHlIeZ+498josvcJBsY/mVt8Ab1 /xQejTxNaxj2PANK2wsHeZV75iR5N9LjiBPumB1gAEy7yEpvCPr8kHA38hULi6iKWzFM N/X/rAtII6riDt6QfZr7KXJoRGy0CDtLfQblQmBlyYMDk8+2bduqFY2h9qB8kKGhWCFz ZaKA== X-Gm-Message-State: AKwxytfYpNppq31a45hefdfNJyqCY3F2Y9ZlVwz3uvJbKrOQ1OMQyjz4 k4RFR6iR6wIZt9NFJqv1l5VcCnuH X-Google-Smtp-Source: ACJfBovAzg5hWuGPpwQdV+VEc7FePh0CCdIM/IXSx1YFG+2Wq6K8WfklbIhGZlEZ046slk678MWKBA== X-Received: by 10.25.56.77 with SMTP id d13mr546893lfj.46.1516132698286; Tue, 16 Jan 2018 11:58:18 -0800 (PST) Received: from gizmo.my.domain (95-27-46-131.broadband.corbina.ru. [95.27.46.131]) by smtp.gmail.com with ESMTPSA id b84sm529039ljf.87.2018.01.16.11.58.17 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 16 Jan 2018 11:58:17 -0800 (PST) From: Oleg Ginzburg To: freebsd-current@freebsd.org Cc: kevans@freebsd.org, dor.bsd@xm0.uk Subject: r328032 broke service Date: Tue, 16 Jan 2018 23:00:08 +0000 Message-ID: <2738677.q6K2ErXNlp@gizmo.my.domain> User-Agent: KMail/4.14.10 (FreeBSD/12.0-CURRENT; KDE/4.14.30; amd64; ; ) MIME-Version: 1.0 X-Mailman-Approved-At: Tue, 16 Jan 2018 20:36:36 +0000 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit 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, 16 Jan 2018 19:58:21 -0000 Looks like https://svnweb.freebsd.org/base?view=revi sion&revision=r328032 breaks any other arguments except '-j' for service(8) From owner-freebsd-current@freebsd.org Tue Jan 16 21:36:11 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C66BCEB9989 for ; Tue, 16 Jan 2018 21:36:11 +0000 (UTC) (envelope-from rezaee.hadi@gmail.com) Received: from mail-lf0-x229.google.com (mail-lf0-x229.google.com [IPv6:2a00:1450:4010:c07::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 484246E17C; Tue, 16 Jan 2018 21:36:11 +0000 (UTC) (envelope-from rezaee.hadi@gmail.com) Received: by mail-lf0-x229.google.com with SMTP id t139so4475887lff.0; Tue, 16 Jan 2018 13:36:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Q0l93dw8qJn9o9pg1yMm0ktK5xKClpdL+KJySLOYVEw=; b=Y6XdT1oqpHg00uEqukC1HfXQT8qZ1/OkcHbVB0W63LuGoA548cpumR2tvxEn4sXoLj ZPZ04kQAuv9vymIX5rAwjuekyRGJXGvyl6l1+0+P+UShOoGcpnyeUD7gI/KIcwSEax0c /kQi6jSEv6YzttE+PH/vMxh9hibjRPoi5XZvaIpJSpFNC/9Gaakrm6zVuPu5A25Uy2Xi fUEWpkKfmtxv1GTE4zoJdriNqUWevdWDl8oFaoErWnscXLsKWb8VQAUCNpAkgA0XgN5/ 93HBsjjuMS3QMNv30Nfu0IqV36j3eJ3QGfMtyyi4MiVfVpN+G8h0R4eUb2uYoepeH1i9 Jmow== 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=Q0l93dw8qJn9o9pg1yMm0ktK5xKClpdL+KJySLOYVEw=; b=SlDIScK4LtsTz5dgL44r2yrgSwAwMVIoPsQXnUvk5Gg96wCuZ9V+/Qw+quIs6mxAgO SWwnBAR1O7SPxN6ReMhp1KG7XVFulai7ufAXIwLCZivfhEOaIqwo5pLanikRDl5Eb1sr fiX9TdGzPXSCY3O+eKFdRGJ4+lhvWl3vrlcW3eSY2SWUVSPxkRM/r7PR+LcdGtKfO18H SAkfBvSst1MmrnKz+IwbJV+gl2QHrc1qJuVbW2opt5MpWhnuHxD95jM3hxBQj9J9tqG4 47ddGEUkuhH5fv9XXpZxrl8DkHcXETXQuKNQWweJz2vJPj244VQ81PC74UkTP3C2oins 7wYw== X-Gm-Message-State: AKGB3mIyJP9WjOmtQZt2JgujMJEzqMkPIGm7ADpzPfYF61ZbavgZnLn9 13RjCuyyqVksGcSKRicPmEyZrrpmqg6ZO5tA+Q0= X-Google-Smtp-Source: ACJfBourtsjdrNA60l2xcK81UPkuiE+H/Vm6cnCNbWFFfiPwhEO9sLu9kp9/PgAYovvy+0Zp8mVnTlBaSbnXQxc6oQs= X-Received: by 10.46.60.22 with SMTP id j22mr25314030lja.111.1516138569066; Tue, 16 Jan 2018 13:36:09 -0800 (PST) MIME-Version: 1.0 References: <2738677.q6K2ErXNlp@gizmo.my.domain> In-Reply-To: From: Hadi Rezaee Date: Tue, 16 Jan 2018 21:35:58 +0000 Message-ID: Subject: Re: r328032 broke service To: Kyle Evans Cc: Oleg Ginzburg , dor.bsd@xm0.uk, freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jan 2018 21:36:11 -0000 Yea actually wanted to report this as soon as i fix the problem on laptop ^^ On Tue, Jan 16, 2018 at 11:54 PM Kyle Evans wrote: > On Tue, Jan 16, 2018 at 5:00 PM, Oleg Ginzburg wrote: > > Looks like > https://svnweb.freebsd.org/base?view=revision&revision=r328032 > > breaks any other arguments except '-j' for service(8) > > Apologies, fixed in r328060 =( > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@freebsd.org Wed Jan 17 11:04:04 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BB840EBD521; Wed, 17 Jan 2018 11:04:04 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 26AE768C68; Wed, 17 Jan 2018 11:04:03 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from freyja.zeit4.iv.bundesimmobilien.de ([87.138.105.249]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0LkfdE-1f9znb3EYe-00aVHA; Wed, 17 Jan 2018 12:03:55 +0100 Date: Wed, 17 Jan 2018 12:03:55 +0100 From: "O. Hartmann" To: freebsd-current , freebsd-ports Subject: CLANG6, java/openjdk[7|8] compiler error: atomic.inline.hpp:70 error: unknown token in expression __asm__ volatile Message-ID: <20180117120355.70cb5521@freyja.zeit4.iv.bundesimmobilien.de> Organization: Walstatt MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:HkksLew1CdgN5q8rlgoIBaXOVHZ0+tPvBZeZQP+EEg3UrqEafzJ 78FtjWXEESBcgoGnMLdwqkaqmqY57a80d4uAYy8GtPVM1WVOFCh5JDYdqfXdqk57Pi2BTA6 ejAWztlZ0zFsZlfW/O1t69MmhAkj9BQSfbrBmP5E7qreqVdduLC3ENofdlwCcWvF4Hf/0SV DjNpb9GDmGvwh1k7YZbtg== X-UI-Out-Filterresults: notjunk:1;V01:K0:zXxhj5rTyHg=:XrbYDnDAu6WnvqJqMIfBCb NmMzKoGXn62Fcs30zyJ1NoO3ekz4hGzlnBjDWKV4vta6V0RvDfDhmQJxJC/Etzn4wy+ByPdQn i2/vrywyX9ffYL74HgHHR4qAVf5lIWwttgylcxTLZjb93wM+snZmwOlAsAJ9LKePa4Yb4b+z5 BOiscUQo2PVkx7RGU+qaTcqIsn9IGNmp9E4HFChxV5xeuzoLnJmaKSSz8KGLSebqe6auvAS1u XuxZYqwd7giIYcerVdXV2EYhSCM9E11sPs6Gn7NR0nlYaDD73itFXfmemCMWfNg+awnqCtzY9 kxuYV3rHh7Hdj5Dj2qqJBagfkpZL+LnQKU0wyz2BXjP6LXN4+EBYtl94rIRlvsgEVIfbl1EvR ngSFOoDL4L5eEp+LKj+Mi9omyhWLtfuERYhYNf8LYb0oCxKtgn0KUno1lFVoGferAWp43gAOp l8F815SyxjdGMfsosFkp79vBEycLD3dd1cbDEmvuXENNPR0/Pr24wCXFOL8xs9fQqCpxcfugW qC5xBONTvMH1evzN9ghc0/1TNhQP993/ohl3OD1YSX7XgAZA+E1gynyCcTxqros2EpE4Z2lSS 80SNUdM5YNpC3Mq5FaeyV8YGqfjhRJ0rNSqr6AZaC9bbGHcZ4w0pbCktj9GqQ8I9ZN8JJGyeo rDlGoufxyQ50hR2WQKVwqUa6QnMSERf6EKwrkH5bO3RGQA56kJbmCFAuUJqtQzeI7pAqSd5l7 BjiRc7REOdu9+IZw70FVRQ0abrSs4zVQMS1DcHEiepjKWWgTALOgXXQdrqBLWrnUgctTaClj4 QCqRlbnBzMHNtYxKVv81GqnFiwVgazoGlby+Pb8NvrTRvJ0Uvo= 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, 17 Jan 2018 11:04:04 -0000 On recent CURRENT (FreeBSD 12.0-CURRENT #0 r328002: Mon Jan 15 15:28:18 CET 2018 amd64) both ports java/openjdk7 and java/openjdk8 fail to compile with devel/openjdk8's error as follows: [...] In file included from /usr/ports/java/openjdk8/work/openjdk/hotspot/src/share/vm/runtime/atomic.inline.hpp:70: /usr/ports/java/openjdk8/work/openjdk/hotspot/src/os_cpu/bsd_x86/vm/atomic_bsd_x86.inline.hpp:95:21: error: unknown token in expression __asm__ volatile (LOCK_IF_MP(%4) "cmpxchgl %1,(%3)" Regards, Oliver From owner-freebsd-current@freebsd.org Wed Jan 17 11:01:19 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A45BBEBD217; Wed, 17 Jan 2018 11:01:19 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0C8A968B04; Wed, 17 Jan 2018 11:01:18 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from freyja.zeit4.iv.bundesimmobilien.de ([87.138.105.249]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0M7H2Y-1enXBQ323i-00x1s0; Wed, 17 Jan 2018 12:01:10 +0100 Date: Wed, 17 Jan 2018 12:01:09 +0100 From: "O. Hartmann" To: freebsd-current , freebsd-ports Subject: CLANG6, java/openjdk[7|8] compiler error: atomic.inline.hpp:70 error: unknown token in expression __asm__ volatile Message-ID: <20180117120109.6b0c16f2@freyja.zeit4.iv.bundesimmobilien.de> Organization: Walstatt MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:kVhN49Pds1R6wslgrK8aKa1esdMX/EokaHn0hbicyNQxuZzlhMl CkuI8igBTchFJgaYFnpk1AWa+PZRzRUpDx9c7XV5HROjTVb7iQcDJaM01btJPLUJd/b09Ra qSD6/YgBvrKAc4P3xo/4RA4s36tIRCqpGy7Yh1NJ1ISabeHSzDZ8UmYBnBKeJSwxK75yE6m +CS+ED2Dt7F5utZe6rRyg== X-UI-Out-Filterresults: notjunk:1;V01:K0:H5MikCGtXGY=:44v22WiUWnJ9p6wYdXIOtO S8feNM4F8y9PPWc5QzrhtVUk3ekSiIP1aJ4W5zcdulLtxk6Pjv2s9YFkH7HFs1nIGRlBYX2dd pPGUYE0wldYo7DacYaSD8O6JGiyERdE2VSnWnioyo2rNlqrsgVt+ONq1jA3sbLuhd7OQvKk/q BDkIjIkkSNoc0PKeJmO9FzN2Am01jCv0S6VZZkpCI+x+Pn3QhxUeKZPLGSM6nDyZKxkqOvcCg FQ7s7HFyTjwTn3ixcyfSwdDHd6NZAzBgkoUmP9qqEqxu4cYjDq9G9Iq/vxFunUviP7GdvA6X7 28iLb0BRtkcFlCuS3VZXXFH9M63iWLaD1GqJ1BmylcVnefdo9Euhfai6cGOOSTfD9kfjQpYy7 28nFKToNajgw6wSxUrAF2mxPYS1SVEyExVHk5ONSYsJNJAP1EVHJxLSlKUDyfy9jPw+myCZcP lihaPCCaBzepsurWCxthhy/OtUk/1zsybtE6b3h639X6YN58OUAy17ilBEpmOPsCub4J6ONMw pujU+X0Oi2G2z4Hvn3+50h+5zG+kY5Uxgw0Mpg/kIAdCL1j70UXDxlaqQOd9UifTQRP09WR43 jauSj+XCqc1DvYMlInpMgpDR8GmXg6XcpMfmo3doncRRuMoEc8xVrEac3gt7WjeKL1uknggLl rF1QGr5LKxIUw4gWvjr5GX11DxSlHUUBNce3hkR4cHCImzQ0CmQYZ5dDTuaj1dX0GhiiuLtx2 2DerRToe//JuHjqGN6wWiGP9NeUhAgf+P/ik7TXZu6LQ6bXJSTwLOD1Z4deLHQ8fG3Y6AjwEN /8cnlxnqFRAEoa4u3p47DdGjG77Y+bhnBrA2fktOgEGFzimfI8= X-Mailman-Approved-At: Wed, 17 Jan 2018 12:03:56 +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: Wed, 17 Jan 2018 11:01:19 -0000 On recent CURRENT (FreeBSD 12.0-CURRENT #0 r328002: Mon Jan 15 15:28:18 CET 2018 amd64) both ports java/openjdk7 and java/openjdk8 fail to compile with devel/openjdk8's error as follows: [...] In file included from /usr/ports/java/openjdk8/work/openjdk/hotspot/src/share/vm/runtime/atomic.inline.hpp:70: /usr/ports/java/openjdk8/work/openjdk/hotspot/src/os_cpu/bsd_x86/vm/atomic_bsd_x86.inline.hpp:95:21: error: unknown token in expression __asm__ volatile (LOCK_IF_MP(%4) "cmpxchgl %1,(%3)" Regards, Oliver From owner-freebsd-current@freebsd.org Wed Jan 17 12:20:04 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 90EBCEC1AEF for ; Wed, 17 Jan 2018 12:20:04 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 7AA176C137 for ; Wed, 17 Jan 2018 12:20:04 +0000 (UTC) (envelope-from david@catwhisker.org) Received: by mailman.ysv.freebsd.org (Postfix) id 7700EEC1AEE; Wed, 17 Jan 2018 12:20:04 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 769DEEC1AED for ; Wed, 17 Jan 2018 12:20:04 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 425966C136 for ; Wed, 17 Jan 2018 12:20:03 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id w0HCJuSG048243 for ; Wed, 17 Jan 2018 12:19:56 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id w0HCJuge048242 for current@freebsd.org; Wed, 17 Jan 2018 04:19:56 -0800 (PST) (envelope-from david) Date: Wed, 17 Jan 2018 04:19:56 -0800 From: David Wolfskill To: current@freebsd.org Subject: r328075 appears to break sbin/fsdb Message-ID: <20180117121956.GS1241@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="MhDS85o8hQkNlKhq" 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, 17 Jan 2018 12:20:04 -0000 --MhDS85o8hQkNlKhq Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable As O. Hartmann noted (in svn-src-head@), the change to rename cgget to cglookup also affects fsdb: --- all_subdir_sbin/fsdb --- --- fsdb.o --- /usr/src/sbin/fsdb/fsdb.c:479:9: error: implicit declaration of function 'c= gget' is invalid in C99 [-Werror,-Wimplicit-function-declaration] cgbp =3D cgget(c); ^ /usr/src/sbin/fsdb/fsdb.c:479:7: error: incompatible integer to pointer con= version assigning to 'struct bufarea *' from 'int' [-Werror,-Wint-conversio= n] cgbp =3D cgget(c); ^ ~~~~~~~~ 2 errors generated. --- all_subdir_usr.bin --- I suspect that replacing "cgget" with "cglookup" in src/sbin/fsdb/fsdb.c:479 will fix it. Peace, david --=20 David H. Wolfskill david@catwhisker.org "unfortunately, no trust!=E2=80=9D -- well, of course! You reap what you s= ow. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --MhDS85o8hQkNlKhq Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEzLfO+ReoAfQwZNd7FTnMQKBJ7hcFAlpfP2xfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEND QjdDRUY5MTdBODAxRjQzMDY0RDc3QjE1MzlDQzQwQTA0OUVFMTcACgkQFTnMQKBJ 7her0wgAsELMnYKKmF8Ia+9ZpVIRQlXx9MMtHPafyOn50uIaWgT6WBzBmQtqYgaY fv4KANc3Lbhsdbr+zjQktyRPoda8in58Y4c7dtTHbANLoEZCTAkEMbUXf8q9tr8E v9K6y7WsV15MD6J+6svpc1Ex8Q1bsD1xTmR49yyYnvBZGuI5WSH1h4hein1NsjQT qsDEDHwa7dtg4+enBcLTdWfB5s9Fiq6Y931M3Pfsb3SlUvHdGNP2DS1ArK12v2ME 2B+XdtSKMpNNTaUyQVlM86Ireju36ry+MJmz1WcfcimMDsBGIzVXY3edXwxFwtcw vT8SPujWEtuHObx/ACRk1DFv8zUfsw== =Xyv1 -----END PGP SIGNATURE----- --MhDS85o8hQkNlKhq-- From owner-freebsd-current@freebsd.org Wed Jan 17 12:34:23 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 59CE4EC2790; Wed, 17 Jan 2018 12:34:23 +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 1D9626CAC0; Wed, 17 Jan 2018 12:34:22 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from coleburn.avinity.tv (unknown [77.95.97.98]) (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 161455FBF; Wed, 17 Jan 2018 13:34:19 +0100 (CET) From: Dimitry Andric Message-Id: Content-Type: multipart/signed; boundary="Apple-Mail=_C90CCE19-7848-466B-851C-A645F4377A8E"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: CLANG6, java/openjdk[7|8] compiler error: atomic.inline.hpp:70 error: unknown token in expression __asm__ volatile Date: Wed, 17 Jan 2018 13:34:18 +0100 In-Reply-To: <20180117120109.6b0c16f2@freyja.zeit4.iv.bundesimmobilien.de> Cc: freebsd-current , freebsd-ports To: "O. Hartmann" References: <20180117120109.6b0c16f2@freyja.zeit4.iv.bundesimmobilien.de> X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jan 2018 12:34:23 -0000 --Apple-Mail=_C90CCE19-7848-466B-851C-A645F4377A8E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 17 Jan 2018, at 12:01, O. Hartmann wrote: >=20 > On recent CURRENT (FreeBSD 12.0-CURRENT #0 r328002: Mon Jan 15 = 15:28:18 CET > 2018 amd64) both ports java/openjdk7 and java/openjdk8 fail to compile = with > devel/openjdk8's error as follows: >=20 >=20 > [...] > In file included > from = /usr/ports/java/openjdk8/work/openjdk/hotspot/src/share/vm/runtime/atomic.= inline.hpp:70: = /usr/ports/java/openjdk8/work/openjdk/hotspot/src/os_cpu/bsd_x86/vm/atomic= _bsd_x86.inline.hpp:95:21: > error: unknown token in expression __asm__ volatile (LOCK_IF_MP(%4) = "cmpxchgl > %1,(%3)" I had the idea this was worked around already, but I am planning on committing an upstream fix for this very soon. -Dimitry --Apple-Mail=_C90CCE19-7848-466B-851C-A645F4377A8E 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 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCWl9CygAKCRCwXqMKLiCW o7nQAJsFQvxOeZAbeeOqZq8KBhNgRWnbowCgrXZ/l/SLTjpJuujwyatl3138EII= =3HIG -----END PGP SIGNATURE----- --Apple-Mail=_C90CCE19-7848-466B-851C-A645F4377A8E-- From owner-freebsd-current@freebsd.org Wed Jan 17 12:35:11 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 648EEEC2915 for ; Wed, 17 Jan 2018 12:35:11 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from forward103j.mail.yandex.net (forward103j.mail.yandex.net [IPv6:2a02:6b8:0:801:2::106]) (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 1C9E76CCDD for ; Wed, 17 Jan 2018 12:35:10 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from mxback15g.mail.yandex.net (mxback15g.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:94]) by forward103j.mail.yandex.net (Yandex) with ESMTP id F01BB34C4E12 for ; Wed, 17 Jan 2018 15:34:58 +0300 (MSK) Received: from smtp2p.mail.yandex.net (smtp2p.mail.yandex.net [2a02:6b8:0:1472:2741:0:8b6:7]) by mxback15g.mail.yandex.net (nwsmtp/Yandex) with ESMTP id wsOSSeZiqF-YwSGvkTf; Wed, 17 Jan 2018 15:34:58 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=passap.ru; s=mail; t=1516192498; bh=0gFk4UntPpCVmxOIroWSU20EDWwFyXXVEKeNDm0dJiM=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=FCbUZbAkiQFCAVKnlnMCLFhxutseF/drYeVsuPbxkrQlAC0bGtaoxG3ES61LUmO9m JE5Zoe5sawNBnmVCUM7OSCg/EX+0zAcCwYmSgkwh2uGp8mT5RolAxibnVux8dhsK9l 1OLUlptjP/r9jeYfOPAIaso46d/OrHKvUro80u1k= Received: by smtp2p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id ztWofgOLlx-YpdunksQ; Wed, 17 Jan 2018 15:34:51 +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=1516192491; bh=0gFk4UntPpCVmxOIroWSU20EDWwFyXXVEKeNDm0dJiM=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=pjPht1Mxwhx8GlOfsBdpLBHIgqA3HUtXBfgDfhZGFtsNP7qnHSWkmEWr/LkxFC2bm xTF2lQOUdlBuIjAsekO0rqmcHUpWWeJ24MlbXZk0KCFef98T5EPuQoGweGhYUFajtV s5SdOs1n/NmT5GvFlSpkj1upjXQoOnDSZwzpzAM8= Authentication-Results: smtp2p.mail.yandex.net; dkim=pass header.i=@passap.ru Subject: Re: CLANG6, java/openjdk[7|8] compiler error: atomic.inline.hpp:70 error: unknown token in expression __asm__ volatile To: freebsd-current@freebsd.org References: <20180117120109.6b0c16f2@freyja.zeit4.iv.bundesimmobilien.de> From: Boris Samorodov Message-ID: <9c50b1a1-03e8-03fa-994a-4fd72a161046@passap.ru> Date: Wed, 17 Jan 2018 15:34:51 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <20180117120109.6b0c16f2@freyja.zeit4.iv.bundesimmobilien.de> 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, 17 Jan 2018 12:35:11 -0000 Hi Oliver, All! 17.01.2018 14:01, O. Hartmann пишет: > On recent CURRENT (FreeBSD 12.0-CURRENT #0 r328002: Mon Jan 15 15:28:18 CET > 2018 amd64) both ports java/openjdk7 and java/openjdk8 fail to compile with > devel/openjdk8's error as follows: > > [...] > In file included > from /usr/ports/java/openjdk8/work/openjdk/hotspot/src/share/vm/runtime/atomic.inline.hpp:70: /usr/ports/java/openjdk8/work/openjdk/hotspot/src/os_cpu/bsd_x86/vm/atomic_bsd_x86.inline.hpp:95:21: > error: unknown token in expression __asm__ volatile (LOCK_IF_MP(%4) "cmpxchgl > %1,(%3)" There is an open PR on the matter: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225054 -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From owner-freebsd-current@freebsd.org Wed Jan 17 13:00:38 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B925FEC3C03 for ; Wed, 17 Jan 2018 13:00:38 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2AF336DB20 for ; Wed, 17 Jan 2018 13:00:37 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from freyja.zeit4.iv.bundesimmobilien.de ([87.138.105.249]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MO7ee-1eWJgF1AGK-005VWg for ; Wed, 17 Jan 2018 14:00:35 +0100 Date: Wed, 17 Jan 2018 14:00:34 +0100 From: "O. Hartmann" To: freebsd-current Subject: Buildworld broken! r328075 broke the world Message-ID: <20180117140034.14d7fb81@freyja.zeit4.iv.bundesimmobilien.de> Organization: Walstatt MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:9b8VAkCFtc2PMZZ7sNymMVOyN/wAA+Xtv+rTDhiSB0sOWnSQLBx 0M9ucNZNS2f591TfUJYM/igY+EHZMazKAOtZP3oaHY1J1bcG7iFit/jtL9/GETfioeHno+M Onv+oDX7qBG1Qxp0tssmcnJh/AWZ7sQIuuaAxH4cWBfiCl/6VW15x3mmpBv4spDflgwmxL/ yilWxIx8G3zSpFKD0vvfQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:/ZLvm+wu/LA=:sgUy88QHbkrMCdf/ANl17A gG0WYmdmvYg5b3auHPS89uOJ/JhTM2/wEjiK1YbcsHXXM9cvwWo2xA4jJbYak6Vp/O/gqFmRF 4B7zPDyYKXQOW+UcALsRpPv6qU3NTZut6wxP0szWaZ9pedv3Cb1ELRc2tdhNaGCnPAxf8AguZ Ml+FFezENU4R4EA/XwGs/NZ2WicJJI23WwpAIXpYfp9As8wfu9SwPF1qnPiOaeexJKoAVoQAm d2SluHVGWWc2U+dvbPP+wqgCb31nDMF+WEYMFHHQnUpHfdNnkeDdWlDNT5tvkuFDl5qj+3CvI W21vc8fn396Jstp6KRI0Ob6LA2rlz4DH2FvL5vCw68EINqz5rs4Kuk9LwnoW/vRyXT9464ZQz Y8e6WzxvDa247wsu15NsOBgTDnjyEbLYjCR/sRgtYZEmAPk1UyRTLlxqrWRBTqUf49TNxp/J/ b8TfqBRogEw5EkYaX5+jluzmQbaJhlEp3Q8LuVUtBrfHRiAxJ2Mzr+lpkC+I8p4JOrbqUGj72 BOvhwDRhc3BNz+EbYbuIzeZRd1Sen8AMjGDM0g2FPJyZ0XILKZZYLYs2u25LJGf255HIBtQRa rl7EuxNN5ZOk3CcsdEPjjvDxgwd1nv6lQxYNu1jiFk3OImSpMWMpUVGP7ywKLleLQipaTdH3x +Jc1ma/4xQIr2wQEkiZkLOPC/Jcix/ZVlyqSajzsIS6KRSLNT5rZAmA7opCp7tVNX1ZhGZac4 7GtOwb++2KIcgpUFXFAIniisrSLmdSUnwIWRB+RRrErwYycScGWAJMfficcpooq4O+uxagmIA Lvecke6Y7gwHy3gkT876ojbqgTCr70a9KoduCjbxSdHVFOKHy0= 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, 17 Jan 2018 13:00:38 -0000 Please can someon look after the recent CURRENT, it seems that on all systems I try to buildworld most recent sources bail out at: [... WITH_LLD_IS_LD]: Building /usr/obj/usr/src/amd64.amd64/rescue/rescue/rescue /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: cgget >>> referenced by fsdb.lo:(_$$hide$$ fsdb.lo findblk) cc: error: linker command failed with exit code 1 (use -v to see invocation) *** Error code 1 at a stage were world has been compiled from scratch (make cleanworld) or at another point, like [...] ===> sbin/fsdb (all) --- all_subdir_rescue --- `pkill.o' is up to date. --- ps_make --- (cd /usr/src/rescue/rescue/../../bin/ps && make -DRESCUE CRUNCH_CFLAGS=-DRESCUE MK_AUTO_OBJ=yes DIRPRFX=rescue/rescue/ps/ fmt.o keyword.o nlist.o print.o ps.o) --- all_subdir_sbin --- Building /usr/obj/usr/src/amd64.amd64/sbin/fsdb/fsdb --- fsdb --- /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: cgget >>> referenced by fsdb.c >>> fsdb.o:(findblk) cc: error: linker command failed with exit code 1 (use -v to see invocation) *** [fsdb] Error code 1 I think this is related to commit r328075. Thanks in advance, Oliver From owner-freebsd-current@freebsd.org Wed Jan 17 20:20:41 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B1E6EEB4FA2 for ; Wed, 17 Jan 2018 20:20:41 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 926008032B for ; Wed, 17 Jan 2018 20:20:40 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from [192.168.0.6] (67-0-236-88.albq.qwest.net [67.0.236.88]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id C10D21928F3 for ; Wed, 17 Jan 2018 12:13:48 +0000 (UTC) Subject: Re: [CFT] sysutils/devcpu-data Intel microcode migration To: freebsd-current@freebsd.org References: <890da368-7dbf-8d4f-6731-5c6e00cfa662@freebsd.org> From: Sean Bruno Message-ID: <91f0af9b-71a2-5252-f266-aa107ef0203c@freebsd.org> Date: Wed, 17 Jan 2018 13:20:33 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <890da368-7dbf-8d4f-6731-5c6e00cfa662@freebsd.org> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="U18iKPRKH4XafYjeiRdOhYhOyFpHRYPDu" 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, 17 Jan 2018 20:20:41 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --U18iKPRKH4XafYjeiRdOhYhOyFpHRYPDu Content-Type: multipart/mixed; boundary="9mnxSm4AD3c0GazLhCEy2czPwdnPRVmDr"; protected-headers="v1" From: Sean Bruno To: freebsd-current@freebsd.org Message-ID: <91f0af9b-71a2-5252-f266-aa107ef0203c@freebsd.org> Subject: Re: [CFT] sysutils/devcpu-data Intel microcode migration References: <890da368-7dbf-8d4f-6731-5c6e00cfa662@freebsd.org> In-Reply-To: <890da368-7dbf-8d4f-6731-5c6e00cfa662@freebsd.org> --9mnxSm4AD3c0GazLhCEy2czPwdnPRVmDr Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 01/15/18 11:14, Sean Bruno wrote: > https://reviews.freebsd.org/D13921 >=20 > In order to better absorb updates as they appear, I'm proposing that we= > switch from the current model of processing the "microcode.dat" legacy > file to consuming the pre-digested update files. >=20 > This update should not change the microcode version that you previously= > received, but I'd like for folks to give it a spin before we commit yet= > another update to this port. >=20 > sean >=20 *sigh* https://reviews.freebsd.org/D13958 Looks like there are some "discrepancies" in the legacy vs current method of distribution of microcode. sean --9mnxSm4AD3c0GazLhCEy2czPwdnPRVmDr-- --U18iKPRKH4XafYjeiRdOhYhOyFpHRYPDu Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEE6MTp+IA1BOHj9Lo0veT1/om1/LYFAlpfsBFfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEU4 QzRFOUY4ODAzNTA0RTFFM0Y0QkEzNEJERTRGNUZFODlCNUZDQjYACgkQveT1/om1 /LYLWQf9HVYOcH68aVZOEdyqY+16SpXUvnoOalorOLWG6oU44Qhzt4jBTHnj3Rwl coBgzStM8xPky3hLgytKlNmYUw3o5BilMfnX98pI7sd6wON5EZtfQCyoXwI3CeTo PXJxTDYAJoDF2VfqfKYfGlnC7JoQJESMmg+YznXXEHvRTVS+KTPMFnTgcvmmpWzS 9vCSgXAJ7x49PzLNFs7GKjG1kzX9yCMtXLE5eV9ZMGgUEWcEUQy57fLr1p569kaQ eSuBgx5aoMNuaLjfFv6M4bF6JLjBkz4AYGfqPNv3oW5UtXK474B+ewVKdGZrl90Q Md5jSyRpmt+dXjR/KLBPf+7TSuO4eg== =6tyC -----END PGP SIGNATURE----- --U18iKPRKH4XafYjeiRdOhYhOyFpHRYPDu-- From owner-freebsd-current@freebsd.org Thu Jan 18 02:48:24 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EF8C3E75D66 for ; Thu, 18 Jan 2018 02:48:24 +0000 (UTC) (envelope-from ultima1252@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 CA50571170 for ; Thu, 18 Jan 2018 02:48:24 +0000 (UTC) (envelope-from ultima1252@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id C9A03E75D64; Thu, 18 Jan 2018 02:48:24 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C9421E75D63 for ; Thu, 18 Jan 2018 02:48:24 +0000 (UTC) (envelope-from ultima1252@gmail.com) Received: from mail-yw0-x22f.google.com (mail-yw0-x22f.google.com [IPv6:2607:f8b0:4002:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 84E737116F for ; Thu, 18 Jan 2018 02:48:24 +0000 (UTC) (envelope-from ultima1252@gmail.com) Received: by mail-yw0-x22f.google.com with SMTP id m19so10053894ywh.12 for ; Wed, 17 Jan 2018 18:48:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=TYRxIRKBeCqTcdJK1Q8DIPEdX+lfrDHk4ky2nA16ycQ=; b=gzHx+q1LFLezPTO+UtzWhGoB9q5wl+LSJZUB0+Ydqw9DU8uE1gz0sSpE3oJZIGnUkz bAdgOWgF2GaoyQjEcplXainVu9zQC/nxa4ICGE3/oBDfv5WHSifXZkUoXWFDaNO6mE88 iHY80zFzDoMrh1yAGkE8ualNgcsEks2Rcnqq/AUIlHiS7xTdikAcBgXclz2cWZONq4M0 s7zejbl16RNkXs1QB1DHbFDz8rw2xA3H1vQ8WJNriOP+DWX/15QsxrVk72DO9J9hEBjn 2KbaNGS3A77oHEf93t+Na7CqN/pzpEHpi4mwhCLdd1Ik7Jarm6TbiZIKP7D/4bCB9GLP vwDg== 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=TYRxIRKBeCqTcdJK1Q8DIPEdX+lfrDHk4ky2nA16ycQ=; b=YAgUKLaQDyG0JnV5LZmLDAL5BuqmrbAstQzZEAONkOXkaPpiU7k6N1in6t2RrKZFW0 oiLJ+ysE30n2qSxrDO6VI7rCgnINNwAT8lSFbgWUPBXqKP3exJUTDm9wPvQO4WtY+/Ds SKQBF0O813EtBygodG9YXiekaL7wMVdznfTgKHOZv9fx2LqgTG65DwPyPx0h2LWiYMGO dE2V1J79SxXdi3qwWzVBFmEIUoUNEvtHF7ZGVkAUSivzCVJkoCA+RHXHzRfhpZ/S+Euz qo5uVovOeuPbbuzkXq/jdiQsqVsPc0peElNmhqBQBy3T9MKUpS3Vyb4WI/6zUtqckh5x Hewg== X-Gm-Message-State: AKwxytd2IPLQaM+ycpXr5ay/6it/yVKyDyjPfrXaVUrgtq9NDGSEcGbs 8GmeZOF1VNZbKuV+blQ0uPdZLbpNasgy17ltcNarhzrG X-Google-Smtp-Source: ACJfBou1u7kGtvTIw7RCdMLzTbc7uO6sW7HeGeWs9GmFpFiMws43TRCzg04w8Y2j0AN2wAqnr2mGkpJs1brSoDof+Vw= X-Received: by 10.129.116.8 with SMTP id p8mr4623248ywc.386.1516243703531; Wed, 17 Jan 2018 18:48:23 -0800 (PST) MIME-Version: 1.0 Received: by 10.129.74.214 with HTTP; Wed, 17 Jan 2018 18:48:23 -0800 (PST) In-Reply-To: References: From: Ultima Date: Wed, 17 Jan 2018 18:48:23 -0800 Message-ID: Subject: Re: New NUMA support coming to CURRENT To: Jeff Roberson Cc: 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, 18 Jan 2018 02:48:25 -0000 Hello Jeff, Few days ago I upgraded my system firmware, upgraded base to r327991 and altered snooping to cluster-on-die. Its hard to say what is making the server feels like a completely system due to all these changes (also running llvm 6.0), but I am betting it is the NUMA optimizations. It is so responsive! Thanks for the amazing work! Best regards, Richard Gallamore On Sat, Jan 13, 2018 at 7:39 PM, Jeff Roberson wrote: > Hello, > > This work has been committed. It is governed by a new 'NUMA' config > option and 'DEVICE_NUMA' and 'VM_NUMA_ALLOC' have both been retired. This > option is fairly light weight and I will likely enable it in GENERIC before > 12.0 release. > > I have heard reports that switching from a default policy of first-touch > to round-robin has caused some performance regression. You can change the > default policy at runtime by doing the following: > > cpuset -s 1 -n first-touch:all > > This is the default set that all others inherit from. You can query the > current default with: > cpuset -g -s 1 > > I will be investigating the regression and tweaking the default policy > based on performance feedback from multiple workloads. This may take some > time. > > numactl is still functional but deprecated. Man pages will be updated > soonish. > > Thank you for your patience as I work on refining this somewhat involved > feature. > > Thanks, > Jeff > > > On Tue, 9 Jan 2018, Jeff Roberson wrote: > > Hello folks, >> >> I am working on merging improved NUMA support with policy implemented by >> cpuset(2) over the next week. This work has been supported by Dell/EMC's >> Isilon product division and Netflix. You can see some discussion of these >> changes here: >> >> https://reviews.freebsd.org/D13403 >> https://reviews.freebsd.org/D13289 >> https://reviews.freebsd.org/D13545 >> >> The work has been done in user/jeff/numa if you want to look at svn >> history or experiment with the branch. It has been tested by Peter Holm on >> i386 and amd64 and it has been verified to work on arm at various points. >> >> We are working towards compatibility with libnuma and linux mbind. These >> commits will bring in improved support for NUMA in the kernel. There are >> new domain specific allocation functions available to kernel for UMA, >> malloc, kmem_, and vm_page*. busdmamem consumers will automatically be >> placed in the correct domain, bringing automatic improvements to some >> device performance. >> >> cpuset will be able to constrains processes, groups of processes, jails, >> etc. to subsets of the system memory domains, just as it can with sets of >> cpus. It can set default policy for any of the above. Threads can use >> cpusets to set policy that specifies a subset of their visible domains. >> >> Available policies are first-touch (local in linux terms), round-robin >> (similar to linux interleave), and preferred. For now, the default is >> round-robin. You can achieve a fixed domain policy by using round-robin >> with a bitmask of a single domain. As the scheduler and VM become more >> sophisticated we may switch the default to first-touch as linux does. >> >> Currently these features are enabled with VM_NUMA_ALLOC and MAXMEMDOM. >> It will eventually be NUMA/MAXMEMDOM to match SMP/MAXCPU. The current NUMA >> syscalls and VM_NUMA_ALLOC code was 'experimental' and will be deprecated. >> numactl will continue to be supported although cpuset should be preferred >> going forward as it supports the full feature set of the new API. >> >> Thank you for your patience as I deal with the inevitable fallout of such >> sweeping changes. If you do have bugs, please file them in bugzilla, or >> reach out to me directly. I don't always have time to catch up on all of >> my mailing list mail and regretfully things slip through the cracks when >> they are not addressed directly to me. >> >> Thanks, >> Jeff >> >> _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@freebsd.org Thu Jan 18 06:49:22 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 04A71EB781A for ; Thu, 18 Jan 2018 06:49:22 +0000 (UTC) (envelope-from kiri@kx.openedu.org) Received: from kx.openedu.org (flets-sg1027.kamome.or.jp [202.216.24.27]) (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 940497BCD0 for ; Thu, 18 Jan 2018 06:49:20 +0000 (UTC) (envelope-from kiri@kx.openedu.org) Received: from kx.openedu.org (kx.openedu.org [202.216.24.27]) by kx.openedu.org (8.14.5/8.14.5) with ESMTP id w0I6Zfdb083944; Thu, 18 Jan 2018 15:35:41 +0900 (JST) (envelope-from kiri@kx.openedu.org) Message-Id: <201801180635.w0I6Zfdb083944@kx.openedu.org> Date: Thu, 18 Jan 2018 15:35:41 +0900 From: KIRIYAMA Kazuhiko To: freebsd-current@freebsd.org Cc: kiri@kx.openedu.org Subject: SG116j install crashed User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.6 MULE XEmacs/21.4 (patch 22) (Instant Classic) (amd64--freebsd) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") 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: Thu, 18 Jan 2018 06:49:22 -0000 Hi, all I've bought Biccamera's original bland note PC (SG116j) impulsively because of cheapness($1780). I've installed 12.0-CURRENT(r327788) right away. Booted smoothly but set loader conf "unset hint.uart.1.at" and configure disk with mmcsd0 58 GB GPT mmcsd0p1 200MB efi mmcsd0p2 54 GB freebsd-ufs / mmcsd0p3 4.2 GB freebsd-swap none But in "Tetching distribution files" of base.txz, crashed with: sdhci_acpi0-slot0: Controller timeout sdhci_acpi0-slot0: ============== REGISTER DUMP ============== sdhci_acpi0-slot0: Sys addr: 0x02158000 | Version: 0x00001002 sdhci_acpi0-slot0: Blk size: 0x00000200 | Blk cnt: 0x000000f8 sdhci_acpi0-slot0: Argument: 0x017f57e8 | Trn mode: 0x00000027 sdhci_acpi0-slot0: Present: 0x1fff0106 | Host ctl: 0x00001025 sdhci_acpi0-slot0: Power: 0x0000000b | Blk gap: 0x00000080 sdhci_acpi0-slot0: Wake-up: 0x00000000 | Clock: 0x00000007 sdhci_acpi0-slot0: Timeout: 0x00000007 | Int stat: 0x00000001 sdhci_acpi0-slot0: Int enab: 0x05ff0033 | Sig enab: 0x05ff003a sdhci_acpi0-slot0: AC12 err: 0x80000000 | Host ctl2:0x0000008b sdhci_acpi0-slot0: Caps: 0x446cc8b2 | Caps2: 0x00000807 sdhci_acpi0-slot0: Max curr: 0x00000000 | ADMA err: 0x00000000 sdhci_acpi0-slot0: ADMA addr:0x00000000 | Slot int: 0x00000000 sdhci_acpi0-slot0: =========================================== mmcsd0: Error indicated: 1 Timeout : (snip) : Stopped at kdb_enter+0x3b: movq $0,kdb_why db> Detail log has put in [1]. BTW I used [2] so all stuffs are within it and it should not be fetched to internet. Is there any idea to go forth? Best regards. [1] http://35.200.82.201/~kiri/freebsd/sg116j/crash_in_install.jpeg [2] FreeBSD-12.0-CURRENT-amd64-20180110-r327788-memstick.img --- KIRIYAMA Kazuhiko From owner-freebsd-current@freebsd.org Thu Jan 18 12:22:04 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0E84AE75EAF for ; Thu, 18 Jan 2018 12:22:04 +0000 (UTC) (envelope-from kiri@kx.openedu.org) Received: from kx.openedu.org (flets-sg1027.kamome.or.jp [202.216.24.27]) (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 8749D6A0F4 for ; Thu, 18 Jan 2018 12:22:02 +0000 (UTC) (envelope-from kiri@kx.openedu.org) Received: from kx.openedu.org (kx.openedu.org [202.216.24.27]) by kx.openedu.org (8.14.5/8.14.5) with ESMTP id w0ICLvnv089320; Thu, 18 Jan 2018 21:21:59 +0900 (JST) (envelope-from kiri@kx.openedu.org) Message-Id: <201801181221.w0ICLvnv089320@kx.openedu.org> Date: Thu, 18 Jan 2018 21:21:57 +0900 From: KIRIYAMA Kazuhiko To: freebsd-current@freebsd.org Cc: kiri@kx.openedu.org Subject: Re: SG116j install crashed In-Reply-To: <201801180635.w0I6Zfdb083944@kx.openedu.org> References: <201801180635.w0I6Zfdb083944@kx.openedu.org> User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.6 MULE XEmacs/21.4 (patch 22) (Instant Classic) (amd64--freebsd) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=ISO-2022-JP 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, 18 Jan 2018 12:22:04 -0000 At Thu, 18 Jan 2018 15:35:41 +0900, $B;d(B wrote: > > Hi, all > > I've bought Biccamera's original bland note PC (SG116j) > impulsively because of cheapness($1780). I've installed > 12.0-CURRENT(r327788) right away. Booted smoothly but set > loader conf "unset hint.uart.1.at" and configure disk with > > mmcsd0 58 GB GPT > mmcsd0p1 200MB efi > mmcsd0p2 54 GB freebsd-ufs / > mmcsd0p3 4.2 GB freebsd-swap none > > But in "Tetching distribution files" of base.txz, crashed > with: > > sdhci_acpi0-slot0: Controller timeout > sdhci_acpi0-slot0: ============== REGISTER DUMP ============== > sdhci_acpi0-slot0: Sys addr: 0x02158000 | Version: 0x00001002 > sdhci_acpi0-slot0: Blk size: 0x00000200 | Blk cnt: 0x000000f8 > sdhci_acpi0-slot0: Argument: 0x017f57e8 | Trn mode: 0x00000027 > sdhci_acpi0-slot0: Present: 0x1fff0106 | Host ctl: 0x00001025 > sdhci_acpi0-slot0: Power: 0x0000000b | Blk gap: 0x00000080 > sdhci_acpi0-slot0: Wake-up: 0x00000000 | Clock: 0x00000007 > sdhci_acpi0-slot0: Timeout: 0x00000007 | Int stat: 0x00000001 > sdhci_acpi0-slot0: Int enab: 0x05ff0033 | Sig enab: 0x05ff003a > sdhci_acpi0-slot0: AC12 err: 0x80000000 | Host ctl2:0x0000008b > sdhci_acpi0-slot0: Caps: 0x446cc8b2 | Caps2: 0x00000807 > sdhci_acpi0-slot0: Max curr: 0x00000000 | ADMA err: 0x00000000 > sdhci_acpi0-slot0: ADMA addr:0x00000000 | Slot int: 0x00000000 > sdhci_acpi0-slot0: =========================================== > mmcsd0: Error indicated: 1 Timeout > : > (snip) > : > Stopped at kdb_enter+0x3b: movq $0,kdb_why > db> Controller timeout seems to be somtimes occured in latest eMMC devices. demsg shows this machine's eMMC is Intel Bay Trail/Braswell eMMC 4.5/4.5.1 Controller as bellow: acpi_button0: on acpi0 acpi_lid0: on acpi0 acpi_acad0: on acpi0 acpi_tz0: on acpi0 sdhci_acpi0: iomem 0x9183a000-0x9183afff irq 45 on acpi0 mmc0: on sdhci_acpi0 sdhci_acpi1: iomem 0x91836000-0x91836fff irq 47 on acpi0 mmc1: on sdhci_acpi1 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 Is Intel Bay Trail/Braswell eMMC 4.5/4.5.1 Controller currently works on FreeBSD 12.0-CURRENT? # Full dmesg up to [1] # [1] http://35.200.82.201/~kiri/freebsd/sg116j/dmesg.boot > > Detail log has put in [1]. BTW I used [2] so all stuffs are > within it and it should not be fetched to internet. > > Is there any idea to go forth? > > Best regards. > > [1] http://35.200.82.201/~kiri/freebsd/sg116j/crash_in_install.jpeg > [2] FreeBSD-12.0-CURRENT-amd64-20180110-r327788-memstick.img > > --- > KIRIYAMA Kazuhiko > --- KIRIYAMA Kazuhiko From owner-freebsd-current@freebsd.org Thu Jan 18 12:52:24 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4EADFE78295 for ; Thu, 18 Jan 2018 12:52:24 +0000 (UTC) (envelope-from kiri@kx.openedu.org) Received: from kx.openedu.org (flets-sg1027.kamome.or.jp [202.216.24.27]) (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 DCA356B9C7 for ; Thu, 18 Jan 2018 12:52:22 +0000 (UTC) (envelope-from kiri@kx.openedu.org) Received: from kx.openedu.org (kx.openedu.org [202.216.24.27]) by kx.openedu.org (8.14.5/8.14.5) with ESMTP id w0ICqKn8089866; Thu, 18 Jan 2018 21:52:20 +0900 (JST) (envelope-from kiri@kx.openedu.org) Message-Id: <201801181252.w0ICqKn8089866@kx.openedu.org> Date: Thu, 18 Jan 2018 21:52:20 +0900 From: KIRIYAMA Kazuhiko To: freebsd-current@freebsd.org Cc: kiri@kx.openedu.org Subject: Re: SG116j install crashed In-Reply-To: <201801180635.w0I6Zfdb083944@kx.openedu.org> References: <201801180635.w0I6Zfdb083944@kx.openedu.org> User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.6 MULE XEmacs/21.4 (patch 22) (Instant Classic) (amd64--freebsd) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") 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: Thu, 18 Jan 2018 12:52:24 -0000 At Thu, 18 Jan 2018 15:35:41 +0900, my wrote: > > Hi, all > > I've bought Biccamera's original bland note PC (SG116j) > impulsively because of cheapness($1780). I've installed > 12.0-CURRENT(r327788) right away. Booted smoothly but set > loader conf "unset hint.uart.1.at" and configure disk with > > mmcsd0 58 GB GPT > mmcsd0p1 200MB efi > mmcsd0p2 54 GB freebsd-ufs / > mmcsd0p3 4.2 GB freebsd-swap none > > But in "Tetching distribution files" of base.txz, crashed > with: > > sdhci_acpi0-slot0: Controller timeout > sdhci_acpi0-slot0: ============== REGISTER DUMP ============== > sdhci_acpi0-slot0: Sys addr: 0x02158000 | Version: 0x00001002 > sdhci_acpi0-slot0: Blk size: 0x00000200 | Blk cnt: 0x000000f8 > sdhci_acpi0-slot0: Argument: 0x017f57e8 | Trn mode: 0x00000027 > sdhci_acpi0-slot0: Present: 0x1fff0106 | Host ctl: 0x00001025 > sdhci_acpi0-slot0: Power: 0x0000000b | Blk gap: 0x00000080 > sdhci_acpi0-slot0: Wake-up: 0x00000000 | Clock: 0x00000007 > sdhci_acpi0-slot0: Timeout: 0x00000007 | Int stat: 0x00000001 > sdhci_acpi0-slot0: Int enab: 0x05ff0033 | Sig enab: 0x05ff003a > sdhci_acpi0-slot0: AC12 err: 0x80000000 | Host ctl2:0x0000008b > sdhci_acpi0-slot0: Caps: 0x446cc8b2 | Caps2: 0x00000807 > sdhci_acpi0-slot0: Max curr: 0x00000000 | ADMA err: 0x00000000 > sdhci_acpi0-slot0: ADMA addr:0x00000000 | Slot int: 0x00000000 > sdhci_acpi0-slot0: =========================================== > mmcsd0: Error indicated: 1 Timeout > : > (snip) > : > Stopped at kdb_enter+0x3b: movq $0,kdb_why > db> > > Detail log has put in [1]. BTW I used [2] so all stuffs are > within it and it should not be fetched to internet. > > Is there any idea to go forth? I've tried to re-install by newfs /dev/mmcsd0p2 as follows: # newfs -E -U -j /dev/mmcsd0p2 and mount /dev/mmcsd0p2 to / then "commit" so installation go a litte forth at "Archive extract" section. But in extracting base.txz crashed: : g_vfs_done():mmcsd0p2[WRITE(offset=2299856,length=11776)]error = 5 panic: brelse: inapprppriate B_PAGING or B_CLUSTER bp 0xfffffe00011d5fc0 : (snip) : KDB: enter: panic [ thread pid 13 tid 100030 ] Stopped at kbd_enter+0x3b: moveq $0,kbd_why db> # Full log image put on [1] # [1] http://35.200.82.201/~kiri/freebsd/sg116j/crash_in_install-2.jpeg > > Best regards. > > [1] http://35.200.82.201/~kiri/freebsd/sg116j/crash_in_install.jpeg > [2] FreeBSD-12.0-CURRENT-amd64-20180110-r327788-memstick.img > > --- > KIRIYAMA Kazuhiko > _______________________________________________ > 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" > --- KIRIYAMA Kazuhiko From owner-freebsd-current@freebsd.org Thu Jan 18 13:11:22 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CBD88E797FB; Thu, 18 Jan 2018 13:11:22 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from hraggstad.unrelenting.technology (hraggstad.unrelenting.technology [71.19.146.151]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hraggstad.unrelenting.technology", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B96086C90A; Thu, 18 Jan 2018 13:11:22 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: by hraggstad.unrelenting.technology (OpenSMTPD) with ESMTPSA id ade421a3 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Thu, 18 Jan 2018 13:11:13 +0000 (UTC) From: Greg V Subject: mlx4 weird error "Failed to map EQ context memory" after update To: freebsd-net@freebsd.org, freebsd-current@freebsd.org Message-ID: <48f48a42-9115-8d97-5093-0e7173b36533@unrelenting.technology> Date: Thu, 18 Jan 2018 16:11:11 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit 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, 18 Jan 2018 13:11:22 -0000 Hi. I've upgraded CURRENT from December 19 (https://github.com/freebsd/freebsd/commit/fd53ccf393f4f8ac1948e97eca108) to today (https://github.com/freebsd/freebsd/commit/391a83c86bb91ae3840cf37b7de478f42cc97e2a) and my Mellanox ConnectX-2 network card stopped working: mlx4_core0: mem 0xfe100000-0xfe1fffff,0xf0800000-0xf0ffffff irq 32 at device 0.0 on pci7 mlx4_core: Mellanox ConnectX core driver v3.4.1 (October 2017) mlx4_core: Initializing mlx4_core mlx4_core0: command 0xffa failed: fw status = 0x1 mlx4_core0: Failed to map EQ context memory, aborting device_attach: mlx4_core0 attach returned 12 Loading the OLD mlx4.ko and mlx4en.ko on the NEW kernel actually does work fine! Reverting all mlx4 changes between then and now (no big changes, mostly just the 1 << 31 thing from D13858) and rebuilding the mlx4 module with CC=clang50 does not help. What happened?! From owner-freebsd-current@freebsd.org Thu Jan 18 16:32:28 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9DA60EB5C54 for ; Thu, 18 Jan 2018 16:32:28 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-qt0-x22b.google.com (mail-qt0-x22b.google.com [IPv6:2607:f8b0:400d:c0d::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 57A3275FA3; Thu, 18 Jan 2018 16:32:28 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: by mail-qt0-x22b.google.com with SMTP id z10so3532375qti.5; Thu, 18 Jan 2018 08:32:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=+7Do3YP9Adn56PfHaLNoS07F8Ad4fpwm/NZu7AeT85Y=; b=CwIBOWE7eRLwXu6CYTD18+jcMp1GHhuJhFAiQoPK6sgq4kepJPiglvVvrTtNB1sMZr pJmfO7qQjFSBO7L710xutBdDJY7E1BOrQPJPqptP2MlC74BmnD4G8zOfkbYQ6/pOMLP9 QesksIhqIhtJ7xrkFanUZKw0kOojBinhl3Il8JaV0P0hWon+zkuuF+Age4nx1OjLIU4h /QGAuIFB4wXWGnab3A6bF41bw3yS99UF3AuMkZ2YV5UWAAnsGS2IYAaWW23nrDf6jAI1 b6/ZIIcBKSPwo5flTu2npQtCfv/Awa8wqGNElb1uR+zNrJM9+DbjJsvUXMT34ZBnKH4W QlKQ== 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=+7Do3YP9Adn56PfHaLNoS07F8Ad4fpwm/NZu7AeT85Y=; b=q+H1kt78LwNQ/cmrQ6jOpjj8PeoWjWJAj2N/YVUket/6D7izwIE/NDWe6eoyqEcWrh i+bjyD/CM2gR6ngd1FsQbNMntjlZPs0OC47DucfQtaxK/cKgzrbEoovG7XozppGtXBOQ KyM7RX9IqvRRZfcrPxDtaJG6Th+DuZOKoJnnUUMB6NT4ccFQe/4O/3rgTZenYvN9fmU+ S3xYo9slHnIl4c9z+J4U4p8zdwihoZl5uqGfmKkICoDtK6ieXnKp4au67FQCHOqs4X60 iIi+6E1CyiXiao9Yy1JO0O2GjLsAby/GUCAlFmA7bXn1z0acS5PnEKyMtvIJzU57sMsm 50Lg== X-Gm-Message-State: AKwxytfpXSRHbBoCF6jFFRtzAsIGBTU+TRTvE4a5Tm0fvsZBr+5JDSwE 2FbNizd2tnSx1olC1EULroYoyd5vDSazrRsIbV4VZQ== X-Google-Smtp-Source: ACJfBotTrejGX60GiRTdK+q/JXNAfFTkWiDF6POGZrkxls7WTMjW9HXuD3elmYM0S5YWy8K0+17ePoWti7WKhhe0vVc= X-Received: by 10.55.200.207 with SMTP id t76mr65307865qkl.291.1516293147379; Thu, 18 Jan 2018 08:32:27 -0800 (PST) MIME-Version: 1.0 Received: by 10.237.54.2 with HTTP; Thu, 18 Jan 2018 08:32:26 -0800 (PST) In-Reply-To: <20180110185336.nlwkwhxu574kybvi@ivaldir.net> References: <20180110185336.nlwkwhxu574kybvi@ivaldir.net> From: Ryan Stone Date: Thu, 18 Jan 2018 11:32:26 -0500 Message-ID: Subject: Re: [self base packages] pkg: packages for wrong OS version: FreeBSD:12:amd64 To: Baptiste Daroussin Cc: Boris Samorodov , FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Jan 2018 16:32:28 -0000 On Wed, Jan 10, 2018 at 1:53 PM, Baptiste Daroussin wrote: > One has to specify pkg -o OSVERSION=1200055 to allow packages built on 1200055 > to install on 1200054. This workaround doesn't appear to work for pkg bootstrap: # pkg -o OSVERSION=1200055 bootstrap 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 Installing pkg-1.10.4... pkg-static: Newer FreeBSD version for package pkg: - package: 1200055 - running kernel: 1200054 Failed to install the following 1 package(s): /tmp//pkg.txz.ngJJEM From owner-freebsd-current@freebsd.org Thu Jan 18 17:00:46 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3F10BEB6E7A for ; Thu, 18 Jan 2018 17:00:46 +0000 (UTC) (envelope-from bapt@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1BA8276D0F; Thu, 18 Jan 2018 17:00:46 +0000 (UTC) (envelope-from bapt@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1235) id 324B51AAD0; Thu, 18 Jan 2018 17:00:45 +0000 (UTC) Received: by ivaldir.etoilebsd.net (Postfix, from userid 1001) id 103BD6AEA3; Thu, 18 Jan 2018 18:00:44 +0100 (CET) Date: Thu, 18 Jan 2018 18:00:44 +0100 From: Baptiste Daroussin To: Ryan Stone Cc: Boris Samorodov , FreeBSD Current Subject: Re: [self base packages] pkg: packages for wrong OS version: FreeBSD:12:amd64 Message-ID: <20180118170043.dkq3tdp7yaej7sgm@ivaldir.net> References: <20180110185336.nlwkwhxu574kybvi@ivaldir.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="fasm4xawjwqiihmp" Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20171215 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, 18 Jan 2018 17:00:46 -0000 --fasm4xawjwqiihmp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 18, 2018 at 11:32:26AM -0500, Ryan Stone wrote: > On Wed, Jan 10, 2018 at 1:53 PM, Baptiste Daroussin wr= ote: > > One has to specify pkg -o OSVERSION=3D1200055 to allow packages built o= n 1200055 > > to install on 1200054. >=20 > This workaround doesn't appear to work for pkg bootstrap: >=20 > # pkg -o OSVERSION=3D1200055 bootstrap > 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..= =2E done > Installing pkg-1.10.4... > pkg-static: Newer FreeBSD version for package pkg: > - package: 1200055 > - running kernel: 1200054 >=20 > Failed to install the following 1 package(s): /tmp//pkg.txz.ngJJEM The bootstrap does not know about OSVERSION, but setting OSVERSION in your = env should fix it Best regards, Bapt --fasm4xawjwqiihmp Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEgOTj3suS2urGXVU3Y4mL3PG3PloFAlpg0rAACgkQY4mL3PG3 Plp5EQ/+Ownq+PwKmmdk6WGkVPFwZJQPTfPx3wLlXggkuvIbfl5//uibfyDcMYuj bT+DC6WKcon/Mz6ltVLv3hveWMdf3SUt1wfOVrm+Yitma4cr6GIWebXHgMQnT0Ba A5hN+xYqh3OPSZLhLRQ6vCgwhrcPSLqk6dN21vZiUSUNnoof1vOwvFE+pcPI/M5u MgK6ARVfV/tR5oNGsTCB5Udcm5p2aao2avId275d0JL55DcFb3xTkzDSGm/H/SKP DcqCr8d07K1Ncu72rCqV23NEnqLWgpA+/LNzx5PL9117v9dDv+qS7h2q9GA8JROY LYzOJp7VMf8LwJnbnaNug1aimC16BObh82Ux2jhY/mnYWALVlWjcIp5Uttd9bj1t bLbe3Cwkldq9aKz8+w9BQX1JlRrjYtCsMJ5/bFGmCToYiZGtt9ugqbW9VmlxJsaa 1OHwzpRbTEapUT3rDviILSkkAN0OQMwMGbhas0/a3JtEdlo6qNLrx2GxaQF9HiT2 c3yelWQ0v4jpS0N7awl/GyENkgOn2mdvbfJz80XtL47tMhh0eo5InLBYCdUeuhG+ W3zL1T3E8qaqIAGfI6jtBQeNoCbrNqw2vi7bhKRpoJ/cIBYKiJQQZvB70e9TTJGh 7kab/IuH10lNe/+vzyUarSqIg81WsG5YdnHKXotx0W+5xHmYcjU= =wkqX -----END PGP SIGNATURE----- --fasm4xawjwqiihmp-- From owner-freebsd-current@freebsd.org Fri Jan 19 09:57:23 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BDE42ECDD2C; Fri, 19 Jan 2018 09:57:23 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 85A587ACFC; Fri, 19 Jan 2018 09:57:22 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 663D026009E; Fri, 19 Jan 2018 10:57:19 +0100 (CET) Subject: Re: mlx4 weird error "Failed to map EQ context memory" after update To: Greg V , freebsd-net@freebsd.org, freebsd-current@freebsd.org References: <48f48a42-9115-8d97-5093-0e7173b36533@unrelenting.technology> From: Hans Petter Selasky Message-ID: Date: Fri, 19 Jan 2018 10:54:27 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <48f48a42-9115-8d97-5093-0e7173b36533@unrelenting.technology> 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: Fri, 19 Jan 2018 09:57:23 -0000 On 01/18/18 14:11, Greg V wrote: > Hi. I've upgraded CURRENT from December 19 > (https://github.com/freebsd/freebsd/commit/fd53ccf393f4f8ac1948e97eca108) to > today > (https://github.com/freebsd/freebsd/commit/391a83c86bb91ae3840cf37b7de478f42cc97e2a) > and my Mellanox ConnectX-2 network card stopped working: > > mlx4_core0: mem 0xfe100000-0xfe1fffff,0xf0800000-0xf0ffffff > irq 32 at device 0.0 on pci7 > mlx4_core: Mellanox ConnectX core driver v3.4.1 (October 2017) > mlx4_core: Initializing mlx4_core > mlx4_core0: command 0xffa failed: fw status = 0x1 > mlx4_core0: Failed to map EQ context memory, aborting > device_attach: mlx4_core0 attach returned 12 > > > Loading the OLD mlx4.ko and mlx4en.ko on the NEW kernel actually does > work fine! > > Reverting all mlx4 changes between then and now (no big changes, mostly > just the 1 << 31 thing from D13858) and rebuilding the mlx4 module with > CC=clang50 does not help. > > What happened?! Hi, Can you do: objdump -Dx /boot/kernel/mlx4.ko > mlx4.ko.txt objdump -Dx /boot/kernel/mlx4en.ko > mlx4en.ko.txt And diff the text result between working and non-working ko's. Can you also make sure that /boot/modules does not contain anything *mlx4* ? --HPS From owner-freebsd-current@freebsd.org Fri Jan 19 21:16:18 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F13FDEC8D8D for ; Fri, 19 Jan 2018 21:16:18 +0000 (UTC) (envelope-from freebsd-current@dino.sk) Received: from mailhost.netlabit.sk (mailhost.netlabit.sk [84.245.65.72]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 78C3F75DFA for ; Fri, 19 Jan 2018 21:16:18 +0000 (UTC) (envelope-from freebsd-current@dino.sk) Received: from zeta.dino.sk (fw3.dino.sk [84.245.95.254]) (AUTH: LOGIN milan) by mailhost.netlabit.sk with ESMTPA; Fri, 19 Jan 2018 22:16:15 +0100 id 00F4BEDD.5A62601F.00014404 Date: Fri, 19 Jan 2018 22:16:15 +0100 From: Milan Obuch To: freebsd-current@freebsd.org Subject: Bug in /usr/src/sys/sys/sf_buf.h? Message-ID: <20180119221615.2ff5cfa4@zeta.dino.sk> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.31; i386-portbld-freebsd10.4) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jan 2018 21:16:19 -0000 Hi, after updating to revision 328171, building 12-CURRENT kernel gives cc -target armv7-gnueabihf-freebsd12.0 --sysroot=/usr/obj/usr/src/arm.armv7/tmp -B/usr/obj/usr/src/arm.armv7/tmp/usr/bin -c -O -pipe -g -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/libfdt -I/usr/src/sys/gnu/dts/include -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -march=armv7a -funwind-tables -MD -MF.depend.md.o -MTmd.o -ffreestanding -fwrapv -gdwarf-2 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -Wno-error-unused-function -Wno-error-pointer-sign -Wno-error-shift-negative-value -Wno-error-address-of-packed-member -mfpu=none -std=iso9899:1999 -Werror /usr/src/sys/dev/md/md.c In file included from /usr/src/sys/dev/md/md.c:90: /usr/src/sys/sys/sf_buf.h:120:11: error: implicit declaration of function 'PHYS_TO_DMAP' is invalid in C99 [-Werror,-Wimplicit-function-declaration] return (PHYS_TO_DMAP(VM_PAGE_TO_PHYS((vm_page_t)sf))); ^ /usr/src/sys/sys/sf_buf.h:120:11: error: this function declaration is not a prototype [-Werror,-Wstrict-prototypes] 2 errors generated. Did a bug slipped in or am I doing something wrong? With revision 328159 nothing like this happened, and I see in svn update output file /sys/sys/sf_buf.h being updated whne updating sources to revision 328171. Regards, Milan From owner-freebsd-current@freebsd.org Fri Jan 19 21:17:48 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E6FD9EC8F54 for ; Fri, 19 Jan 2018 21:17:48 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (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 D36F975FDD for ; Fri, 19 Jan 2018 21:17:48 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from helicon.physics.ucla.edu (helicon.physics.ucla.edu [169.232.156.253]) (authenticated bits=0) by c.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id w0JLHdXv015815 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for ; Fri, 19 Jan 2018 13:17:40 -0800 Subject: Re: Bug in /usr/src/sys/sys/sf_buf.h? To: freebsd-current@freebsd.org References: <20180119221615.2ff5cfa4@zeta.dino.sk> From: Nathan Whitehorn Message-ID: <947237b5-b488-433e-3011-1d450bf5fa12@freebsd.org> Date: Fri, 19 Jan 2018 13:17:38 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <20180119221615.2ff5cfa4@zeta.dino.sk> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Sonic-CAuth: UmFuZG9tSVZy5YYZzruWIcKSP96nU05o/abEr2bmXo+rYbrG5jivN/wj6VUlOp+87hDmvbGYpWJMpWENeg/9+Zt47AFiS9Ihdtd4qQtFxVw= X-Sonic-ID: C;AsLDLV795xGAX9zi2dYaJA== M;gOadLl795xGAX9zi2dYaJA== X-Spam-Flag: No X-Sonic-Spam-Details: 0.0/5.0 by cerberusd 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, 19 Jan 2018 21:17:49 -0000 This is my fault. Apologies. I will fix it immediately. -Nathan On 01/19/18 13:16, Milan Obuch wrote: > Hi, > > after updating to revision 328171, building 12-CURRENT kernel gives > > cc -target armv7-gnueabihf-freebsd12.0 > --sysroot=/usr/obj/usr/src/arm.armv7/tmp > -B/usr/obj/usr/src/arm.armv7/tmp/usr/bin -c -O -pipe -g -nostdinc -I. > -I/usr/src/sys -I/usr/src/sys/contrib/libfdt > -I/usr/src/sys/gnu/dts/include -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS > -include opt_global.h -march=armv7a -funwind-tables -MD > -MF.depend.md.o -MTmd.o -ffreestanding -fwrapv -gdwarf-2 -Wall > -Wredundant-decls -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef > -Wno-pointer-sign -D__printf__=__freebsd_kprintf__ > -Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas > -Wno-error-tautological-compare -Wno-error-empty-body > -Wno-error-parentheses-equality -Wno-error-unused-function > -Wno-error-pointer-sign -Wno-error-shift-negative-value > -Wno-error-address-of-packed-member -mfpu=none -std=iso9899:1999 > -Werror /usr/src/sys/dev/md/md.c > > In file included from /usr/src/sys/dev/md/md.c:90: > > /usr/src/sys/sys/sf_buf.h:120:11: error: implicit declaration of > function 'PHYS_TO_DMAP' is invalid in C99 > [-Werror,-Wimplicit-function-declaration] > > return (PHYS_TO_DMAP(VM_PAGE_TO_PHYS((vm_page_t)sf))); > > ^ > > /usr/src/sys/sys/sf_buf.h:120:11: error: this function declaration is > not a prototype [-Werror,-Wstrict-prototypes] > > 2 errors generated. > > Did a bug slipped in or am I doing something wrong? With revision > 328159 nothing like this happened, and I see in svn update output > file /sys/sys/sf_buf.h being updated whne updating sources to revision > 328171. > > Regards, > Milan > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@freebsd.org Fri Jan 19 23:17:31 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 55025ECE978; Fri, 19 Jan 2018 23:17:31 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from hraggstad.unrelenting.technology (hraggstad.unrelenting.technology [71.19.146.151]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hraggstad.unrelenting.technology", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4046A7BD3A; Fri, 19 Jan 2018 23:17:30 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: by hraggstad.unrelenting.technology (OpenSMTPD) with ESMTPSA id 5d72516e TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Fri, 19 Jan 2018 23:17:22 +0000 (UTC) Subject: Re: mlx4 weird error "Failed to map EQ context memory" after update To: Hans Petter Selasky , freebsd-net@freebsd.org, freebsd-current@freebsd.org References: <48f48a42-9115-8d97-5093-0e7173b36533@unrelenting.technology> From: Greg V Message-ID: Date: Sat, 20 Jan 2018 02:17:19 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit 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: Fri, 19 Jan 2018 23:17:31 -0000 On 01/19/2018 12:54, Hans Petter Selasky wrote: > On 01/18/18 14:11, Greg V wrote: >> Hi. I've upgraded CURRENT from December 19 >> (https://github.com/freebsd/freebsd/commit/fd53ccf393f4f8ac1948e97eca108) >> to today >> (https://github.com/freebsd/freebsd/commit/391a83c86bb91ae3840cf37b7de478f42cc97e2a) >> and my Mellanox ConnectX-2 network card stopped working: >> >> mlx4_core0: mem >> 0xfe100000-0xfe1fffff,0xf0800000-0xf0ffffff irq 32 at device 0.0 on pci7 >> mlx4_core: Mellanox ConnectX core driver v3.4.1 (October 2017) >> mlx4_core: Initializing mlx4_core >> mlx4_core0: command 0xffa failed: fw status = 0x1 >> mlx4_core0: Failed to map EQ context memory, aborting >> device_attach: mlx4_core0 attach returned 12 >> >> >> Loading the OLD mlx4.ko and mlx4en.ko on the NEW kernel actually does >> work fine! >> >> Reverting all mlx4 changes between then and now (no big changes, >> mostly just the 1 << 31 thing from D13858) and rebuilding the mlx4 >> module with CC=clang50 does not help. >> >> What happened?! > > Hi, > > Can you do: > > objdump -Dx /boot/kernel/mlx4.ko > mlx4.ko.txt > objdump -Dx /boot/kernel/mlx4en.ko > mlx4en.ko.txt > > And diff the text result between working and non-working ko's. That results in 180883 lines (9.2 megabytes) of diff for mlx4.ko. The CC=clang50 one is only a bit better at 7.6 MB :( > Can you also make sure that /boot/modules does not contain anything > *mlx4* ? Yeah, it did not contain that. From owner-freebsd-current@freebsd.org Sat Jan 20 06:49:41 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 57918EBE396 for ; Sat, 20 Jan 2018 06:49:41 +0000 (UTC) (envelope-from freebsd-current@dino.sk) Received: from mailhost.netlabit.sk (mailhost.netlabit.sk [84.245.65.72]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E89A56B3D0; Sat, 20 Jan 2018 06:49:40 +0000 (UTC) (envelope-from freebsd-current@dino.sk) Received: from zeta.dino.sk (fw3.dino.sk [84.245.95.254]) (AUTH: LOGIN milan) by mailhost.netlabit.sk with ESMTPA; Sat, 20 Jan 2018 07:49:31 +0100 id 00F4BE7F.5A62E67B.00003305 Date: Sat, 20 Jan 2018 07:49:30 +0100 From: Milan Obuch To: Nathan Whitehorn Cc: freebsd-current@freebsd.org Subject: Re: Bug in /usr/src/sys/sys/sf_buf.h? Message-ID: <20180120074930.2bb8054e@zeta.dino.sk> In-Reply-To: <947237b5-b488-433e-3011-1d450bf5fa12@freebsd.org> References: <20180119221615.2ff5cfa4@zeta.dino.sk> <947237b5-b488-433e-3011-1d450bf5fa12@freebsd.org> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.31; i386-portbld-freebsd10.4) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Jan 2018 06:49:41 -0000 On Fri, 19 Jan 2018 13:17:38 -0800 Nathan Whitehorn wrote: > This is my fault. Apologies. I will fix it immediately. > -Nathan > Revision 328179, fix confirmed. Thanks. Milan > On 01/19/18 13:16, Milan Obuch wrote: > > Hi, > > > > after updating to revision 328171, building 12-CURRENT kernel gives > > > > cc -target armv7-gnueabihf-freebsd12.0 > > --sysroot=/usr/obj/usr/src/arm.armv7/tmp > > -B/usr/obj/usr/src/arm.armv7/tmp/usr/bin -c -O -pipe -g -nostdinc > > -I. -I/usr/src/sys -I/usr/src/sys/contrib/libfdt > > -I/usr/src/sys/gnu/dts/include -D_KERNEL > > -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -march=armv7a > > -funwind-tables -MD -MF.depend.md.o -MTmd.o -ffreestanding -fwrapv > > -gdwarf-2 -Wall -Wredundant-decls -Wnested-externs > > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline > > -Wcast-qual -Wundef -Wno-pointer-sign > > -D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs > > -fdiagnostics-show-option -Wno-unknown-pragmas > > -Wno-error-tautological-compare -Wno-error-empty-body > > -Wno-error-parentheses-equality -Wno-error-unused-function > > -Wno-error-pointer-sign -Wno-error-shift-negative-value > > -Wno-error-address-of-packed-member -mfpu=none -std=iso9899:1999 > > -Werror /usr/src/sys/dev/md/md.c > > > > In file included from /usr/src/sys/dev/md/md.c:90: > > > > /usr/src/sys/sys/sf_buf.h:120:11: error: implicit declaration of > > function 'PHYS_TO_DMAP' is invalid in C99 > > [-Werror,-Wimplicit-function-declaration] > > > > return (PHYS_TO_DMAP(VM_PAGE_TO_PHYS((vm_page_t)sf))); > > > > ^ > > > > /usr/src/sys/sys/sf_buf.h:120:11: error: this function declaration > > is not a prototype [-Werror,-Wstrict-prototypes] > > > > 2 errors generated. > > > > Did a bug slipped in or am I doing something wrong? With revision > > 328159 nothing like this happened, and I see in svn update output > > file /sys/sys/sf_buf.h being updated whne updating sources to > > revision 328171. > > > > Regards, > > Milan > From owner-freebsd-current@freebsd.org Sat Jan 20 09:21:52 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 59AE8EC53D3; Sat, 20 Jan 2018 09:21:52 +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 1BCEC701F8; Sat, 20 Jan 2018 09:21:52 +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 A803A26012B; Sat, 20 Jan 2018 10:21:49 +0100 (CET) Subject: Re: mlx4 weird error "Failed to map EQ context memory" after update To: Greg V , freebsd-net@freebsd.org, freebsd-current@freebsd.org References: <48f48a42-9115-8d97-5093-0e7173b36533@unrelenting.technology> From: Hans Petter Selasky Message-ID: Date: Sat, 20 Jan 2018 10:18:57 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.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, 20 Jan 2018 09:21:52 -0000 On 01/20/18 00:17, Greg V via freebsd-net wrote: > > On 01/19/2018 12:54, Hans Petter Selasky wrote: >> On 01/18/18 14:11, Greg V wrote: >>> Hi. I've upgraded CURRENT from December 19 >>> (https://github.com/freebsd/freebsd/commit/fd53ccf393f4f8ac1948e97eca108) >>> to today >>> (https://github.com/freebsd/freebsd/commit/391a83c86bb91ae3840cf37b7de478f42cc97e2a) >>> and my Mellanox ConnectX-2 network card stopped working: >>> >>> mlx4_core0: mem >>> 0xfe100000-0xfe1fffff,0xf0800000-0xf0ffffff irq 32 at device 0.0 on pci7 >>> mlx4_core: Mellanox ConnectX core driver v3.4.1 (October 2017) >>> mlx4_core: Initializing mlx4_core >>> mlx4_core0: command 0xffa failed: fw status = 0x1 >>> mlx4_core0: Failed to map EQ context memory, aborting >>> device_attach: mlx4_core0 attach returned 12 >>> >>> >>> Loading the OLD mlx4.ko and mlx4en.ko on the NEW kernel actually does >>> work fine! >>> >>> Reverting all mlx4 changes between then and now (no big changes, >>> mostly just the 1 << 31 thing from D13858) and rebuilding the mlx4 >>> module with CC=clang50 does not help. >>> >>> What happened?! >> >> Hi, >> >> Can you do: >> >> objdump -Dx /boot/kernel/mlx4.ko > mlx4.ko.txt >> objdump -Dx /boot/kernel/mlx4en.ko > mlx4en.ko.txt >> >> And diff the text result between working and non-working ko's. > That results in 180883 lines (9.2 megabytes) of diff for mlx4.ko. The > CC=clang50 one is only a bit better at 7.6 MB :( Can you open this diff using "meld". And look for instructions which have changed, not only their location. --HPS From owner-freebsd-current@freebsd.org Sat Jan 20 11:25:14 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A3186ECB058 for ; Sat, 20 Jan 2018 11:25:14 +0000 (UTC) (envelope-from kiri@kx.openedu.org) Received: from kx.openedu.org (flets-sg1027.kamome.or.jp [202.216.24.27]) (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 2460174ED8 for ; Sat, 20 Jan 2018 11:25:13 +0000 (UTC) (envelope-from kiri@kx.openedu.org) Received: from kx.openedu.org (kx.openedu.org [202.216.24.27]) by kx.openedu.org (8.14.5/8.14.5) with ESMTP id w0KBP8Hl039214; Sat, 20 Jan 2018 20:25:09 +0900 (JST) (envelope-from kiri@kx.openedu.org) Message-Id: <201801201125.w0KBP8Hl039214@kx.openedu.org> Date: Sat, 20 Jan 2018 20:25:08 +0900 From: KIRIYAMA Kazuhiko To: freebsd-current@freebsd.org Cc: kiri@kx.openedu.org Subject: Re: SG116j install crashed In-Reply-To: <201801180635.w0I6Zfdb083944@kx.openedu.org> References: <201801180635.w0I6Zfdb083944@kx.openedu.org> User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.6 MULE XEmacs/21.4 (patch 22) (Instant Classic) (amd64--freebsd) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") 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: Sat, 20 Jan 2018 11:25:14 -0000 At Thu, 18 Jan 2018 15:35:41 +0900, my wrote: > > Hi, all > > I've bought Biccamera's original bland note PC (SG116j) > impulsively because of cheapness($1780). I've installed > 12.0-CURRENT(r327788) right away. Booted smoothly but set > loader conf "unset hint.uart.1.at" and configure disk with > > mmcsd0 58 GB GPT > mmcsd0p1 200MB efi > mmcsd0p2 54 GB freebsd-ufs / > mmcsd0p3 4.2 GB freebsd-swap none > > But in "Tetching distribution files" of base.txz, crashed > with: > > sdhci_acpi0-slot0: Controller timeout > sdhci_acpi0-slot0: ============== REGISTER DUMP ============== > sdhci_acpi0-slot0: Sys addr: 0x02158000 | Version: 0x00001002 > sdhci_acpi0-slot0: Blk size: 0x00000200 | Blk cnt: 0x000000f8 > sdhci_acpi0-slot0: Argument: 0x017f57e8 | Trn mode: 0x00000027 > sdhci_acpi0-slot0: Present: 0x1fff0106 | Host ctl: 0x00001025 > sdhci_acpi0-slot0: Power: 0x0000000b | Blk gap: 0x00000080 > sdhci_acpi0-slot0: Wake-up: 0x00000000 | Clock: 0x00000007 > sdhci_acpi0-slot0: Timeout: 0x00000007 | Int stat: 0x00000001 > sdhci_acpi0-slot0: Int enab: 0x05ff0033 | Sig enab: 0x05ff003a > sdhci_acpi0-slot0: AC12 err: 0x80000000 | Host ctl2:0x0000008b > sdhci_acpi0-slot0: Caps: 0x446cc8b2 | Caps2: 0x00000807 > sdhci_acpi0-slot0: Max curr: 0x00000000 | ADMA err: 0x00000000 > sdhci_acpi0-slot0: ADMA addr:0x00000000 | Slot int: 0x00000000 > sdhci_acpi0-slot0: =========================================== > mmcsd0: Error indicated: 1 Timeout > : > (snip) > : > Stopped at kdb_enter+0x3b: movq $0,kdb_why > db> > > Detail log has put in [1]. BTW I used [2] so all stuffs are > within it and it should not be fetched to internet. > > Is there any idea to go forth? > > Best regards. > > [1] http://35.200.82.201/~kiri/freebsd/sg116j/crash_in_install.jpeg > [2] FreeBSD-12.0-CURRENT-amd64-20180110-r327788-memstick.img I've got r328126 memstic and install with it, then all went to perfect! Thanx for FreeBSD-CURRENT team! --- KIRIYAMA Kazuhiko > > --- > KIRIYAMA Kazuhiko >