From owner-freebsd-current@freebsd.org Sun Jun 3 01:08:19 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 07462FDF532 for ; Sun, 3 Jun 2018 01:08:19 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: from mail-it0-x22d.google.com (mail-it0-x22d.google.com [IPv6:2607:f8b0:4001:c0b::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 893AB84AA9 for ; Sun, 3 Jun 2018 01:08:18 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: by mail-it0-x22d.google.com with SMTP id d10-v6so6062058itj.1 for ; Sat, 02 Jun 2018 18:08:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardenedbsd-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :user-agent; bh=V0DFp7E8zDq+yyECaXCM9SXbX3dsG3XFjYkYlo9RICg=; b=MPeBNgTQG3RjWk3Y+P9GNPjM54C4G+6wPhgwd8pRFwnuc1q9Cia2mEFgTOlBeLMg+t rF85MQEQ+s3fZeIdRjEJ3RFDcPbSZnhQQSzmRkhi3GL62EE8uy0edayWtv0oIUmDexPs iYmlNhe2WcC875LqM9PnGdVOTlu1z4nmzyXPPeTcOxpc6zO7NvnH8x1PtpsgF5QnG6NG sWgf9A6mBmrIIPj1FBjlmGx3ViObgyRK+VgEkT3yGjc/OSe3rNKDzUAxy1Kj/tw0Uu/g rYbRC4iXOCRjNYPzmziBm+4n8oAcAWAlesgBx7Lf6rhL6OHmlk3PtWc+zTWrCYKqMDoL sf1Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:user-agent; bh=V0DFp7E8zDq+yyECaXCM9SXbX3dsG3XFjYkYlo9RICg=; b=HIqi9zlXVwVhrIUOAUrxZHB00MsS5WMDvI9anFU43okqTmVMdLwKxjROlp9lSQEiNS fQTXE9hl5wm3t46zAyro2WbEsRuYMny4oDKiXS6CfvHgCrSEtWOQ017CyC8CEXETueQq XhPy3LxlWIxfMXfI67i2xFOOutvv9MOU+Lf1gHe4cLfTyfXPImA7OYUphy3wHyYFmHAS X4igLKnji3EazwFIbC4ijt/MEJKYyNMn83Ae4l2W1jUVLPO90Ih8vl+7StzQxYzVGaVu hc2r7bVPhZx/TcUEKXOmkkpLQ4mP82suqmjlyJtm7D1A6M/n7kyU45suuRcw4FvIckoa 7SjQ== X-Gm-Message-State: APt69E2xXlcb/UUvsNSmj863rcgoMVdE6T6B/gZqF8ALX/9AQf5w/l0/ 0X96KR7V99L8kSX9Xq1h+vgsJl87BFaKHsZ5QQpFnB4mG5PhWGJ6XwrMyUZSzOIZQtptyF5g1Je xaMobExnzYqeqzzLEAVk/JYP9R9I3GAJIq1uZgcQGJNi8C2Y0FLDkD+yXONl1q1fh1naytdd1ob 2mkvuAPAc= X-Google-Smtp-Source: ADUXVKLNOWvcz3cjCWz1Hx3fLFJl+c0NPSDQYuhp+pvt/NkGLhEwDYxsyyMtJkyjOhfAlZqCUlT0Zw== X-Received: by 2002:a24:6214:: with SMTP id d20-v6mr9083717itc.12.1527988097645; Sat, 02 Jun 2018 18:08:17 -0700 (PDT) Received: from mutt-hbsd (tor-exit5-readme.dfri.se. [171.25.193.25]) by smtp.gmail.com with ESMTPSA id g138-v6sm3430643iog.62.2018.06.02.18.08.14 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sat, 02 Jun 2018 18:08:16 -0700 (PDT) Date: Sat, 2 Jun 2018 21:07:50 -0400 From: Shawn Webb To: freebsd-current@freebsd.org Cc: mmacy@freebsd.org Subject: Weird conditional logic in lib/libpmc/Makefile Message-ID: <20180603010750.zo4qngsqouiajcpo@mutt-hbsd> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="6bvesglmduh72hbc" Content-Disposition: inline X-Operating-System: FreeBSD mutt-hbsd 12.0-CURRENT FreeBSD 12.0-CURRENT X-PGP-Key: http://pgp.mit.edu/pks/lookup?op=vindex&search=0x6A84658F52456EEE User-Agent: NeoMutt/20180323 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 01:08:19 -0000 --6bvesglmduh72hbc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hey all, Below is some logic pasted from lib/libpmc/Makefile: =2Eif ${MACHINE_ARCH} =3D=3D "amd64" || ${MACHINE_ARCH} =3D=3D "i386" =2Eif ${MACHINE_ARCH} =3D=3D "aarch64" EVENT_ARCH=3D"arm64" =2Eelif ${MACHINE_ARCH} =3D=3D "amd64" || ${MACHINE_ARCH} =3D=3D "i386" EVENT_ARCH=3D"x86" =2Eelif ${MACHINE_ARCH} =3D=3D "powerpc" EVENT_ARCH=3D"powerpc" =2Eendif JEVENTS=3D ${BTOOLSPATH:U.}/pmu-events/jevents # This file is built in a subdirectory so never try to rebuild # it here due to missing meta file. ${JEVENTS}: .NOMETA libpmc_events.c: ${JEVENTS} ${JEVENTS} ${EVENT_ARCH} ${.CURDIR}/pmu-events/arch libpmc_events.c SRCS+=3D libpmc_events.c =2Eendif Why perform the conditionals for aarch64 and powerpc when it can't be those? "Am I missing something? I'm looping in Matt Macy, who was the last person to touch the file. Thanks, --=20 Shawn Webb Cofounder and Security Engineer HardenedBSD Tor-ified Signal: +1 443-546-8752 Tor+XMPP+OTR: lattera@is.a.hacker.sx GPG Key ID: 0x6A84658F52456EEE GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE --6bvesglmduh72hbc Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEKrq2ve9q9Ia+iT2eaoRlj1JFbu4FAlsTP2IACgkQaoRlj1JF bu45mg/8CCfv2XCKlRlzPtqPNO+9XD4vMGeicyTV0OvIOTOp5HXiiXe72PDyBP+P D9rvgnpfK5e400k4H/ELnByaqdgyWbOiLSySBXAY8Z3aZlI2ftP0+X89DY4F5FJs yrUaKavTQGkOqXL5R+acga8CkqqvXfgz8IHScewDnjTJoa5ZaJu0LoJpf3ABQBfO 941IZ/cNsCilwbEc08cwxu01JJv0/8PASZu83ABbBKdmUBmv/KLnmkPAoLrpkri3 mHEHhGQ8N3butgUWMFXZV9sYCVxmVnMyze2s2ccD16goQDuNW3xZCimnf7wi25bS 1sl7DlTtTaWsuhN5S527wdIWeqQKirLZ5HCa2RpwuS/lVdjWaqa4pfct+S8nWRq3 5aIj31XmSCcvD3DnBLBkZaftFT6M+N3WsC7llKnVREly0MzFZkv30mVJB0rQShfn 11MThyfWWYEJnTGmRI9dFA+G6/wpvpPefkd9Yle9FbSHoNS0ySt916HwJswzoLfJ QICFJSPMNST4CMvaDEWhVZONot2FbAzNTM1nnlvY81NBFK6fobR1Jps7LTCjqiqT Om8NKtgh4/Ob4o8hCnfWbvMICL4Zt5UPLBkoaxWUDfYAWUXxPzZE1GzWVQd3v28C gpKNNYQOza0vVi7YwWBfd8rpU0wAWzBa0xNRVFIeIv7zfHlrFrw= =KB6N -----END PGP SIGNATURE----- --6bvesglmduh72hbc-- From owner-freebsd-current@freebsd.org Sun Jun 3 05:13:54 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4ADABFF5047 for ; Sun, 3 Jun 2018 05:13:54 +0000 (UTC) (envelope-from dsifriend@gmail.com) Received: from mail-yw0-x22c.google.com (mail-yw0-x22c.google.com [IPv6:2607:f8b0:4002:c05::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 D38FD6F8AD for ; Sun, 3 Jun 2018 05:13:53 +0000 (UTC) (envelope-from dsifriend@gmail.com) Received: by mail-yw0-x22c.google.com with SMTP id b125-v6so6572893ywe.1 for ; Sat, 02 Jun 2018 22:13:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:references:subject:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=KAvyEIpvXccgYAcmWib2rTBlP+zkQx/KrxBGc1ejQ1A=; b=dSrJ7InkiRlLdnvWyNZp7/tJjlVMJATN5QIeusqMzmR48c7uv0Ew4QdBO1VUJ0z/am zHp1n31moS8dP1HutsGbARhMNBlOet0+nhiHzGRHcgAs0MCP9Sr6UHUrLyyQTp22w0q4 684DTNPahoeTFAsKWPwLtahZOWRxB33Lm7dVjPEURwqyIRlT1yRkOMqYXR6mFJMz8Fmz XChOQs7ATTPBRfrex/EdkoP/FSHsRDc4x7HRjad8sVZHg9EX/HKtUmyCnXMPLgvJdc7B 1JY3i6LjPXNMdEdT4fgOr30GjYfk/+x1O8JpijChXfnJh70dnla5g6XrnF2wlXYs0KJ/ GqqQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:references:subject:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=KAvyEIpvXccgYAcmWib2rTBlP+zkQx/KrxBGc1ejQ1A=; b=FUS7oojLHMwjQwfLZo1jEuXq2Zrcf4LMsSZ2Oltx51mZHbennlkyXVz+akF5Fdz1pW uJlRTiwIRCbCKN7PWdF7cT2xSGswgCtch0glSRop/YdIa9pkzaXVorgfXvaTnHxNvpFu bCjJ60QY2wxHUcy7SlaEzPwZVuPEhl24iecIRMp19kjvBKjGxyiazrW6oxsoXm7F3mr+ 0vd2gi/rwH9K9sksHRneRaTgvFv38a3wuwdA7d/63PfpQlCn6Z7sq7o4QfMUvDVDmav4 zJPlkmieN+D/qWqUtdpZ+U2ibwE8JNa0z6ElXqRreXiaVTeCxzBe55Ia5R6UjK55IP1j OviQ== X-Gm-Message-State: ALKqPweiLBHWAss6puNAde1dNKi1edVFbQDvwJN5XTuTvBntt8ZXGXYn nHu4+7dAKox5Dr7EAokdkAeBds1g X-Google-Smtp-Source: ADUXVKK6aUdlxurlG9VGxBH2HY2/gFe8b6lKte+IAIMDygAlJYPqZ6bHqNIOcUtC6EAmqpTnAl5Ksg== X-Received: by 2002:a0d:f301:: with SMTP id c1-v6mr5471336ywf.200.1528002832993; Sat, 02 Jun 2018 22:13:52 -0700 (PDT) Received: from ?IPv6:2600:380:952c:ae7c:599c:815:5170:3d66? ([2600:380:952c:ae7c:599c:815:5170:3d66]) by smtp.gmail.com with ESMTPSA id 205-v6sm18751120ywv.79.2018.06.02.22.13.51 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 02 Jun 2018 22:13:52 -0700 (PDT) To: freebsd-current@freebsd.org References: <0E69C450-42AE-438A-8C33-54B8E4B561F5@grem.de> Subject: Re: Elantech Touchpad Woes - Support for Elantech touchpads over i2c/SMBus still possibly missing From: Albert Message-ID: <5dd8bac9-d5c5-01e6-aea1-998be132a025@gmail.com> Date: Sun, 3 Jun 2018 01:13:50 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <0E69C450-42AE-438A-8C33-54B8E4B561F5@grem.de> Content-Language: en-US Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 05:13:54 -0000 Michael, Good to know you still have plans to work on that eventually. It'd be much appreciated. Looking at the source for your cyapa driver, I see you've ported it from the DragonFlyBSD driver (and they in turn adapted it from the Linux one). I should've looked into that earlier... Instead I spent most of my day trying to get OpenBSD running to try and follow Tom's hint at possible support there, but I had so many more issues along the way that in the end I figured "if I'm having trouble even getting a keyboard to work on this with my system, a touchpad will likely be the least of my worries." So, I'm back to my FreeBSD CURRENT install, still no touchpad support (obviously). I guess I'll be doing some more research on these things and tinkering with what I find. Unfortunately, I'm moving overseas in a couple of weeks and leaving my desktop behind, which means I need to have this laptop in full working condition by then, so if I don't make any progress, I'll have to somewhat reluctantly go back to Linux for the time being. If/when that happens, I'll still be happy to help with any testing. MfG, - Albert From owner-freebsd-current@freebsd.org Sun Jun 3 05:23:10 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 50C21FF5E88 for ; Sun, 3 Jun 2018 05:23:10 +0000 (UTC) (envelope-from dsifriend@gmail.com) Received: from mail-yw0-x235.google.com (mail-yw0-x235.google.com [IPv6:2607:f8b0:4002:c05::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D02B8700DF for ; Sun, 3 Jun 2018 05:23:09 +0000 (UTC) (envelope-from dsifriend@gmail.com) Received: by mail-yw0-x235.google.com with SMTP id p129-v6so518505ywg.7 for ; Sat, 02 Jun 2018 22:23:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:references:subject:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=4F6dn5anp+1asVlAkQOw8BL09VWfYWlS+noDL8aeCds=; b=alJtl+ERMSDASZnlAo583RVD65pByN0hRwas8gd2IPkTKUfc3z7ahK+IXly9bxfGDT 1uHtNEw4daEt9XGWcniua6K2dC0VHuIvHhG6Xn+cj5a+G+Mq0TuLCbzpCRpquulsSaKk rj5i0ksWSNqnoq9TEjF/mpLo/ihhJYmpZGV7jMr6c7wDyDGkEU3wJKTIL74itURdhs6s eFacsLQsJ32hiQHvb3Jhmr0AdJAaKEgC7igc2ivW+yx8+CtXVxqnLGRpVKRLzQKSoO8Z w7k54Y/FHSLXThucNI2NLBM4lBGD2REZFZ8j/dmwvHz2QdinhwQGuPTMFBdNTA9OoSKp lInA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:references:subject:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=4F6dn5anp+1asVlAkQOw8BL09VWfYWlS+noDL8aeCds=; b=X9VJjy7GeDrmiWd5p7C8fCSQp42zxo00vjWA/VuWxvBLbENZ1SjqNJjgvEwR4XCkGw vHb/Hy5LUSfJBYh7poho43K0pu/jiGABIcO0ac+T6o0kJco4RkgfjZCtGLLKSkk8w7y0 j3Zvy45DykC+wcf3EW6YbTxREwFtrdZHiAU5GwWkMQrOuiPberT/uSbV1C/GMGYd4gZU xLg3+xg/qOKX3TExqmoc4nAX3k4ocpcHF3SDN0dE6XjqetabKXiJlp7oWNgfCS1MKnPi NR5/9Efvg7VJh04uDw/zAmgEz2ZI1nuZXF20m6iGxh6rzLYjG5+SYOhJvNKLdPdwZmIO fbWQ== X-Gm-Message-State: ALKqPwdvaao4AXa7MqHDB6UyvK6hKowTw7ZT9SINIkC1NM01tUnOsjM7 AWDsk3BArd+SG5zLs0SbHCDtVHgr X-Google-Smtp-Source: ADUXVKJebha8sXWXmKENwG+Vs2U2/dmzVHYpavCcZX/mMOBxoUShxa6V+PvAMl3EBq7h0EUNEBnfYw== X-Received: by 2002:a81:778b:: with SMTP id s133-v6mr8745068ywc.31.1528003389138; Sat, 02 Jun 2018 22:23:09 -0700 (PDT) Received: from ?IPv6:2600:380:952c:ae7c:599c:815:5170:3d66? ([2600:380:952c:ae7c:599c:815:5170:3d66]) by smtp.gmail.com with ESMTPSA id l197-v6sm7728088ywe.61.2018.06.02.22.23.07 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 02 Jun 2018 22:23:08 -0700 (PDT) To: freebsd-current@freebsd.org References: Subject: Re: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted From: Albert Message-ID: <247b08cf-29ae-2410-ed52-1f211c1df565@gmail.com> Date: Sun, 3 Jun 2018 01:23:06 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 05:23:10 -0000 Hi, I successfully tested the memstick.img on: Acer Chromebook 14 (EDGAR) [CB3-431-C5EX] The Results: UEFI (Coreboot) works perfectly, no issues there. BIOS (SeaBIOS) does *NOT* work. It puts the machine into a bootloop until the install medium is disconnected. It does, however, make it past the FreeBSD boot loader on the first try. From owner-freebsd-current@freebsd.org Sun Jun 3 05:27:27 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BA693EF3653 for ; Sun, 3 Jun 2018 05:27:27 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic301-2.consmr.mail.bf2.yahoo.com (sonic301-2.consmr.mail.bf2.yahoo.com [74.6.129.41]) (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 8444370338 for ; Sun, 3 Jun 2018 05:27:27 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: KVYQ760VM1kEyJVQPrUHfherAji4BEZD_8LxyUfkr078Y8Px.Ij9u5uJr8tdsEo iYzmv3RtGyKecif3B19U68g2YWgXwd2nT3pgesb.sgSYi3M9_HenjrsfdJMzzR96c64IXwluO3Jb 660_0J2_YYFchI6XdTh9VxUhGLCawRXEgrLUwtBiuxyZ2xESw5K_bOAwv0AQeJ3SpOqcmQzBOe3A fidBtQe2nidH8taIudSc.Xnjw7EukxNa3MOMwdFXrCqyCGmLUNseklfBKJR7DCRsjBkDWk.rlk3U eYOeqVVAej1WskpvjaqEYIC9kcO7zMBPidqmSHHYYXEyAaOEfeGtKlt114fJgVCQZyhkvpkr.K0f qOHpUUJULI3LK1v9G0DtNaJ16ifZULGrXtOSOcgUJAdRvEjdyVdi2LrbokZsJ3qctNZ6DbSXoWsi LhYyydZq4I4AIxW64g2Yysg01DEGo4M77gZ.D5w_dFnXGb7A7knY1YFm62_hwpo9NxtjcuMskJRV KfR4_EQcTWpaf0qGo2FAV2Q1UAWOWJrPocTX0zGHFcYVWSufZwAF03kcdyD2jeyKGaRxT25mQYDZ pOOzmfZ7p31bbD_Fg6lM2CFhd7eX99ajTfVbOmnXpY2wKfVpFPA2SW9m6qcHSMiJ4qOXRnyrMyui .4aL7Hvrql7BcwRNWz2.kxZRWJi6OoU15hfmF Received: from sonic.gate.mail.ne1.yahoo.com by sonic301.consmr.mail.bf2.yahoo.com with HTTP; Sun, 3 Jun 2018 05:27:26 +0000 Received: from ip70-189-131-151.lv.lv.cox.net (EHLO [192.168.0.109]) ([70.189.131.151]) by smtp419.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 36999e1161658bf229fd8e2d47e713cf; Sun, 03 Jun 2018 05:27:24 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: Re: Weird conditional logic in lib/libpmc/Makefile Message-Id: Date: Sat, 2 Jun 2018 22:27:22 -0700 Cc: mmacy@mattmacy.io To: shawn.webb@hardenedbsd.org, FreeBSD Current X-Mailer: Apple Mail (2.3445.8.2) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 05:27:27 -0000 Shawn Webb shawn.webb at hardenedbsd.org wrote on Sun Jun 3 01:08:19 UTC 2018 : > Below is some logic pasted from lib/libpmc/Makefile: > > .if ${MACHINE_ARCH} == "amd64" || ${MACHINE_ARCH} == "i386" > > .if ${MACHINE_ARCH} == "aarch64" > EVENT_ARCH="arm64" > .elif ${MACHINE_ARCH} == "amd64" || ${MACHINE_ARCH} == "i386" > EVENT_ARCH="x86" > .elif ${MACHINE_ARCH} == "powerpc" > EVENT_ARCH="powerpc" > .endif > > JEVENTS= ${BTOOLSPATH:U.}/pmu-events/jevents > # This file is built in a subdirectory so never try to rebuild > # it here due to missing meta file. > ${JEVENTS}: .NOMETA > > libpmc_events.c: ${JEVENTS} > ${JEVENTS} ${EVENT_ARCH} ${.CURDIR}/pmu-events/arch libpmc_events.c > SRCS+= libpmc_events.c > .endif > > Why perform the conditionals for aarch64 and powerpc when it can't be > those? "Am I missing something? > > I'm looping in Matt Macy, who was the last person to touch the file. It appears that every version of lib/libpmc/Makefile from head -r334242 and later has some variation of the odd nesting/value combinations that has "EVENT_ARCH" examples that are impossible to select as the code is structured. (The file version prior to -r334242 is from -r298107 .) === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Sun Jun 3 06:40:36 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AC1DAEFE3F1; Sun, 3 Jun 2018 06:40:36 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49C087312F; Sun, 3 Jun 2018 06:40:36 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.110.112]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1fPMgt-0000Jz-3Q; Sun, 03 Jun 2018 08:40:35 +0200 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-arm@freebsd.org Date: Sun, 03 Jun 2018 08:40:36 +0200 Cc: "FreeBSD Current" Subject: cpu_reset failed (RPI-3B+) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.4.0 X-Scan-Signature: a07cf4f22b7e0347d98fbeb4081a69be X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 06:40:36 -0000 Hello, Under normal conditions my RPI3 reboots normally, but from the panic command in the debugger after a crash I get: "cpu_reset failed". See screenshot: https://imagebin.ca/v/43zEQRdQYLMZ I installed the snapshot image from FreeBSD.org from last Tuesday: FreeBSD rpi3 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r334337: Tue May 29 18:14:46 UTC 2018 root@releng3.nyi.freebsd.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC arm64 Any thoughts? Can I try a patch? Regards, Ronald. From owner-freebsd-current@freebsd.org Sun Jun 3 10:02:31 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ED047FDED98; Sun, 3 Jun 2018 10:02:30 +0000 (UTC) (envelope-from hans@beastielabs.net) Received: from testsoekris.fritz.box (unknown [IPv6:2001:985:87e:1:200:24ff:fec9:5934]) (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 7769D7C377; Sun, 3 Jun 2018 10:02:30 +0000 (UTC) (envelope-from hans@beastielabs.net) Received: from beastie.fritz.box (beastie.fritz.box [192.168.66.176]) by testsoekris.fritz.box (8.14.7/8.14.7) with ESMTP id w53A2R1I008871; Sun, 3 Jun 2018 12:02:27 +0200 (CEST) (envelope-from hans@beastielabs.net) Subject: Re: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted To: Glen Barber Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org, Ed Maste References: <20180530155039.GE97814@FreeBSD.org> From: Hans Ottevanger Message-ID: Date: Sun, 3 Jun 2018 12:02:27 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <20180530155039.GE97814@FreeBSD.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 10:02:31 -0000 On 05/30/18 17:50, Glen Barber wrote: > Hi, > > Could folks please help boot-test the most recent 12.0-CURRENT amd64 > memstick images on various hardware? Note, this is not a request to > install 12.0-CURRENT, only a boot-test with various system knobs > tweaked. > > The most recent images are available at: > https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-mini-memstick.img > https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-memstick.img > > We are interested in testing both UEFI and CSM/BIOS/legacy mode, as we > would like to get this included in the upcoming 11.2-RELEASE if the > change that had been committed addresses several boot issues reported > recently. > > Please help test, and report back (both successes and failures). > Hi, I tried to boot the memstick.img on the following two systems (both fairly ancient and just having a BIOS): ASUS N4L-VM DH, CPU T7400 @2.16GHz Intel DP965LT, CPU Q6600 @2.40GHz Both booted perfectly. With FreeBSD 11.1 the latter system needed a freshly written USB stick to be treated with "gpart recover da0 && gpart set -a active da0" before it would boot, so this is certainly an improvement. Kind regards, Hans Ottevanger www.beastielabs.net From owner-freebsd-current@freebsd.org Sun Jun 3 10:30:12 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 10AD9FE208A for ; Sun, 3 Jun 2018 10:30:12 +0000 (UTC) (envelope-from vidwer@gmail.com) Received: from mail-it0-x232.google.com (mail-it0-x232.google.com [IPv6:2607:f8b0:4001:c0b::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8C2AF7D603 for ; Sun, 3 Jun 2018 10:30:11 +0000 (UTC) (envelope-from vidwer@gmail.com) Received: by mail-it0-x232.google.com with SMTP id a3-v6so6864184itd.0 for ; Sun, 03 Jun 2018 03:30:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=E/rxVYI9uxPs5gS8nw/AoEz9kreGNJKvIVRB8a2A3Dg=; b=a/5G565FmNgb+KgrA6Yp1Xj2ZxZNtLEX+q8dbFKugByrAcSkg4h7FiwwJ1KWZKLDp4 6TzsdgeLJrxAGAXW3ciVr2zKfquwPzMbAIycOKcH+m6Yo2zldapvlOYiFuqCJzmPqzdd y8As5xcaYuOODpDljJqFHPP61kDWlAmU5bKjPTxUDq+R0EeqaV6yDsBiRIEYxTTLJ13a Iu0BWnhysO9G/VJSjICJpQXJNVZf0U/Ofo/qUh7MdluKIxOIkoI0YbC/sUoIfVP5hSo6 iF69gsaDwm5HRfj2HbF6yfBQmTFoLUgJscsYTXU8jbqBMP+rWrdnI1UrPlnAxvGooCsp m2pw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=E/rxVYI9uxPs5gS8nw/AoEz9kreGNJKvIVRB8a2A3Dg=; b=KAWyQP5KhuCSVY+45RfepvtR/2TjYJj1hhpCcWK8AwF6WrJULWIHVyt1T2cAYiC93w C4DHJZTmLYdECA/x0FA10FBbp2i2mWQlP/ecE65tJWHOIuMt7b1sngmZjm7lUwZ5NmPR zmHq7qyWCES4sIyip2Nk13A/NhzxdhnFb6+fYY6pivf15UNKVu8DpMkSCwutm6Gj2Gnd 9mjBdS+KDi0YEoIsrUQVBc1TnOU6iebsOWmZuhme8KQLllG7mHEU+D0gvJe5Wf9XNHpF QRLzHPqT+PxPQqTqpptpYhTSkwDiSck/kTu6sYLMEa/sS3xkYoauaKgUsD76Er8sHIUd 5C+g== X-Gm-Message-State: APt69E2Kb6BnNyr3EK6uq+U0qgpjFw4Mv94i2wkpn4mSHWaDXq6AxWmW y5/nw04ofYPYR9rV0118AiAayw5BU9gTEY89fvUUng== X-Google-Smtp-Source: ADUXVKK5FbN7KZUHzZGehdsP1TXA4AbmhrjwwfeSytItSIjsP9L75cyjKGSKd+wSI7tN4nEki0vFkT+Kw7yw5nW8IZg= X-Received: by 2002:a24:ef05:: with SMTP id i5-v6mr10241683ith.112.1528021810940; Sun, 03 Jun 2018 03:30:10 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a4f:5307:0:0:0:0:0 with HTTP; Sun, 3 Jun 2018 03:30:10 -0700 (PDT) In-Reply-To: <247b08cf-29ae-2410-ed52-1f211c1df565@gmail.com> References: <247b08cf-29ae-2410-ed52-1f211c1df565@gmail.com> From: Idwer Vollering Date: Sun, 3 Jun 2018 12:30:10 +0200 Message-ID: Subject: Re: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted To: freebsd-current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 10:30:12 -0000 2018-06-03 7:23 GMT+02:00 Albert : > Hi, > > > I successfully tested the memstick.img on: > Acer Chromebook 14 (EDGAR) [CB3-431-C5EX] > > The Results: > UEFI (Coreboot) works perfectly, no issues there. > BIOS (SeaBIOS) does *NOT* work. It puts the machine into a bootloop until > the install medium is disconnected. It does, however, make it past the > FreeBSD boot loader on the first try. That's odd, which version of SeaBIOS are you using? did you had to run 'gpart recover '? CFT report: I'm able to boot FreeBSD-12.0-CURRENT-amd64-20180529-r334337-mini-memstick.img using coreboot with SeaBIOS 1.11.1 just fine. > > > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Sun Jun 3 10:31:13 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C0199FE21DF for ; Sun, 3 Jun 2018 10:31:13 +0000 (UTC) (envelope-from matt.xtaz@gmail.com) Received: from mail-wr0-x243.google.com (mail-wr0-x243.google.com [IPv6:2a00:1450:400c:c0c::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F07667D868; Sun, 3 Jun 2018 10:31:12 +0000 (UTC) (envelope-from matt.xtaz@gmail.com) Received: by mail-wr0-x243.google.com with SMTP id v13-v6so28538400wrp.13; Sun, 03 Jun 2018 03:31:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=jQQz/jLi1ln+kNwDG8WClmkpTwjWHfA4tdhr66/LYsg=; b=dOxenCdgkJAShCr01VWvHws1Ordq4YqkwX6eZF24hL21+gd8hC5lR+3hhcfaGj9WFe EVPYk3A5GhLyJPUFOu+HfjNrma6XyvT5GrPmogyDbuqZnhbkDR3EpwQgCzzpkiRyRR/G HMNBfwsiGMnWfhtXJ0HzXDD97vl6VPd/cA9hd92YOEwcxjJthc/Jni07RO4v0L7pVKbf aRskEABKwcaEiKpMJlt6c4pL6QpXjx6dRKlhdZjkE52wUmzeL6F0gsabofxXp4TIVZTu 0Hx6hzyoGiVgDQ9iAyExgn9qoqGA+ivsJS6VFYtjfmTarbWq+QidYvK6/Dzohi6S/j1/ FbJw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=jQQz/jLi1ln+kNwDG8WClmkpTwjWHfA4tdhr66/LYsg=; b=g77ehIBvjVUEWM7R1IpCwrYTdSryIVDYdYB7Uc4/7amOdMq5hOKfJlcomC2rw2Jjk4 N24qn8UiK00nHKdaWVOvYiz0t6XtWOE/cVKIKaS9l05YiQesLgc1pPX599O28wCvUlxc 5TBAt/Hd5psCfFnWXnm51rgrScvdLCCgZIX0HkUa7nh3ezWPWKySDNnKcky4Nd6Y6Umx emH/TcySUf7F6+j3RBP0KYJsq2n+SwsQJ6QWSPoRV+28MEZpFeHvfm5IeqPHSud39KMV vTzIhT9LJN5o8NWJXN+mrH6hR+V2DHpIzm5mDiQmF3vvEmdv+PyeII9oulBiUkSr15/S YOQQ== X-Gm-Message-State: ALKqPwfYcJYuwDVZ5a1dW4IXhnVHc1NEkVxWi8i71YD80cMvM/Ht2tLd oQUeszadjPxzwMPiSYwL0qXFoZiW X-Google-Smtp-Source: ADUXVKJsAhDjzhplMfz5aYx59iOHXtK+nAX6oOaEIljGK9oIZ+N8azRZUxDGBKDHYs1/uklYkBDZSg== X-Received: by 2002:adf:ad8a:: with SMTP id w10-v6mr14358673wrc.83.1528021872024; Sun, 03 Jun 2018 03:31:12 -0700 (PDT) Received: from gmail.com (tao.xtaz.uk. [2a02:390:7e52::10]) by smtp.gmail.com with ESMTPSA id q13-v6sm5417448wmc.29.2018.06.03.03.31.11 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 03 Jun 2018 03:31:11 -0700 (PDT) Date: Sun, 3 Jun 2018 11:31:09 +0100 From: Matt Smith To: Konstantin Belousov Cc: Dimitry Andric , Warner Losh , Benjamin Kaduk , Gary Jennejohn , FreeBSD Current Subject: Re: ``make buildkernel'' fails when /usr/obj is empty Message-ID: <20180603103108.GA17738@gmail.com> Mail-Followup-To: Matt Smith , Konstantin Belousov , Dimitry Andric , Warner Losh , Benjamin Kaduk , Gary Jennejohn , FreeBSD Current References: <20180531095222.399e7a37@ernst.home> <20180531095850.5845fd7a@ernst.home> <20180531160406.GD27985@kduck.kaduk.org> <32C087A4-1B67-4694-B769-16A347D4804E@FreeBSD.org> <7464D18D-2879-4C2A-ADD3-BF84D80940BB@FreeBSD.org> <20180531195003.GZ3789@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20180531195003.GZ3789@kib.kiev.ua> User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 10:31:14 -0000 On May 31 22:50, Konstantin Belousov wrote: >On Thu, May 31, 2018 at 08:19:20PM +0200, Dimitry Andric wrote: >> On 31 May 2018, at 20:11, Warner Losh wrote: >> > >> > On Thu, May 31, 2018 at 11:47 AM, Dimitry Andric wrote: >> > On 31 May 2018, at 18:04, Benjamin Kaduk wrote: >> > > On Thu, May 31, 2018 at 09:58:50AM +0200, Gary Jennejohn wrote: >> > >> On Thu, 31 May 2018 09:52:22 +0200 >> > >> Gary Jennejohn wrote: >> ... >> > > Whatever happened to the "run buildworld or kernel-toolchain before >> > > buildkernel" requirement? >> > >> > That is still a requirement, yes. Otherwise, you might have outdated >> > toolchain components are in your /usr/obj. >> > >> > Usually you can get away without doing that, and now that clang is the toolchain that's rebuilt (and that's not fast) people try to get away with it more and more... >> >> Actually clang doesn't get updated *that* often, but there is a minor >> snag that one of llvm's config files (lib/clang/include/llvm/Config/config.h) >> includes , so each time __FreeBSD_version is bumped, quite >> a lot of dependencies get triggered... >> >> The version is only used for two checks: >> >> #if __FreeBSD_version >= 1000052 >> /* Define to 1 if you have the `backtrace' function. */ >> #define HAVE_BACKTRACE TRUE >> >> and: >> >> /* Define to 1 if you have the `futimens' function. */ >> #if __FreeBSD_version >= 1100056 >> #define HAVE_FUTIMENS 1 >> #endif >> >> Maybe the first check could be dropped, assuming that backtrace() is >> always available, but I'm not sure about futimens(). Is there any >> supported version of FreeBSD left that does *not* have it? >Or you can manually define the symbols as needed on each branch, >eliminating the need for osreldate.h and reusable if some other >configuration variable needs to be conditionally set. Are these the kind of things that could get done in current and stable? Currently llvm/clang is rebuilt on pretty much every buildworld cycle that I do because of this which makes using things like WITH_META_MODE pretty pointless. It would be great to get this kind of change in the trees. -- Matt From owner-freebsd-current@freebsd.org Sun Jun 3 11:48:08 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6155BEFE4D1 for ; Sun, 3 Jun 2018 11:48:08 +0000 (UTC) (envelope-from alexvpetrov@gmail.com) Received: from mail-lf0-x233.google.com (mail-lf0-x233.google.com [IPv6:2a00:1450:4010:c07::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8964580983 for ; Sun, 3 Jun 2018 11:48:07 +0000 (UTC) (envelope-from alexvpetrov@gmail.com) Received: by mail-lf0-x233.google.com with SMTP id d24-v6so21028133lfa.8 for ; Sun, 03 Jun 2018 04:48:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:openpgp:autocrypt:message-id:date:user-agent :mime-version:content-language:content-transfer-encoding; bh=BhTjV7oBFXYFr9jmOn2/DmNQ3IqCOBLKC1gAHu8NrNk=; b=o1moI4SM4FVvD9eXcD/1QwQnBdzumyeHERG3XXKChcfX5SiLd7QdsGA9JkQaE0P8id I8LeU5m4DB4NmvH3ajY/AD3/XWOF37U44YnjBXPps+X6dZAa4B80RlSDgVLWAVdo7WhJ GVY1xI56tQv6UyxrThPeNwbc9xnb4nhmQ+EgLCExczF67dij7dK+TzuGOGtFm6zz65Gj XC+VFNrsxTZVQFAtsphlVKi8Doi6eEUEBMXdOHZxAB93Tw4J50rFegEBMiEV8cQo4634 AtImywuIk1VKTQm02ZwM8z+iUIEiWe/PaYcwBkJFBGDihKCP+alBf327E221BXR2kDjT wXxA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:openpgp:autocrypt:message-id :date:user-agent:mime-version:content-language :content-transfer-encoding; bh=BhTjV7oBFXYFr9jmOn2/DmNQ3IqCOBLKC1gAHu8NrNk=; b=tsADwI1jPBh2UKa2otVUSCaayeQsl19fI5vaafQU6YmhesrEQReIeR7lLCQQZ4wRMl FcgDtY1qGrpBuhV4RRquiuEpOLl8gWsbkGeVkM03pDNAdKn9Eo6dLglpM1ORIWJVPICC jp4VwBSY0M3IFr4vM28K6UzkxDTWLiFoEhgZQMilVBva8bhrzGq6Q0l9J/e1V/mZvJs5 +f3BPtyiVp0DhbiBGk/YW9oHpaNct3qvN6P3nISFkQ/3AYkEoblkiJt6jWwRvFSuvBfJ 7ZWGfLtGo1JYgPkN2FYvS/iQ8gXq0trtKFXni3yJ8RcURLAYw7R8xBhx23vPQ30vojaD ArEg== X-Gm-Message-State: ALKqPwffcuMci+NYNe5WAn3K+MZK27k/bj64Cvr/8AQW7T5UBbMnxjal RE01tAUFJvrGBR6KbmnQUkPliA== X-Google-Smtp-Source: ADUXVKJPgk2K5Q4pjh1CLH/O91jO2OZ26yggwgvtWuACfAoAOvv0Irp7FYKuIJZSucTMVYoAF7RQgA== X-Received: by 2002:a2e:635b:: with SMTP id x88-v6mr12944904ljb.103.1528026485238; Sun, 03 Jun 2018 04:48:05 -0700 (PDT) Received: from alex.super (stone.g-service.ru. [84.22.141.217]) by smtp.googlemail.com with ESMTPSA id w6-v6sm949747ljw.70.2018.06.03.04.48.03 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 03 Jun 2018 04:48:03 -0700 (PDT) To: FreeBSD Current From: "Alex V. Petrov" Subject: Error build nvidia-driver with r334555 Openpgp: preference=signencrypt Autocrypt: addr=alexvpetrov@gmail.com; prefer-encrypt=mutual; keydata= xsFNBFr3oA0BEADMSXiVd/IwYhJPMQ6LXbZ7jTA/RXuzrGYaR++UENx5QJ6/HJ/3myTeMnZE nNa0Zme+oKw/9s5x7rBTP6mL5ta7VSYpnPX932mAjT9J4nS7iW/wWNBqcXn7wDCog2TV8Ww3 13SUP2YaKoJKJLxddiZD6AJrkafB9EE/AycMQ8XxMao1lVS+/KAo0yciOsnSlIJCWhF00b3j xDlHLvehrDa4S3EB13bF6uE0XU5nFfMNHtBav2mwD9t01hNioCNTV1hXwmsS/L1n5PR5FyJJ yYtjeohrAUiGKGJU9lJJ6tROBhzV/k3OsOGPyajFOVsW0vUueYfgw+IAPYdOZIAONgNdxkvs tRLQxYPCBMN1FvQ7GlIhq7ob+mxuA1imXx3xzlYy5tu4QzB383qZtLqQnZpysjYooAbHl+eN vB2ldvH9TZxm3fxxNL6zgYAXE/pNgFoqg/ILmhDwvvHzApHqVCKU3g6yii0KPxD7susaUWcL JYgrmt2BIE0RuiQRGWyS0L277D/YGmVnPNHxPi58DBs2iexDm7jw7PhlmfOw44N9w+O09D2S gqmBHySAtsq9Z5LoM81F+LrOoVmpYczZWErS917Gua1X7K3wrXoqQC8qcSiHZpEcBl/Uohii QWzjQJot5LT7rvfFHpnSOXAKgN7enVM7KxTJAYK1U343GGdepQARAQABzTZBbGV4VlBldHJv diAoZmlyc3QgZ2xvYmFsIGtleSkgPGFsZXh2cGV0cm92QGdtYWlsLmNvbT7CwY4EEwEIADgW IQRvKPTT2TJuh37ANx313p8aVpVkcAUCWvegDQIbAwULCQgHAgYVCgkICwIEFgIDAQIeAQIX gAAKCRD13p8aVpVkcLLeEADClYAElEInGGjtLfH4jdjvTDaQTsrwT5/1E5/h8yxI4yn7hCt1 Dh+iCSUNLdPO88nZV2jP8bMQXFBKSbC0nAJXd8O+8t9AfSWoUC6IMzncxKTK/jZuJTCToCUR XZ+47+uJaBp51rpw3pFX8UrFlYSF6Dz97dI2cGHfx3xAOnowKxyHfthxS8waKWgbMOceds78 BP2+Q0iLCpoC9rO4KDc+w+h8z21eHIE9VHadTHpnKVF82voPH8XWvznTOCpYrdBwUtIyD/DV XRb0xcFsOSkvmReYX7u4QuOPLSc86sEWh4hXTFLAOdfeTjrDTDmBcmFpltmW1j+5t4mI1dK8 gptREM8gMJVJw3jjcO6jADeXX9q5C8/lX0sEGz9uC4oU5nkOMyfzd9Anb+9bCs7pMxhqAKjA 8tqJPPkmJU8WzMCs+uudIiQ8W9qIETwUJWxizQ3kvlzLfWRz5n93Y9kzSmjw81aiIJK/HFY8 wsW5zNo6JBn57cMPx8nBC4E2zM09ffmqSpjDwXfvZF2IIR8L4VTiKi3ovwLglJP+Qbs5HXNn 6K40cPNqfnHzPLwXwd/co04B/VVr+cKZuE58kYGty9Xs9q/SEpObDnxnLxMNHUNJJuRgOiti TKDkteHuKm6NA8v05o3TDQ5HU9szEoE5uoi/3pQ1ktfA/K3LkDwbotXL+87BTQRa96ANARAA w5+/xcaCP6iwsi2CFQ4pAWksdmPBEHA2VPn1ym3C6opjbyWUp6sn25eTWppdhA9rUqbM/zV/ hAFRT67oZJKBYNRaMoDdO8BsVZsg/u76QF/GuhbUjIk0tFFdpddMXl0zKAJJMCfDRxURRWv7 NW6sY/EZ4Dal5s4xOT+UrWGag3qoaIRdzw5bJRP+o75L90cE8pd7+Pd9cVJOOtTAwx0E4bPq dPSa6CPDSvzd9D3mw37dPzXysyQkQTy0OM7255E2wjYz3RbJxB3utybPVN3XJBD5EyA8IYeS ic1/03UrkRNv4XrLnlg7xLv96ZeCrf/BDNQW23iVwbISUAk4TXL7xs2TGYOmowZ89mMEcbfW ChX3YLAuAeWzgpMcrDC00izOxG0spkkrHL7/i1iSu2MKhv5qMTVgchlSktdd+KTba5keleHv ULQ3feGUKf9eTkKgES6q4rKrae0tIwByTLhhDVbkXqR6v8zrpJSscrvJ3tMNgquJKy5ATIUB nvUE2hMkSwtnJ2vQ/Z0zGt6c5KxI57/hsb148tXp1v3gAq9d6i8c8ChxSR/kUlqAvzl2QGcn CFVN6nfOzyNfBPZ61abNzkzjzyhOK4Gq4gQvx4QXhDp3jEME7rPM0Tqf0venb1Dp7SIHwggV yJglGApwoUvD4kKNIC7KDr+s/UjbBp4ExFMAEQEAAcLBdgQYAQgAIBYhBG8o9NPZMm6HfsA3 HfXenxpWlWRwBQJa96ANAhsMAAoJEPXenxpWlWRwAaEQAKm0imG5Fm37JZi+5faXJv/ZLZGl r4TVg4u1kMktdTQRrTXa3Qs0i3wTtOZe1p3xCCzPx+97iYETHragDTdAFUO+v+Llin26L1Zl z4huyIqgGSuTuekQfn6eoMZbcF+wzah4j/mvXQVpJBF2qQi1YdHSapWDlweuiuk01y8C3eHv 3qfFB/OJwXhwj0HKhkGkB2dLXuLtIk4GCXh4/g22tWz/SB0gsSXU7WhJFb0CyxETGR9YKxM8 CNl5tVRLqsBC6yQLvcAJgJci73PfMiHKnjxrz//+0xQO1TPeruWsd8nLYvziT38CyX42Mbaj 01WpvB0qOeTGtwGFmyyrnE8fYpd3CE0uAl9BnHqafAabl9+09x3wf+lEkkO2bK59akZz3BPU 8Lz2BAgskyS81WZCthQYUrUozFEx/31x8JJ95EQFNW9t8HBa51r4QhedSNKxLbT3Sx8hH0iq Z8wYkGw0og9U1DqgFzxE2HSGZSDG3I1DrPDqhcM/6Y0V98wS+XreuS88DYYck37+L7bTGiyZ WYFNZk1ChcIBk8hgKn5nFOCWO2rX06RI9zorzSpEg6lB2STae1Up5oEj8QqfYmfO3cp2Qhvj F3c2/i8KpWkJQkAgNrv428FIlx9SiPu9gvNTTYuLIOdZLQvInTmKs2uCoB6JDAW75axDhBbR FvM3Vpv/ Message-ID: <83fec8d8-699f-e86c-9884-9d8698a86a91@gmail.com> Date: Sun, 3 Jun 2018 18:48:01 +0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 11:48:08 -0000 cc -O2 -pipe -fno-strict-aliasing -DNV_VERSION_STRING=\"390.59\" -D__KERNEL__ -DNVRM -Wno-unused-function -Wuninitialized -O2 -fno-strict-aliasing -mno-red-zone -mcmodel=kernel -Wno-sign-co mpare -Wno-format-extra-args -UDEBUG -U_DEBUG -DNDEBUG -Werror=undef -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I../common/inc -I. -I/usr/src/sys -I/usr/src/sys/contrib/ck/include -fno- common -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -MD -MF.depend.nvlink_freebsd.o -MTnvlink_freebsd.o -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchr onous-unwind-tables -ffreestanding -fwrapv -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wcast-qual -Wundef -Wno-pointe r-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-equ ality -Wno-error-unused-function -Wno-error-pointer-sign -Wno-error-shift-negative-value -Wno-address-of-packed-member -mno-aes -mno-avx -std=iso9899:1999 -c nvlink_freebsd.c -o nvlink_fre ebsd.o --- nvidia_subr.o --- nvidia_subr.c:367:26: error: 'memset' call operates on objects of type 'struct nv_ioctl_card_info' while the size is based on a different type 'struct nv_ioctl_card_info *' [-Werror,-Wsizeof -pointer-memaccess] memset(ci, 0, sizeof(ci)); ~~ ^~ nvidia_subr.c:367:26: note: did you mean to dereference the argument to 'sizeof' (and multiply it by the number of elements)? memset(ci, 0, sizeof(ci)); ^~ 1 error generated. *** [nvidia_subr.o] Error code 1 make[4]: stopped in /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86_64-390.59/src/nvidia 1 error make[4]: stopped in /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86_64-390.59/src/nvidia *** [all_subdir_src/nvidia] Error code 2 make[3]: stopped in /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86_64-390.59/src 1 error make[3]: stopped in /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86_64-390.59/src *** [all_subdir_src] Error code 2 make[2]: stopped in /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86_64-390.59 1 error make[2]: stopped in /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86_64-390.59 ===> Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** Error code 1 -- ----- Alex. From owner-freebsd-current@freebsd.org Sun Jun 3 12:08:36 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ADC88F7257D for ; Sun, 3 Jun 2018 12:08:36 +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 EE9FA81963; Sun, 3 Jun 2018 12:08:35 +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 w53C8Ydc004880; Sun, 3 Jun 2018 12:08:34 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id w53C8Y8t004879; Sun, 3 Jun 2018 05:08:34 -0700 (PDT) (envelope-from david) Date: Sun, 3 Jun 2018 05:08:34 -0700 From: David Wolfskill To: "Alex V. Petrov" Cc: FreeBSD Current Subject: Re: Error build nvidia-driver with r334555 Message-ID: <20180603120834.GT1389@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , "Alex V. Petrov" , FreeBSD Current References: <83fec8d8-699f-e86c-9884-9d8698a86a91@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Yg/4YF7t1SayoUom" Content-Disposition: inline In-Reply-To: <83fec8d8-699f-e86c-9884-9d8698a86a91@gmail.com> User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 12:08:36 -0000 --Yg/4YF7t1SayoUom Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jun 03, 2018 at 06:48:01PM +0700, Alex V. Petrov wrote: > .... > --- nvidia_subr.o --- >=20 >=20 > nvidia_subr.c:367:26: error: 'memset' call operates on objects of type > 'struct nv_ioctl_card_info' while the size is based on a different type > 'struct nv_ioctl_card_info *' [-Werror,-Wsizeof > -pointer-memaccess] > memset(ci, 0, sizeof(ci)); > ~~ ^~ > nvidia_subr.c:367:26: note: did you mean to dereference the argument to > 'sizeof' (and multiply it by the number of elements)? >=20 > memset(ci, 0, sizeof(ci)); > ^~ > 1 error generated. > *** [nvidia_subr.o] Error code 1 > .... Aye; please ref. for additional details. The issue has been narrowed down to the range r334529 - r334535; I'm suspecting r334533 and/or r334534. (Not that the commits are in any way "faulty" -- merely that the nvidia-driver port may need some "evasive action" to allow for the change). Peace, david --=20 David H. Wolfskill david@catwhisker.org Mr. Trump, you reap what you sow: This is YOUR trade war. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --Yg/4YF7t1SayoUom Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEzLfO+ReoAfQwZNd7FTnMQKBJ7hcFAlsT2kFfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEND QjdDRUY5MTdBODAxRjQzMDY0RDc3QjE1MzlDQzQwQTA0OUVFMTcACgkQFTnMQKBJ 7hcD2Qf/RGiTBLWuYSuyx7evgeAlhSz3O5OEOk665tYA3ftmXEH7sIzcwQHCjkoQ 9vshBiNJjwPiF0/lYNMksSlNpVQt6NbZ+Lx8N8Pjzdt6La/+X4XtiJLEmYfclgVj F1QDRN4CXjNVbwDXQNTHGr76Sk588j0J3Jzp+pohc1/pzLHygctcYlv3nDtPUDM5 Gjj32ktYQTjFogCLBUQes8XNPgDj/xvd2n+cOoJDNUINDTJUwHWMoMxvqE2SGlLt fc9kl19cO64P2tSsM5lKngOfxE19/HjRFxIjJQTvxfDxGne8GjLU4rG3Ku/53Xme dOYHC9zPUZikP3bES6iUNKm2PWxAwg== =4UxO -----END PGP SIGNATURE----- --Yg/4YF7t1SayoUom-- From owner-freebsd-current@freebsd.org Sun Jun 3 12:22:00 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2C5EAF7408B for ; Sun, 3 Jun 2018 12:22:00 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 83BBA82303 for ; Sun, 3 Jun 2018 12:21:59 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTP id w53CLguZ038423; Sun, 3 Jun 2018 15:21:45 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w53CLguZ038423 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w53CLg5d038422; Sun, 3 Jun 2018 15:21:42 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 3 Jun 2018 15:21:42 +0300 From: Konstantin Belousov To: David Wolfskill , "Alex V. Petrov" , FreeBSD Current Subject: Re: Error build nvidia-driver with r334555 Message-ID: <20180603122142.GM3789@kib.kiev.ua> References: <83fec8d8-699f-e86c-9884-9d8698a86a91@gmail.com> <20180603120834.GT1389@albert.catwhisker.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180603120834.GT1389@albert.catwhisker.org> User-Agent: Mutt/1.10.0 (2018-05-17) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 12:22:00 -0000 On Sun, Jun 03, 2018 at 05:08:34AM -0700, David Wolfskill wrote: > On Sun, Jun 03, 2018 at 06:48:01PM +0700, Alex V. Petrov wrote: > > .... > > --- nvidia_subr.o --- > > > > > > nvidia_subr.c:367:26: error: 'memset' call operates on objects of type > > 'struct nv_ioctl_card_info' while the size is based on a different type > > 'struct nv_ioctl_card_info *' [-Werror,-Wsizeof > > -pointer-memaccess] > > memset(ci, 0, sizeof(ci)); > > ~~ ^~ > > nvidia_subr.c:367:26: note: did you mean to dereference the argument to > > 'sizeof' (and multiply it by the number of elements)? > > > > memset(ci, 0, sizeof(ci)); > > ^~ > > 1 error generated. > > *** [nvidia_subr.o] Error code 1 > > .... > > Aye; please ref. > for > additional details. > > The issue has been narrowed down to the range r334529 - r334535; I'm > suspecting r334533 and/or r334534. (Not that the commits are in any way > "faulty" -- merely that the nvidia-driver port may need some "evasive > action" to allow for the change). Even not looking at the actual code, I am quite sure that the line nvidia_subr.c:367 should be changed to memset(ci, 0, sizeof(*ci)); This is a bug in the driver sources. From owner-freebsd-current@freebsd.org Sun Jun 3 12:34:25 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 58F6CF75938 for ; Sun, 3 Jun 2018 12:34:25 +0000 (UTC) (envelope-from waitman@waitman.net) Received: from mail2.protonmail.ch (mail2.protonmail.ch [185.70.40.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.protonmail.ch", Issuer "QuoVadis Global SSL ICA G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E308E82B88 for ; Sun, 3 Jun 2018 12:34:24 +0000 (UTC) (envelope-from waitman@waitman.net) Date: Sun, 03 Jun 2018 08:34:13 -0400 To: "freebsd-current@freebsd.org" From: Waitman Gobble Reply-To: Waitman Gobble Subject: Re: Error build nvidia-driver with r334555 Message-ID: In-Reply-To: <20180603122142.GM3789@kib.kiev.ua> References: <83fec8d8-699f-e86c-9884-9d8698a86a91@gmail.com> <20180603120834.GT1389@albert.catwhisker.org> <20180603122142.GM3789@kib.kiev.ua> Feedback-ID: a9EiCCViSiSHQ6Bx5OnM7zSE3j9mdPjjMltovBgA7v_vv_C4nKI9vbMXvmk_xW33cGmibh2zGAa2Co0Llrno4A==:Ext:ProtonMail MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.1 required=5.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.protonmail.ch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 12:34:25 -0000 =E2=80=8B =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me= ssage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 On June 3, 2018 8:21 AM, Konstantin Belousov wrote: > On Sun, Jun 03, 2018 at 05:08:34AM -0700, David Wolfskill wrote: >=20 > > On Sun, Jun 03, 2018 at 06:48:01PM +0700, Alex V. Petrov wrote: > >=20 > > > .... > > >=20 > > > --- nvidia_subr.o --- > > >=20 > > > nvidia_subr.c:367:26: error: 'memset' call operates on objects of typ= e > > >=20 > > > 'struct nv_ioctl_card_info' while the size is based on a different ty= pe > > >=20 > > > 'struct nv_ioctl_card_info *' [-Werror,-Wsizeof > > >=20 > > > -pointer-memaccess] > > >=20 > > > memset(ci, 0, sizeof(ci)); > > >=20 > > > ~~ ^~ > > >=20 > > > nvidia_subr.c:367:26: note: did you mean to dereference the argument = to > > >=20 > > > 'sizeof' (and multiply it by the number of elements)? > > >=20 > > > memset(ci, 0, sizeof(ci)); > > > ^~ > > > =20 > > >=20 > > > 1 error generated. > > >=20 > > > *** [nvidia_subr.o] Error code 1 > > >=20 > > > .... > >=20 > > Aye; please ref. > >=20 > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228709 for > >=20 > > additional details. > >=20 > > The issue has been narrowed down to the range r334529 - r334535; I'm > >=20 > > suspecting r334533 and/or r334534. (Not that the commits are in any way > >=20 > > "faulty" -- merely that the nvidia-driver port may need some "evasive > >=20 > > action" to allow for the change). >=20 > Even not looking at the actual code, I am quite sure that the line >=20 > nvidia_subr.c:367 should be changed to >=20 > memset(ci, 0, sizeof(*ci)); >=20 > This is a bug in the driver sources. >=20 > freebsd-current@freebsd.org mailing list >=20 > https://lists.freebsd.org/mailman/listinfo/freebsd-current >=20 > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " That solved the build problem for me.=20 I haven't noticed any other issues with nvidia driver. Waitman Gobble Sent with ProtonMail Secure Email.=E2=80=8B From owner-freebsd-current@freebsd.org Sun Jun 3 12:42:34 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E10EAF76CC4 for ; Sun, 3 Jun 2018 12:42:33 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from dec.sakura.ne.jp (dec.sakura.ne.jp [210.188.226.8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 356808328E; Sun, 3 Jun 2018 12:42:32 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from fortune.joker.local (124-18-70-98.dz.commufa.jp [124.18.70.98]) (authenticated bits=0) by dec.sakura.ne.jp (8.15.2/8.15.2/[SAKURA-WEB]/20080708) with ESMTPA id w53CgMet065165; Sun, 3 Jun 2018 21:42:22 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Sun, 3 Jun 2018 21:42:22 +0900 From: Tomoaki AOKI To: freebsd-current@freebsd.org Cc: alexvpetrov@gmail.com, mjg@FreeBSD.org, danfe@FreeBSD.org, ler@FreeBSD.org Subject: Re: Error build nvidia-driver with r334555 Message-Id: <20180603214222.953748e1eb7a0b39e11214ae@dec.sakura.ne.jp> In-Reply-To: <83fec8d8-699f-e86c-9884-9d8698a86a91@gmail.com> References: <83fec8d8-699f-e86c-9884-9d8698a86a91@gmail.com> Reply-To: junchoon@dec.sakura.ne.jp Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd11.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 12:42:34 -0000 This is caused by r334533 and/or r334534 (memset-related changes). sysutils/lsof is also affected. You should revert r334533 and r334534 temporarily until nvidia-driver support this change. CC'ing the revision author and maintainers of both ports. On Sun, 3 Jun 2018 18:48:01 +0700 "Alex V. Petrov" wrote: > cc -O2 -pipe -fno-strict-aliasing -DNV_VERSION_STRING=\"390.59\" > -D__KERNEL__ -DNVRM -Wno-unused-function -Wuninitialized -O2 > -fno-strict-aliasing -mno-red-zone -mcmodel=kernel -Wno-sign-co > mpare -Wno-format-extra-args -UDEBUG -U_DEBUG -DNDEBUG -Werror=undef > -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I../common/inc -I. > -I/usr/src/sys -I/usr/src/sys/contrib/ck/include -fno- > common -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -MD > -MF.depend.nvlink_freebsd.o -MTnvlink_freebsd.o -mcmodel=kernel > -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchr > onous-unwind-tables -ffreestanding -fwrapv -fstack-protector -Wall > -Wredundant-decls -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Wcast-qual -Wundef -Wno-pointe > r-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-equ > ality -Wno-error-unused-function -Wno-error-pointer-sign > -Wno-error-shift-negative-value -Wno-address-of-packed-member -mno-aes > -mno-avx -std=iso9899:1999 -c nvlink_freebsd.c -o nvlink_fre > ebsd.o > > > --- nvidia_subr.o --- > > > nvidia_subr.c:367:26: error: 'memset' call operates on objects of type > 'struct nv_ioctl_card_info' while the size is based on a different type > 'struct nv_ioctl_card_info *' [-Werror,-Wsizeof > -pointer-memaccess] > memset(ci, 0, sizeof(ci)); > ~~ ^~ > nvidia_subr.c:367:26: note: did you mean to dereference the argument to > 'sizeof' (and multiply it by the number of elements)? > > memset(ci, 0, sizeof(ci)); > ^~ > 1 error generated. > *** [nvidia_subr.o] Error code 1 > > make[4]: stopped in > /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86_64-390.59/src/nvidia > 1 error > > make[4]: stopped in > /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86_64-390.59/src/nvidia > *** [all_subdir_src/nvidia] Error code 2 > > make[3]: stopped in > /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86_64-390.59/src > 1 error > > make[3]: stopped in > /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86_64-390.59/src > *** [all_subdir_src] Error code 2 > > make[2]: stopped in > /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86_64-390.59 > 1 error > > make[2]: stopped in > /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86_64-390.59 > ===> Compilation failed unexpectedly. > Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to > the maintainer. > *** Error code 1 > > -- > ----- > Alex. > _______________________________________________ > 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" > -- Tomoaki AOKI From owner-freebsd-current@freebsd.org Sun Jun 3 12:48:49 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C736CF77B3A for ; Sun, 3 Jun 2018 12:48:49 +0000 (UTC) (envelope-from freebsd@grem.de) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id 5290383746 for ; Sun, 3 Jun 2018 12:48:48 +0000 (UTC) (envelope-from freebsd@grem.de) Received: (qmail 81891 invoked by uid 89); 3 Jun 2018 12:48:42 -0000 Received: from unknown (HELO bsd64.grem.de) (mg@grem.de@194.97.158.70) by mail.grem.de with ESMTPA; 3 Jun 2018 12:48:42 -0000 Date: Sun, 3 Jun 2018 14:48:40 +0200 From: Michael Gmelin To: "freebsd-current@freebsd.org" Cc: Matthias Apitz , jhb@freebsd.org Subject: Fatal trap 12: page fault on Acer Chromebook 720 (peppy) Message-ID: <20180603144840.44bfea41@bsd64.grem.de> X-Mailer: Claws Mail 3.15.1 (GTK+ 2.24.31; amd64-portbld-freebsd10.3) X-Face: $wrgCtfdVw_H9WAY?S&9+/F"!41z'L$uo*WzT8miX?kZ~W~Lr5W7v?j0Sde\mwB&/ypo^}> +a'4xMc^^KroE~+v^&^#[B">soBo1y6(TW6#UZiC]o>C6`ej+i Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEWJBwe5BQDl LASZU0/LTEWEfHbyj0Txi32+sKrp1Mv944X8/fm1rS+cAAAACXBIWXMAAAsTAAAL EwEAmpwYAAAAB3RJTUUH3wESCxwC7OBhbgAAACFpVFh0Q29tbWVudAAAAAAAQ3Jl YXRlZCB3aXRoIFRoZSBHSU1QbbCXAAAAAghJREFUOMu11DFvEzEUAGCfEhBVFzuq AKkLd0O6VrIQsLXVSZXoWE5N1K3DobBBA9fQpRWc8OkWouaIjedWKiyREOKs+3PY fvalCNjgLVHeF7/3bMtBzV8C/VsQ8tecEgCcDgrzjekwKZ7TwsJZd/ywEKwwP+ZM 8P3drTsAwWn2mpWuDDuYiK1bFs6De0KUUFw0tWxm+D4AIhuuvZqtyWYeO7jQ4Aea 7jUqI+ixhQoHex4WshEvSXdood7stlv4oSuFOC4tqGcr0NjEqXgV4mMJO38nld4+ xKNxRDon7khyKVqY7YR4d+Cg0OMrkWXZOM7YDkEfKiilCn1qYv4mighZiynuHHOA Wq9QJq+BIES7lMFUtcikMnkDGHUoncA+uHgrP0ctIEqfwLHzeSo+eUA66AqzwN6n 2ZHJhw6Qh/PoyC/QENyEyC/AyNjq74Bs+3UH0xYwzDUC4B97HgLocg1QLYgDDO1v f3UX9Y307Ew4AHh67YAFFsxEpkXwpXY3eIgMhAAE3R19L919nNnuD2wlPcDE3UeT L2ytEICQib9BXgS2fU8PrD82ToYO1OEmMSnYTjSqSv9wdC0tPYC+rQRQD9ESnldF CyqfmiYW+tlALt8gH2xrMdC/youbjzPXEun+/ReXsMCDyve3dZc09fn2Oas8oXGc Jj6/fOeK5UmSMPmf/jL+GD8BEj0k/Fn6IO4AAAAASUVORK5CYII= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 12:48:50 -0000 Hi, After upgrading CURRENT to r333992 (from something at least a year old, quite some changes in mp_machdep.c since), this machine crashes on boot: Copyright (c) 1992-2018 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 12.0-CURRENT #1 r333992: Tue May 22 00:31:04 CEST 2018 root@flimsy:/usr/obj/usr/src/amd64.amd64/sys/flimsy amd64 FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) (based on LLVM 6.0.0) WARNING: WITNESS option enabled, expect reduced performance. VT(vga): resolution 640x480 CPU: Intel(R) Celeron(R) 2955U @ 1.40GHz (1396.80-MHz K8-class CPU) Origin="GenuineIntel" Id=0x40651 Family=0x6 Model=0x45 Stepping=1 Features=0xbfebfbff Features2=0x4ddaebbf AMD Features=0x2c100800 AMD Features2=0x21 Structured Extended Features=0x2603 XSAVE Features=0x1 VT-x: (disabled in BIOS) PAT,HLT,MTF,PAUSE,EPT,UG,VPID TSC: P-state invariant, performance statistics real memory = 4301258752 (4102 MB) avail memory = 1907572736 (1819 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0xfffff80001000000 fault code = supervisor write data, protection violation instruction pointer = 0x20:Oxffffffff8102955f stack pointer = 0x28:0xffffffff82a79be0 frame pointer = 0x28:0xffffffff82a79c10 code segment = base Ox0, limit Oxfffff, type Ox1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = resume, IOPL = 0 current process = 0 () [ thread pid 0 tid 0 ] Stopped at native_start_all_aps+0x08f: movq %rax,(%rsi) db> Any key press in the debugger will reboot the machine. Booting with kern.smp.disabled=1 works. Any ideas? -m -- Michael Gmelin From owner-freebsd-current@freebsd.org Sun Jun 3 13:20:26 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EA410F7CCE1 for ; Sun, 3 Jun 2018 13:20:25 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-qk0-x242.google.com (mail-qk0-x242.google.com [IPv6:2607:f8b0:400d:c09::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 86B5D84B9F; Sun, 3 Jun 2018 13:20:25 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: by mail-qk0-x242.google.com with SMTP id d130-v6so17869973qkc.2; Sun, 03 Jun 2018 06:20:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=fY4BTTFswERKq9rX+5Y0B/xjby0Y+zXPuLsxdW4Tgas=; b=uUTi5rsbCoRAv25pzDgtubGTlf/hVaAiczxzaKiPgtfP0KBmNYcniTG8j+1ZSrkt0V B0GQhSJPpG7gPirRNypousnqyU2Rs37EDCQMnCBBLoSHccr+YQnATPOiQ/j2efhwvtrQ JN28sX1FXGAk1d7DSy274nOnqI2Ww/SzXXio4n2x+uYRtQWJS8VB96VRR2y+TgI8gq1G /mbqSWzcJz3bput1AuPbGxfRZu3rNnYt7Lv2f0Gn4tBlSF7MkeagEq354dI0MnEu9X1O l11M6GtCRxy5b8MH6+NCNdz83MyTU1TSYJveNA1VCaIQ/OLNNN1EQRe+LqLxRvNhgsr4 gt9w== 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=fY4BTTFswERKq9rX+5Y0B/xjby0Y+zXPuLsxdW4Tgas=; b=FquTFZke/jcSwhQhcBdsgu6n2Y/jebp0V3lht7SeWWaheUKQ2/cmKp4W1aN5a9Zt4e 8o/aHDwU9zCdUb9WQMB6w5NZi/TPkcIO+Rdl+tgVuLAhvT3N3P9FUh6xyFz561xDSODX T3oeMyihrxcSB+2u25MpFTmek7FqFw9CKpoNIWfDOnH5oHil/wLz3o/kQIK4h8vBiVyD wm2h/uOK7d+Lnd5OTH9Hn7YDblNyoziexSkoGpxi4RG1OgriCqHeem+nXvnhO0uXJH+k PxXFZQWjeY3sTK8TrnJkd215lXhk4hOB0SdaRnsuSQM62fbJFRbBaprfWFpggRhpc5/9 D49w== X-Gm-Message-State: APt69E385oRRGV9J0cBJhmBgZhiKXAOWW6qvwtxFn5dYEwd91NVT5mZZ zaUU0wOkCmFLLHECfcndvNu1LUGPa5DmSIWEzBk= X-Google-Smtp-Source: ADUXVKKo2BzUUGgXoun1AhXp52CgovkyzYXvDxStswp3yE0Y1f1YIcWQG9MUm58XhisTfaIYDdiIAG5/pLAvuAFQ5+I= X-Received: by 2002:a37:9342:: with SMTP id v63-v6mr16886369qkd.40.1528032025155; Sun, 03 Jun 2018 06:20:25 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ac8:1c4e:0:0:0:0:0 with HTTP; Sun, 3 Jun 2018 06:20:24 -0700 (PDT) In-Reply-To: <20180603214222.953748e1eb7a0b39e11214ae@dec.sakura.ne.jp> References: <83fec8d8-699f-e86c-9884-9d8698a86a91@gmail.com> <20180603214222.953748e1eb7a0b39e11214ae@dec.sakura.ne.jp> From: Mateusz Guzik Date: Sun, 3 Jun 2018 15:20:24 +0200 Message-ID: Subject: Re: Error build nvidia-driver with r334555 To: junchoon@dec.sakura.ne.jp Cc: FreeBSD Current , alexvpetrov@gmail.com, Mateusz Guzik , Alexey Dokuchaev , ler@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 13:20:26 -0000 On Sun, Jun 3, 2018 at 2:42 PM, Tomoaki AOKI wrote: > This is caused by r334533 and/or r334534 (memset-related changes). > sysutils/lsof is also affected. > > You should revert r334533 and r334534 temporarily until nvidia-driver > support this change. > > CC'ing the revision author and maintainers of both ports. > > Support in what sense? The error message clearly indicates a bug in the driver (also trivially fixable). Is there a problem adding a patch to files/? diff -ru src.orig/nvidia/nvidia_subr.c src/nvidia/nvidia_subr.c --- src.orig/nvidia/nvidia_subr.c 2018-06-03 13:19:56.490480000 +0000 +++ src/nvidia/nvidia_subr.c 2018-06-03 13:21:15.289344000 +0000 @@ -364,7 +364,7 @@ } ci = args; - memset(ci, 0, sizeof(ci)); + memset(ci, 0, sizeof(*ci)); for (i = 0; i < NV_MAX_DEVICES; i++) { sc = devclass_get_softc(nvidia_devclass, i); As for lsof: --- dlsof.h.orig 2018-06-03 13:16:14.712701000 +0000 +++ dlsof.h 2018-06-03 13:17:15.042655000 +0000 @@ -489,6 +489,12 @@ # endif /* FREEBSDV>=2020 */ #undef bzero /* avoid _KERNEL conflict */ +#undef bcmp +#undef bcopy +#undef memcmp +#undef memmove +#undef memcpy +#undef memset #include -- Mateusz Guzik From owner-freebsd-current@freebsd.org Sun Jun 3 13:21:21 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4DF7CF7CFF8 for ; Sun, 3 Jun 2018 13:21:21 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C75BC84E10; Sun, 3 Jun 2018 13:21:20 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTP id w53DLAFO067979; Sun, 3 Jun 2018 16:21:13 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w53DLAFO067979 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w53DLA83067977; Sun, 3 Jun 2018 16:21:10 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 3 Jun 2018 16:21:10 +0300 From: Konstantin Belousov To: Michael Gmelin Cc: "freebsd-current@freebsd.org" , Matthias Apitz , jhb@freebsd.org Subject: Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy) Message-ID: <20180603132110.GP3789@kib.kiev.ua> References: <20180603144840.44bfea41@bsd64.grem.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180603144840.44bfea41@bsd64.grem.de> User-Agent: Mutt/1.10.0 (2018-05-17) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 13:21:21 -0000 On Sun, Jun 03, 2018 at 02:48:40PM +0200, Michael Gmelin wrote: > Hi, > > After upgrading CURRENT to r333992 (from something at least a year > old, quite some changes in mp_machdep.c since), this machine crashes > on boot: > > Copyright (c) 1992-2018 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 12.0-CURRENT #1 r333992: Tue May 22 00:31:04 CEST 2018 > root@flimsy:/usr/obj/usr/src/amd64.amd64/sys/flimsy amd64 > FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) (based on LLVM 6.0.0) > WARNING: WITNESS option enabled, expect reduced performance. > VT(vga): resolution 640x480 > CPU: Intel(R) Celeron(R) 2955U @ 1.40GHz (1396.80-MHz K8-class CPU) > Origin="GenuineIntel" Id=0x40651 Family=0x6 Model=0x45 Stepping=1 > Features=0xbfebfbff CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > Features2=0x4ddaebbf xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,TSCDLT,XSAVE,OSXSAVE,RDRAND> > AMD Features=0x2c100800 > AMD Features2=0x21 > Structured Extended Features=0x2603 > XSAVE Features=0x1 > VT-x: (disabled in BIOS) PAT,HLT,MTF,PAUSE,EPT,UG,VPID > TSC: P-state invariant, performance statistics > real memory = 4301258752 (4102 MB) > avail memory = 1907572736 (1819 MB) > Event timer "LAPIC" quality 600 > ACPI APIC Table: What does this mean ? Did you flashed coreboot ? > kernel trap 12 with interrupts disabled > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0xfffff80001000000 > fault code = supervisor write data, protection violation > instruction pointer = 0x20:Oxffffffff8102955f > stack pointer = 0x28:0xffffffff82a79be0 > frame pointer = 0x28:0xffffffff82a79c10 > code segment = base Ox0, limit Oxfffff, type Ox1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = resume, IOPL = 0 > current process = 0 () > [ thread pid 0 tid 0 ] > Stopped at native_start_all_aps+0x08f: movq %rax,(%rsi) Look up the source line number for this address. > db> > > Any key press in the debugger will reboot the machine. > > Booting with kern.smp.disabled=1 works. > > Any ideas? > > -m > > -- > Michael Gmelin > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Sun Jun 3 13:30:58 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A5DF2F7E1BA for ; Sun, 3 Jun 2018 13:30:58 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org (thebighonker.lerctr.org [IPv6:2001:470:1f0f:3ad:bb:dcff:fe50:d900]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.lerctr.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48956854B9; Sun, 3 Jun 2018 13:30:58 +0000 (UTC) (envelope-from ler@lerctr.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lerctr.org; s=lerami; h=Content-type:Mime-version:In-Reply-To:References:Message-ID:CC: To:From:Subject:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=2LpcuLjnrinqR4nURMe5TqUOVGUy0zUsFfbapfuDd18=; b=Qd6jcBnrrsBiSHDPu/DWenQ40m i4EJyEXISvLWZDYfMsTgyseDAW+GhXwcFQxpLyhzQNg79m6ev7aDAJ4aWsdQADzn8XyS9fLPnZ+k4 HbPedmfR2cwef2KzYscQT5uyTm7wdyqq22N4EU4ZSwpTnf4lokE27GLWJ5K+T/On/fu8=; Received: from [2600:1700:210:b18f:3c8b:5e5:f3d8:df46] (port=60944 helo=[192.168.200.50]) by thebighonker.lerctr.org with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91 (FreeBSD)) (envelope-from ) id 1fPT60-000A55-5l; Sun, 03 Jun 2018 08:30:56 -0500 User-Agent: Microsoft-MacOutlook/10.f.0.180530 Date: Sun, 03 Jun 2018 08:30:54 -0500 Subject: Re: Error build nvidia-driver with r334555 From: Larry Rosenman To: Mateusz Guzik , CC: FreeBSD Current , , Mateusz Guzik , Alexey Dokuchaev Message-ID: <8E820581-3359-4EBA-8C82-6B35638E9920@lerctr.org> Thread-Topic: Error build nvidia-driver with r334555 References: <83fec8d8-699f-e86c-9884-9d8698a86a91@gmail.com> <20180603214222.953748e1eb7a0b39e11214ae@dec.sakura.ne.jp> In-Reply-To: Mime-version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 13:30:58 -0000 sysutils/lsof fixed in r471495. Thanks, Mateusz! -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: ler@lerctr.org US Mail: 5708 Sabbia Drive, Round Rock, TX 78665-2106 From: Mateusz Guzik Date: Sunday, June 3, 2018 at 8:20 AM To: Cc: "freebsd-current@freebsd.org" , , Mateusz Guzik , Alexey Dokuchaev , Subject: Re: Error build nvidia-driver with r334555 On Sun, Jun 3, 2018 at 2:42 PM, Tomoaki AOKI wrote: This is caused by r334533 and/or r334534 (memset-related changes). sysutils/lsof is also affected. You should revert r334533 and r334534 temporarily until nvidia-driver support this change. CC'ing the revision author and maintainers of both ports. Support in what sense? The error message clearly indicates a bug in the driver (also trivially fixable). Is there a problem adding a patch to files/? diff -ru src.orig/nvidia/nvidia_subr.c src/nvidia/nvidia_subr.c --- src.orig/nvidia/nvidia_subr.c 2018-06-03 13:19:56.490480000 +0000 +++ src/nvidia/nvidia_subr.c 2018-06-03 13:21:15.289344000 +0000 @@ -364,7 +364,7 @@ } ci = args; - memset(ci, 0, sizeof(ci)); + memset(ci, 0, sizeof(*ci)); for (i = 0; i < NV_MAX_DEVICES; i++) { sc = devclass_get_softc(nvidia_devclass, i); As for lsof: --- dlsof.h.orig 2018-06-03 13:16:14.712701000 +0000 +++ dlsof.h 2018-06-03 13:17:15.042655000 +0000 @@ -489,6 +489,12 @@ # endif /* FREEBSDV>=2020 */ #undef bzero /* avoid _KERNEL conflict */ +#undef bcmp +#undef bcopy +#undef memcmp +#undef memmove +#undef memcpy +#undef memset #include -- Mateusz Guzik From owner-freebsd-current@freebsd.org Sun Jun 3 14:31:20 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 995C9FDB083 for ; Sun, 3 Jun 2018 14:31:20 +0000 (UTC) (envelope-from dsifriend@gmail.com) Received: from mail-vk0-x22e.google.com (mail-vk0-x22e.google.com [IPv6:2607:f8b0:400c:c05::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 2F40568523 for ; Sun, 3 Jun 2018 14:31:20 +0000 (UTC) (envelope-from dsifriend@gmail.com) Received: by mail-vk0-x22e.google.com with SMTP id w8-v6so3621396vkh.4 for ; Sun, 03 Jun 2018 07:31:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=5SaJI3Xp0yZIrfTH1RY4T0KHrndsAiiV97xXos1bnkE=; b=XWW4t4RhOVzsI//OMEAeh7qwTQQfG6F0hgo+E+p5icnzCQIgYOZMP615064pmrALPd hgUgyvCCoUcmQn1YbixEREpDDDUXfUr2/qWHip3nrLQfZGAa3/42WD99UxQYAzci3z4M sPZSBKWGVVyqfk3FcEj2Bs56XnQaZJe7CR8iQYNIIPfWJ0sY+o00ojdbKsIAL+RUZlco dlVaLBaXxOjYNP+W/bg4GZzkvpKXp5etS7PDomId5JaSU6mG0zIMiYspnRyVyA3o1Hu3 bnp7Vc6C2JrZpmqh06j6TftWeqRqIAjhVSiFikLD84+nzu1NjELli/wI6gn3uwxDgKCj Rslw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=5SaJI3Xp0yZIrfTH1RY4T0KHrndsAiiV97xXos1bnkE=; b=TPAWNGKAVAqQM45MMNnqRHSx07SxWynAPZ7YJc81nXiMaoxpqL3ZQ0yiNnxUGkLZBp bdD6PkrheGMzfHcjL4tgsLTX3WGpekpdV3EUAx9h1U53qu2zkE36AkzUtGpVrG3u4zJF 0NsLNz4pGME5GYYDp1Dj+CY/FE8H8qQ8odGlGgHpF8YSp1Tn/ZVZWnfJDME2ND+oUXue EpbMt0LMtClSvC8i6rWAGlP7q4RVCL1wMSA7z6GDbwjIbgayy6TxgKd7eydTdOue/r1j aEsMsi9PU3EIPiaAdry8UZlKWa8q/eCSadykggGck8TOvDmPUS4dro0S8ubaKIxIMgcD RESA== X-Gm-Message-State: ALKqPweOLLtGZr6OlEyIMEz0JHQom91Wl3QaIGL1p79aF/cDPIgscxbg LUtQWqVgI8t4vvxoCzzRC6nhO2VQ X-Google-Smtp-Source: ADUXVKJGu3DJSzNSgMNKSjCBQ/NMNXNeRB36gA9K11YewDZ+wjBrsXCaSmKbcgxvAO5/ECa95dYwew== X-Received: by 2002:a1f:5fc1:: with SMTP id t184-v6mr10912966vkb.140.1528036279416; Sun, 03 Jun 2018 07:31:19 -0700 (PDT) Received: from [192.168.1.117] ([24.171.250.32]) by smtp.gmail.com with ESMTPSA id 123-v6sm15756107vkg.47.2018.06.03.07.31.18 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 03 Jun 2018 07:31:18 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted From: Albert Gem X-Mailer: iPhone Mail (15E302) In-Reply-To: Date: Sun, 3 Jun 2018 10:31:15 -0400 Cc: freebsd-current Content-Transfer-Encoding: 7bit Message-Id: References: <247b08cf-29ae-2410-ed52-1f211c1df565@gmail.com> To: Idwer Vollering X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 14:31:20 -0000 SeaBIOS 1.10.2 Upgrading seems to do the trick > Am 03.06.2018 um 06:25 schrieb Idwer Vollering : > > 2018-06-03 7:23 GMT+02:00 Albert : >> Hi, >> >> >> I successfully tested the memstick.img on: >> Acer Chromebook 14 (EDGAR) [CB3-431-C5EX] >> >> The Results: >> UEFI (Coreboot) works perfectly, no issues there. >> BIOS (SeaBIOS) does *NOT* work. It puts the machine into a bootloop until >> the install medium is disconnected. It does, however, make it past the >> FreeBSD boot loader on the first try. > > That's odd, which version of SeaBIOS are you using? did you had to run > 'gpart recover '? > > CFT report: I'm able to boot > FreeBSD-12.0-CURRENT-amd64-20180529-r334337-mini-memstick.img using > coreboot with SeaBIOS 1.11.1 just fine. > >> >> >> >> >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Sun Jun 3 14:55:03 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EEE0FFDDDA1 for ; Sun, 3 Jun 2018 14:55:02 +0000 (UTC) (envelope-from freebsd@grem.de) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id 6E36B6969F for ; Sun, 3 Jun 2018 14:55:02 +0000 (UTC) (envelope-from freebsd@grem.de) Received: (qmail 83026 invoked by uid 89); 3 Jun 2018 14:55:01 -0000 Received: from unknown (HELO bsd64.grem.de) (mg@grem.de@194.97.158.70) by mail.grem.de with ESMTPA; 3 Jun 2018 14:55:01 -0000 Date: Sun, 3 Jun 2018 16:55:00 +0200 From: Michael Gmelin To: Konstantin Belousov Cc: Michael Gmelin , "freebsd-current@freebsd.org" , Matthias Apitz , jhb@freebsd.org Subject: Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy) Message-ID: <20180603165500.361ec894@bsd64.grem.de> In-Reply-To: <20180603132110.GP3789@kib.kiev.ua> References: <20180603144840.44bfea41@bsd64.grem.de> <20180603132110.GP3789@kib.kiev.ua> X-Mailer: Claws Mail 3.15.1 (GTK+ 2.24.31; amd64-portbld-freebsd10.3) X-Face: $wrgCtfdVw_H9WAY?S&9+/F"!41z'L$uo*WzT8miX?kZ~W~Lr5W7v?j0Sde\mwB&/ypo^}> +a'4xMc^^KroE~+v^&^#[B">soBo1y6(TW6#UZiC]o>C6`ej+i Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEWJBwe5BQDl LASZU0/LTEWEfHbyj0Txi32+sKrp1Mv944X8/fm1rS+cAAAACXBIWXMAAAsTAAAL EwEAmpwYAAAAB3RJTUUH3wESCxwC7OBhbgAAACFpVFh0Q29tbWVudAAAAAAAQ3Jl YXRlZCB3aXRoIFRoZSBHSU1QbbCXAAAAAghJREFUOMu11DFvEzEUAGCfEhBVFzuq AKkLd0O6VrIQsLXVSZXoWE5N1K3DobBBA9fQpRWc8OkWouaIjedWKiyREOKs+3PY fvalCNjgLVHeF7/3bMtBzV8C/VsQ8tecEgCcDgrzjekwKZ7TwsJZd/ywEKwwP+ZM 8P3drTsAwWn2mpWuDDuYiK1bFs6De0KUUFw0tWxm+D4AIhuuvZqtyWYeO7jQ4Aea 7jUqI+ixhQoHex4WshEvSXdood7stlv4oSuFOC4tqGcr0NjEqXgV4mMJO38nld4+ xKNxRDon7khyKVqY7YR4d+Cg0OMrkWXZOM7YDkEfKiilCn1qYv4mighZiynuHHOA Wq9QJq+BIES7lMFUtcikMnkDGHUoncA+uHgrP0ctIEqfwLHzeSo+eUA66AqzwN6n 2ZHJhw6Qh/PoyC/QENyEyC/AyNjq74Bs+3UH0xYwzDUC4B97HgLocg1QLYgDDO1v f3UX9Y307Ew4AHh67YAFFsxEpkXwpXY3eIgMhAAE3R19L919nNnuD2wlPcDE3UeT L2ytEICQib9BXgS2fU8PrD82ToYO1OEmMSnYTjSqSv9wdC0tPYC+rQRQD9ESnldF CyqfmiYW+tlALt8gH2xrMdC/youbjzPXEun+/ReXsMCDyve3dZc09fn2Oas8oXGc Jj6/fOeK5UmSMPmf/jL+GD8BEj0k/Fn6IO4AAAAASUVORK5CYII= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 14:55:03 -0000 On Sun, 3 Jun 2018 16:21:10 +0300 Konstantin Belousov wrote: > On Sun, Jun 03, 2018 at 02:48:40PM +0200, Michael Gmelin wrote: > > Hi, > > > > After upgrading CURRENT to r333992 (from something at least a year > > old, quite some changes in mp_machdep.c since), this machine crashes > > on boot: > > > > Copyright (c) 1992-2018 The FreeBSD Project. > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, > > 1994 The Regents of the University of California. All rights > > reserved. FreeBSD is a registered trademark of The FreeBSD > > Foundation. FreeBSD 12.0-CURRENT #1 r333992: Tue May 22 00:31:04 > > CEST 2018 root@flimsy:/usr/obj/usr/src/amd64.amd64/sys/flimsy amd64 > > FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) (based > > on LLVM 6.0.0) WARNING: WITNESS option enabled, expect reduced > > performance. VT(vga): resolution 640x480 > > CPU: Intel(R) Celeron(R) 2955U @ 1.40GHz (1396.80-MHz K8-class CPU) > > Origin="GenuineIntel" Id=0x40651 Family=0x6 Model=0x45 > > Stepping=1 > > Features=0xbfebfbff > CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > > Features2=0x4ddaebbf > xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,TSCDLT,XSAVE,OSXSAVE,RDRAND> > > AMD Features=0x2c100800 AMD > > Features2=0x21 Structured Extended > > Features=0x2603 XSAVE > > Features=0x1 VT-x: (disabled in BIOS) > > PAT,HLT,MTF,PAUSE,EPT,UG,VPID TSC: P-state invariant, performance > > statistics real memory = 4301258752 (4102 MB) > > avail memory = 1907572736 (1819 MB) > > Event timer "LAPIC" quality 600 > > ACPI APIC Table: > What does this mean ? Did you flashed coreboot ? This machine comes with it by default (my model was delivered with SeaBIOS 20131018_145217-build121-m2). So I didn't flash anything (didn't feel like bricking it). > > > kernel trap 12 with interrupts disabled > > > > Fatal trap 12: page fault while in kernel mode > > cpuid = 0; apic id = 00 > > fault virtual address = 0xfffff80001000000 > > fault code = supervisor write data, protection > > violation instruction pointer = 0x20:Oxffffffff8102955f > > stack pointer = 0x28:0xffffffff82a79be0 > > frame pointer = 0x28:0xffffffff82a79c10 > > code segment = base Ox0, limit Oxfffff, type Ox1b > > = DPL 0, pres 1, long 1, def32 0, gran 1 > > processor eflags = resume, IOPL = 0 > > current process = 0 () > > [ thread pid 0 tid 0 ] > > Stopped at native_start_all_aps+0x08f: movq > > %rax,(%rsi) > Look up the source line number for this address. > I guess that's sys/amd64/amd64/support.S line 854 (in rdmsr), called by native_start_all_aps. Any additional hints how I can track it down? Thanks, Michael > > db> > > > > Any key press in the debugger will reboot the machine. > > > > Booting with kern.smp.disabled=1 works. > > > > Any ideas? > > > > -m > > > > -- > > Michael Gmelin > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to > > "freebsd-current-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" -- Michael Gmelin From owner-freebsd-current@freebsd.org Sun Jun 3 15:04:35 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 39382FDF00F for ; Sun, 3 Jun 2018 15:04:35 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AFED869D55; Sun, 3 Jun 2018 15:04:34 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTP id w53F4Nq0030057; Sun, 3 Jun 2018 18:04:26 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w53F4Nq0030057 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w53F4Nc7030056; Sun, 3 Jun 2018 18:04:23 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 3 Jun 2018 18:04:23 +0300 From: Konstantin Belousov To: Michael Gmelin Cc: "freebsd-current@freebsd.org" , Matthias Apitz , jhb@freebsd.org Subject: Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy) Message-ID: <20180603150423.GQ3789@kib.kiev.ua> References: <20180603144840.44bfea41@bsd64.grem.de> <20180603132110.GP3789@kib.kiev.ua> <20180603165500.361ec894@bsd64.grem.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180603165500.361ec894@bsd64.grem.de> User-Agent: Mutt/1.10.0 (2018-05-17) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 15:04:35 -0000 On Sun, Jun 03, 2018 at 04:55:00PM +0200, Michael Gmelin wrote: > > > On Sun, 3 Jun 2018 16:21:10 +0300 > Konstantin Belousov wrote: > > > On Sun, Jun 03, 2018 at 02:48:40PM +0200, Michael Gmelin wrote: > > > Hi, > > > > > > After upgrading CURRENT to r333992 (from something at least a year > > > old, quite some changes in mp_machdep.c since), this machine crashes > > > on boot: > > > > > > Copyright (c) 1992-2018 The FreeBSD Project. > > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, > > > 1994 The Regents of the University of California. All rights > > > reserved. FreeBSD is a registered trademark of The FreeBSD > > > Foundation. FreeBSD 12.0-CURRENT #1 r333992: Tue May 22 00:31:04 > > > CEST 2018 root@flimsy:/usr/obj/usr/src/amd64.amd64/sys/flimsy amd64 > > > FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) (based > > > on LLVM 6.0.0) WARNING: WITNESS option enabled, expect reduced > > > performance. VT(vga): resolution 640x480 > > > CPU: Intel(R) Celeron(R) 2955U @ 1.40GHz (1396.80-MHz K8-class CPU) > > > Origin="GenuineIntel" Id=0x40651 Family=0x6 Model=0x45 > > > Stepping=1 > > > Features=0xbfebfbff > > CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > > > Features2=0x4ddaebbf > > xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,TSCDLT,XSAVE,OSXSAVE,RDRAND> > > > AMD Features=0x2c100800 AMD > > > Features2=0x21 Structured Extended > > > Features=0x2603 XSAVE > > > Features=0x1 VT-x: (disabled in BIOS) > > > PAT,HLT,MTF,PAUSE,EPT,UG,VPID TSC: P-state invariant, performance > > > statistics real memory = 4301258752 (4102 MB) > > > avail memory = 1907572736 (1819 MB) > > > Event timer "LAPIC" quality 600 > > > ACPI APIC Table: > > What does this mean ? Did you flashed coreboot ? > > This machine comes with it by default (my model was delivered with > SeaBIOS 20131018_145217-build121-m2). So I didn't flash anything > (didn't feel like bricking it). > > > > > > kernel trap 12 with interrupts disabled > > > > > > Fatal trap 12: page fault while in kernel mode > > > cpuid = 0; apic id = 00 > > > fault virtual address = 0xfffff80001000000 > > > fault code = supervisor write data, protection > > > violation instruction pointer = 0x20:Oxffffffff8102955f > > > stack pointer = 0x28:0xffffffff82a79be0 > > > frame pointer = 0x28:0xffffffff82a79c10 > > > code segment = base Ox0, limit Oxfffff, type Ox1b > > > = DPL 0, pres 1, long 1, def32 0, gran 1 > > > processor eflags = resume, IOPL = 0 > > > current process = 0 () > > > [ thread pid 0 tid 0 ] > > > Stopped at native_start_all_aps+0x08f: movq > > > %rax,(%rsi) > > Look up the source line number for this address. > > > > I guess that's sys/amd64/amd64/support.S line 854 (in rdmsr), called by > native_start_all_aps. Any additional hints how I can track it down? Why did you decided that this is rdmsr_safe() ? First, native_start_all_aps() does not call rdmsr, second the ddb report clearly indicates that the fault occured acessing DMAP in native_start_all_aps(). Just look up the source line by the address native_start_all_aps+0x08f. From owner-freebsd-current@freebsd.org Sun Jun 3 15:12:18 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 14930FE0160 for ; Sun, 3 Jun 2018 15:12:18 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-yw0-x242.google.com (mail-yw0-x242.google.com [IPv6:2607:f8b0:4002:c05::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A63E76A5CD for ; Sun, 3 Jun 2018 15:12:17 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-yw0-x242.google.com with SMTP id v68-v6so9744573ywd.3 for ; Sun, 03 Jun 2018 08:12:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=n/umkDUQQTqKL0aa14ssEA0Qu5cODIeP8+6B4hPPNzA=; b=fMRAafY11WbLuPCfAsLqoT66eRWj5RMcZ+AqhARQGK8FZm5jPb7lRNDO6Nya3uN7yg osVqWrWC/wI9et4wCKURy9p5HDQ2ldJefQMNeeRuPqcDArF0LIT6WSH9wQhOfTNVVMUT x6Z/lHB0zWpbVeg7FxJcx/AnYDlNq65M1+Dpo= 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=n/umkDUQQTqKL0aa14ssEA0Qu5cODIeP8+6B4hPPNzA=; b=e+/FafUzTYh8AxsVpXPqmdNw1BfRyHdggfY3s6RDmhQIBcqyLRnoKkj1ieM4vjglNW lnbaIJW5PhtX1QI2AChwj7nK54HE+KfNDWadp375eYgxDbaVeQ+3I257utYSqlIWob4B TDQxftoJR9qKWTpdB6Tm7jOlx0cPM4ImS+pogal8cuuxMwMbuLS0LZpcYmbS0tqA1c00 k31K7U8BE+4s9spqSE+7tzDnJStLvb3CbX+LyxOsfeJLmJR6avbkYfYIkWWVncGFRG0y S2z41EKyrKHQV2N1piYqs0+vVlrLVEjHdXt3QPHQSI7ElfhaMy6USbR/mekdhznzItF4 qGJQ== X-Gm-Message-State: ALKqPwdnCID0+z+CyHEg5SeaCx5GGxTYDDZsxFxnpsYcvGXV/tyof+7y 40zdrG/TAzmpaoYUT6Xl7MeAajiAvQX7Kf5x06zcaV+i X-Google-Smtp-Source: ADUXVKLkQ/ZLoC/ps6F75vZoyR8vTycTu7ihAJzbDhLzxqukR40rZcNme5QESVjjVtsHV9PCTYQZbtguer0LSK/j+Z4= X-Received: by 2002:a81:af1d:: with SMTP id n29-v6mr9427905ywh.113.1528038736891; Sun, 03 Jun 2018 08:12:16 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a25:ef50:0:0:0:0:0 with HTTP; Sun, 3 Jun 2018 08:11:46 -0700 (PDT) In-Reply-To: <7464D18D-2879-4C2A-ADD3-BF84D80940BB@FreeBSD.org> References: <20180531095222.399e7a37@ernst.home> <20180531095850.5845fd7a@ernst.home> <20180531160406.GD27985@kduck.kaduk.org> <32C087A4-1B67-4694-B769-16A347D4804E@FreeBSD.org> <7464D18D-2879-4C2A-ADD3-BF84D80940BB@FreeBSD.org> From: Eitan Adler Date: Sun, 3 Jun 2018 08:11:46 -0700 Message-ID: Subject: Re: ``make buildkernel'' fails when /usr/obj is empty To: Dimitry Andric Cc: Warner Losh , Benjamin Kaduk , Gary Jennejohn , FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 15:12:18 -0000 On 31 May 2018 at 11:19, Dimitry Andric wrote: > On 31 May 2018, at 20:11, Warner Losh wrote: >> >> On Thu, May 31, 2018 at 11:47 AM, Dimitry Andric wrote: >> On 31 May 2018, at 18:04, Benjamin Kaduk wrote: >> > On Thu, May 31, 2018 at 09:58:50AM +0200, Gary Jennejohn wrote: >> >> On Thu, 31 May 2018 09:52:22 +0200 >> >> Gary Jennejohn wrote: > ... >> > Whatever happened to the "run buildworld or kernel-toolchain before >> > buildkernel" requirement? >> >> That is still a requirement, yes. Otherwise, you might have outdated >> toolchain components are in your /usr/obj. >> >> Usually you can get away without doing that, and now that clang is the toolchain that's rebuilt (and that's not fast) people try to get away with it more and more... > > Actually clang doesn't get updated *that* often, but there is a minor > snag that one of llvm's config files (lib/clang/include/llvm/Config/config.h) > includes , so each time __FreeBSD_version is bumped, quite > a lot of dependencies get triggered... > > The version is only used for two checks: > > #if __FreeBSD_version >= 1000052 > /* Define to 1 if you have the `backtrace' function. */ > #define HAVE_BACKTRACE TRUE > > and: > > /* Define to 1 if you have the `futimens' function. */ > #if __FreeBSD_version >= 1100056 > #define HAVE_FUTIMENS 1 > #endif > > Maybe the first check could be dropped, assuming that backtrace() is > always available, but I'm not sure about futimens(). Is there any > supported version of FreeBSD left that does *not* have it? 10.4 is supported until October 31, 2018 but it might be worth making the change in -current ? -- Eitan Adler From owner-freebsd-current@freebsd.org Sun Jun 3 14:53:51 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 178C6FDDB38 for ; Sun, 3 Jun 2018 14:53:51 +0000 (UTC) (envelope-from mail@dbalan.in) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AB28369644 for ; Sun, 3 Jun 2018 14:53:50 +0000 (UTC) (envelope-from mail@dbalan.in) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id A824F20CE1; Sun, 3 Jun 2018 10:53:49 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Sun, 03 Jun 2018 10:53:49 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dbalan.in; h=cc :content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=w8iBMSpHMja/doVjE7b8O/vfbBwz2lZBCCukTuxcIIk=; b=3IC4+BxB IdIKYzgJtrPrGNbEvT9o+XjU9rqzYvtP88qTxvcb2oN8E7MNpAiaupR/2o5Lnxrs Wrs3QRGeaGEwHNqlMpueFPdrtMiNBalUS7zMqKuz/iopfvuF2EfTjSV+A2vircix 7cEKP6/F732fjTQa0w9FxsUVPH2h0oNTuKJSeoWoX5DWkUZRtolXJbwqq+ICFu88 w0IaoMBupH54s9v5xtEIKjvCjC0Xk2vlzuhlnD/bBAESEO+Vde5t51m4bxzGFI5i vdevRgM2IpVB9dA9j2U0T0O/M3fBVeIln9uoST+0dLyinwFWQE8PXAVwZl6SNKUK OWG9e0LL5xpleQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=w8iBMSpHMja/doVjE7b8O/vfbBwz2 lZBCCukTuxcIIk=; b=Xd1lpDhPTN2I+aHtXJZHog2/c/ow8jS+o98u6jVBJAbwN QxIIshZ8mqkh7rcxT6/UAE5fXw0XKgLlPPmFkEfc0wbgHvHwNn3rRzAQx6uYeg16 lXAqD8JJRgI9jmXlVaxIhpNyZUrGBZGMr3xPpnbXRMB0t9YGRSr7lcS+7NoEB9LL qgVb9i3jjXnyRZqSeblMMkBPN3d+v1GJRyLLUxcay1lCxjmA6DYuzxTYs7EXYVJt aZWJXEcO5hTd54eId0+4Z6zlFyI+3MLjgs78MBqBz8cWM5c+zgocACyGXIOkmmtX G21AIykG45hRrYFL2TH53knyFv3vSJeepAiYmPFKA== X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Sender: Received: from localhost (unknown [106.51.19.236]) by mail.messagingengine.com (Postfix) with ESMTPA id D9B6E1027E; Sun, 3 Jun 2018 10:53:48 -0400 (EDT) Date: Sun, 3 Jun 2018 20:23:42 +0530 From: Dhananjay Balan To: Christoph Moench-Tegeder Cc: freebsd-current@freebsd.org Subject: Re: Can't seem to use 5GHz APs with Intel wireless Message-ID: <20180603145342.qziiv7awhr4cvs73@kazhap> References: <20180601091031.72u7tqfkatsl3guh@kazhap> <20180601223711.GA93642@elch.exwg.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180601223711.GA93642@elch.exwg.net> User-Agent: NeoMutt/20180512 X-Mailman-Approved-At: Sun, 03 Jun 2018 15:29:40 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 14:53:51 -0000 On Sat, Jun 02, 2018 at 12:37:12AM +0200, Christoph Moench-Tegeder wrote: > Did you try adding "mode 11a" to select 5GHz band? (This might be > out-of-date, as my WiFi stuff is all on 11) (currently I'm also > using 2.4GHz only, for compatibility with some devices and the fact > that I have quite some trouble running 2.4GHz and 5GHz from the same > interface at the same time). I did a bit more testing, I have to admit that I am not well versed in wifi internals. 1. ifconfig wlan0 list aps shows my aps having rate 54M (Im not entirely sure what this means). But however when I connect to it, it shows up as 11g wlan0: flags=8843 metric 0 mtu 1500 ether a4:4e:31:02:70:3c inet 192.168.23.111 netmask 0xffffff00 broadcast 192.168.23.255 nd6 options=29 media: IEEE 802.11 Wireless Ethernet MCS mode 11ng status: associated ssid LA03 channel 6 (2437 MHz 11g ht/20) bssid 52:d9:e7:47:c0:c2 regdomain FCC4 country DE authmode WPA2/802.11i privacy ON deftxkey UNDEF AES-CCM 2:128-bit txpower 30 bmiss 10 scanvalid 60 protmode CTS ampdulimit 64k ampdudensity 8 -amsdutx amsdurx shortgi -stbc -ldpc wme roaming MANUAL groups: wlan 2. Adding mode 11a to rc.conf didn't change anything. Still connects to 2.4Ghz band. 3. ifconfing wlan0 scan still doesn't show my 5Ghz only APs (at least some I tested) Also, what does 11a mean? shouldn't it be 11n? - dbalan From owner-freebsd-current@freebsd.org Sun Jun 3 16:06:08 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 58291FD36FB for ; Sun, 3 Jun 2018 16:06:08 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-io0-x241.google.com (mail-io0-x241.google.com [IPv6:2607:f8b0:4001:c06::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DF11B6C91C for ; Sun, 3 Jun 2018 16:06:07 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: by mail-io0-x241.google.com with SMTP id s26-v6so3559113ioj.4 for ; Sun, 03 Jun 2018 09:06:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=yxCv/BmRwDWoXSXpHgYXw3GfGxz0d3bD/5GYP4bMfmQ=; b=mmXhMJAdsAn2sJO9nmrTvb/6tGShOpLfZfUZcHYushcAOAToFZXdsnzC2zPOuCf86l aZ8mQi+SUpgU31TZc+6JoLrFtwMTveSS7dVt5VWW26t0dEF9GaP2Nj/9hw5h+8OTWRsG 41y/Dh/HR6S7toZXfI4DpbCYK2sGYTFlVzTy7qPAI6F0ggfK7m21HkjDvdn9RqJvBMlI yV7G8hCG4djr7L7QXmcB+9LwgRJLcRO3aj7PgUxkcWKrtyg3P8Sseb4H3Ys5XKJpUM4X XJNz5u/Jg5ztuDYuyvZf6LtpRy01O4PazD5OHfZQNX7nNUn5acK9Ebw+hIN1Govh0UxP 3P/g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=yxCv/BmRwDWoXSXpHgYXw3GfGxz0d3bD/5GYP4bMfmQ=; b=ftLeRpWTSXHpxBW7lLnlsxT20/MtskTU+DOCx1cEbb7bFh8aRjV1zOahdjV8nOyoSI N+1lSQcvWpTLBp4m5gpguW7GhBjw4vlfKA3gAd8kEETBpvK7wNdXf8gyioa2vN8b6ZSs pB4lHuU1byXTevzXEZzF2Qkxirb8R4r+NXGNQKjkLunOsDWvEfoqeyjeNTRnvoNbu47H 7OrRNhEVbXB9dFuZm3YKAFJmMkmWvTVW2o8GVaia0FKG/dVk0Vi84OsP21hJBfqRESX2 RMccKCFD9Isz9hebgV5S1oeTUhM5QH2k7CW2RNl/8Su1pXuT3b9cxvr38CdKspfpy6W5 FuOQ== X-Gm-Message-State: ALKqPweAvtGGfi38WDV7KDsvrQpw+688elfBruA2nIhSbLCGNJtODesn kbEejNrDSm0nMKGI1drh9/K4xwccXW2gstk0UCQ= X-Google-Smtp-Source: ADUXVKJw2vDFMtB1lOM2uRscSUHJwUzrJe+jt/kIRH1Edlit0DKm6+rDo846G5YPzx5+2Xps26qDW3XA9wjmriUFzws= X-Received: by 2002:a6b:214a:: with SMTP id h71-v6mr16989128ioh.229.1528041967194; Sun, 03 Jun 2018 09:06:07 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a02:8d5c:0:0:0:0:0 with HTTP; Sun, 3 Jun 2018 09:06:06 -0700 (PDT) In-Reply-To: <20180603145342.qziiv7awhr4cvs73@kazhap> References: <20180601091031.72u7tqfkatsl3guh@kazhap> <20180601223711.GA93642@elch.exwg.net> <20180603145342.qziiv7awhr4cvs73@kazhap> From: Adam Date: Sun, 3 Jun 2018 11:06:06 -0500 Message-ID: Subject: Re: Can't seem to use 5GHz APs with Intel wireless To: Dhananjay Balan Cc: Christoph Moench-Tegeder , FreeBSD CURRENT Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 16:06:08 -0000 On Sun, Jun 3, 2018 at 9:53 AM, Dhananjay Balan wrote: > On Sat, Jun 02, 2018 at 12:37:12AM +0200, Christoph Moench-Tegeder wrote: > > Did you try adding "mode 11a" to select 5GHz band? (This might be > > out-of-date, as my WiFi stuff is all on 11) (currently I'm also > > using 2.4GHz only, for compatibility with some devices and the fact > > that I have quite some trouble running 2.4GHz and 5GHz from the same > > interface at the same time). > > I did a bit more testing, I have to admit that I am not well versed in > wifi internals. > > 1. ifconfig wlan0 list aps shows my aps having rate 54M (Im not entirely > sure what this means). > But however when I connect to it, it shows up as 11g > > wlan0: flags=8843 metric 0 mtu > 1500 > ether a4:4e:31:02:70:3c > inet 192.168.23.111 netmask 0xffffff00 broadcast 192.168.23.255 > nd6 options=29 > media: IEEE 802.11 Wireless Ethernet MCS mode 11ng > status: associated > ssid LA03 channel 6 (2437 MHz 11g ht/20) bssid 52:d9:e7:47:c0:c2 > regdomain FCC4 country DE authmode WPA2/802.11i privacy ON > deftxkey UNDEF AES-CCM 2:128-bit txpower 30 bmiss 10 scanvalid 60 > protmode CTS ampdulimit 64k ampdudensity 8 -amsdutx amsdurx shortgi > -stbc -ldpc wme roaming MANUAL > groups: wlan > I do not believe the response you are replying to actually addressed 5gz which is different than mode. You may be able to achieve better speeds using channel parameters. man ifconfig. A simple test is to have your AP present SSID of 2.4 and 5 as different names. If the 5 doesn't show in the above command, 5 isn't working. > 2. Adding mode 11a to rc.conf didn't change anything. Still connects to > 2.4Ghz band. > Yup > 3. ifconfing wlan0 scan still doesn't show my 5Ghz only APs (at least some > I tested) > I don't believe the iwn driver is capable of 5gz. At least mine doesn't work on CURRENT. > Also, what does 11a mean? shouldn't it be 11n? > - > dbalan > _______________________________________________ > 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" > -- Adam From owner-freebsd-current@freebsd.org Sun Jun 3 17:33:45 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F0505FE379A for ; Sun, 3 Jun 2018 17:33:44 +0000 (UTC) (envelope-from cmt@burggraben.net) Received: from smtp.burggraben.net (smtp.burggraben.net [IPv6:2a01:4f8:140:50a2::3:1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "ns.exwg.net", Issuer "Christoph Moench-Tegeder" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8BE1670DFE for ; Sun, 3 Jun 2018 17:33:44 +0000 (UTC) (envelope-from cmt@burggraben.net) Received: from localhost (localhost [127.0.0.1]) by smtp.burggraben.net (Postfix) with ESMTP id 482DA6002F3 for ; Sun, 3 Jun 2018 19:33:42 +0200 (CEST) X-Spam-Scanned: by amavisd-new at exwg.net Received: from smtp.burggraben.net ([127.0.0.1]) by localhost (ns.burggraben.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aX7IQe-k1tZT for ; Sun, 3 Jun 2018 19:33:31 +0200 (CEST) Received: from squirrel.exwg.net (unknown [145.253.109.162]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "squirrel.exwg.net", Issuer "Christoph Moench-Tegeder" (verified OK)) by smtp.burggraben.net (Postfix) with ESMTPS for ; Sun, 3 Jun 2018 19:33:31 +0200 (CEST) Received: by squirrel.exwg.net (Postfix, from userid 1000) id AE4F92C29EA; Sun, 3 Jun 2018 19:33:30 +0200 (CEST) Date: Sun, 3 Jun 2018 19:33:30 +0200 From: Christoph Moench-Tegeder To: freebsd-current@freebsd.org Subject: Re: Can't seem to use 5GHz APs with Intel wireless Message-ID: <20180603173330.p6h7x6vznzxwbqmp@squirrel.exwg.net> References: <20180601091031.72u7tqfkatsl3guh@kazhap> <20180601223711.GA93642@elch.exwg.net> <20180603145342.qziiv7awhr4cvs73@kazhap> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20180603145342.qziiv7awhr4cvs73@kazhap> User-Agent: NeoMutt/20170113 (1.7.2) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 17:33:45 -0000 ## Dhananjay Balan (mail@dbalan.in): > On Sat, Jun 02, 2018 at 12:37:12AM +0200, Christoph Moench-Tegeder wrote: > > Did you try adding "mode 11a" to select 5GHz band? (This might be > > out-of-date, as my WiFi stuff is all on 11) (currently I'm also > > using 2.4GHz only, for compatibility with some devices and the fact > > that I have quite some trouble running 2.4GHz and 5GHz from the same > > interface at the same time). > > I did a bit more testing, I have to admit that I am not well versed in > wifi internals. Here's the non-technical overview: https://en.wikipedia.org/wiki/IEEE_802.11 (The real details can be really gory, but this should be good enough). > 1. ifconfig wlan0 list aps shows my aps having rate 54M (Im not entirely > sure what this means). > But however when I connect to it, it shows up as 11g A data rate of 54 MBit/s would be perfectly in sync with 11g - 20MHz channel width, OFDM modulation, 2.4 GHz. And we see that in this line: > ssid LA03 channel 6 (2437 MHz 11g ht/20) bssid 52:d9:e7:47:c0:c2 And this shows that even MIMO ("Multiple Input, Multiple Output" has been activated (that's the "n" in "11ng"): > media: IEEE 802.11 Wireless Ethernet MCS mode 11ng The 5GHz part of 802.11 is 802.11a (and related, like ac), there's no 5GHz band in 11g. I'm a little puzzled about this: > regdomain FCC4 country DE authmode WPA2/802.11i privacy ON Is the regdomain/country setting correct for your area and matches your AP? Especially in the 5GHz band there are some "gaps" - not all channels may be used in all countries (because of possible interference with radar equipment and other stuff). See: https://en.wikipedia.org/wiki/List_of_WLAN_channels#5_GHz_(802.11a/h/j/n/ac/ax) Regards, Christoph -- Spare Space. From owner-freebsd-current@freebsd.org Sun Jun 3 17:44:08 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 419C3FE4B00 for ; Sun, 3 Jun 2018 17:44:08 +0000 (UTC) (envelope-from cmt@burggraben.net) Received: from smtp.burggraben.net (smtp.burggraben.net [IPv6:2a01:4f8:140:50a2::3:1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "ns.exwg.net", Issuer "Christoph Moench-Tegeder" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D0C937149B for ; Sun, 3 Jun 2018 17:44:07 +0000 (UTC) (envelope-from cmt@burggraben.net) Received: from localhost (localhost [127.0.0.1]) by smtp.burggraben.net (Postfix) with ESMTP id C85376002F3 for ; Sun, 3 Jun 2018 19:44:06 +0200 (CEST) X-Spam-Scanned: by amavisd-new at exwg.net Received: from smtp.burggraben.net ([127.0.0.1]) by localhost (ns.burggraben.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9V5vN9Eyjitm for ; Sun, 3 Jun 2018 19:44:01 +0200 (CEST) Received: from squirrel.exwg.net (unknown [145.253.109.162]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "squirrel.exwg.net", Issuer "Christoph Moench-Tegeder" (verified OK)) by smtp.burggraben.net (Postfix) with ESMTPS for ; Sun, 3 Jun 2018 19:44:01 +0200 (CEST) Received: by squirrel.exwg.net (Postfix, from userid 1000) id 6D3D12C29E3; Sun, 3 Jun 2018 19:44:01 +0200 (CEST) Date: Sun, 3 Jun 2018 19:44:01 +0200 From: Christoph Moench-Tegeder To: freebsd-current@freebsd.org Subject: Re: Can't seem to use 5GHz APs with Intel wireless Message-ID: <20180603174401.rbxa3fcnuoprogow@squirrel.exwg.net> References: <20180601091031.72u7tqfkatsl3guh@kazhap> <20180601223711.GA93642@elch.exwg.net> <20180603145342.qziiv7awhr4cvs73@kazhap> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170113 (1.7.2) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 17:44:08 -0000 ## Adam (amvandemore@gmail.com): > > 3. ifconfing wlan0 scan still doesn't show my 5Ghz only APs (at least some > > I tested) > > I don't believe the iwn driver is capable of 5gz. At least mine doesn't > work on CURRENT. The iwn driver has code for 5GHz (I've no idea if that's complete). But looking at that reminded me: there are many "iwn" devices, including some having "BGN" appended to their names - I'd guess those devices don't support 5GHz aka 11a mode. Regards, Christoph -- From owner-freebsd-current@freebsd.org Sun Jun 3 18:13:46 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CD9AAFE814A for ; Sun, 3 Jun 2018 18:13:46 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5C33672C08 for ; Sun, 3 Jun 2018 18:13:46 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id PXQwfMqY6SzNNPXQyfWUL5; Sun, 03 Jun 2018 12:08:53 -0600 X-Authority-Analysis: v=2.3 cv=KuxjJ1eN c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=kj9zAlcOel0A:10 a=7mUfYlMuFuIA:10 a=kgfhYre9AAAA:8 a=pGLkceISAAAA:8 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=hqx1a1BDsZXljwEO1yYA:9 a=CjuIK1q_8ugA:10 a=o4YRySerR8EA:10 a=FOgIJflhCR-CFpFWLMjf:22 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 a=cEB5NwCL2tbdTkCdtNfK:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id A3DB7270A; Sun, 3 Jun 2018 11:08:50 -0700 (PDT) Received: from slippy.cwsent.com (localhost [127.0.0.1]) by slippy.cwsent.com (8.15.2/8.15.2) with ESMTP id w53I8oEc074731; Sun, 3 Jun 2018 11:08:50 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Received: from slippy (cy@localhost) by slippy.cwsent.com (8.15.2/8.15.2/Submit) with ESMTP id w53I8okL074728; Sun, 3 Jun 2018 11:08:50 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <201806031808.w53I8okL074728@slippy.cwsent.com> X-Authentication-Warning: slippy.cwsent.com: cy owned process doing -bs X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Christoph Moench-Tegeder cc: freebsd-current@freebsd.org Subject: Re: Can't seem to use 5GHz APs with Intel wireless In-Reply-To: Message from Christoph Moench-Tegeder of "Sun, 03 Jun 2018 19:44:01 +0200." <20180603174401.rbxa3fcnuoprogow@squirrel.exwg.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 03 Jun 2018 11:08:50 -0700 X-CMAE-Envelope: MS4wfI8ALj1VwtofzY/h0Yj70DJZI2RRUxKKDwkd8hjh+0w+TwdqJYag8ZN5NaNBiG8pdCWk+0JpMrelo6Mg86WHy2a61KO9PDjcb7Gub4+7mBHea7t5hikz Nj04BF7QK+rGRLdqQ/OJBSveTpGZkX6j0EVxUsCeZ8ZzORVP8LVWzVJ65ivLDhtZDoB30nGW9YCEY06CrA9WOXF80wpl4qFw9hWWFNI5nyGqQAkOrP8TqPe0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 18:13:47 -0000 In message <20180603174401.rbxa3fcnuoprogow@squirrel.exwg.net>, Christoph Moenc h-Tegeder writes: > ## Adam (amvandemore@gmail.com): > > > > 3. ifconfing wlan0 scan still doesn't show my 5Ghz only APs (at least som > e > > > I tested) > > > > I don't believe the iwn driver is capable of 5gz. At least mine doesn't > > work on CURRENT. > > The iwn driver has code for 5GHz (I've no idea if that's complete). > But looking at that reminded me: there are many "iwn" devices, including > some having "BGN" appended to their names - I'd guess those devices > don't support 5GHz aka 11a mode. My iwn device (iwn0: ) supports 5 GHz. I just disabled my 2.4 GHz APs and reassociated: wlan0: flags=8843 metric 0 mtu 1500 ether nd6 options=29 media: IEEE 802.11 Wireless Ethernet MCS mode 11na status: associated ssid XXXXXXXX-5G channel 153 (5765 MHz 11a ht/40-) bssid regdomain FCC country US authmode WPA2/802.11i privacy ON deftxkey UNDEF AES-CCM 2:128-bit txpower 23 bmiss 120 mcastrate 6 mgmtrate 6 scanvalid 16959 ampdulimit 64k ampdudensity 8 -amsdutx amsdurx shortgi -stbc -ldpc wme roaming MANUAL groups: wlan Some devices do and others don't. For example, I have an ath card for this same laptop (I swapped out my iwn card for an ath card for a short while) that supports station mode (BTW iwn firmware doesn't), discovering my ath device firmware does not support 5 GHz. I suspect that some iwn devices may be similarly "crippled", though the driver supports 5 GHz the firmware does not. My point is it's not a binary issue. You may need to Google your particular card to determine if the manufacturer has implemented the feature or not. I did for my ath card discovering not all implementations are equal. I wouldn't be surprised this might be true of iwn as well. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. From owner-freebsd-current@freebsd.org Sun Jun 3 18:33:24 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2BCD4FEA84A for ; Sun, 3 Jun 2018 18:33:24 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from CAN01-QB1-obe.outbound.protection.outlook.com (mail-eopbgr660085.outbound.protection.outlook.com [40.107.66.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT TLS CA 4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AF5507470C for ; Sun, 3 Jun 2018 18:33:23 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from YTOPR0101MB0953.CANPRD01.PROD.OUTLOOK.COM (52.132.44.24) by YTOPR0101MB1418.CANPRD01.PROD.OUTLOOK.COM (52.132.47.22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.797.11; Sun, 3 Jun 2018 18:33:21 +0000 Received: from YTOPR0101MB0953.CANPRD01.PROD.OUTLOOK.COM ([fe80::a860:9237:2e9f:f87f]) by YTOPR0101MB0953.CANPRD01.PROD.OUTLOOK.COM ([fe80::a860:9237:2e9f:f87f%3]) with mapi id 15.20.0820.012; Sun, 3 Jun 2018 18:33:21 +0000 From: Rick Macklem To: "freebsd-current@freebsd.org" Subject: SPDX-License-Id for new files Thread-Topic: SPDX-License-Id for new files Thread-Index: AQHT+2jjxDsSwgMGw0G2a7l3Q+rckA== Date: Sun, 3 Jun 2018 18:33:21 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=rmacklem@uoguelph.ca; x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; YTOPR0101MB1418; 7:mc6WhyBe8brh2MukOD8xUazPN4xycjswPL3bSPlGeuoR98MMWyq2htshwEPgS8jgwfBsRBLfnulUsdt1UguihTejUs9gFkE9AcROPrazAiNhT55rpWzrtFn6F8GRE1Bt9kaGezbQbbbxRqR1ZIqLhetqrShr44vjVM59jdzlUaRV9FPPtpcACklyyVSz6ccGv2gjpbH1YvSc6N4mljb4JEdwhYL1jmslcLhEH/O2jEIl5tPd0CAeqMji2/hmsxN6 x-ms-exchange-antispam-srfa-diagnostics: SOS; x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(8989080)(5600026)(4534165)(4627221)(201703031133081)(201702281549075)(8990040)(2017052603328)(7153060)(7193020); SRVR:YTOPR0101MB1418; x-ms-traffictypediagnostic: YTOPR0101MB1418: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(5213294742642); x-ms-exchange-senderadcheck: 1 x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(3231254)(944501410)(52105095)(10201501046)(3002001)(93006095)(93001095)(149027)(150027)(6041310)(20161123564045)(20161123560045)(20161123562045)(201703131423095)(201702281529075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(6072148)(201708071742011)(7699016); SRVR:YTOPR0101MB1418; BCL:0; PCL:0; RULEID:; SRVR:YTOPR0101MB1418; x-forefront-prvs: 069255B8B8 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(376002)(39380400002)(396003)(346002)(366004)(199004)(189003)(5250100002)(2906002)(102836004)(68736007)(6506007)(305945005)(99286004)(186003)(8676002)(74316002)(6916009)(2351001)(86362001)(8936002)(558084003)(26005)(97736004)(74482002)(7696005)(106356001)(81166006)(55016002)(478600001)(2501003)(5640700003)(3280700002)(105586002)(9686003)(2900100001)(81156014)(25786009)(6436002)(486006)(14454004)(786003)(33656002)(316002)(3660700001)(476003)(53936002)(5660300001); DIR:OUT; SFP:1101; SCL:1; SRVR:YTOPR0101MB1418; H:YTOPR0101MB0953.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: uoguelph.ca does not designate permitted sender hosts) x-microsoft-antispam-message-info: j0JwnKU0IqESBWwjPs1Kgv/H5OjgFAjE89GA2nrbBj8CgB5IXE2IOydS/h4qkv5kN3oG/FRyxXzlTUbp6S3DwBL39jJZI5VBMEs3eecAQ43Fzj1G2xFgfEdvoO24aEoekmTyi9b2r1mHTugGqiCQz8lHNMMczf4KuYGBopMXK8JbbyjkLaFqYsEyNrFE4ThH spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-MS-Office365-Filtering-Correlation-Id: ee0f6296-67c0-4b57-af34-08d5c9807c26 X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-Network-Message-Id: ee0f6296-67c0-4b57-af34-08d5c9807c26 X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Jun 2018 18:33:21.7762 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTOPR0101MB1418 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 18:33:24 -0000 I have a few (3) new files in the projects/pnfs-planb-server subversion tre= e that all have the 2 clause FreeBSD copyright. Do I just add the "SPDX..." line for this license at the top of the copyrig= ht comment or is there some other exercise needed to be done for this? Thanks, rick From owner-freebsd-current@freebsd.org Sun Jun 3 19:15:17 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 036FAFEF2C4 for ; Sun, 3 Jun 2018 19:15:17 +0000 (UTC) (envelope-from Alexander@leidinger.net) Received: from mailgate.Leidinger.net (mailgate.leidinger.net [IPv6:2a00:1828:2000:375::1:5]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 85C4B76737 for ; Sun, 3 Jun 2018 19:15:16 +0000 (UTC) (envelope-from Alexander@leidinger.net) Date: Sun, 03 Jun 2018 21:14:50 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=leidinger.net; s=outgoing-alex; t=1528053313; bh=8vg9Y9S+t3e4OMh3vowB2NdF8Ik/9UmswU6z6gVWmSA=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=OQoYiWoKYst3hOZ1KtaNHg8uktm3/kLxMqzkQ1+FQMgGO7SYKb1ozJtuDUGWDdYGR R8QVtdooOiI71fG/MZ066NTfsdxxFDiD7aI/QklX5hKbahVNMRKXDTYNAJrPCl/w7E yhcKRMmJDqm8Bc11eqXrbcAQ67VymdJ5ywSHtj8HiAMUN+QMOV4Ycr+VvToYOIsC9c USLGbgJ0E0eVrJZiBVyPUIU52EFCF8uSHGPMp64up6r5tTBG9PRF0tFHofouGrXc+C KUE8PaRJYAIpco80HN9Kbk1vlgfZKOJrHjS75F1bHh7cO4Kv45IyMqMUCNU1ScASfY pIzmE4eXsWUrQ== Message-ID: <20180603211450.Horde.pI-Fom6S1tUcaHvTF4MUjin@webmail.leidinger.net> From: Alexander Leidinger To: Slawa Olhovchenkov Cc: Kirill Ponomarev , freebsd-current@freebsd.org Subject: Re: Deadlocks / hangs in ZFS References: <20180522101749.Horde.Wxz9gSxx1xArxkYMQqTL0iZ@webmail.leidinger.net> <20180522122924.GC1954@zxy.spb.ru> <20180522161632.Horde.ROSnBoZixBoE9ZBGp5VBQgZ@webmail.leidinger.net> <20180522144055.GD1954@zxy.spb.ru> <20180527194159.v54ox3vlthpuvx4q@jo> <20180527220612.GK1926@zxy.spb.ru> <20180528090201.Horde._E4JZcuEaZHfj_BNzWjci2O@webmail.leidinger.net> In-Reply-To: <20180528090201.Horde._E4JZcuEaZHfj_BNzWjci2O@webmail.leidinger.net> User-Agent: Horde Application Framework 5 Content-Type: multipart/signed; boundary="=_Cx5T3iuW7Dhz7q26lZ8LyU1"; protocol="application/pgp-signature"; micalg=pgp-sha1 MIME-Version: 1.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 19:15:17 -0000 This message is in MIME format and has been PGP signed. --=_Cx5T3iuW7Dhz7q26lZ8LyU1 Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Quoting Alexander Leidinger (from Mon, 28=20=20 May=202018 09:02:01 +0200): > Quoting Slawa Olhovchenkov (from Mon, 28 May 2018=20=20 >=2001:06:12 +0300): > >> On Sun, May 27, 2018 at 09:41:59PM +0200, Kirill Ponomarev wrote: >> >>> On 05/22, Slawa Olhovchenkov wrote: >>>> > It has been a while since I tried Karl's patch the last time, and I >>>> > stopped because it didn't apply to -current anymore at some point. >>>> > Will what is provided right now in the patch work on -current? >>>> >>>> I am mean yes, after s/vm_cnt.v_free_count/vm_free_count()/g >>>> I am don't know how to have two distinct patch (for stable and=20=20 >>>>=20current) in one review. >>> >>> I'm experiencing these issues sporadically as well, would you mind >>> to publish this patch for fresh current? >> >> Week ago I am adopt and publish patch to fresh current and stable, is >> adopt need again? > > I applied the patch in the review yesterday to rev 333966, it=20=20 >=20applied OK (with some fuzz). I will try to reproduce my issue with=20= =20 >=20the patch. The behavior changed (or the system was long enough in this state=20=20 without=20me noticing it). I have a panic now: panic: deadlkres: possible deadlock detected for 0xfffff803766db580,=20=20 blocked=20for 1803003 ticks I only have the textdump. Is nayone up to debug this? If yes, I switch=20= =20 to=20normal dumps, just tell me what I shall check for. db:0:kdb.enter.panic> run lockinfo db:1:lockinfo> show locks No such command; use "help" to list available commands db:1:lockinfo> show alllocks No such command; use "help" to list available commands db:1:lockinfo> show lockedvnods Locked vnodes db:0:kdb.enter.panic> show pcpu cpuid =3D 6 dynamic pcpu =3D 0xfffffe008f03e840 curthread =3D 0xfffff80370c82000: pid 0 tid 100218 "deadlkres" curpcb =3D 0xfffffe0116472cc0 fpcurthread =3D none idlethread =3D 0xfffff803700b9580: tid 100008 "idle: cpu6" curpmap =3D 0xffffffff80d28448 tssp =3D 0xffffffff80d96d90 commontssp =3D 0xffffffff80d96d90 rsp0 =3D 0xfffffe0116472cc0 gs32p =3D 0xffffffff80d9d9c8 ldt =3D 0xffffffff80d9da08 tss =3D 0xffffffff80d9d9f8 db:0:kdb.enter.panic> bt Tracing pid 0 tid 100218 td 0xfffff80370c82000 kdb_enter() at kdb_enter+0x3b/frame 0xfffffe0116472aa0 vpanic() at vpanic+0x1c0/frame 0xfffffe0116472b00 panic() at panic+0x43/frame 0xfffffe0116472b60 deadlkres() at deadlkres+0x3a6/frame 0xfffffe0116472bb0 fork_exit() at fork_exit+0x84/frame 0xfffffe0116472bf0 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0116472bf0 --- trap 0, rip =3D 0, rsp =3D 0, rbp =3D 0 --- Bye, Alexander. --=20 http://www.Leidinger.net=20Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_Cx5T3iuW7Dhz7q26lZ8LyU1 Content-Type: application/pgp-signature Content-Description: Digitale PGP-Signatur Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJbFD4qAAoJEKrxQhqFIICE8BEP/AnXcLRV4mup++4RTI/jk41O qDwZkqI/VwD/Pa0I25nfpzW93tuBOHbhFxqILfrwMhx5dKCCu6hoM3BzDZ9kxoVS KxKXFuQFM96M46aKoUeVi1hwSEZqTiI3z9mlWpAlqOvwFKYDARj7A5mOY7I2KFyN kokrTJ6NpY5sW4NtlegODEkVkoERn3VGY42vqS9BMvPpbW09dIQtiChxE6hUUMXG YlJMuw/M/m1q0b2wuQ+RQuMUvyQYgpwP9qrls33/BHd9T8quaO2vvWO5U3iNSPIg PnO0wvrSiVhhWNyKuuxQfqyQZD908p1er3q65VXZYhnar6KEL87hDy2kbG9CPFkd oXCRG60NyG7WLEuVLH4BuZHLcU3i2cE1fHIyx5FCxQzxfkdA59j61tJk2iyNV7vL WJ3fcAAxSXTeLclpttnTw6yMCL09C3WqKCbWxmoyyQg3w5ZyVVlkDKHf2BVy8Zeq 3YE17snuZHrrUMRLW6ubnLiCfiXDQtX2DW4Jg5CwTSFvOPjhxEYpgXU1hlnaIGFd xN0kkNlMN9p9CdktslUDZZHD/Nh9OnvXW0BCln7y6DUYbWSb+j7rRkCblYtIP1Br wwYGXl/vaRuVjMHqcv+bR39ga+8b+QPm6E87aC959aqxL97HlyqukCLSbCKmJ7+D MdZd1HObFJK2ltl5JKVF =d67T -----END PGP SIGNATURE----- --=_Cx5T3iuW7Dhz7q26lZ8LyU1-- From owner-freebsd-current@freebsd.org Sun Jun 3 19:28:29 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 14384FF0A20 for ; Sun, 3 Jun 2018 19:28:29 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 96513773AF for ; Sun, 3 Jun 2018 19:28:28 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1fPYfm-0009Al-52; Sun, 03 Jun 2018 22:28:14 +0300 Date: Sun, 3 Jun 2018 22:28:14 +0300 From: Slawa Olhovchenkov To: Alexander Leidinger Cc: Kirill Ponomarev , freebsd-current@freebsd.org Subject: Re: Deadlocks / hangs in ZFS Message-ID: <20180603192814.GP1926@zxy.spb.ru> References: <20180522101749.Horde.Wxz9gSxx1xArxkYMQqTL0iZ@webmail.leidinger.net> <20180522122924.GC1954@zxy.spb.ru> <20180522161632.Horde.ROSnBoZixBoE9ZBGp5VBQgZ@webmail.leidinger.net> <20180522144055.GD1954@zxy.spb.ru> <20180527194159.v54ox3vlthpuvx4q@jo> <20180527220612.GK1926@zxy.spb.ru> <20180528090201.Horde._E4JZcuEaZHfj_BNzWjci2O@webmail.leidinger.net> <20180603211450.Horde.pI-Fom6S1tUcaHvTF4MUjin@webmail.leidinger.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180603211450.Horde.pI-Fom6S1tUcaHvTF4MUjin@webmail.leidinger.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 19:28:29 -0000 On Sun, Jun 03, 2018 at 09:14:50PM +0200, Alexander Leidinger wrote: > Quoting Alexander Leidinger (from Mon, 28 > May 2018 09:02:01 +0200): > > > Quoting Slawa Olhovchenkov (from Mon, 28 May 2018 > > 01:06:12 +0300): > > > >> On Sun, May 27, 2018 at 09:41:59PM +0200, Kirill Ponomarev wrote: > >> > >>> On 05/22, Slawa Olhovchenkov wrote: > >>>> > It has been a while since I tried Karl's patch the last time, and I > >>>> > stopped because it didn't apply to -current anymore at some point. > >>>> > Will what is provided right now in the patch work on -current? > >>>> > >>>> I am mean yes, after s/vm_cnt.v_free_count/vm_free_count()/g > >>>> I am don't know how to have two distinct patch (for stable and > >>>> current) in one review. > >>> > >>> I'm experiencing these issues sporadically as well, would you mind > >>> to publish this patch for fresh current? > >> > >> Week ago I am adopt and publish patch to fresh current and stable, is > >> adopt need again? > > > > I applied the patch in the review yesterday to rev 333966, it > > applied OK (with some fuzz). I will try to reproduce my issue with > > the patch. > > The behavior changed (or the system was long enough in this state > without me noticing it). I have a panic now: > panic: deadlkres: possible deadlock detected for 0xfffff803766db580, > blocked for 1803003 ticks Hmm, may be first determinate locked function addr2line -ie /boot/kernel/kernel 0xfffff803766db580 or kgdb x/10i 0xfffff803766db580 > I only have the textdump. Is nayone up to debug this? If yes, I switch > to normal dumps, just tell me what I shall check for. > > db:0:kdb.enter.panic> run lockinfo > db:1:lockinfo> show locks > No such command; use "help" to list available commands > db:1:lockinfo> show alllocks > No such command; use "help" to list available commands > db:1:lockinfo> show lockedvnods > Locked vnodes > db:0:kdb.enter.panic> show pcpu > cpuid = 6 > dynamic pcpu = 0xfffffe008f03e840 > curthread = 0xfffff80370c82000: pid 0 tid 100218 "deadlkres" > curpcb = 0xfffffe0116472cc0 > fpcurthread = none > idlethread = 0xfffff803700b9580: tid 100008 "idle: cpu6" > curpmap = 0xffffffff80d28448 > tssp = 0xffffffff80d96d90 > commontssp = 0xffffffff80d96d90 > rsp0 = 0xfffffe0116472cc0 > gs32p = 0xffffffff80d9d9c8 > ldt = 0xffffffff80d9da08 > tss = 0xffffffff80d9d9f8 > db:0:kdb.enter.panic> bt > Tracing pid 0 tid 100218 td 0xfffff80370c82000 > kdb_enter() at kdb_enter+0x3b/frame 0xfffffe0116472aa0 > vpanic() at vpanic+0x1c0/frame 0xfffffe0116472b00 > panic() at panic+0x43/frame 0xfffffe0116472b60 > deadlkres() at deadlkres+0x3a6/frame 0xfffffe0116472bb0 > fork_exit() at fork_exit+0x84/frame 0xfffffe0116472bf0 > fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0116472bf0 > --- trap 0, rip = 0, rsp = 0, rbp = 0 --- > > > Bye, > Alexander. > > -- > http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF > http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF From owner-freebsd-current@freebsd.org Sun Jun 3 19:34:24 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CAEEBFF157D for ; Sun, 3 Jun 2018 19:34:24 +0000 (UTC) (envelope-from Alexander@leidinger.net) Received: from mailgate.Leidinger.net (mailgate.leidinger.net [IPv6:2a00:1828:2000:375::1:5]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 645017793A for ; Sun, 3 Jun 2018 19:34:24 +0000 (UTC) (envelope-from Alexander@leidinger.net) Date: Sun, 03 Jun 2018 21:34:03 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=leidinger.net; s=outgoing-alex; t=1528054463; bh=CEnC5k/umCVGIdIFIpWIAq7gBfoK1X2Feth0swY3Ptg=; h=Date:From:To:Subject:References:In-Reply-To; b=hMEheSALBtA/Xfw0jh7VLC0vercFQ2Xc+/g4owFgSH3RmIkFiWMzEABHWp8ptwNZY QOZ6AaPLyHo1GbeyIkcbahcnves+3PlzUnLd1D4KcgWIYMJWclnk+HVmc/sNhwW94i W4oPw7BM4FCJzNaEoCxhW6ygZvQFxZFk7wJzdjgB7dZhTqbcuYnpllGTZkjW/9Oab4 /wd+aijzEWf64iGa9dxSalA/b9G6k0iYtGxMWi6OSQewecAlGzMEoWzz7EjgznoF8Z DbEAXjDIU72Go+9iSTyVVf9Dg4XtuoowqDpaUuP6u/lsJfWApgTKmzym5eBYtmj0ef drPAISpHu+gOw== Message-ID: <20180603213403.Horde.xck3Nm8f0hyYVjQV0ZOBjBC@webmail.leidinger.net> From: Alexander Leidinger To: freebsd-current@freebsd.org Subject: Re: Recent changes in routing or IPv6 related parts? References: <20180522101222.Horde.qCL_Frz6tcSPJrYy4UFWDEH@webmail.leidinger.net> <34db4188119c29a5e38c9216b15f3411@udns.ultimatedns.net> <20180527211217.Horde.opQzHI4VOIxPiirx10J9wTe@webmail.leidinger.net> In-Reply-To: <20180527211217.Horde.opQzHI4VOIxPiirx10J9wTe@webmail.leidinger.net> User-Agent: Horde Application Framework 5 Content-Type: multipart/signed; boundary="=_KjeBhcgzIWME3TIofBZSKL3"; protocol="application/pgp-signature"; micalg=pgp-sha1 MIME-Version: 1.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 19:34:25 -0000 This message is in MIME format and has been PGP signed. --=_KjeBhcgzIWME3TIofBZSKL3 Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Quoting Alexander Leidinger (from Sun, 27=20=20 May=202018 21:12:17 +0200): > Quoting Chris H (from Tue, 22 May 2018=20=20 >=2009:59:04 -0700): >> Hello, Alexander. >> I'm not sure if this landed in -CURRENT. I only know it landed in 11. >> But your trouble might be related to pr #224247 : >> >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224247 >> >> Hope this helps. > > Thanks, I've compiled a kernel which will print a message with the=20=20 >=20interface name when a packet will be dropped because of this. If I=20= =20 >=20see something which makes it look like it could be related, I will=20= =20 >=20disable it and try again. It doesn't look like this is causing the issues I see. I have added=20=20 some=20printfs in the silent-discard parts and nothing in printed when=20= =20 the=20workaround-script detects the issue. Bye, Alexander. --=20 http://www.Leidinger.net=20Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_KjeBhcgzIWME3TIofBZSKL3 Content-Type: application/pgp-signature Content-Description: Digitale PGP-Signatur Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJbFEKrAAoJEKrxQhqFIICEXRcP/27CPDABybcEx7iCTUT0MVZV rDERONvgJBbiEhjXignOVHhKvkSP0i8bd9URs+V36FAe7QvGif7MKLCX1CWHP5un ZOZUIpeVfOkFj/XUEjaxERUhkD+VOYp6tMLXM9yOr5w0xWqzTgSTneTaPR0sIjQL BEx5PsURc77ffzwd08sfvmqzBIrCmWMF9AKtdq1ykVU/p/iqWF5gkbc+ndd+afgv liRsJsu6iaZzEAhXsZoj1SGpd++NEVvDFuIeYc5z25ALH0PDNX//hY9j3qL25U2N 9H6iDXnDA4nOdlWMrywn42fCgFttWh2prT2kh/rISntRlh0H6ncc33dkJedc7n41 PO7vNLDefUdzxLpmM4m9Wekg9dt0bztQUbjyyE7/5rX8lR8ZO/dYXycSbrd2RUNK 9ZI95XymwUceWXK6iR4qe87swJFQcQEltRnSuQVDqLaNEkLno6W5//FpJPZKqhTv 6B9dYKVxqi2F6t//BCO6LCY9B5dMBXiuaOeEy3c9GdZcau/7rbQMOmrIEuZDzhN3 rB9VQnTk30YYQl6Pcayfb+mjiuInvRrjqu9Tri4YgVzNUomcUuyuQoKZmva+eoPw rSLinW2fc6zmfRAGNUr3XLNxFrZruOjXiDBaJzZL2cMBVELjEEA0sMYPL9+ecpow 70nNtmudVjW9qhx7MIKt =QTsr -----END PGP SIGNATURE----- --=_KjeBhcgzIWME3TIofBZSKL3-- From owner-freebsd-current@freebsd.org Sun Jun 3 19:46:09 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 077FDFF2C92 for ; Sun, 3 Jun 2018 19:46:09 +0000 (UTC) (envelope-from yuri@rawbw.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 A05247859A for ; Sun, 3 Jun 2018 19:46:08 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: by mailman.ysv.freebsd.org (Postfix) id 6435BFF2C8F; Sun, 3 Jun 2018 19:46:08 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 52BEEFF2C8E for ; Sun, 3 Jun 2018 19:46:08 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id C067B78599 for ; Sun, 3 Jun 2018 19:46:07 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from yv.noip.me (c-24-4-131-132.hsd1.ca.comcast.net [24.4.131.132]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id w53Jk5G5019855 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Sun, 3 Jun 2018 12:46:06 -0700 (PDT) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-24-4-131-132.hsd1.ca.comcast.net [24.4.131.132] claimed to be yv.noip.me To: current From: Yuri Subject: ACPI is broken on CURRENT Message-ID: <8fcdd0ab-e4f7-8562-cd8e-1689411d45a9@rawbw.com> Date: Sun, 3 Jun 2018 12:46:04 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 19:46:09 -0000 I couldn't make the S3 suspend to work at all. Please see the bug report: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228654 Yuri From owner-freebsd-current@freebsd.org Sun Jun 3 19:50:25 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 64FF6FF35AE for ; Sun, 3 Jun 2018 19:50:25 +0000 (UTC) (envelope-from freebsd@grem.de) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id BF57B78A70 for ; Sun, 3 Jun 2018 19:50:24 +0000 (UTC) (envelope-from freebsd@grem.de) Received: (qmail 86481 invoked by uid 89); 3 Jun 2018 19:50:22 -0000 Received: from unknown (HELO bsd64.grem.de) (mg@grem.de@194.97.158.70) by mail.grem.de with ESMTPA; 3 Jun 2018 19:50:22 -0000 Date: Sun, 3 Jun 2018 21:50:20 +0200 From: Michael Gmelin To: Konstantin Belousov Cc: Michael Gmelin , "freebsd-current@freebsd.org" , Matthias Apitz , jhb@freebsd.org Subject: Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy) Message-ID: <20180603215020.452a81d8@bsd64.grem.de> In-Reply-To: <20180603150423.GQ3789@kib.kiev.ua> References: <20180603144840.44bfea41@bsd64.grem.de> <20180603132110.GP3789@kib.kiev.ua> <20180603165500.361ec894@bsd64.grem.de> <20180603150423.GQ3789@kib.kiev.ua> X-Mailer: Claws Mail 3.15.1 (GTK+ 2.24.31; amd64-portbld-freebsd10.3) X-Face: $wrgCtfdVw_H9WAY?S&9+/F"!41z'L$uo*WzT8miX?kZ~W~Lr5W7v?j0Sde\mwB&/ypo^}> +a'4xMc^^KroE~+v^&^#[B">soBo1y6(TW6#UZiC]o>C6`ej+i Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEWJBwe5BQDl LASZU0/LTEWEfHbyj0Txi32+sKrp1Mv944X8/fm1rS+cAAAACXBIWXMAAAsTAAAL EwEAmpwYAAAAB3RJTUUH3wESCxwC7OBhbgAAACFpVFh0Q29tbWVudAAAAAAAQ3Jl YXRlZCB3aXRoIFRoZSBHSU1QbbCXAAAAAghJREFUOMu11DFvEzEUAGCfEhBVFzuq AKkLd0O6VrIQsLXVSZXoWE5N1K3DobBBA9fQpRWc8OkWouaIjedWKiyREOKs+3PY fvalCNjgLVHeF7/3bMtBzV8C/VsQ8tecEgCcDgrzjekwKZ7TwsJZd/ywEKwwP+ZM 8P3drTsAwWn2mpWuDDuYiK1bFs6De0KUUFw0tWxm+D4AIhuuvZqtyWYeO7jQ4Aea 7jUqI+ixhQoHex4WshEvSXdood7stlv4oSuFOC4tqGcr0NjEqXgV4mMJO38nld4+ xKNxRDon7khyKVqY7YR4d+Cg0OMrkWXZOM7YDkEfKiilCn1qYv4mighZiynuHHOA Wq9QJq+BIES7lMFUtcikMnkDGHUoncA+uHgrP0ctIEqfwLHzeSo+eUA66AqzwN6n 2ZHJhw6Qh/PoyC/QENyEyC/AyNjq74Bs+3UH0xYwzDUC4B97HgLocg1QLYgDDO1v f3UX9Y307Ew4AHh67YAFFsxEpkXwpXY3eIgMhAAE3R19L919nNnuD2wlPcDE3UeT L2ytEICQib9BXgS2fU8PrD82ToYO1OEmMSnYTjSqSv9wdC0tPYC+rQRQD9ESnldF CyqfmiYW+tlALt8gH2xrMdC/youbjzPXEun+/ReXsMCDyve3dZc09fn2Oas8oXGc Jj6/fOeK5UmSMPmf/jL+GD8BEj0k/Fn6IO4AAAAASUVORK5CYII= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 19:50:25 -0000 On Sun, 3 Jun 2018 18:04:23 +0300 Konstantin Belousov wrote: > On Sun, Jun 03, 2018 at 04:55:00PM +0200, Michael Gmelin wrote: > > > > > > On Sun, 3 Jun 2018 16:21:10 +0300 > > Konstantin Belousov wrote: > > > > > On Sun, Jun 03, 2018 at 02:48:40PM +0200, Michael Gmelin wrote: > > > > Hi, > > > > > > > > After upgrading CURRENT to r333992 (from something at least a > > > > year old, quite some changes in mp_machdep.c since), this > > > > machine crashes on boot: > > > > > > > > Copyright (c) 1992-2018 The FreeBSD Project. > > > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, > > > > 1993, 1994 The Regents of the University of California. All > > > > rights reserved. FreeBSD is a registered trademark of The > > > > FreeBSD Foundation. FreeBSD 12.0-CURRENT #1 r333992: Tue May 22 > > > > 00:31:04 CEST 2018 > > > > root@flimsy:/usr/obj/usr/src/amd64.amd64/sys/flimsy amd64 > > > > FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) > > > > (based on LLVM 6.0.0) WARNING: WITNESS option enabled, expect > > > > reduced performance. VT(vga): resolution 640x480 CPU: Intel(R) > > > > Celeron(R) 2955U @ 1.40GHz (1396.80-MHz K8-class CPU) > > > > Origin="GenuineIntel" Id=0x40651 Family=0x6 Model=0x45 > > > > Stepping=1 > > > > Features=0xbfebfbff > > > CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > > > > Features2=0x4ddaebbf > > > xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,TSCDLT,XSAVE,OSXSAVE,RDRAND> > > > > AMD Features=0x2c100800 AMD > > > > Features2=0x21 Structured Extended > > > > Features=0x2603 XSAVE > > > > Features=0x1 VT-x: (disabled in BIOS) > > > > PAT,HLT,MTF,PAUSE,EPT,UG,VPID TSC: P-state invariant, > > > > performance statistics real memory = 4301258752 (4102 MB) > > > > avail memory = 1907572736 (1819 MB) Event timer "LAPIC" quality > > > > 600 ACPI APIC Table: > > > What does this mean ? Did you flashed coreboot ? > > > > This machine comes with it by default (my model was delivered with > > SeaBIOS 20131018_145217-build121-m2). So I didn't flash anything > > (didn't feel like bricking it). > > > > > > > > > kernel trap 12 with interrupts disabled > > > > > > > > Fatal trap 12: page fault while in kernel mode > > > > cpuid = 0; apic id = 00 > > > > fault virtual address = 0xfffff80001000000 > > > > fault code = supervisor write data, protection > > > > violation instruction pointer = 0x20:Oxffffffff8102955f > > > > stack pointer = 0x28:0xffffffff82a79be0 > > > > frame pointer = 0x28:0xffffffff82a79c10 > > > > code segment = base Ox0, limit Oxfffff, type Ox1b > > > > = DPL 0, pres 1, long 1, def32 0, gran > > > > 1 processor eflags = resume, IOPL = 0 > > > > current process = 0 () > > > > [ thread pid 0 tid 0 ] > > > > Stopped at native_start_all_aps+0x08f: movq > > > > %rax,(%rsi) > > > Look up the source line number for this address. > > > > > > > I guess that's sys/amd64/amd64/support.S line 854 (in rdmsr), > > called by native_start_all_aps. Any additional hints how I can > > track it down? > Why did you decided that this is rdmsr_safe() ? First, > native_start_all_aps() does not call rdmsr, second the ddb > report clearly indicates that the fault occured acessing DMAP in > native_start_all_aps(). > > Just look up the source line by the address > native_start_all_aps+0x08f. Okay, according to kgbd this should be here: https://svnweb.freebsd.org/base/head/sys/amd64/amd64/mp_machdep.c?revision=333368&view=markup#l369 364 365 /* Create the initial 1GB replicated page tables */ 366 for (i = 0; i < 512; i++) { 367 /* Each slot of the level 4 pages points to the same level 3 page */ 368 pt4[i] = (u_int64_t)(uintptr_t)(mptramp_pagetables + PAGE_SIZE); 369 pt4[i] |= PG_V | PG_RW | PG_U; 370 371 /* Each slot of the level 3 pages points to the same level 2 page */ 372 pt3[i] = (u_int64_t)(uintptr_t)(mptramp_pagetables + (2 * PAGE_SIZE)); 373 pt3[i] |= PG_V | PG_RW | PG_U; 374 375 /* The level 2 page slots are mapped with 2MB pages for 1GB. */ 376 pt2[i] = i * (2 * 1024 * 1024); 377 pt2[i] |= PG_V | PG_RW | PG_PS | PG_U; 378 } -m p.s. This machine uses quirks in biosmem.c, see Type '?' for a list of command, 'help' for more detailed help. OK biosmem bios_basemem: 0x9e400 bios_extmem: 0x3ff00000 memtop: 0x3c000000 high_heap_base: 0x3c000000 high_heap_size: 0x4000000 bios_quirks: 0x01 BQ_DISTRUST_820_EXTMEM b_bios_probed: 0x0a B_BASEMEM_12 B_EXTMEM_E801 -- Michael Gmelin -- Michael Gmelin From owner-freebsd-current@freebsd.org Sun Jun 3 19:09:59 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 13137FEE904 for ; Sun, 3 Jun 2018 19:09:59 +0000 (UTC) (envelope-from doctorwhoguy@gmail.com) Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 96C54761A2 for ; Sun, 3 Jun 2018 19:09:58 +0000 (UTC) (envelope-from doctorwhoguy@gmail.com) Received: by mail-io0-x229.google.com with SMTP id d22-v6so20942337iof.13 for ; Sun, 03 Jun 2018 12:09:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=EusAH+a4tRaf55EAsK55rd8NnQuv6rnBQ1CftlQzlzk=; b=OzxW9ktSwUwpUupK28D3l/Dbh5fqASqnNu1H6exXx6leEMkdPstVDbALJF4jUa1KtE eGExiCGcn1f1BNQH7XXADYz5t4O4biKxHQiFinzlJ6iQFuJL27C2fYhw7x+BXLBOpqFz 7U5QLkW+5AMe5p9MJ8mScc0KUCAr2v2Z81zYcuIZCMAUo3mZxUYkO6JG7O+z7AIlCJow 6NhqowHvZDrymKA5sngc/5IG8OWclFxnuhMtlFcTpTWv5Yd6qOSix0UjRE5924LO5wkF lOVgrpL7WOCGmJUgisgC7bxX0OiiCh+9tRXMlHWeHgwfgEOhZV+987qb6UTo7hHpcEUm SBcA== 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=EusAH+a4tRaf55EAsK55rd8NnQuv6rnBQ1CftlQzlzk=; b=jp56g/rclv1pjSfZ9kgS9C2qvU/1HXBB4AzuWdpyCS0Xw/8lRyxfga0/7LuGwVsc2J K5rC9zPK/i1lBzNTprRE/pLHNqVAZikfCvSEqrhSZVgAXTeD6rVHGtLwn4URxwfphWr3 QhUobJoWEGgrDS9drES+EFrg9OURg8UintLpEOSSu0G6iGPgnBu8XR8b/WCAT6oupYBB 5b6Bqxd+A0QG3sDqG4XVzP/4UdHKMU4OLRfhTSrFGD5GULqle1Ol6zmMHvc7f3/eYi2U K5l9XaRXPu6pzfEteoeYWX4WTvcKky1BCULCg9x/Wla6O3Cli8kAOiGX3jbGFNxVQRc6 fnoQ== X-Gm-Message-State: APt69E2yeS//SkIwovybZ9tPl6hsNvMJlzksbKoX8XXxAs8q2f5mZReC pStkvCfb3Mh87KjOZdbKgOIQcrFo7bhP6oQ7Z3E= X-Google-Smtp-Source: ADUXVKKH9CMLrJO1qH0yP9AHlACwcEdWRjRBBUl1rmovSDzsLWmQH9oBiZs55XXfZ90pOK2m434NFDtGBM2FBH6IOi4= X-Received: by 2002:a6b:9c95:: with SMTP id f143-v6mr9645841ioe.22.1528052997703; Sun, 03 Jun 2018 12:09:57 -0700 (PDT) MIME-Version: 1.0 From: Patrick McMunn Date: Sun, 3 Jun 2018 14:09:45 -0500 Message-ID: Subject: local_unbound segfaults at boot To: freebsd-current@freebsd.org X-Mailman-Approved-At: Sun, 03 Jun 2018 19:59:07 +0000 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 19:09:59 -0000 I believe the problem of local_unbound segfaulting began after I compiled the source after the large commit to unbound on Saturday, May 12, 2018 (about 3 weeks ago). I assumed the problem was probably common if I was experiencing it, but I've seen no other mentions of it. I'm not sure what info I need to provide, but will do so upon request. From owner-freebsd-current@freebsd.org Sun Jun 3 20:53:52 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D7957FD3FD8 for ; Sun, 3 Jun 2018 20:53:51 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 463B37BC13; Sun, 3 Jun 2018 20:53:51 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTP id w53KreKO024720; Sun, 3 Jun 2018 23:53:43 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w53KreKO024720 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w53KrexX024717; Sun, 3 Jun 2018 23:53:40 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 3 Jun 2018 23:53:40 +0300 From: Konstantin Belousov To: Michael Gmelin Cc: "freebsd-current@freebsd.org" , Matthias Apitz , jhb@freebsd.org Subject: Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy) Message-ID: <20180603205340.GS3789@kib.kiev.ua> References: <20180603144840.44bfea41@bsd64.grem.de> <20180603132110.GP3789@kib.kiev.ua> <20180603165500.361ec894@bsd64.grem.de> <20180603150423.GQ3789@kib.kiev.ua> <20180603215020.452a81d8@bsd64.grem.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180603215020.452a81d8@bsd64.grem.de> User-Agent: Mutt/1.10.0 (2018-05-17) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 20:53:52 -0000 On Sun, Jun 03, 2018 at 09:50:20PM +0200, Michael Gmelin wrote: > > > On Sun, 3 Jun 2018 18:04:23 +0300 > Konstantin Belousov wrote: > > > On Sun, Jun 03, 2018 at 04:55:00PM +0200, Michael Gmelin wrote: > > > > > > > > > On Sun, 3 Jun 2018 16:21:10 +0300 > > > Konstantin Belousov wrote: > > > > > > > On Sun, Jun 03, 2018 at 02:48:40PM +0200, Michael Gmelin wrote: > > > > > Hi, > > > > > > > > > > After upgrading CURRENT to r333992 (from something at least a > > > > > year old, quite some changes in mp_machdep.c since), this > > > > > machine crashes on boot: > > > > > > > > > > Copyright (c) 1992-2018 The FreeBSD Project. > > > > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, > > > > > 1993, 1994 The Regents of the University of California. All > > > > > rights reserved. FreeBSD is a registered trademark of The > > > > > FreeBSD Foundation. FreeBSD 12.0-CURRENT #1 r333992: Tue May 22 > > > > > 00:31:04 CEST 2018 > > > > > root@flimsy:/usr/obj/usr/src/amd64.amd64/sys/flimsy amd64 > > > > > FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) > > > > > (based on LLVM 6.0.0) WARNING: WITNESS option enabled, expect > > > > > reduced performance. VT(vga): resolution 640x480 CPU: Intel(R) > > > > > Celeron(R) 2955U @ 1.40GHz (1396.80-MHz K8-class CPU) > > > > > Origin="GenuineIntel" Id=0x40651 Family=0x6 Model=0x45 > > > > > Stepping=1 > > > > > Features=0xbfebfbff > > > > CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > > > > > Features2=0x4ddaebbf > > > > xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,TSCDLT,XSAVE,OSXSAVE,RDRAND> > > > > > AMD Features=0x2c100800 AMD > > > > > Features2=0x21 Structured Extended > > > > > Features=0x2603 XSAVE > > > > > Features=0x1 VT-x: (disabled in BIOS) > > > > > PAT,HLT,MTF,PAUSE,EPT,UG,VPID TSC: P-state invariant, > > > > > performance statistics real memory = 4301258752 (4102 MB) > > > > > avail memory = 1907572736 (1819 MB) Event timer "LAPIC" quality > > > > > 600 ACPI APIC Table: > > > > What does this mean ? Did you flashed coreboot ? > > > > > > This machine comes with it by default (my model was delivered with > > > SeaBIOS 20131018_145217-build121-m2). So I didn't flash anything > > > (didn't feel like bricking it). > > > > > > > > > > > > kernel trap 12 with interrupts disabled > > > > > > > > > > Fatal trap 12: page fault while in kernel mode > > > > > cpuid = 0; apic id = 00 > > > > > fault virtual address = 0xfffff80001000000 > > > > > fault code = supervisor write data, protection > > > > > violation instruction pointer = 0x20:Oxffffffff8102955f > > > > > stack pointer = 0x28:0xffffffff82a79be0 > > > > > frame pointer = 0x28:0xffffffff82a79c10 > > > > > code segment = base Ox0, limit Oxfffff, type Ox1b > > > > > = DPL 0, pres 1, long 1, def32 0, gran > > > > > 1 processor eflags = resume, IOPL = 0 > > > > > current process = 0 () > > > > > [ thread pid 0 tid 0 ] > > > > > Stopped at native_start_all_aps+0x08f: movq > > > > > %rax,(%rsi) > > > > Look up the source line number for this address. > > > > > > > > > > I guess that's sys/amd64/amd64/support.S line 854 (in rdmsr), > > > called by native_start_all_aps. Any additional hints how I can > > > track it down? > > Why did you decided that this is rdmsr_safe() ? First, > > native_start_all_aps() does not call rdmsr, second the ddb > > report clearly indicates that the fault occured acessing DMAP in > > native_start_all_aps(). > > > > Just look up the source line by the address > > native_start_all_aps+0x08f. > > Okay, according to kgbd this should be here: > > https://svnweb.freebsd.org/base/head/sys/amd64/amd64/mp_machdep.c?revision=333368&view=markup#l369 > > 364 > 365 /* Create the initial 1GB replicated page tables */ > 366 for (i = 0; i < 512; i++) { > 367 /* Each slot of the level 4 pages points to the same > level 3 page */ 368 pt4[i] = > (u_int64_t)(uintptr_t)(mptramp_pagetables + PAGE_SIZE); 369 > pt4[i] |= PG_V | PG_RW | PG_U; 370 > 371 /* Each slot of the level 3 pages points to the same > level 2 page */ 372 pt3[i] = > (u_int64_t)(uintptr_t)(mptramp_pagetables + (2 * PAGE_SIZE)); > 373 pt3[i] |= PG_V | PG_RW | PG_U; 374 > 375 /* The level 2 page slots are mapped with 2MB pages for > 1GB. */ 376 pt2[i] = i * (2 * 1024 * 1024); > 377 pt2[i] |= PG_V | PG_RW | PG_PS | PG_U; > 378 } > > -m You have fault on write due to read-only mapping of the portion of the direct map, which maps the kernel text. It is consistent with the faulting address. It is not clear if it is something new on your machine, or before the kernel text was silently corrupted, since ro protection is somewhat recent. It seems that mp_bootaddress() selected the bad place for the bootstrap page tables. Even more, we do not include the kernel text into the physmem[] array, so it is not clear how did it happen. This code was also changed recently. Can you add the print of the physmap[] array somewhere before the panic, to see what is the kernel idea of the available memory ? It should be already done if you have serial console and set debug.late_console tunable to 0. > > p.s. This machine uses quirks in biosmem.c, see > > Type '?' for a list of command, 'help' for more detailed > help. > OK biosmem > bios_basemem: 0x9e400 > bios_extmem: 0x3ff00000 > memtop: 0x3c000000 > high_heap_base: 0x3c000000 > high_heap_size: 0x4000000 > bios_quirks: 0x01 BQ_DISTRUST_820_EXTMEM > b_bios_probed: 0x0a B_BASEMEM_12 B_EXTMEM_E801 > > -- > Michael Gmelin > > -- > Michael Gmelin From owner-freebsd-current@freebsd.org Sun Jun 3 21:28:49 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 65C4AFDE628 for ; Sun, 3 Jun 2018 21:28:49 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from CAN01-TO1-obe.outbound.protection.outlook.com (mail-eopbgr670084.outbound.protection.outlook.com [40.107.67.84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT TLS CA 4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 006C87DFFB for ; Sun, 3 Jun 2018 21:28:48 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from YTOPR0101MB0953.CANPRD01.PROD.OUTLOOK.COM (52.132.44.24) by YTOPR0101MB1900.CANPRD01.PROD.OUTLOOK.COM (52.132.49.140) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.820.12; Sun, 3 Jun 2018 21:28:47 +0000 Received: from YTOPR0101MB0953.CANPRD01.PROD.OUTLOOK.COM ([fe80::a860:9237:2e9f:f87f]) by YTOPR0101MB0953.CANPRD01.PROD.OUTLOOK.COM ([fe80::a860:9237:2e9f:f87f%3]) with mapi id 15.20.0820.015; Sun, 3 Jun 2018 21:28:47 +0000 From: Rick Macklem To: "freebsd-current@freebsd.org" Subject: how to deal with variable set but not used warnings? Thread-Topic: how to deal with variable set but not used warnings? Thread-Index: AQHT+4Ei+kHu8bdJXk68BDSBUTlIlQ== Date: Sun, 3 Jun 2018 21:28:47 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; YTOPR0101MB1900; 7:98srb8/R8EWIHX+LiyxUj2pYfEoCga0JPBXnIxCdLGrwx9SShU2FrW1xUlIsXxRd3JETB5lFe87vDjSv644569uGLEMT0zfClaU4FQNgli3rzcJ3oberbceKRwH67Vnd26I/sb8F7QxFtZBDxdEP8QoqT49Ss0eJFasTrhKFDN3zpHTeRY94/wofhsQH4bOu4Dqkoa99adwBoE8kTc1kEhRTgkAAihQ2jyy28LWk6pvNSyT4ZXGFXeO0wpLOPcGw x-ms-exchange-antispam-srfa-diagnostics: SOS; x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(8989080)(5600026)(4534165)(4627221)(201703031133081)(201702281549075)(8990040)(2017052603328)(7153060)(7193020); SRVR:YTOPR0101MB1900; x-ms-traffictypediagnostic: YTOPR0101MB1900: authentication-results: spf=none (sender IP is ) smtp.mailfrom=rmacklem@uoguelph.ca; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-ms-exchange-senderadcheck: 1 x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(10201501046)(3002001)(93006095)(93001095)(3231254)(944501410)(52105095)(149027)(150027)(6041310)(20161123558120)(201703131423095)(201702281529075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(20161123560045)(20161123564045)(6072148)(201708071742011)(7699016); SRVR:YTOPR0101MB1900; BCL:0; PCL:0; RULEID:; SRVR:YTOPR0101MB1900; x-forefront-prvs: 069255B8B8 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(396003)(376002)(366004)(39380400002)(39860400002)(189003)(199004)(99286004)(68736007)(305945005)(102836004)(81156014)(81166006)(26005)(2351001)(105586002)(86362001)(106356001)(74316002)(478600001)(33656002)(316002)(25786009)(786003)(3660700001)(74482002)(3280700002)(14454004)(97736004)(5660300001)(2501003)(476003)(8676002)(5640700003)(9686003)(55016002)(8936002)(6916009)(186003)(53936002)(6506007)(6436002)(2906002)(2900100001)(7696005)(486006)(5250100002); DIR:OUT; SFP:1101; SCL:1; SRVR:YTOPR0101MB1900; H:YTOPR0101MB0953.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: uoguelph.ca does not designate permitted sender hosts) x-microsoft-antispam-message-info: E+gGKbrVkpI+6lXIqGwL5O9sm+3faTv4f03BDhN4e630zmSN7BiokXqsvvt0uCweURn9jD67BOIT4/eEpGMyjmha9aYN/UpjiYYjLr+aNP9ZyDWU4LzaXzt44ytIBqeVUnJWYaTzXgopuhUh6Am5/7OQdDbNxjv1l/hklMzQOYyXs2fLFPoYEB/nDSMR0nzq spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-MS-Office365-Filtering-Correlation-Id: 16243b8e-55ff-4718-1469-08d5c998fdcb X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-Network-Message-Id: 16243b8e-55ff-4718-1469-08d5c998fdcb X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Jun 2018 21:28:47.2324 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTOPR0101MB1900 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 21:28:49 -0000 mmacy has sent me a bunch of warnings of the "variable set but not used" ki= nd generated by gcc8. When I've looked at the code, these are for RPC arguments I parse but do no= t use at this time. I'd like to leave the code in place, since these arguments may be needed i= n the future and it is hard to figure out how to get them years from now, when th= ey might be needed. I can think of 3 ways to handle this: 1 - Get rid of the code. (As above, I'd rather not do this.) 2 - Wrap the code with "#if 0"/"#endif" or similar. I'll admit that I find = this rather ugly and tends to make the code harder to follow. 3 - Leave the code and add a comment w.r.t. why the variables are set but n= ot used. So, what do others think is the preferable alternative? (Or maybe you have a #4 that seems better than any of these.) Thanks for your comments, rick= From owner-freebsd-current@freebsd.org Sun Jun 3 21:33:04 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 65CF9FDEFD7 for ; Sun, 3 Jun 2018 21:33:04 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x22e.google.com (mail-io0-x22e.google.com [IPv6:2607:f8b0:4001:c06::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 ECFFE7E4AF for ; Sun, 3 Jun 2018 21:33:03 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x22e.google.com with SMTP id t6-v6so17175501iob.10 for ; Sun, 03 Jun 2018 14:33:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=kDeDyUj2k5TfL2GWbSK+/OvT4+p3jvq+9cPNpT8YkP0=; b=YSufHy9oP4C4BwjlY0I77UNyKGt+c6FavlTgIwAbUKy5qB709UD/j/lteivFM5kAeN +BeDW+ctpThgKZ5lOqdUjKMK47LoSPDaux9139wacx6tr+APU6BlA+C6VAW0jq1xaPm8 9F7BHRcIormlqx0L7b1uEheQfa/U+m3HX1yI+6E9maJ8Zy13S7wqZFk7RnecNAQ2u1mc yxiOU3DOijNO4r17YKe8ql/+eHhFxpwdcMWXymvDV1hlNhftKXDk2dqz906N9mWYSASU eqkU7d8l7uGfZgc5cDRM6bCMnDH/FIhYaPbOak5WY5uM3lq6cVEpunK6RuGKConnwIWY rQxg== 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=kDeDyUj2k5TfL2GWbSK+/OvT4+p3jvq+9cPNpT8YkP0=; b=I/u57bLiqv6jD8tGA4sQe3e1jD/jxi6lYGvJdE/6LFPSu6rRhfgLt6TZgN9lIy0CLD BtCBdqMbUnSpYYuDegF3KMJlTMgObRmGuPze1ACRW94A7ZQZzMBlovsWZX82ZN+vqHi0 ZB6wkn4vyNKBlZplsPPsIujdnhgOx0ETtZVUQVLtQO4Q1QU+Q11I3EhTp+A10UF+H/Fb vxijDQfWSOpl/JhPJ6cyAFyi1BUdOI+y7twhkEoD53yP+02DonWL5yGlW1nzsPcy7Yhd 1Lc3CQCYU98HG/KtMpT52z1kwhhEXbK/lEhWOt1eLRhMn6zfeppi71Qod9bVD+ONn3ek gCCw== X-Gm-Message-State: ALKqPwfdu6Qbye6ClOGtCrP00AZbqQLqtxAkVPymQZqsrbFg8+091KXr aQmUDEfTzEYyAYDmIjH4Ne+eWTNK6C3Vk9YDPK54Qw== X-Google-Smtp-Source: ADUXVKJ2yOzj3jYg0xuIoyUvdLHs31dzpu16b+dBQ4EmL3riiL8KLB5XeG0lOAtop3gHPlYDkZ8ZbkrOQ39K0UxVk34= X-Received: by 2002:a6b:284b:: with SMTP id o72-v6mr18764350ioo.168.1528061583232; Sun, 03 Jun 2018 14:33:03 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:d028:0:0:0:0:0 with HTTP; Sun, 3 Jun 2018 14:33:02 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: References: From: Warner Losh Date: Sun, 3 Jun 2018 15:33:02 -0600 X-Google-Sender-Auth: PAC8ovYuv4hkqEYLvdmWdWgBawg Message-ID: Subject: Re: how to deal with variable set but not used warnings? To: Rick Macklem Cc: "freebsd-current@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 21:33:04 -0000 On Sun, Jun 3, 2018 at 3:28 PM, Rick Macklem wrote: > mmacy has sent me a bunch of warnings of the "variable set but not used" > kind > generated by gcc8. > > When I've looked at the code, these are for RPC arguments I parse but do > not > use at this time. > I'd like to leave the code in place, since these arguments may be needed > in the > future and it is hard to figure out how to get them years from now, when > they > might be needed. > I can think of 3 ways to handle this: > 1 - Get rid of the code. (As above, I'd rather not do this.) > 2 - Wrap the code with "#if 0"/"#endif" or similar. I'll admit that I find > this rather > ugly and tends to make the code harder to follow. > 3 - Leave the code and add a comment w.r.t. why the variables are set but > not used. > > So, what do others think is the preferable alternative? > (Or maybe you have a #4 that seems better than any of these.) > 4. Disable the stupid warning in the Makefile / build system. If you don't care, and there's a good reason for what you are doing (sounds like there is), better to just disable the warning as so much useless noise. Warner From owner-freebsd-current@freebsd.org Sun Jun 3 21:40:18 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6550AFDFF6C for ; Sun, 3 Jun 2018 21:40:18 +0000 (UTC) (envelope-from theron.tarigo@gmail.com) Received: from mail-pg0-x229.google.com (mail-pg0-x229.google.com [IPv6:2607:f8b0:400e:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D68347EB42 for ; Sun, 3 Jun 2018 21:40:17 +0000 (UTC) (envelope-from theron.tarigo@gmail.com) Received: by mail-pg0-x229.google.com with SMTP id e11-v6so4359866pgq.0 for ; Sun, 03 Jun 2018 14:40:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:subject:to:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=tmDvpxIIzUSqKatZDhO/6k1TIjYyrgcAcDJb6GHTkz4=; b=Wo41tlrQsY2iklze8lvxA4Glt0d30TydW57gRVPWDne0uHRJ4zmUpHw/L4RjS3XLQG 0rfquT32hkpH4q9hxfJcVsMX2eFelkMTv6M64Wu4WSEi66kmABaF4/hiVKSsvuJHxIIw Tfkr+MfuWkbCKSWGekQj0+Wt6sP649GV3hNc2ehRPfVPkwBvwdUtX08WFbhBLFait0Zi Q9u4BFDWjDGFzw57P+EzAdzkeo2LIK7wExCfQCjNeJf+X8Iw2mfBbdB8i9tBjEV5Hl2U xdYrtw03bRnoQrcYSVUk9mkRSwndKsKSb198V2MZD8W17Gm6n0q1RycP5L50Q4P9JHPQ A2Gw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=tmDvpxIIzUSqKatZDhO/6k1TIjYyrgcAcDJb6GHTkz4=; b=Q6GuoH/3U8Eu1FqYxveRJ+lz/3ACvIhxVxLaEo9Qq0wr2FBIXGz2ZoU2s6paVK36q/ m4lw5nROyvhT8zZeGly3crpEcuhDpMcvXNfZ7fJSWraO21CsVqmt6qO4WpequEF5hbUP a4gGxnixhR4fBfkUmwBtdInqL5CgiaJx7rG44qDfrTeOEBC+Qr9yWBQThX7yKePodWMg 7E8MhjyxwnhrOXeX6z2naeJ9SDYrVACVREOB5Dlt0FCCjD0NGr6r3PZLCSn9Rtpfdbir +hDAQUmmm72Edij1RCexDMSGgkbWcum0EaugqqXqwdnYld7iU8+81RG9i7EAshMA2GxC Noug== X-Gm-Message-State: ALKqPwcnA3sUbJ5zX1qZNbGB0aJYEl/HdsA0Gl0WafLfrnOrDcmkNxPj Tf45oYNhw9j9nbTodBB17Sq9BEBI X-Google-Smtp-Source: ADUXVKK1vlCVwG25tYTzG6i06IphLXuqa3M2ekQMXCtaTRsnUL9Nv9Cep97FiTVaXl5dgx4KtJziKQ== X-Received: by 2002:a65:590f:: with SMTP id f15-v6mr15163817pgu.111.1528062016807; Sun, 03 Jun 2018 14:40:16 -0700 (PDT) Received: from [192.168.1.10] (c-73-170-47-221.hsd1.ca.comcast.net. [73.170.47.221]) by smtp.gmail.com with ESMTPSA id x2-v6sm906014pfn.11.2018.06.03.14.40.16 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 03 Jun 2018 14:40:16 -0700 (PDT) Sender: Theron Tarigo Subject: Re: how to deal with variable set but not used warnings? To: freebsd-current@freebsd.org References: From: Theron Message-ID: Date: Sun, 3 Jun 2018 17:40:15 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: 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.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 21:40:18 -0000 On 06/03/18 17:33, Warner Losh wrote: > On Sun, Jun 3, 2018 at 3:28 PM, Rick Macklem wrote: > >> mmacy has sent me a bunch of warnings of the "variable set but not used" >> kind >> generated by gcc8. >> >> When I've looked at the code, these are for RPC arguments I parse but do >> not >> use at this time. >> I'd like to leave the code in place, since these arguments may be needed >> in the >> future and it is hard to figure out how to get them years from now, when >> they >> might be needed. >> I can think of 3 ways to handle this: >> 1 - Get rid of the code. (As above, I'd rather not do this.) >> 2 - Wrap the code with "#if 0"/"#endif" or similar. I'll admit that I find >> this rather >> ugly and tends to make the code harder to follow. >> 3 - Leave the code and add a comment w.r.t. why the variables are set but >> not used. >> >> So, what do others think is the preferable alternative? >> (Or maybe you have a #4 that seems better than any of these.) >> > 4. Disable the stupid warning in the Makefile / build system. If you don't > care, and there's a good reason for what you are doing (sounds like there > is), better to just disable the warning as so much useless noise. > > Warner > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" Or possibly, alongside a comment as in (3), use one of these: 5 - Disable warning pragma - http://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Pragmas.html 6 - Use __attribute__((unused)) - https://gcc.gnu.org/onlinedocs/gcc/Common-Variable-Attributes.html#Common-Variable-Attributes From owner-freebsd-current@freebsd.org Sun Jun 3 22:06:32 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E2941FE3201 for ; Sun, 3 Jun 2018 22:06:31 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-no.shaw.ca (smtp-out-no.shaw.ca [64.59.134.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 705027FF1D for ; Sun, 3 Jun 2018 22:06:31 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id Pb8mfMCCivB5RPb8nfWhGa; Sun, 03 Jun 2018 16:06:23 -0600 X-Authority-Analysis: v=2.3 cv=PvS9kTE3 c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=kj9zAlcOel0A:10 a=7mUfYlMuFuIA:10 a=xfDLHkLGAAAA:8 a=hF2rLc1pAAAA:8 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=f4XEX6ON5feEunTDJdkA:9 a=CjuIK1q_8ugA:10 a=iB5APFlFwgEA:10 a=IfaqVvZgccqrtc8gcwf2:22 a=O9OM7dhJW_8Hj9EqqvKN:22 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id 17CB32C6A; Sun, 3 Jun 2018 15:06:20 -0700 (PDT) Received: from slippy.cwsent.com (localhost [127.0.0.1]) by slippy.cwsent.com (8.15.2/8.15.2) with ESMTP id w53M6JSZ095955; Sun, 3 Jun 2018 15:06:19 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Received: from slippy (cy@localhost) by slippy.cwsent.com (8.15.2/8.15.2/Submit) with ESMTP id w53M6Jkp095952; Sun, 3 Jun 2018 15:06:19 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <201806032206.w53M6Jkp095952@slippy.cwsent.com> X-Authentication-Warning: slippy.cwsent.com: cy owned process doing -bs X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Warner Losh cc: Rick Macklem , "freebsd-current@freebsd.org" Subject: Re: how to deal with variable set but not used warnings? In-Reply-To: Message from Warner Losh of "Sun, 03 Jun 2018 15:33:02 -0600." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 03 Jun 2018 15:06:19 -0700 X-CMAE-Envelope: MS4wfPy6ZbTKRg2azon6lyqLjj07Yp+Qk2xJZu00udsxOL2vVyp4E9xtQG2zHo9aHBxcy+dIWmqbjkkEV1ssFYTumjZbFATkS4Bc73H5zd3Z/WG9oP2lMz/9 0iMyIBhjUXgyZLzDenR4d8nrkBRq+VPp5juXM9SnB2BLrtD1K6SXZreY9xAQQOyW5S3MDhq2mf9Cy7lK82eWuawuYXNHphajmrx2AIE32YwQuW3kT0FBekp+ I4O+gfQGiTtHLUiLy2NeYQ== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 22:06:32 -0000 In message , Warner Losh writes: > On Sun, Jun 3, 2018 at 3:28 PM, Rick Macklem wrote: > > > mmacy has sent me a bunch of warnings of the "variable set but not used" > > kind > > generated by gcc8. > > > > When I've looked at the code, these are for RPC arguments I parse but do > > not > > use at this time. > > I'd like to leave the code in place, since these arguments may be needed > > in the > > future and it is hard to figure out how to get them years from now, when > > they > > might be needed. > > I can think of 3 ways to handle this: > > 1 - Get rid of the code. (As above, I'd rather not do this.) > > 2 - Wrap the code with "#if 0"/"#endif" or similar. I'll admit that I find > > this rather > > ugly and tends to make the code harder to follow. > > 3 - Leave the code and add a comment w.r.t. why the variables are set but > > not used. > > > > So, what do others think is the preferable alternative? > > (Or maybe you have a #4 that seems better than any of these.) > > > > 4. Disable the stupid warning in the Makefile / build system. If you don't > care, and there's a good reason for what you are doing (sounds like there > is), better to just disable the warning as so much useless noise. And leave a comment in the Makefile in case someone decides to re-enable the warning at some later date. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. From owner-freebsd-current@freebsd.org Sun Jun 3 22:20:02 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5A74AFE4CF0 for ; Sun, 3 Jun 2018 22:20:02 +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 E0EEE808D9 for ; Sun, 3 Jun 2018 22:20:01 +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 w53MJtFj046000 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 3 Jun 2018 15:19:55 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id w53MJtmK045999; Sun, 3 Jun 2018 15:19:55 -0700 (PDT) (envelope-from sgk) Date: Sun, 3 Jun 2018 15:19:55 -0700 From: Steve Kargl To: Rick Macklem Cc: "freebsd-current@freebsd.org" Subject: Re: how to deal with variable set but not used warnings? Message-ID: <20180603221955.GA45990@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.2 (2017-12-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 22:20:02 -0000 On Sun, Jun 03, 2018 at 09:28:47PM +0000, Rick Macklem wrote: > mmacy has sent me a bunch of warnings of the "variable set but not used" kind > generated by gcc8. > > When I've looked at the code, these are for RPC arguments I parse but do not > use at this time. > I'd like to leave the code in place, since these arguments may be needed in the > future and it is hard to figure out how to get them years from now, when they > might be needed. > I can think of 3 ways to handle this: > 1 - Get rid of the code. (As above, I'd rather not do this.) > 2 - Wrap the code with "#if 0"/"#endif" or similar. I'll admit that I find this rather > ugly and tends to make the code harder to follow. > 3 - Leave the code and add a comment w.r.t. why the variables are set but not used. > > So, what do others think is the preferable alternative? > (Or maybe you have a #4 that seems better than any of these.) > CFLAGS+=-Wno-unused -- Steve From owner-freebsd-current@freebsd.org Sun Jun 3 21:43:49 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 815B8FE0853 for ; Sun, 3 Jun 2018 21:43:49 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 146C97F0F0 for ; Sun, 3 Jun 2018 21:43:49 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: by mail-io0-x22b.google.com with SMTP id l19-v6so25982855ioj.5 for ; Sun, 03 Jun 2018 14:43:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=7KiM17tltfiIlmjVfJ0vGNee5SHAqeyZBhTLJSm6Vtk=; b=OE9pGQTL79mj6xmmUr90D4GX/kAIoN8VfecFiXaCUe8C7dF9N+ELgj9hASGtQcSRax 9MEE4ieVVN6d4Y8yvCsrzs8aTsr2bEaLN0kpIoSCBReaPBXmCY7EBQy/HaxNhDHWmPwb mw5FtYutCqkas1WxtXXdR1o73pe0XvWj8vHd6pgg2obPP1Yq8CyX1uzloxjXhE0iGZ8P l0jAYkNSRhGO7x2YxFtgrrTonb5KrX35Ut29/7QrxsG3ZxiwPf04iepr/NfstZ7kQEXI CGbrAVh05s9jMfjh4ALUU6o5PeJTE9XSdnunqoy8COFKnxpyPmu3CRevQFBZCcMCTPcz ClyA== 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=7KiM17tltfiIlmjVfJ0vGNee5SHAqeyZBhTLJSm6Vtk=; b=Bh6gLSamENTg/bJ0D9gHhOTyU+1TTMJNV8L7dMpIVoKUpkea1yIKUBYsxwQKbr5Qb9 bYNYxNvHYiZAdxecnM8b8BEnto/GxYCJSg9AAM5KQHePz+5FFAHNwaSJk7SnalgHzUMZ 09XfUFUCyYCSmJqoCZJ/UMy9AzNe6S1wCcVvAGv6QwiLMFxGZWQhIxt2BlX3Btq8d/aq buyBsNXeB1iQFZWmK++8mp6+eOH5C4gA62PSq8yk9/Gp0PKSd4ARZKP2C3AE4bjuthyd aYwzA4ybNxlqxi2K023aDfp0IPKP69Y0xzC0RckmGxkMqrcdihmXIWnqZwXzBtZcdi91 Xsdw== X-Gm-Message-State: ALKqPwcfhkZCnPcIbX9/35ZtXsxU+Mm4ebG29mP/BDDQhODPpx21qe9v xCHPQiZeDkFdt2Uy+02GQWyP7Pb+x4W2SNCF0ac= X-Google-Smtp-Source: ADUXVKJg8bph+FJgXAS2qOs8NsezU9vxoq/VhpAI6c9wqEo3+g6ea/KajNjBEmexH+JQKuY55nJfhvS+ebPVQfGs1Iw= X-Received: by 2002:a6b:582:: with SMTP id 124-v6mr11061268iof.94.1528062228350; Sun, 03 Jun 2018 14:43:48 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a02:8cd:0:0:0:0:0 with HTTP; Sun, 3 Jun 2018 14:43:47 -0700 (PDT) In-Reply-To: References: From: Matthew Macy Date: Sun, 3 Jun 2018 14:43:47 -0700 Message-ID: Subject: Re: how to deal with variable set but not used warnings? To: Theron Cc: freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Mailman-Approved-At: Sun, 03 Jun 2018 22:41:50 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 21:43:49 -0000 On Sun, Jun 3, 2018 at 2:40 PM, Theron wrote: >> 4. Disable the stupid warning in the Makefile / build system. If you don't >> care, and there's a good reason for what you are doing (sounds like there >> is), better to just disable the warning as so much useless noise. >> >> Warner >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > Or possibly, alongside a comment as in (3), use one of these: > 5 - Disable warning pragma - > http://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Pragmas.html > 6 - Use __attribute__((unused)) - > https://gcc.gnu.org/onlinedocs/gcc/Common-Variable-Attributes.html#Common-Variable-Attributes There is already an __unused alias for #6. It's what I've used to annotate variables that are only used by INVARIANTS builds. It legitimately finds a bunch of dead code. However, 90+% of the instances of the warning are not interesting. -M From owner-freebsd-current@freebsd.org Sun Jun 3 22:46:36 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6F304FE7E22 for ; Sun, 3 Jun 2018 22:46:36 +0000 (UTC) (envelope-from freebsd@grem.de) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id E207281C6F for ; Sun, 3 Jun 2018 22:46:35 +0000 (UTC) (envelope-from freebsd@grem.de) Received: (qmail 89240 invoked by uid 89); 3 Jun 2018 22:46:34 -0000 Received: from unknown (HELO bsd64.grem.de) (mg@grem.de@93.104.95.157) by mail.grem.de with ESMTPA; 3 Jun 2018 22:46:34 -0000 Date: Mon, 4 Jun 2018 00:46:32 +0200 From: Michael Gmelin To: Konstantin Belousov Cc: Michael Gmelin , "freebsd-current@freebsd.org" , Matthias Apitz , jhb@freebsd.org Subject: Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy) Message-ID: <20180604004632.56ca6afa@bsd64.grem.de> In-Reply-To: <20180603205340.GS3789@kib.kiev.ua> References: <20180603144840.44bfea41@bsd64.grem.de> <20180603132110.GP3789@kib.kiev.ua> <20180603165500.361ec894@bsd64.grem.de> <20180603150423.GQ3789@kib.kiev.ua> <20180603215020.452a81d8@bsd64.grem.de> <20180603205340.GS3789@kib.kiev.ua> X-Mailer: Claws Mail 3.15.1 (GTK+ 2.24.31; amd64-portbld-freebsd10.3) X-Face: $wrgCtfdVw_H9WAY?S&9+/F"!41z'L$uo*WzT8miX?kZ~W~Lr5W7v?j0Sde\mwB&/ypo^}> +a'4xMc^^KroE~+v^&^#[B">soBo1y6(TW6#UZiC]o>C6`ej+i Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEWJBwe5BQDl LASZU0/LTEWEfHbyj0Txi32+sKrp1Mv944X8/fm1rS+cAAAACXBIWXMAAAsTAAAL EwEAmpwYAAAAB3RJTUUH3wESCxwC7OBhbgAAACFpVFh0Q29tbWVudAAAAAAAQ3Jl YXRlZCB3aXRoIFRoZSBHSU1QbbCXAAAAAghJREFUOMu11DFvEzEUAGCfEhBVFzuq AKkLd0O6VrIQsLXVSZXoWE5N1K3DobBBA9fQpRWc8OkWouaIjedWKiyREOKs+3PY fvalCNjgLVHeF7/3bMtBzV8C/VsQ8tecEgCcDgrzjekwKZ7TwsJZd/ywEKwwP+ZM 8P3drTsAwWn2mpWuDDuYiK1bFs6De0KUUFw0tWxm+D4AIhuuvZqtyWYeO7jQ4Aea 7jUqI+ixhQoHex4WshEvSXdood7stlv4oSuFOC4tqGcr0NjEqXgV4mMJO38nld4+ xKNxRDon7khyKVqY7YR4d+Cg0OMrkWXZOM7YDkEfKiilCn1qYv4mighZiynuHHOA Wq9QJq+BIES7lMFUtcikMnkDGHUoncA+uHgrP0ctIEqfwLHzeSo+eUA66AqzwN6n 2ZHJhw6Qh/PoyC/QENyEyC/AyNjq74Bs+3UH0xYwzDUC4B97HgLocg1QLYgDDO1v f3UX9Y307Ew4AHh67YAFFsxEpkXwpXY3eIgMhAAE3R19L919nNnuD2wlPcDE3UeT L2ytEICQib9BXgS2fU8PrD82ToYO1OEmMSnYTjSqSv9wdC0tPYC+rQRQD9ESnldF CyqfmiYW+tlALt8gH2xrMdC/youbjzPXEun+/ReXsMCDyve3dZc09fn2Oas8oXGc Jj6/fOeK5UmSMPmf/jL+GD8BEj0k/Fn6IO4AAAAASUVORK5CYII= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 22:46:36 -0000 On Sun, 3 Jun 2018 23:53:40 +0300 Konstantin Belousov wrote: > On Sun, Jun 03, 2018 at 09:50:20PM +0200, Michael Gmelin wrote: > > > > > > On Sun, 3 Jun 2018 18:04:23 +0300 > > Konstantin Belousov wrote: > > > > > On Sun, Jun 03, 2018 at 04:55:00PM +0200, Michael Gmelin wrote: > > > > > > > > > > > > On Sun, 3 Jun 2018 16:21:10 +0300 > > > > Konstantin Belousov wrote: > > > > > > > > > On Sun, Jun 03, 2018 at 02:48:40PM +0200, Michael Gmelin > > > > > wrote: > > > > > > Hi, > > > > > > > > > > > > After upgrading CURRENT to r333992 (from something at least > > > > > > a year old, quite some changes in mp_machdep.c since), this > > > > > > machine crashes on boot: > > > > > > > > > > > > Copyright (c) 1992-2018 The FreeBSD Project. > > > > > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, > > > > > > 1992, 1993, 1994 The Regents of the University of > > > > > > California. All rights reserved. FreeBSD is a registered > > > > > > trademark of The FreeBSD Foundation. FreeBSD 12.0-CURRENT > > > > > > #1 r333992: Tue May 22 00:31:04 CEST 2018 > > > > > > root@flimsy:/usr/obj/usr/src/amd64.amd64/sys/flimsy amd64 > > > > > > FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) > > > > > > (based on LLVM 6.0.0) WARNING: WITNESS option enabled, > > > > > > expect reduced performance. VT(vga): resolution 640x480 > > > > > > CPU: Intel(R) Celeron(R) 2955U @ 1.40GHz (1396.80-MHz > > > > > > K8-class CPU) Origin="GenuineIntel" Id=0x40651 > > > > > > Family=0x6 Model=0x45 Stepping=1 > > > > > > Features=0xbfebfbff > > > > > CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > > > > > > Features2=0x4ddaebbf > > > > > xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,TSCDLT,XSAVE,OSXSAVE,RDRAND> > > > > > > AMD Features=0x2c100800 AMD > > > > > > Features2=0x21 Structured Extended > > > > > > Features=0x2603 XSAVE > > > > > > Features=0x1 VT-x: (disabled in BIOS) > > > > > > PAT,HLT,MTF,PAUSE,EPT,UG,VPID TSC: P-state invariant, > > > > > > performance statistics real memory = 4301258752 (4102 MB) > > > > > > avail memory = 1907572736 (1819 MB) Event timer "LAPIC" > > > > > > quality 600 ACPI APIC Table: > > > > > What does this mean ? Did you flashed coreboot ? > > > > > > > > This machine comes with it by default (my model was delivered > > > > with SeaBIOS 20131018_145217-build121-m2). So I didn't flash > > > > anything (didn't feel like bricking it). > > > > > > > > > > > > > > > kernel trap 12 with interrupts disabled > > > > > > > > > > > > Fatal trap 12: page fault while in kernel mode > > > > > > cpuid = 0; apic id = 00 > > > > > > fault virtual address = 0xfffff80001000000 > > > > > > fault code = supervisor write data, protection > > > > > > violation instruction pointer = 0x20:Oxffffffff8102955f > > > > > > stack pointer = 0x28:0xffffffff82a79be0 > > > > > > frame pointer = 0x28:0xffffffff82a79c10 > > > > > > code segment = base Ox0, limit Oxfffff, type > > > > > > Ox1b = DPL 0, pres 1, long 1, def32 0, gran > > > > > > 1 processor eflags = resume, IOPL = 0 > > > > > > current process = 0 () > > > > > > [ thread pid 0 tid 0 ] > > > > > > Stopped at native_start_all_aps+0x08f: movq > > > > > > %rax,(%rsi) > > > > > Look up the source line number for this address. > > > > > > > > > > > > > I guess that's sys/amd64/amd64/support.S line 854 (in rdmsr), > > > > called by native_start_all_aps. Any additional hints how I can > > > > track it down? > > > Why did you decided that this is rdmsr_safe() ? First, > > > native_start_all_aps() does not call rdmsr, second the ddb > > > report clearly indicates that the fault occured acessing DMAP in > > > native_start_all_aps(). > > > > > > Just look up the source line by the address > > > native_start_all_aps+0x08f. > > > > Okay, according to kgbd this should be here: > > > > https://svnweb.freebsd.org/base/head/sys/amd64/amd64/mp_machdep.c?revision=333368&view=markup#l369 > > > > 364 > > 365 /* Create the initial 1GB replicated page tables */ > > 366 for (i = 0; i < 512; i++) { > > 367 /* Each slot of the level 4 pages points to the same > > level 3 page */ 368 pt4[i] = > > (u_int64_t)(uintptr_t)(mptramp_pagetables + PAGE_SIZE); 369 > > pt4[i] |= PG_V | PG_RW | PG_U; 370 > > 371 /* Each slot of the level 3 pages points to the same > > level 2 page */ 372 pt3[i] = > > (u_int64_t)(uintptr_t)(mptramp_pagetables + (2 * PAGE_SIZE)); > > 373 pt3[i] |= PG_V | PG_RW | PG_U; 374 > > 375 /* The level 2 page slots are mapped with 2MB pages > > for 1GB. */ 376 pt2[i] = i * (2 * 1024 * 1024); > > 377 pt2[i] |= PG_V | PG_RW | PG_PS | PG_U; > > 378 } > > > > -m > You have fault on write due to read-only mapping of the portion of > the direct map, which maps the kernel text. It is consistent with > the faulting address. It is not clear if it is something new on > your machine, or before the kernel text was silently corrupted, since > ro protection is somewhat recent. > > It seems that mp_bootaddress() selected the bad place for the > bootstrap page tables. Even more, we do not include the kernel text > into the physmem[] array, so it is not clear how did it happen. This > code was also changed recently. > > Can you add the print of the physmap[] array somewhere before the > panic, to see what is the kernel idea of the available memory ? It > should be already done if you have serial console and set > debug.late_console tunable to 0. This is a sad little machine without any kind of serial console. Physmap looks like this after calling getmemsize(): [0]: 0x10000 [1]: 0x30000 [2]: 0x40000 [3]: 0x9e000 [4]: 0x100000 [5]: 0xf00000 [6]: 0x1003000 [7]: 0x7bf7a000 Physical memory chunks logged in cpu_startup are: 0x0000000000010000 - 0x000000000002ffff, 141072 bytes (32 pages) 0x0000000000040000 - 0x000000000009dfff, 385024 bytes (94 pages) 0x0000000000100000 - 0x00000000001fffff, 1048576 bytes (256 pages) 0x0000000002c00000 - 0x0000000075467fff, 1921417216 bytes (469096 pages) 0x0000000100000000 - 0x00000001005e7fff, 6193152 bytes (1512 pages) -m > > > > > p.s. This machine uses quirks in biosmem.c, see > > > > Type '?' for a list of command, 'help' for more detailed > > help. > > OK biosmem > > bios_basemem: 0x9e400 > > bios_extmem: 0x3ff00000 > > memtop: 0x3c000000 > > high_heap_base: 0x3c000000 > > high_heap_size: 0x4000000 > > bios_quirks: 0x01 BQ_DISTRUST_820_EXTMEM > > b_bios_probed: 0x0a B_BASEMEM_12 B_EXTMEM_E801 > > > > -- > > Michael Gmelin > > > > -- > > Michael Gmelin -- Michael Gmelin From owner-freebsd-current@freebsd.org Sun Jun 3 23:03:01 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F0A7BFE9C87 for ; Sun, 3 Jun 2018 23:03:00 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3ECDB828F7 for ; Sun, 3 Jun 2018 23:03:00 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w53N2uPr093140; Sun, 3 Jun 2018 16:02:56 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w53N2ufE093139; Sun, 3 Jun 2018 16:02:56 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201806032302.w53N2ufE093139@pdx.rh.CN85.dnsmgr.net> Subject: Re: SPDX-License-Id for new files In-Reply-To: To: Rick Macklem Date: Sun, 3 Jun 2018 16:02:56 -0700 (PDT) CC: "freebsd-current@freebsd.org" X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 23:03:01 -0000 > I have a few (3) new files in the projects/pnfs-planb-server subversion tree > that all have the 2 clause FreeBSD copyright. > > Do I just add the "SPDX..." line for this license at the top of the copyright comment > or is there some other exercise needed to be done for this? Just add the SPDX line, Try to make it the first line inside the block comment: /*- * SPDX-License-Identifier: BSD-2-Clause Regards, -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Mon Jun 4 01:13:16 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 32709FD07C0 for ; Mon, 4 Jun 2018 01:13:16 +0000 (UTC) (envelope-from bkidney@briankidney.ca) Received: from mail-qk0-x236.google.com (mail-qk0-x236.google.com [IPv6:2607:f8b0:400d:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C70DC68271 for ; Mon, 4 Jun 2018 01:13:15 +0000 (UTC) (envelope-from bkidney@briankidney.ca) Received: by mail-qk0-x236.google.com with SMTP id g14-v6so11659617qkm.6 for ; Sun, 03 Jun 2018 18:13:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=briankidney-ca.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version; bh=0ezgBxhnRSzd1fnYOazwt7O07ugtVdIXF7xSzP6rX1I=; b=mV5EsSgb77uPJ5AV/gtUVH4iKZxhjfSfiEv9nxYjUJHrlPXtIfaukgoA/yXNvN4yy/ hotV1ky/jiCcfHdxVZitdJZ6ZpII946yHohFfWz6v7kfXvEr2MXNfkV2w849eBs5rGeP QyNpjSrCGi70LwT0GR6VIRoh8LzSzyFoB/DolB7qvib3Kcw8+TqkNLkdvpgJtKKgNrHW Eo2mTRq+kWNHjrvgP+Q6AhMpbBPw6Iz4iQu3WElwnXyvkPOXpiOQYR7oo2KiUPCGzQ+W hCY9kVark3O+xgjcOlkFDZ4kgHvxc4UyjMzW1yeMdqZP6FVck11wIde8RTL4fs1Qb01T 40Xg== 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:in-reply-to :references:mime-version; bh=0ezgBxhnRSzd1fnYOazwt7O07ugtVdIXF7xSzP6rX1I=; b=edXa2ARDfKxcFsm7bLhk8ih19fZhobg7ll9PtUJ6C+pjZvhj1vrACg138FIFCOV7Yo XBqP40vS1HBBT2NkVKS48CpVAJP3R7uboIzABLLlWQUUv6BI0aDxizG9+noi34zLX41K iVduSlZ58Pp6d9GJOlsPCo/WzWu0jUxpLy/fTxYaB981guhpwHG09V/wxVJU8peQSltf yiQRYh0WtOEBbeewtXP3BuV/JegjOaJxYtXBCNDd3rOIhg6SfLfmadPoBTXgEe/h6dZr ZZwJe+VOIEDjaBP3c5E8SkK3/x+5q3mVKgQogZCAYgfGCYFZ5aNxIE5HPy8fbqEecO+2 9bOA== X-Gm-Message-State: APt69E1m3OAKxEe4kW9r6qfP8wjlz3bpCe5MPCxIATQ3V/+Cj6VgcT1d r1WbLE5xkn6Ts+J63FhZE6W15g== X-Google-Smtp-Source: ADUXVKI1fWAHYuuq/8wt1sPy4D/TDrzgVx5gYjg4XLu3Y0vs48xHYwViWqI0W1VMI8bMwLTJbLpSwg== X-Received: by 2002:a37:bcc2:: with SMTP id m185-v6mr17593183qkf.367.1528074795005; Sun, 03 Jun 2018 18:13:15 -0700 (PDT) Received: from [192.168.1.10] (mtprnf0117w-156-57-81-89.dhcp-dynamic.fibreop.nl.bellaliant.net. [156.57.81.89]) by smtp.gmail.com with ESMTPSA id w6-v6sm5037091qtj.71.2018.06.03.18.13.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 03 Jun 2018 18:13:14 -0700 (PDT) From: "Brian Kidney" To: Albert Cc: freebsd-current@freebsd.org Subject: Re: Elantech Touchpad Woes - Support for Elantech touchpads over i2c/SMBus still possibly missing Date: Sun, 03 Jun 2018 22:43:12 -0230 X-Mailer: MailMate (1.11.2r5479) Message-ID: In-Reply-To: <5dd8bac9-d5c5-01e6-aea1-998be132a025@gmail.com> References: <0E69C450-42AE-438A-8C33-54B8E4B561F5@grem.de> <5dd8bac9-d5c5-01e6-aea1-998be132a025@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2018 01:13:16 -0000 Hi all, I have a ASUS Zenbook UX430U with the same problem. I am heading to BSDCan (and the FreeBSD Dev Submit as a guest) this week and could spend some time working on this in the hacker lounge. That said, I am new to FreeBSD driver code, so I could use some guidance to help me along. Anyone headed to the conference that might be able to lend me a hand? Thanks, Brian Brian Kidney, M.Eng., P.Eng. PGP Fingerprint: B8C9 D174 BABC 7FD8 67D0 DF84 FDEE B338 F248 A893 On 3 Jun 2018, at 2:43, Albert wrote: > Michael, > > Good to know you still have plans to work on that eventually. It'd be > much appreciated. > > Looking at the source for your cyapa driver, I see you've ported it > from the DragonFlyBSD driver (and they in turn adapted it from the > Linux one). I should've looked into that earlier... Instead I spent > most of my day trying to get OpenBSD running to try and follow Tom's > hint at possible support there, but I had so many more issues along > the way that in the end I figured "if I'm having trouble even getting > a keyboard to work on this with my system, a touchpad will likely be > the least of my worries." > > So, I'm back to my FreeBSD CURRENT install, still no touchpad support > (obviously). I guess I'll be doing some more research on these things > and tinkering with what I find. Unfortunately, I'm moving overseas in > a couple of weeks and leaving my desktop behind, which means I need to > have this laptop in full working condition by then, so if I don't make > any progress, I'll have to somewhat reluctantly go back to Linux for > the time being. If/when that happens, I'll still be happy to help with > any testing. > > MfG, > > - Albert > > _______________________________________________ > 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 Jun 4 02:50:20 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 52980FE21E8 for ; Mon, 4 Jun 2018 02:50:20 +0000 (UTC) (envelope-from mail@dbalan.in) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F16F06BA97 for ; Mon, 4 Jun 2018 02:50:19 +0000 (UTC) (envelope-from mail@dbalan.in) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 58B5D21A57; Sun, 3 Jun 2018 22:50:19 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Sun, 03 Jun 2018 22:50:19 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dbalan.in; h=cc :content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=F7e63muLAwWJYdtIJkMyLy4z7ff1kc3mtI0SF8zwvyI=; b=OB/rs50H ZCUlUUIdkmysU/yrlPauNYtgwEx6Ww/BhUXlkrQrjxV7EvT0OtcdHzjiTdwwxZvY AlJc0CuOVFG9hqee6vIRJK+tKMDayZo1fDHOwIE2FQAWf6fDow1kOEmfFVQKuEfY iqQRuHR3Jqc1QB2T27GGPVwnZVsHTDjZv4pKG6aUJOFAaZ4zq4m/OOotJJQkBp1/ SRg6Q/5K0H9QvfvomPghzUIEP3e8VsbBLfw2PtQhpadAggtDPiYVIH1lP/oZcsha ngPkm3vmErRT7TL4Yf7K6e2LmKzhKehGqjux8DFgxMMm73ktRZ/RQTPM8s3cLrLe ovdZz9n6OfidNA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=F7e63muLAwWJYdtIJkMyLy4z7ff1k c3mtI0SF8zwvyI=; b=XKE0GUVIbPVaptHcjTYiqdSZXMnOSyH5HdqEI6Ifit3n4 1XYha+PntC5qz19jgNCJdMtMx7n2SppFkH88pE0EdDklPdo/Du1TzwqA/BwFnJeg bNRQuKewghM70UpAyACJCJb+OWzr4h7peWH16kpAj8uDozl+2ZAs1jY+SbwQA5Fm hi8Wv0MvWempZwcrk2Wlak19rt8T/Sr/mSDefjp8dhAp0zxnQlUtL8/oTxnj30pP EMohx8o4DpXodoJOQbMxGSqVMDR6nrZI+Sy72XjhHyKSN9zhxkGymtoKUo8GfZM3 62N0U1EyzoKczoNPguCK24G8YLhXV5e2IRYbbXPHQ== X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Sender: Received: from localhost (unknown [223.226.69.125]) by mail.messagingengine.com (Postfix) with ESMTPA id 82B5010266; Sun, 3 Jun 2018 22:50:18 -0400 (EDT) Date: Mon, 4 Jun 2018 08:20:16 +0530 From: Dhananjay Balan To: Christoph Moench-Tegeder Cc: freebsd-current@freebsd.org Subject: Re: Can't seem to use 5GHz APs with Intel wireless Message-ID: <20180604025016.xe5ezrkjum7gs3pv@kazhap> References: <20180601091031.72u7tqfkatsl3guh@kazhap> <20180601223711.GA93642@elch.exwg.net> <20180603145342.qziiv7awhr4cvs73@kazhap> <20180603173330.p6h7x6vznzxwbqmp@squirrel.exwg.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180603173330.p6h7x6vznzxwbqmp@squirrel.exwg.net> User-Agent: NeoMutt/20180512 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2018 02:50:20 -0000 On Sun, Jun 03, 2018 at 07:33:30PM +0200, Christoph Moench-Tegeder wrote: > Is the regdomain/country setting correct for your area and matches your > AP? Especially in the 5GHz band there are some "gaps" - not all channels > may be used in all countries (because of possible interference with > radar equipment and other stuff). See: > https://en.wikipedia.org/wiki/List_of_WLAN_channels#5_GHz_(802.11a/h/j/n/ac/ax) > Thanks for taking time to explain. Turns out PEBKAC. I had this offending line burried in rc.conf create_args_wlan0="country DE regdomain FCC4" According to regdomain(5) So I was forcing my card to do 2.4Ghz it seems, removed it - everything worked like charm. I can see and connect to 5GHz 11a aps. wlan0: flags=8843 metric 0 mtu 1500 ether xxxx inet 192.168.1.13 netmask 0xffffff00 broadcast 192.168.1.255 nd6 options=29 media: IEEE 802.11 Wireless Ethernet MCS mode 11na status: associated ssid xxxx channel 36 (5180 MHz 11a ht/40+) bssid xxxxxxxx regdomain FCC country US authmode WPA2/802.11i privacy ON deftxkey UNDEF TKIP 2:128-bit txpower 17 bmiss 10 mcastrate 6 mgmtrate 6 scanvalid 60 ampdulimit 64k ampdudensity 4 -amsdutx amsdurx shortgi -stbc -ldpc wme roaming MANUAL - dbalan From owner-freebsd-current@freebsd.org Mon Jun 4 11:07:12 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 76C0FFF5637 for ; Mon, 4 Jun 2018 11:07:12 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F30DF807D5; Mon, 4 Jun 2018 11:07:11 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTP id w54B6tit019883; Mon, 4 Jun 2018 14:06:58 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w54B6tit019883 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w54B6t03019867; Mon, 4 Jun 2018 14:06:55 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 4 Jun 2018 14:06:55 +0300 From: Konstantin Belousov To: Michael Gmelin Cc: "freebsd-current@freebsd.org" , Matthias Apitz , jhb@freebsd.org Subject: Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy) Message-ID: <20180604110654.GA2450@kib.kiev.ua> References: <20180603144840.44bfea41@bsd64.grem.de> <20180603132110.GP3789@kib.kiev.ua> <20180603165500.361ec894@bsd64.grem.de> <20180603150423.GQ3789@kib.kiev.ua> <20180603215020.452a81d8@bsd64.grem.de> <20180603205340.GS3789@kib.kiev.ua> <20180604004632.56ca6afa@bsd64.grem.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180604004632.56ca6afa@bsd64.grem.de> User-Agent: Mutt/1.10.0 (2018-05-17) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2018 11:07:12 -0000 On Mon, Jun 04, 2018 at 12:46:32AM +0200, Michael Gmelin wrote: > > > On Sun, 3 Jun 2018 23:53:40 +0300 > Konstantin Belousov wrote: > > > On Sun, Jun 03, 2018 at 09:50:20PM +0200, Michael Gmelin wrote: > > > > > > > > > On Sun, 3 Jun 2018 18:04:23 +0300 > > > Konstantin Belousov wrote: > > > > > > > On Sun, Jun 03, 2018 at 04:55:00PM +0200, Michael Gmelin wrote: > > > > > > > > > > > > > > > On Sun, 3 Jun 2018 16:21:10 +0300 > > > > > Konstantin Belousov wrote: > > > > > > > > > > > On Sun, Jun 03, 2018 at 02:48:40PM +0200, Michael Gmelin > > > > > > wrote: > > > > > > > Hi, > > > > > > > > > > > > > > After upgrading CURRENT to r333992 (from something at least > > > > > > > a year old, quite some changes in mp_machdep.c since), this > > > > > > > machine crashes on boot: > > > > > > > > > > > > > > Copyright (c) 1992-2018 The FreeBSD Project. > > > > > > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, > > > > > > > 1992, 1993, 1994 The Regents of the University of > > > > > > > California. All rights reserved. FreeBSD is a registered > > > > > > > trademark of The FreeBSD Foundation. FreeBSD 12.0-CURRENT > > > > > > > #1 r333992: Tue May 22 00:31:04 CEST 2018 > > > > > > > root@flimsy:/usr/obj/usr/src/amd64.amd64/sys/flimsy amd64 > > > > > > > FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) > > > > > > > (based on LLVM 6.0.0) WARNING: WITNESS option enabled, > > > > > > > expect reduced performance. VT(vga): resolution 640x480 > > > > > > > CPU: Intel(R) Celeron(R) 2955U @ 1.40GHz (1396.80-MHz > > > > > > > K8-class CPU) Origin="GenuineIntel" Id=0x40651 > > > > > > > Family=0x6 Model=0x45 Stepping=1 > > > > > > > Features=0xbfebfbff > > > > > > CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > > > > > > > Features2=0x4ddaebbf > > > > > > xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,TSCDLT,XSAVE,OSXSAVE,RDRAND> > > > > > > > AMD Features=0x2c100800 AMD > > > > > > > Features2=0x21 Structured Extended > > > > > > > Features=0x2603 XSAVE > > > > > > > Features=0x1 VT-x: (disabled in BIOS) > > > > > > > PAT,HLT,MTF,PAUSE,EPT,UG,VPID TSC: P-state invariant, > > > > > > > performance statistics real memory = 4301258752 (4102 MB) > > > > > > > avail memory = 1907572736 (1819 MB) Event timer "LAPIC" > > > > > > > quality 600 ACPI APIC Table: > > > > > > What does this mean ? Did you flashed coreboot ? > > > > > > > > > > This machine comes with it by default (my model was delivered > > > > > with SeaBIOS 20131018_145217-build121-m2). So I didn't flash > > > > > anything (didn't feel like bricking it). > > > > > > > > > > > > > > > > > > kernel trap 12 with interrupts disabled > > > > > > > > > > > > > > Fatal trap 12: page fault while in kernel mode > > > > > > > cpuid = 0; apic id = 00 > > > > > > > fault virtual address = 0xfffff80001000000 > > > > > > > fault code = supervisor write data, protection > > > > > > > violation instruction pointer = 0x20:Oxffffffff8102955f > > > > > > > stack pointer = 0x28:0xffffffff82a79be0 > > > > > > > frame pointer = 0x28:0xffffffff82a79c10 > > > > > > > code segment = base Ox0, limit Oxfffff, type > > > > > > > Ox1b = DPL 0, pres 1, long 1, def32 0, gran > > > > > > > 1 processor eflags = resume, IOPL = 0 > > > > > > > current process = 0 () > > > > > > > [ thread pid 0 tid 0 ] > > > > > > > Stopped at native_start_all_aps+0x08f: movq > > > > > > > %rax,(%rsi) > > > > > > Look up the source line number for this address. > > > > > > > > > > > > > > > > I guess that's sys/amd64/amd64/support.S line 854 (in rdmsr), > > > > > called by native_start_all_aps. Any additional hints how I can > > > > > track it down? > > > > Why did you decided that this is rdmsr_safe() ? First, > > > > native_start_all_aps() does not call rdmsr, second the ddb > > > > report clearly indicates that the fault occured acessing DMAP in > > > > native_start_all_aps(). > > > > > > > > Just look up the source line by the address > > > > native_start_all_aps+0x08f. > > > > > > Okay, according to kgbd this should be here: > > > > > > https://svnweb.freebsd.org/base/head/sys/amd64/amd64/mp_machdep.c?revision=333368&view=markup#l369 > > > > > > 364 > > > 365 /* Create the initial 1GB replicated page tables */ > > > 366 for (i = 0; i < 512; i++) { > > > 367 /* Each slot of the level 4 pages points to the same > > > level 3 page */ 368 pt4[i] = > > > (u_int64_t)(uintptr_t)(mptramp_pagetables + PAGE_SIZE); 369 > > > pt4[i] |= PG_V | PG_RW | PG_U; 370 > > > 371 /* Each slot of the level 3 pages points to the same > > > level 2 page */ 372 pt3[i] = > > > (u_int64_t)(uintptr_t)(mptramp_pagetables + (2 * PAGE_SIZE)); > > > 373 pt3[i] |= PG_V | PG_RW | PG_U; 374 > > > 375 /* The level 2 page slots are mapped with 2MB pages > > > for 1GB. */ 376 pt2[i] = i * (2 * 1024 * 1024); > > > 377 pt2[i] |= PG_V | PG_RW | PG_PS | PG_U; > > > 378 } > > > > > > -m > > You have fault on write due to read-only mapping of the portion of > > the direct map, which maps the kernel text. It is consistent with > > the faulting address. It is not clear if it is something new on > > your machine, or before the kernel text was silently corrupted, since > > ro protection is somewhat recent. > > > > It seems that mp_bootaddress() selected the bad place for the > > bootstrap page tables. Even more, we do not include the kernel text > > into the physmem[] array, so it is not clear how did it happen. This > > code was also changed recently. > > > > Can you add the print of the physmap[] array somewhere before the > > panic, to see what is the kernel idea of the available memory ? It > > should be already done if you have serial console and set > > debug.late_console tunable to 0. > > This is a sad little machine without any kind of serial console. > > Physmap looks like this after calling getmemsize(): > > [0]: 0x10000 > [1]: 0x30000 > [2]: 0x40000 > [3]: 0x9e000 > [4]: 0x100000 > [5]: 0xf00000 > [6]: 0x1003000 > [7]: 0x7bf7a000 > > Physical memory chunks logged in cpu_startup are: > > 0x0000000000010000 - 0x000000000002ffff, 141072 bytes (32 pages) > 0x0000000000040000 - 0x000000000009dfff, 385024 bytes (94 pages) These two chunks reports are consistent with the physmap[0-1, 2-3]. > 0x0000000000100000 - 0x00000000001fffff, 1048576 bytes (256 pages) > 0x0000000002c00000 - 0x0000000075467fff, 1921417216 bytes (469096 pages) > 0x0000000100000000 - 0x00000001005e7fff, 6193152 bytes (1512 pages) But these three looks completely unrelated to the rest of the physmap, perhaps except the physmap[4]. We allocate boot pages from the top of the last physmap chunk, but I am certain that we do not consume that much memory for boot to make physmap[7] from the last reported address. Are you sure that there are no typos in the values above ? > > -m > > > > > > > > > p.s. This machine uses quirks in biosmem.c, see > > > > > > Type '?' for a list of command, 'help' for more detailed > > > help. > > > OK biosmem > > > bios_basemem: 0x9e400 > > > bios_extmem: 0x3ff00000 > > > memtop: 0x3c000000 > > > high_heap_base: 0x3c000000 > > > high_heap_size: 0x4000000 > > > bios_quirks: 0x01 BQ_DISTRUST_820_EXTMEM > > > b_bios_probed: 0x0a B_BASEMEM_12 B_EXTMEM_E801 > > > > > > -- > > > Michael Gmelin > > > > > > -- > > > Michael Gmelin > > > > -- > Michael Gmelin From owner-freebsd-current@freebsd.org Mon Jun 4 11:48:18 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CA2F3FD06C9 for ; Mon, 4 Jun 2018 11:48:17 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from CAN01-TO1-obe.outbound.protection.outlook.com (mail-eopbgr670068.outbound.protection.outlook.com [40.107.67.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT TLS CA 4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5AFAB8251A for ; Mon, 4 Jun 2018 11:48:17 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from YTOPR0101MB0953.CANPRD01.PROD.OUTLOOK.COM (52.132.44.24) by YTOPR0101MB0841.CANPRD01.PROD.OUTLOOK.COM (52.132.48.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.820.11; Mon, 4 Jun 2018 11:48:15 +0000 Received: from YTOPR0101MB0953.CANPRD01.PROD.OUTLOOK.COM ([fe80::a860:9237:2e9f:f87f]) by YTOPR0101MB0953.CANPRD01.PROD.OUTLOOK.COM ([fe80::a860:9237:2e9f:f87f%3]) with mapi id 15.20.0820.015; Mon, 4 Jun 2018 11:48:15 +0000 From: Rick Macklem To: Matthew Macy , Theron CC: "freebsd-current@freebsd.org" Subject: Re: how to deal with variable set but not used warnings? Thread-Topic: how to deal with variable set but not used warnings? Thread-Index: AQHT+4Ei+kHu8bdJXk68BDSBUTlIlaRPDeQAgAACBICAAAD8gIAA6p4/ Date: Mon, 4 Jun 2018 11:48:15 +0000 Message-ID: References: , In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=rmacklem@uoguelph.ca; x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; YTOPR0101MB0841; 7:+yAWtvafW+s62xYBTbBdJqrbC19Peve4sRbcXFe+BEuxRScDV1J2EHDgdqLs1hE5e7sK8NwfBCrDpOQdj6S5Cm+x7AxlKROv/qIRuoA9Mm5ygOz964XVkLqd5kcRdkqmRmTqolBSqUKH622ek+Ft8lSb48c7m4fYZyblRe4KSyztfagcJvLr5/C0EsU3lZ92Z4JE1/q7/+Nq3EDPmX/AJ5XkDVYOc8/jUP7I5Rn0bBqQ+bizoWt7tHAL7GQEsy6i x-ms-exchange-antispam-srfa-diagnostics: SOS; x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(8989080)(5600026)(4534165)(4627221)(201703031133081)(201702281549075)(8990040)(2017052603328)(7153060)(7193020); SRVR:YTOPR0101MB0841; x-ms-traffictypediagnostic: YTOPR0101MB0841: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(22074186197030)(85827821059158)(183786458502308)(75325880899374); x-ms-exchange-senderadcheck: 1 x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(3002001)(3231254)(944501410)(52105095)(93006095)(93001095)(10201501046)(149027)(150027)(6041310)(201703131423095)(201702281529075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(20161123562045)(20161123564045)(20161123560045)(6072148)(201708071742011)(7699016); SRVR:YTOPR0101MB0841; BCL:0; PCL:0; RULEID:; SRVR:YTOPR0101MB0841; x-forefront-prvs: 069373DFB6 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(39380400002)(376002)(346002)(366004)(396003)(199004)(189003)(6506007)(186003)(102836004)(97736004)(11346002)(966005)(316002)(786003)(446003)(26005)(110136005)(2906002)(478600001)(55016002)(4326008)(33656002)(229853002)(68736007)(3280700002)(3660700001)(8936002)(19625735003)(476003)(6306002)(7696005)(8676002)(76176011)(74482002)(105586002)(99286004)(6436002)(106356001)(93886005)(74316002)(25786009)(2900100001)(14454004)(81156014)(81166006)(53936002)(86362001)(5250100002)(59450400001)(9686003)(486006)(6246003)(39060400002)(5660300001)(305945005); DIR:OUT; SFP:1101; SCL:1; SRVR:YTOPR0101MB0841; H:YTOPR0101MB0953.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: uoguelph.ca does not designate permitted sender hosts) x-microsoft-antispam-message-info: 68EJ12KHdqPPM0W2C0erkIm3DpC1fiAbI6gd+VgYjQWRB6dGP3UAiVuZDImR8f/OZR92D0/yfqygTQI5SHxfxgEOUHiIEK4/jD2C+4/qtpirHvLha5gltaXp3rvd425XrOMUyFUINRcJrMCStgiGUqZOPJfmDt7sw5CkDV+w8XcsQV5LyFoy+PikF47bKBXM spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-MS-Office365-Filtering-Correlation-Id: 9d0f86db-5d12-4b42-e1c9-08d5ca110f0b X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-Network-Message-Id: 9d0f86db-5d12-4b42-e1c9-08d5ca110f0b X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Jun 2018 11:48:15.8172 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTOPR0101MB0841 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2018 11:48:18 -0000 Matthew Macy wrote: >On Sun, Jun 3, 2018 at 2:40 PM, Theron wrote: >>> 4. Disable the stupid warning in the Makefile / build system. If you do= n't >>> care, and there's a good reason for what you are doing (sounds like the= re >>> is), better to just disable the warning as so much useless noise. >>> >>> Warner >>> _______________________________________________ >>> freebsd-current@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" >> >> Or possibly, alongside a comment as in (3), use one of these: >> 5 - Disable warning pragma - >> http://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Pragmas.html >> 6 - Use __attribute__((unused)) - > https://gcc.gnu.org/onlinedocs/gcc/Common-Variable-Attributes.html#Common= -Variable-Attributes > > >There is already an __unused alias for #6. It's what I've used to >annotate variables that are only used by INVARIANTS builds. It >legitimately finds a bunch of dead code. However, 90+% of the >instances of the warning are not interesting. Ok. I didn't realize that __unused would work for this case of "set but not= used" but I just tried it on the older gcc48 I have lying around and it worked. (clang doesn't seem to warn or care about these cases.) I may use this, since I avoid messing with the make files like the plague. Thanks, rick From owner-freebsd-current@freebsd.org Mon Jun 4 12:25:12 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 44E68FDB498 for ; Mon, 4 Jun 2018 12:25:12 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from dec.sakura.ne.jp (dec.sakura.ne.jp [210.188.226.8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7E235845B9; Mon, 4 Jun 2018 12:25:11 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from fortune.joker.local (124-18-70-98.dz.commufa.jp [124.18.70.98]) (authenticated bits=0) by dec.sakura.ne.jp (8.15.2/8.15.2/[SAKURA-WEB]/20080708) with ESMTPA id w54CP6Bq087595; Mon, 4 Jun 2018 21:25:06 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Mon, 4 Jun 2018 21:25:06 +0900 From: Tomoaki AOKI To: Mateusz Guzik Cc: FreeBSD Current , alexvpetrov@gmail.com, Mateusz Guzik , Alexey Dokuchaev , ler@freebsd.org Subject: Re: Error build nvidia-driver with r334555 Message-Id: <20180604212506.819f91b9f7954a6063c66a32@dec.sakura.ne.jp> In-Reply-To: References: <83fec8d8-699f-e86c-9884-9d8698a86a91@gmail.com> <20180603214222.953748e1eb7a0b39e11214ae@dec.sakura.ne.jp> Reply-To: junchoon@dec.sakura.ne.jp Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd11.1) Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="Multipart=_Mon__4_Jun_2018_21_25_06_+0900_gPC_eyWaOYs1M.i7" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2018 12:25:12 -0000 This is a multi-part message in MIME format. --Multipart=_Mon__4_Jun_2018_21_25_06_+0900_gPC_eyWaOYs1M.i7 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Sun, 3 Jun 2018 15:20:24 +0200 Mateusz Guzik wrote: > On Sun, Jun 3, 2018 at 2:42 PM, Tomoaki AOKI > wrote: > > > This is caused by r334533 and/or r334534 (memset-related changes). > > sysutils/lsof is also affected. > > > > You should revert r334533 and r334534 temporarily until nvidia-driver > > support this change. > > > > CC'ing the revision author and maintainers of both ports. > > > > > Support in what sense? The error message clearly indicates a bug in the > driver I meant "need some work to be built with r334533 (and r334534), including fix for newly-became-prominent bug(s), because both x11/nvidia-driver and sysutils/lsof were built OK before r334533. Now understood that 3rd param SHALL be the size of destination "value", NOT the size of destination "pointer". > (also trivially fixable). Is there a problem adding a patch to files/? Built and worked fine. Thanks! Fix for sysutils/lsof is already committed by Larry as r471495. Thanks, Larry! As x11/nvidia-driver is the master port for legacy drivers, and legacy drivers (nvidia-driver-304 and nvidia-driver-340 ATM) has different src directory layout, it needs some cludge in Makefile. See attached (edited) Makefile. (Not a diff.) And at the same time, your patch needs some fix (filename part only, though). Attached extra-patch-* must be copied into files/ dir. *extra-patch-src_nvidia__subr.c is the fixed one for legacy driver. extra-patch-src_nvidia_nvidia__subr.c contains your original patch. Note that legacy drivers are only build-tested. Sorry for delay! Regards. > > diff -ru src.orig/nvidia/nvidia_subr.c src/nvidia/nvidia_subr.c > --- src.orig/nvidia/nvidia_subr.c 2018-06-03 13:19:56.490480000 +0000 > +++ src/nvidia/nvidia_subr.c 2018-06-03 13:21:15.289344000 +0000 > @@ -364,7 +364,7 @@ > } > > ci = args; > - memset(ci, 0, sizeof(ci)); > + memset(ci, 0, sizeof(*ci)); > > for (i = 0; i < NV_MAX_DEVICES; i++) { > sc = devclass_get_softc(nvidia_devclass, i); > > > As for lsof: > --- dlsof.h.orig 2018-06-03 13:16:14.712701000 +0000 > +++ dlsof.h 2018-06-03 13:17:15.042655000 +0000 > @@ -489,6 +489,12 @@ > # endif /* FREEBSDV>=2020 */ > > #undef bzero /* avoid _KERNEL conflict */ > +#undef bcmp > +#undef bcopy > +#undef memcmp > +#undef memmove > +#undef memcpy > +#undef memset > #include > > -- > Mateusz Guzik > _______________________________________________ > 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" > -- Tomoaki AOKI --Multipart=_Mon__4_Jun_2018_21_25_06_+0900_gPC_eyWaOYs1M.i7 Content-Type: application/octet-stream; name="Makefile" Content-Disposition: attachment; filename="Makefile" Content-Transfer-Encoding: base64 IyBDcmVhdGVkIGJ5OiBTdGlqbiBIb29wIDxzdGlqbkB3aW4udHVlLm5sPgojICRGcmVlQlNEOiBo ZWFkL3gxMS9udmlkaWEtZHJpdmVyL01ha2VmaWxlIDQ3MDk3MiAyMDE4LTA1LTI3IDA5OjE5OjUx WiBkYW5mZSAkCiMKIyBGb3IgdGhvc2Ugd29uZGVyaW5nIHdoeSB0aGlzIHBvcnQgaXMgbm90IHVu ZGVyIGB4MTEtZHJpdmVycycgY2F0ZWdvcnksCiMgaGF2ZSBhIGxvb2sgYXQgaHR0cHM6Ly9idWdz LmZyZWVic2Qub3JnL2J1Z3ppbGxhL3Nob3dfYnVnLmNnaT9pZD0xMjE5MzAuCiMKIyBTdGFydGlu ZyB3aXRoIHZlcnNpb24gMS4wLTc2NjcsIE5WaWRpYSBoYXMgZHJvcHBlZCBzdXBwb3J0IGZvciBu dW1lcm91cwojICJsZWdhY3kiIEdQVXMuICBDb25zdWx0IE5WaWRpYSBSRUFETUUgKHRoZSBBcHBl bmRpeCkgdG8gZmluZCBvdXQgd2hldGhlcgojIHlvdSBuZWVkIHRvIHVzZSBsZWdhY3kgZHJpdmVy IHZlcnNpb24gYW5kIGluc3RhbGwgb25lIG9mIGNvcnJlc3BvbmRpbmcKIyBzbGF2ZSBwb3J0cyBp bnN0ZWFkIChgeDExL252aWRpYS1kcml2ZXItMzQwJyBvciBgeDExL252aWRpYS1kcml2ZXItMzA0 JykuCgpQT1JUTkFNRT0JbnZpZGlhLWRyaXZlcgpESVNUVkVSU0lPTj89CTM5MC41OQojIEFsd2F5 cyB0cnkgdG8gc2V0IFBPUlRSRVZJU0lPTiBhcyBpdCBjYW4gYmUgb3ZlcnJpZGRlbiBieSB0aGUg c2xhdmUgcG9ydHMKUE9SVFJFVklTSU9OPz0JMApDQVRFR09SSUVTPQl4MTEKTUFTVEVSX1NJVEVT PQlOVklESUEvWEZyZWU4Ni9GcmVlQlNELSR7QVJDSF9TVUZYfS8ke0RJU1RWRVJTSU9OfQpESVNU TkFNRT0JTlZJRElBLUZyZWVCU0QtJHtBUkNIX1NVRlh9LSR7RElTVFZFUlNJT059CgpNQUlOVEFJ TkVSPQlkYW5mZUBGcmVlQlNELm9yZwpDT01NRU5UPQlOVmlkaWEgZ3JhcGhpY3MgY2FyZCBiaW5h cnkgZHJpdmVycyBmb3IgaGFyZHdhcmUgT3BlbkdMIHJlbmRlcmluZwoKTElDRU5TRT0JTlZJRElB CkxJQ0VOU0VfTkFNRT0JTGljZW5zZSBGb3IgQ3VzdG9tZXIgVXNlIG9mIE5WSURJQSBTb2Z0d2Fy ZQpMSUNFTlNFX0ZJTEU9CSR7V1JLU1JDfS9kb2MvbGljZW5zZS50eHQKTElDRU5TRV9QRVJNUz0J ZGlzdC1taXJyb3Igbm8tZGlzdC1zZWxsIHBrZy1taXJyb3Igbm8tcGtnLXNlbGwgYXV0by1hY2Nl cHQKCk9OTFlfRk9SX0FSQ0hTPQlpMzg2IGFtZDY0CgpBUkNIX1NVRlg9CXg4NiR7QVJDSDpTL2kz ODYvLzpTL2FtZC9fL30KVVNFUz0JCWttb2QgdWlkZml4ClVTRV9YT1JHPQl4MTEgeG9yZy1zZXJ2 ZXIgeGV4dApVU0VfR0w9CQlnbApVU0VfTERDT05GSUc9CXllcwoKIyBOVklESUFfUk9PVCBpcyBu b3Qgc2V0IGluIHNyYy9NYWtlZmlsZSwgd2hpY2ggcmVzdWx0cyBpbiBib2d1cyAtSS9zcmMKIyBw YXNzZWQgdG8gY29tcGlsZXIgYW5kIGJyb2tlbiBidWlsZCBvbiBIRUFEIHNpbmNlIHIyMjEzMjAg d2hlbiBvcHRpb24KIyAtV21pc3NpbmctaW5jbHVkZS1kaXJzIHdhcyBhZGRlZCBmb3Iga2VybmVs IHNvdXJjZXMuICBVbnRpbCBwcm9wZXJseQojIGZpeGVkIHVwc3RyZWFtIChhY3Jvc3MgYWxsIHZl cnNpb25zLCBpbmNsdWRpbmcgbGVnYWN5IG9uZXMpLCB1c2UgdGhpcwojIGhhY2sgYmVsb3cgdG8g dW5pdmVyc2FsbHkgc2V0IE5WSURJQV9ST09ULiAgQWxzbyBwcm92aWRlIFgxMUJBU0UgdmFsdWUK IyBzaW5jZSBpdCBpcyBzdGlsbCB1c2VkIGJ5IGxlZ2FjeSBkcml2ZXJzLgpNQUtFX0VOVj0JTlZJ RElBX1JPT1Q9JHtXUktTUkN9IFgxMUJBU0U9JHtMT0NBTEJBU0V9ClNVQl9GSUxFUz0JcGtnLWRl aW5zdGFsbCBwa2ctaW5zdGFsbCBwa2ctbWVzc2FnZSBudmlkaWEuY29uZgpET0NTRElSPQkke1BS RUZJWH0vc2hhcmUvZG9jL05WSURJQV9HTFgtMS4wCk1PRFVMRVNESVI9CWxpYi94b3JnL21vZHVs ZXMKUE9SVERPQ1M9CSoKCiMgTlZWRVJTSU9OIGlzIGZsb2F0IHNpbmNlIHIzNzIwNjUgKGludGVn ZXIgdmFsdWVzIGJlY29tZSBsZXNzIHJlYWRhYmxlCiMgYWZ0ZXIgbWlub3IgdmVyc2lvbiBjb3Vs ZCBvY2N1cHkgdGhyZWUgZGlnaXRzKQouaWYgJHtESVNUVkVSU0lPTjpDL1swLTldKy8vZ30gPT0g Ii4uIgkJIyBtYWpvci5taW5vci51cGRhdGUKTlZWRVJTSU9OPQkke0RJU1RWRVJTSU9OOlMvLi8u MC86Un0ke0RJU1RWRVJTSU9OOkV9Ci5lbHNlCQkJCQkJIyBtYWpvci5taW5vcgouICBpZiAke0RJ U1RWRVJTSU9OOkV9IDwgMTAwCk5WVkVSU0lPTj0JJHtESVNUVkVSU0lPTjpTLy4vLjAvfQkJIyBh bGxvdyBtaW5vciA+IDk5Ci4gIGVsc2UKTlZWRVJTSU9OPQkke0RJU1RWRVJTSU9OfQouICBlbmRp ZgouZW5kaWYKCi5pZiAke05WVkVSU0lPTn0gPj0gMzMxLjAxMwpTVUJfTElTVCs9CU5WR0w9IiIK LmVsc2UKU1VCX0xJU1QrPQlOVkdMPSJcIyAiCi5lbmRpZgoKLmlmICR7TlZWRVJTSU9OfSA8IDM1 NS4wMDYKRVhUUkFfUEFUQ0hFUz0JJHtGSUxFU0RJUn0vZXh0cmEtcGF0Y2gtc3JjLU1ha2VmaWxl IFwKCQkke0ZJTEVTRElSfS9leHRyYS1wYXRjaC1zcmMtbnYtZnJlZWJzZC5oIFwKCQkke0ZJTEVT RElSfS9leHRyYS1wYXRjaC1zcmMtbnYtbWlzYy5oIFwKCQkke0ZJTEVTRElSfS9leHRyYS1wYXRj aC1zcmNfbnZpZGlhX19zdWJyLmMKTlZTUkM9CQkuCi5lbHNlCkVYVFJBX1BBVENIRVM9CSR7RklM RVNESVJ9L2V4dHJhLXBhdGNoLXNyY19udmlkaWFfTWFrZWZpbGUgXAoJCSR7RklMRVNESVJ9L2V4 dHJhLXBhdGNoLXNyY19udmlkaWFfbnYtZnJlZWJzZC5oIFwKCQkke0ZJTEVTRElSfS9leHRyYS1w YXRjaC1zcmNfbnZpZGlhX252LW1pc2MuaCBcCgkJJHtGSUxFU0RJUn0vZXh0cmEtcGF0Y2gtc3Jj X252aWRpYV9udmlkaWFfX3N1YnIuYwpOVlNSQz0JCW52aWRpYQouZW5kaWYKLmlmICR7TlZWRVJT SU9OfSA+PSAzNTguMDA5CiMgSW5pdGlhbGl6ZSBtZW1vcnkgYWxsb2NhdGlvbnMgdG8gYXZvaWQg c3B1cmlvdXMgImxvY2sgcmUtaW5pdGlhbGl6YXRpb24iCiMgZXJyb3JzLiAgQSBsaXR0bGUgbW9y ZSBkZXRhaWwgY2FuIGJlIGZvdW5kIGluIGJ1ZyAyMDEzNDAgc3RhcnRpbmcgYXJvdW5kCiMgY29t bWVudCAjNTAuCkVYVFJBX1BBVENIRVMrPQkke0ZJTEVTRElSfS9leHRyYS1wYXRjaC1zcmNfbnZp ZGlhLW1vZGVzZXRfbnZpZGlhLW1vZGVzZXQtZnJlZWJzZC5jCi5lbmRpZgoKT1BUSU9OU19ERUZJ TkU9CUFDUElfUE0gTElOVVggV0JJTlZEIERPQ1MKT1BUSU9OU19ERUZJTkVfaTM4Nj0JUEFFCk9Q VElPTlNfREVGQVVMVD0JTElOVVgKCkFDUElfUE1fREVTQz0JCUFDUEkgUG93ZXIgTWFuYWdlbWVu dCBzdXBwb3J0CkxJTlVYX0RFU0M9CQlMaW51eCBjb21wYXRpYmlsaXR5IHN1cHBvcnQKUEFFX0RF U0M9CQlQaHlzaWNhbCBBZGRyZXNzIEV4dGVuc2lvbnMgc3VwcG9ydApXQklOVkRfREVTQz0JCUZs dXNoIENQVSBjYWNoZXMgZGlyZWN0bHkgd2l0aCBXQklOVkQKCi5pZiAke05WVkVSU0lPTn0gPCAz MTAuMDE0Ck9QVElPTlNfREVGSU5FKz0JRlJFRUJTRF9BR1AKRlJFRUJTRF9BR1BfREVTQz0JVXNl IEZyZWVCU0QgQUdQIEdBUlQgZHJpdmVyCi5lbmRpZgoKUExJU1RfU1VCKz0JTElOVVhCQVNFPSR7 TElOVVhCQVNFfSBTSExJQl9WRVJTSU9OPSR7UE9SVFZFUlNJT059IFwKCQlNT0RVTEVTRElSPSR7 TU9EVUxFU0RJUn0KCi5pbmNsdWRlIDxic2QucG9ydC5vcHRpb25zLm1rPgoKLmlmICR7UE9SVF9P UFRJT05TOk1MSU5VWH0KQ09ORkxJQ1RTX0lOU1RBTEw9CWxpbnV4Wy1fXWRyaS1bMC05XSogbGlu dXgtZjEwLWRyaS1bMC05XSoKVVNFUys9CQlsaW51eApVU0VfTElOVVg9CWJhc2U6YnVpbGQscnVu IHhvcmdsaWJzClBMSVNUX1NVQis9CUxJTlVYPSIiCi5lbHNlClBMSVNUX1NVQis9CUxJTlVYPSJA Y29tbWVudCAiCiMgUHJvcGFnYXRlIFdJVEhPVVRfTElOVVggdmFyaWFibGUgZG93biB0byBpbm5l ciBNYWtlZmlsZXMKTUFLRV9FTlYrPQlXSVRIT1VUX0xJTlVYPXllcwouZW5kaWYKCnBvc3QtcGF0 Y2g6IC5TSUxFTlQKIyBXZSBzaG91bGQgc3VwcG9ydCAtQ1VSUkVOVDoga2lsbCB0aGUgY2hlY2sK CSR7UkVJTlBMQUNFX0NNRH0gLWUgJzI0LDI2ZCcgJHtXUktTUkN9L3NyYy8ke05WU1JDfS9udi1m cmVlYnNkLmgKIyBBZGp1c3QgTGludXggaGVhZGVycyAjaW5jbHVkZSdzIGFmdGVyIEZyZWVCU0Qg c3JjIHIyNDYwODUKCSR7UkVJTlBMQUNFX0NNRH0gLUUgJy8jaW5jbHVkZSAibWFjaGluZVwvXC5c LlwvbGludXgoMzIpP1wvbGludXguaCIvIFwKCQl7IHggOyBzLy4qLyNpbmNsdWRlICJtYWNoaW5l XC8uLlwvLi5cL2NvbXBhdFwvbGludXhcL2xpbnV4X2lvY3RsLmgiLyA7IEggOyB4IDsgfScgXAoJ CQkke1dSS1NSQ30vc3JjLyR7TlZTUkN9L252aWRpYV9saW51eC5jCiMgQWRqdXN0IGB2bV9vYmpl Y3QnIGxvY2tpbmcgYWZ0ZXIgRnJlZUJTRCBzcmMgcjI0ODA4NAoJJHtSRUlOUExBQ0VfQ01EfSAt ZSAnLyNpbmNsdWRlIDx2bVwvdm1fb2JqZWN0Lmg+LyBcCgkJeyB4IDsgcy8uKi8jaW5jbHVkZSA8 c3lzXC9yd2xvY2suaD4vIDsgRyA7IH0nIFwKCQkJJHtXUktTUkN9L3NyYy8ke05WU1JDfS9udi1m cmVlYnNkLmgKCSR7UkVJTlBMQUNFX0NNRH0gLUUgJ3MvKFZNX09CSkVDVF8pKFVOKT8oTE9DSykv XDFXXDJcMy8nIFwKCQkke1dSS1NSQ30vc3JjLyR7TlZTUkN9L252aWRpYV9zdWJyLmMKIyBBZGp1 c3Qga21lbSg5KSBjYWxscyBhZnRlciBGcmVlQlNEIHNyYyByMjU0MDI1Ci5pZiAke05WVkVSU0lP Tn0gPCAzMzEuMDY3Cgkke1JFSU5QTEFDRV9DTUR9IC1lICcva21lbV8vcy9rZXJuZWxfbWFwL2tl cm5lbF9hcmVuYS8nIFwKCQkke1dSS1NSQ30vc3JjLyR7TlZTUkN9L252aWRpYV9zdWJyLmMKLmVu ZGlmCiMgQ2hhc2UgYHN5cy9jYXBhYmlsaXR5LmgnIHJlbmFtZSB0byBgc3lzL2NhcHNpY3VtLmgn IGluIEZyZWVCU0Qgc3JjIHIyNjMyMzIKCSR7UkVJTlBMQUNFX0NNRH0gLWUgJ3M6c3lzL2NhcGFi aWxpdHlcLmg6c3lzL2NhcHNpY3VtLmg6JyBcCgkJJHtXUktTUkN9L3NyYy8ke05WU1JDfS9udi1m cmVlYnNkLmgKLmlmICR7TlZWRVJTSU9OfSA+PSAzNTguMDA5Cgkke1JFSU5QTEFDRV9DTUR9IC1l ICdzOnN5cy9jYXBhYmlsaXR5XC5oOnN5cy9jYXBzaWN1bS5oOicgXAoJCSR7V1JLU1JDfS9zcmMv bnZpZGlhLW1vZGVzZXQvbnZpZGlhLW1vZGVzZXQtZnJlZWJzZC5jCi5lbmRpZgojIEZpeCBDVExG TEFHXyogdmFsdWVzIGZvciBTWVNDVExfQUREX1BST0MoKSBhZnRlciBGcmVlQlNEIHNyYyByMjcz Mzc3Cgkke1JFSU5QTEFDRV9DTUR9IC1lICcvU1lTQ1RMX0FERF9QUk9DLywvOy8gXAoJCXMvXltb OmJsYW5rOl1dKkNUTEZMQUdfUkQvQ1RMVFlQRV9TVFJJTkcgfCYvJyBcCgkJCSR7V1JLU1JDfS9z cmMvJHtOVlNSQ30vbnZpZGlhX3N5c2N0bC5jCiMgUmVwbGFjZSBgZF90aHJlYWRfdCcgKEZyZWVC U0QgNCBzdXBwb3J0IGNvbXBhdCBzaGltKSB3aXRoIGBzdHJ1Y3QgdGhyZWFkJwoJJHtSRUlOUExB Q0VfQ01EfSAtZSAncy9kX3RocmVhZF90L3N0cnVjdCB0aHJlYWQvJyBcCgkJJHtXUktTUkN9L3Ny Yy8ke05WU1JDfS9udmlkaWFfY3RsLmMgXAoJCSR7V1JLU1JDfS9zcmMvJHtOVlNSQ30vbnZpZGlh X2Rldi5jIFwKCQkke1dSS1NSQ30vc3JjLyR7TlZTUkN9L252aWRpYV9saW51eC5jCi5pZiAke05W VkVSU0lPTn0gPj0gMzU4LjAwOQoJJHtSRUlOUExBQ0VfQ01EfSAtZSAncy9kX3RocmVhZF90L3N0 cnVjdCB0aHJlYWQvJyBcCgkJJHtXUktTUkN9L3NyYy9udmlkaWEtbW9kZXNldC9udmlkaWEtbW9k ZXNldC1mcmVlYnNkLmMKLmVuZGlmCiMgUmVzcGVjdCBXSVRIT1VUX0xJTlVYIHNldHRpbmcKCSR7 UkVJTlBMQUNFX0NNRH0gLWUgJ3MvZXhpc3RzKFwvLiovJiBcJlwmICFkZWZpbmVkKFdJVEhPVVRf TElOVVgpLycgXAoJCSR7V1JLU1JDfS9saWIvTWFrZWZpbGUKIyBEbyBub3QgaW5zdGFsbCBWRFBB VSBsaWJyYXJpZXMgd2hpY2ggYXJlIHByb3ZpZGVkIGJ5IGBtdWx0aW1lZGlhL2xpYnZkcGF1Jwoj IHBvcnQgZm9yIGEgd2hpbGUgbm93Cgkke1JFSU5QTEFDRV9DTUR9IC1lICcvbGlidmRwYXVbWzpi bGFuazpdX11bXm5dL2QgOyBcCgkJcy9uYW1lIGxpYnZkcGF1LyZfbnZpZGlhLycgJHtXUktTUkN9 L2xpYi9NYWtlZmlsZQojIERvIG5vdCBidWlsZCBhbnkgYmluYXJpZXMgKG5hdGl2ZSBudmlkaWEt c2V0dGluZ3MgYW5kIG52aWRpYS14Y29uZmlnIGFyZQojIHByb3ZpZGVkIGJ5IGNvcnJlc3BvbmRp bmcgcG9ydHMpIGFuZCBtYW51YWwgcGFnZXMKCSR7UkVJTlBMQUNFX0NNRH0gLUUgJ3MvKGV4dGVu c2lvbikuKi9cMS8nICR7V1JLU1JDfS94MTEvTWFrZWZpbGUKCSR7UkVJTlBMQUNFX0NNRH0gLWUg Jy9iaW4vZCA7IC9tYW4vZCcgJHtXUktTUkN9L3gxMS9NYWtlZmlsZQojIEFsc28gZG8gbm90IGlu c3RhbGwgbGlibnZpZGlhLWd0ayogbGlicmFyaWVzIHdoaWNoIGFyZSBmb3IgbnZpZGlhLXNldHRp bmdzCi5pZiAke05WVkVSU0lPTn0gPj0gMzQ2LjAxNgoJJHtSRUlOUExBQ0VfQ01EfSAtZSAnL2xp Ym52aWRpYS1ndGsvZCcgJHtXUktTUkN9L2xpYi9NYWtlZmlsZQouZW5kaWYKIyBBZGp1c3QgaW5z dGFsbGF0aW9uIHBhdGggb2YgYSBjb25mbGljdGluZyBmaWxlIChzaGFyZWQgYmV0d2VlbgojIG52 aWRpYS1kcml2ZXIgYW5kIHhvcmctc2VydmVyKSB0byBlYXNlIHBhY2thZ2UgbWFuYWdlciB3b3Jr Cgkke1JFSU5QTEFDRV9DTUR9IC1lICcvTElCRElSL3M6eG9yZy9tb2R1bGVzL2V4dGVuc2lvbnM6 Ji8ubnZpZGlhOicgXAoJCSR7V1JLU1JDfS94MTEvZXh0ZW5zaW9uL01ha2VmaWxlCiMgRG8gbm90 IGV4ZWN1dGUgYWZ0ZXJpbnN0YWxsIHRhcmdldCAocHJldmVudCBhdXRvbWF0aWMgbW9kdWxlIHJl Z2lzdHJhdGlvbgojIGFuZCAic21hcnQiIGluc3RhbGxhdGlvbiBvZiBjb25mbGljdGluZyBmaWxl cyBoZXVyaXN0aWNzKQoJJHtSRUlOUExBQ0VfQ01EfSAtZSAncy9hZnRlcmluc3RhbGwvJl9kb250 ZXhlY3V0ZS8nICR7V1JLU1JDfS9NYWtlZmlsZQoJJHtSRUlOUExBQ0VfQ01EfSAtZSAncy9iZWZv cmVpbnN0YWxsLyZfZG9udGV4ZWN1dGUvJyBcCgkJJHtXUktTUkN9L2xpYi9NYWtlZmlsZSAke1dS S1NSQ30vc3JjLyR7TlZTUkN9L01ha2VmaWxlCiMgL3Vzci9zaGFyZS9udmlkaWEgcGF0aCBpcyBo YXJkY29kZWQgaW4gbGliR0wgYW5kIG52aWRpYS1zZXR0aW5ncywgYnV0IHdlCiMgd29uJ3QgYWRo ZXJlIHRvIHRoaXMgc3R1cGlkaXR5IGFuZCBpbnN0YWxsIG52aWRpYS1hcHBsaWNhdGlvbi1wcm9m aWxlcy0qCiMgZmlsZXMgYXMgcGFydCBvZiBkb2N1bWVudGF0aW9uCi5pZiAke05WVkVSU0lPTn0g Pj0gMzM0LjAxNgoJJHtSRUlOUExBQ0VfQ01EfSAtZSAncywvdXNyL3NoYXJlL252aWRpYSwke1NU QUdFRElSfSR7RE9DU0RJUn0sJyBcCgkJJHtXUktTUkN9L2xpYi9saWJHTC9NYWtlZmlsZSAke1dS S1NSQ30vZG9jL01ha2VmaWxlCi5lbmRpZgojIEZpbmFsbHksIHByb2Nlc3MgT1BUSU9OUwouaWYg JHtQT1JUX09QVElPTlM6TUZSRUVCU0RfQUdQfQoJJHtSRUlOUExBQ0VfQ01EfSAtRSAncy91bmRl ZiAoTlZfU1VQUE9SVF9PU19BR1ApL2RlZmluZSBcMS8nIFwKCQkke1dSS1NSQ30vc3JjLyR7TlZT UkN9L252LWZyZWVic2QuaAouZW5kaWYKLmlmICR7UE9SVF9PUFRJT05TOk1BQ1BJX1BNfQoJJHtS RUlOUExBQ0VfQ01EfSAtRSAncy91bmRlZiAoTlZfU1VQUE9SVF9BQ1BJX1BNKS9kZWZpbmUgXDEv JyBcCgkJJHtXUktTUkN9L3NyYy8ke05WU1JDfS9udi1mcmVlYnNkLmgKLmVuZGlmCi5pZiAhICR7 UE9SVF9PUFRJT05TOk1MSU5VWH0KCSR7UkVJTlBMQUNFX0NNRH0gLUUgJ3MvZGVmaW5lIChOVl9T VVBQT1JUX0xJTlVYX0NPTVBBVCkvdW5kZWYgXDEvJyBcCgkJJHtXUktTUkN9L3NyYy8ke05WU1JD fS9udi1mcmVlYnNkLmgKLiAgaWYgJHtOVlZFUlNJT059ID49IDM1OC4wMDkKCSR7UkVJTlBMQUNF X0NNRH0gLUUgJ3MvZGVmaW5lIChOVktNU19TVVBQT1JUX0xJTlVYX0NPTVBBVCkvdW5kZWYgXDEv JyBcCgkJJHtXUktTUkN9L3NyYy9udmlkaWEtbW9kZXNldC9udmlkaWEtbW9kZXNldC1mcmVlYnNk LmMKLiAgZW5kaWYKLmVuZGlmCi5pZiAke1BPUlRfT1BUSU9OUzpNUEFFfQoJJHtSRUlOUExBQ0Vf Q01EfSAtRSAncy91bmRlZiAoTlZfU1VQUE9SVF9QQUUpL2RlZmluZSBcMS8nIFwKCQkke1dSS1NS Q30vc3JjLyR7TlZTUkN9L252LWZyZWVic2QuaAouZW5kaWYKLmlmICR7UE9SVF9PUFRJT05TOk1X QklOVkR9Cgkke1JFSU5QTEFDRV9DTUR9IC1FICdzL3VuZGVmIChOVl9VU0VfV0JJTlZEKS9kZWZp bmUgXDEvJyBcCgkJJHtXUktTUkN9L3NyYy8ke05WU1JDfS9udi1mcmVlYnNkLmgKLmVuZGlmCiMg Q29uZGl0aW9uYWxseSBpbnN0YWxsIGRvY3VtZW50YXRpb24gKGJ1dCB5b3UgZ2VuZXJhbGx5IHdh bnQgaXQpCi5pZiAhICR7UE9SVF9PUFRJT05TOk1ET0NTfQoJJHtSRUlOUExBQ0VfQ01EfSAtRSAn cy8oeDExKS4qL1wxLyA7IC9kb2MvZCcgJHtXUktTUkN9L01ha2VmaWxlCi5lbmRpZgoKcHJlLWlu c3RhbGw6CglAJHtNS0RJUn0gJHtTVEFHRURJUn0ke1BSRUZJWH0vJHtNT0RVTEVTRElSfS9kcml2 ZXJzIFwKCQkke1NUQUdFRElSfSR7UFJFRklYfS8ke01PRFVMRVNESVJ9L2V4dGVuc2lvbnMKCnBv c3QtaW5zdGFsbDogLlNJTEVOVAoJJHtJTlNUQUxMX1NDUklQVH0gJHtXUktTUkN9L29iai9udmlk aWEtYnVnLXJlcG9ydC5zaCBcCgkJJHtTVEFHRURJUn0ke1BSRUZJWH0vYmluCiMgcGtnLXBsaXN0 IGlzIGFscmVhZHkgb3ZlcmJsb2F0ZWQsIHNvIHVzZSB0aGVzZSBoYWNrcyBpbnN0ZWFkIG9mIFBM SVNUX1NVQidzCi5pZiAke05WVkVSU0lPTn0gPj0gMzA0LjEyOCAmJiAke05WVkVSU0lPTn0gPCAz MTAuMDE5IHx8ICR7TlZWRVJTSU9OfSA+PSAzNjEuMDE2Cgkke1JFSU5QTEFDRV9DTUR9IC1FICcv bGlidmRwYXUoX3RyYWNlKT9cLnNvL2QnICR7VE1QUExJU1R9Ci5lbmRpZgouaWYgJHtOVlZFUlNJ T059ID49IDMxMC4wMTkKCSR7UkVJTlBMQUNFX0NNRH0gLWUgJy9saWJYdk1DTlZJRElBL2QnICR7 VE1QUExJU1R9Ci5lbHNlCSMgc29tZSBhcHBsaWNhdGlvbnMgbmVlZCB0aGlzIHN5bWxpbmsgKHNl ZSBQUiBwb3J0cy83Mjg3NykKCSR7TE59IC1zZiBsaWJYdk1DTlZJRElBLnNvLjEgXAoJCSR7U1RB R0VESVJ9JHtQUkVGSVh9L2xpYi9saWJYdk1DTlZJRElBX2R5bmFtaWMuc28uMQouZW5kaWYKLmlm ICR7TlZWRVJTSU9OfSA8IDMzMS4wMTMgfHwgJHtBUkNIfSA9PSBhbWQ2NCAmJiAke05WVkVSU0lP Tn0gPCAzMzQuMDE2Cgkke1JFSU5QTEFDRV9DTUR9IC1FICcvbGliKG52aWRpYS0pPyhFR0x8ZWds Y29yZXxHTEVTdnxnbHNpKS9kJyBcCgkJJHtUTVBQTElTVH0KLmVuZGlmCi5pZiAke05WVkVSU0lP Tn0gPCAzNTIuMDA5Cgkke1JFSU5QTEFDRV9DTUR9IC1FICcvKGxpYik/bnZpZGlhLShkZWJ1Z2R1 bXB8c21pfG1sKS9kJyAke1RNUFBMSVNUfQouZW5kaWYKLmlmICR7TlZWRVJTSU9OfSA8IDM1NS4w MDYKCSR7UkVJTlBMQUNFX0NNRH0gLUUgJy8obGliRUdMX252aWRpYXxHTGRpc3BhdGNofE9wZW5H TCkvZCcgJHtUTVBQTElTVH0KLmVsc2UKCSR7UkVJTlBMQUNFX0NNRH0gJ3MvbGliRUdMXC5zb1wu JHtQT1JUVkVSU0lPTn0vbGliRUdMLnNvLycgXAoJCSR7VE1QUExJU1R9Ci5lbmRpZgouaWYgJHtO VlZFUlNJT059IDwgMzU4LjAwOQoJJHtSRUlOUExBQ0VfQ01EfSAnL252aWRpYS1tb2Rlc2V0Lmtv L2QnICR7VE1QUExJU1R9Ci5lbmRpZgouaWYgJHtOVlZFUlNJT059ID49IDM2MS4wMjgKCSR7UkVJ TlBMQUNFX0NNRH0gLUUgJy8oRUdMX252aWRpYVwuc298R0xFU3ZbMTJdKF9DTSk/KFwuc29cLlsw LTldK1wuWzAtOV0rKSkkJC9kJyBcCgkJJHtUTVBQTElTVH0KLmVsc2UKCSR7UkVJTlBMQUNFX0NN RH0gLUUgJy9cL2xpYlwvbGliR0xFU3ZbMTJdKF9DTSk/KFwuc28pPyhfbnZpZGlhLnNvKFwuWzAt OV18XC5bMC05XStcLlswLTldKyk/KT8kJC9kIDsgXAoJCS9saWJFR0xfbnZpZGlhXC5zb1wuJHtQ T1JUVkVSU0lPTn0vZCcgJHtUTVBQTElTVH0KLmVuZGlmCiMgcmVuYW1lIGxpYkdMLnNvLCBsaWJF R0wuc28gYW5kIGxpYkdMRVN2Mi5zbwoJJHtNVn0gLWYgJHtTVEFHRURJUn0ke1BSRUZJWH0vbGli L2xpYkdMLnNvIFwKCQkke1NUQUdFRElSfSR7UFJFRklYfS9saWIvbGliR0wtTlZJRElBLnNvCgkk e01WfSAtZiAke1NUQUdFRElSfSR7UFJFRklYfS9saWIvbGliR0wuc28uMSBcCgkJJHtTVEFHRURJ Un0ke1BSRUZJWH0vbGliL2xpYkdMLU5WSURJQS5zby4xCi5pZiAke05WVkVSU0lPTn0gPj0gMzMx LjAxMwoJJHtNVn0gLWYgJHtTVEFHRURJUn0ke1BSRUZJWH0vbGliL2xpYkVHTC5zbyBcCgkJJHtT VEFHRURJUn0ke1BSRUZJWH0vbGliL2xpYkVHTC1OVklESUEuc28KCSR7TVZ9IC1mICR7U1RBR0VE SVJ9JHtQUkVGSVh9L2xpYi9saWJFR0wuc28uMSBcCgkJJHtTVEFHRURJUn0ke1BSRUZJWH0vbGli L2xpYkVHTC1OVklESUEuc28uMQoJJHtNVn0gLWYgJHtTVEFHRURJUn0ke1BSRUZJWH0vbGliL2xp YkdMRVN2Mi5zbyBcCgkJJHtTVEFHRURJUn0ke1BSRUZJWH0vbGliL2xpYkdMRVN2Mi1OVklESUEu c28KCSR7TVZ9IC1mICR7U1RBR0VESVJ9JHtQUkVGSVh9L2xpYi9saWJHTEVTdjIuc28uMiBcCgkJ JHtTVEFHRURJUn0ke1BSRUZJWH0vbGliL2xpYkdMRVN2Mi1OVklESUEuc28uMgouZW5kaWYKCUAk e01LRElSfSAke1NUQUdFRElSfSR7UFJFRklYfS9ldGMvbGlibWFwLmQvCgkke0lOU1RBTExfREFU QX0gJHtXUktESVJ9L252aWRpYS5jb25mIFwKCQkke1NUQUdFRElSfSR7UFJFRklYfS9ldGMvbGli bWFwLmQvCgojIFRhcmdldCBiZWxvdyBjYW4gYmUgdXNlZCBpbnN0ZWFkIG9mIHN0YW5kYXJkIGBt YWtlc3VtJyB0byBjb3JyZWN0bHkKIyB1cGRhdGUgZGlzdGluZm8gKGkuZS4sIGtlZXBpbmcgb3Ro ZXIgZHJpdmVyIHZlcnNpb24gZW50cmllcyBpbnRhY3QpCi5pZiAkey5UQVJHRVRTOk11cGRhdGUt ZGlzdGluZm99CkRJU1RJTkZPX0ZJTEU9CSR7TUFTVEVSRElSfS9kaXN0aW5mby5uZXcKLmVuZGlm Cgp1cGRhdGUtZGlzdGluZm86IG1ha2VzdW0gLlNJTEVOVAoJJHtSRUlOUExBQ0VfQ01EfSAtZSAn LyR7QVJDSF9TVUZYfS0ke05WVkVSU0lPTjpSfS9zL14vfi8nIFwKCQkke01BU1RFUkRJUn0vZGlz dGluZm8KCSR7UkVJTlBMQUNFX0NNRH0gLWUgJy9eflNIQTI1Ni9yICR7RElTVElORk9fRklMRX0n IC1lICcvXn4vZCcgXAoJCSR7TUFTVEVSRElSfS9kaXN0aW5mbwoJJHtSTX0gJHtESVNUSU5GT19G SUxFfSAke01BU1RFUkRJUn0vZGlzdGluZm8uYmFrCgouaW5jbHVkZSA8YnNkLnBvcnQubWs+Cg== --Multipart=_Mon__4_Jun_2018_21_25_06_+0900_gPC_eyWaOYs1M.i7-- From owner-freebsd-current@freebsd.org Mon Jun 4 14:15:13 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E796EFE5DE2 for ; Mon, 4 Jun 2018 14:15:12 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::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 7D46268F33 for ; Mon, 4 Jun 2018 14:15:12 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: by mail-io0-x231.google.com with SMTP id l19-v6so28420439ioj.5 for ; Mon, 04 Jun 2018 07:15:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=sqSzlvy2AqIRshW4ce+wT4xmKWZqrWxedBl7Hx0XwyI=; b=GQ0SCybWAvdUL1ZTWgNtafebL0GL5FVaR7WNKmPqlxXv8LxFyzvSSF5ku6lkb3MPkT TogzUkn6OQI+/4fJ4OkOCpDV99OFwmknSvtZZXreIHrvfGiBFI6g8MEbGW5iwNE7lLxM H1vsVPHDHV3zOeFL0KzWGzKym1l4XQQPWIvSr/QobrUbnEHuDMquWoQWdy0IJb5n1z4u IYodYYwk6D5qaNzxJCJtCDpCJWK0HaV5WJDoMeV4IphYgghW2ilrTyCGE2pcD12zl+Zh LjYmDhvOVql3/Q70VXrkFW6OESMWRQAnFfBuzDHEN4yTJVolcT35rsJpTjJ4jP51yKKF RCUA== 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=sqSzlvy2AqIRshW4ce+wT4xmKWZqrWxedBl7Hx0XwyI=; b=K9WSQsGZNeaNA9LwtZYVlWsD8NaOZUgCO7JTrFv5q/Roevj4ewxVIjE9iaOPJz4qk1 p+Mw1Li1IcAhH4YdZQHTteifIn0Qii+TmaY3S+v1I+16ZL15gbIInSiB4lND4vjQsfl6 +Pp5TiEH+uEgIw9yD6KMp1f5NOpnpVMozJAOLgnOHoGNJig6RMXEo8zl8fSXxD6bHR0k VQHcp149f6z+TZFShdO7TroPSjhaCY806sqzehhmTdnKWXkoloU/qiYdKDuapebh1vye hyDHnmXZU2P+gxUOYhZL2KhO7I5lP8yMHHQjl7ceBq0smnRsxyVvrnDXg3QJ/kdK/fub a+OA== X-Gm-Message-State: APt69E3DM70HZy4QNXw6MEjSqLhJQx+YFMCbKPvFzLl5Ypf4E11gvj8J oVzaHUxY1kPz5VbNLctlq5FYxLxx7dC80eEO8eI= X-Google-Smtp-Source: ADUXVKIj5R5OVvNkjR9ta2WHaOKwq+CZXqiI3h0nxjDFdLMMM7SvXDlhqQoQJv3/i03L591Po43IxGWxY1Y6OP9cWKM= X-Received: by 2002:a6b:e008:: with SMTP id z8-v6mr1740057iog.296.1528121711790; Mon, 04 Jun 2018 07:15:11 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a02:8d5c:0:0:0:0:0 with HTTP; Mon, 4 Jun 2018 07:15:11 -0700 (PDT) In-Reply-To: <20180604025016.xe5ezrkjum7gs3pv@kazhap> References: <20180601091031.72u7tqfkatsl3guh@kazhap> <20180601223711.GA93642@elch.exwg.net> <20180603145342.qziiv7awhr4cvs73@kazhap> <20180603173330.p6h7x6vznzxwbqmp@squirrel.exwg.net> <20180604025016.xe5ezrkjum7gs3pv@kazhap> From: Adam Date: Mon, 4 Jun 2018 09:15:11 -0500 Message-ID: Subject: Re: Can't seem to use 5GHz APs with Intel wireless To: Dhananjay Balan Cc: Christoph Moench-Tegeder , FreeBSD CURRENT Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2018 14:15:13 -0000 On Sun, Jun 3, 2018 at 9:50 PM, Dhananjay Balan wrote: > On Sun, Jun 03, 2018 at 07:33:30PM +0200, Christoph Moench-Tegeder wrote: > > > Is the regdomain/country setting correct for your area and matches your > > AP? Especially in the 5GHz band there are some "gaps" - not all channels > > may be used in all countries (because of possible interference with > > radar equipment and other stuff). See: > > https://en.wikipedia.org/wiki/List_of_WLAN_channels#5_GHz_( > 802.11a/h/j/n/ac/ax) > > > > Thanks for taking time to explain. > > Turns out PEBKAC. I had this offending line burried in rc.conf > > create_args_wlan0="country DE regdomain FCC4" > > According to regdomain(5) > > So I was forcing my card to do 2.4Ghz it seems, removed it - everything > worked like charm. I can see and connect to 5GHz 11a aps. > > wlan0: flags=8843 metric 0 mtu > 1500 > ether xxxx > inet 192.168.1.13 netmask 0xffffff00 broadcast 192.168.1.255 > nd6 options=29 > media: IEEE 802.11 Wireless Ethernet MCS mode 11na > status: associated > ssid xxxx channel 36 (5180 MHz 11a ht/40+) bssid xxxxxxxx > regdomain FCC country US authmode WPA2/802.11i privacy ON > deftxkey UNDEF TKIP 2:128-bit txpower 17 bmiss 10 mcastrate 6 > mgmtrate 6 scanvalid 60 ampdulimit 64k ampdudensity 4 -amsdutx > amsdurx > shortgi -stbc -ldpc wme roaming MANUAL > > Thanks for the posting. It appears I made some errors in my previous response. I'm using an iwm, not iwn. And after your pointer I changed my country to NO which then allows me to see, but not associate to 5gz. Good yours is working. -- Adam From owner-freebsd-current@freebsd.org Mon Jun 4 15:41:50 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 04A31FEEBBF for ; Mon, 4 Jun 2018 15:41:50 +0000 (UTC) (envelope-from clbuisson@orange.fr) Received: from smtp.smtpout.orange.fr (smtp08.smtpout.orange.fr [80.12.242.130]) by mx1.freebsd.org (Postfix) with ESMTP id 868776E11E for ; Mon, 4 Jun 2018 15:41:49 +0000 (UTC) (envelope-from clbuisson@orange.fr) Received: from localhost ([109.222.3.199]) by mwinf5d31 with ME id ufaA1x00E4Hdxet03faAoQ; Mon, 04 Jun 2018 17:34:11 +0200 X-ME-Helo: localhost X-ME-Auth: Y2xidWlzc29uQHdhbmFkb28uZnI= X-ME-Date: Mon, 04 Jun 2018 17:34:11 +0200 X-ME-IP: 109.222.3.199 To: FreeBSD Current From: Claude Buisson Subject: error building libpmc_events.c Message-ID: <517b70cf-c5dc-db7b-7887-43cd74f3e10c@orange.fr> Date: Mon, 4 Jun 2018 17:34:10 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2018 15:41:50 -0000 Hi, During a buildworld of head on amd64, from 332518 to 334590, the build stops with: --- all_subdir_lib/libpmc --- ===> lib/libpmc (all) --- libpmc_events.c --- ./pmu-events/jevents "x86" /home/src/lib/libpmc/pmu-events/arch libpmc_events.c sh: ./pmu-events/jevents: not found *** [libpmc_events.c] Error code 127 ... TIA CBu From owner-freebsd-current@freebsd.org Mon Jun 4 15:10:42 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7F4B0FEB495; Mon, 4 Jun 2018 15:10:42 +0000 (UTC) (envelope-from Martin.Ambroz@tudc.cz) Received: from sis0000phaux836.ecps.cz (sis0000phaux836.ecps.cz [81.19.46.25]) by mx1.freebsd.org (Postfix) with ESMTP id 327396BABE; Mon, 4 Jun 2018 15:10:41 +0000 (UTC) (envelope-from Martin.Ambroz@tudc.cz) Received: from sis0000phaux703.ecps.cz (unknown [10.4.71.53]) by sis0000phaux836.ecps.cz (Postfix) with ESMTP id 40zypx334Sz8ycPx; Mon, 4 Jun 2018 15:02:49 +0000 (UTC) Received: from sis0000phaux703.ecps.cz (localhost [127.0.0.1]) by sis0000phaux703.ecps.cz (Postfix) with ESMTP id 40zypx2CC7zdHGHL; Mon, 4 Jun 2018 15:02:49 +0000 (UTC) Received: from cd00000olcnt050.mail.cd.cz (cd00000olcnt050.mail.cd.cz [10.16.5.25]) by sis0000phaux703.ecps.cz (Postfix) with ESMTP id 40zypx1MstzdHGHH; Mon, 4 Jun 2018 15:02:49 +0000 (UTC) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable Subject: RE: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Mon, 4 Jun 2018 17:02:39 +0200 Message-ID: <09882402DE3EFD46AEE62C518AF3B4E5043BBF73@cd00000olcnt050.mail.cd.cz> In-Reply-To: <20180530155039.GE97814@FreeBSD.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted Thread-Index: AdP4LoCBDb7Idgb0RT+uVWnVZNhxZgD5jL3A References: <20180530155039.GE97814@FreeBSD.org> From: To: , X-Virus-Scanned: ClamAV using ClamSMTP X-Mailman-Approved-At: Mon, 04 Jun 2018 15:58:33 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2018 15:10:42 -0000 > Hi, > > Could folks please help boot-test the most recent 12.0-CURRENT amd64 = memstick images on various hardware? Note, this is not a request to = install 12.0- > CURRENT, only a boot-test with various system knobs tweaked. > > The most recent images are available at: > = https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/Fr= eeBSD-12.0-CURRENT-amd64-20180529-r334337-mini-memstick.img > = https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/Fr= eeBSD-12.0-CURRENT-amd64-20180529-r334337-memstick.img > > We are interested in testing both UEFI and CSM/BIOS/legacy mode, as we = would like to get this included in the upcoming 11.2-RELEASE if the = change that > had been committed addresses several boot issues reported = recently. > > Please help test, and report back (both successes and failures). > > Thanks, > > Glen Went well on Lenovo Thinkpad X250, Fujitsu Celsius W530 and Lenovo = ThinkCentre M710s. Martin From owner-freebsd-current@freebsd.org Mon Jun 4 17:46:36 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 96689FD408C for ; Mon, 4 Jun 2018 17:46:36 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 478A274CE6; Mon, 4 Jun 2018 17:46:36 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1033) id 373E5F70C; Mon, 4 Jun 2018 17:46:36 +0000 (UTC) Date: Mon, 4 Jun 2018 17:46:36 +0000 From: Alexey Dokuchaev To: Tomoaki AOKI Cc: freebsd-current@freebsd.org, alexvpetrov@gmail.com, mjg@FreeBSD.org, ler@FreeBSD.org Subject: Re: Error build nvidia-driver with r334555 Message-ID: <20180604174636.GA29016@FreeBSD.org> References: <83fec8d8-699f-e86c-9884-9d8698a86a91@gmail.com> <20180603214222.953748e1eb7a0b39e11214ae@dec.sakura.ne.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180603214222.953748e1eb7a0b39e11214ae@dec.sakura.ne.jp> User-Agent: Mutt/1.9.5 (2018-04-13) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2018 17:46:36 -0000 On Sun, Jun 03, 2018 at 09:42:22PM +0900, Tomoaki AOKI wrote: > This is caused by r334533 and/or r334534 (memset-related changes). > sysutils/lsof is also affected. > > You should revert r334533 and r334534 temporarily until nvidia-driver > support this change. nVidia driver port was fixed as of r471574. ./danfe From owner-freebsd-current@freebsd.org Mon Jun 4 17:50:56 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E242BFD468F for ; Mon, 4 Jun 2018 17:50:55 +0000 (UTC) (envelope-from alexvpetrov@gmail.com) Received: from mail-lf0-x233.google.com (mail-lf0-x233.google.com [IPv6:2a00:1450:4010:c07::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1E97B7505E; Mon, 4 Jun 2018 17:50:55 +0000 (UTC) (envelope-from alexvpetrov@gmail.com) Received: by mail-lf0-x233.google.com with SMTP id q11-v6so26586282lfc.7; Mon, 04 Jun 2018 10:50:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:openpgp:autocrypt:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=iyfu4JiGGP08nsLdfivMPkFMkPvLd2illwiJhA6bTEI=; b=dEtHRS6dIKICdlkxzg/rZPHYPYTjCSvVZ8ayfKrveVfbJQazctgNiOKzWRyYH4cvkH /d04erWxvs+YyVMZfBtJYX7Ufn6uZTFyYDml2PWWSCodksQjPtL3F2ty38It78mATKUn zHlDvK5muowSUuDLekiukGJtZX/7m/SnBSwvnHs4NKfiDLrBTFuvbF82yL089RY5W+J6 7vL4y7zFyTKoleFDG/vLZk5fuBWS3Rud578rjuVG7iXi5HW2lprB4uSv8j+sVWzLYmS6 irJcgSZS50lLPQrcgyz22nCH/jGRooNE6Pxy+wcZ4Pdn6Rjogp5WYJM1xVwNXH6aRgCc MPBQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=iyfu4JiGGP08nsLdfivMPkFMkPvLd2illwiJhA6bTEI=; b=t6pFQBRiFn0bNuO5HLhkHdLQX08DMYYT7ZsyMOaSiFdabeh0qBiDbPxSuwSss3Rvgj D/wnEUadEjP0kTyjy9e/N7NkqSFOJsiv2zNteR3NZ3hQSspISqe/a1bKUPh/SAHQXIpv uId0x4+LHOU1MYgn77BQjl/Fnv0fcqIDrBYyE2so0Yula413Hq6PErpH3PcB5ierBDon jtUfNfR6+9csi3ZJuCCpxHNI/mewUcJSP48mH/J+GxBvBst5iXwdnSKf/whlMvyD03Qw uWp/nOFO3gfbJLsJtVQiX8fxvcw75Q6RN3mZGJfaZRwR+CVR8VcxIffCyCruIh4tcqDq bUVA== X-Gm-Message-State: APt69E15PryVV9WKcNVMX/dV60HcZ3WxOKtnxBSPNTZXygVEmexvePXX LzxTlPEZeK9DaaaDfLQ6Fxj0/Jp8 X-Google-Smtp-Source: ADUXVKLnXzUPdZxzGK5phKXn1dK2cAh1PgwC4XncqSNJUWuJBa59o+1MTxIaD/GlXUtRsjuPS9ZzeQ== X-Received: by 2002:a2e:3810:: with SMTP id f16-v6mr4540477lja.25.1528134653428; Mon, 04 Jun 2018 10:50:53 -0700 (PDT) Received: from alex.super (stone.g-service.ru. [84.22.141.217]) by smtp.googlemail.com with ESMTPSA id b2-v6sm3451370lji.85.2018.06.04.10.50.51 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 04 Jun 2018 10:50:51 -0700 (PDT) Subject: Re: Error build nvidia-driver with r334555 To: Alexey Dokuchaev , Tomoaki AOKI Cc: freebsd-current@freebsd.org, mjg@FreeBSD.org, ler@FreeBSD.org References: <83fec8d8-699f-e86c-9884-9d8698a86a91@gmail.com> <20180603214222.953748e1eb7a0b39e11214ae@dec.sakura.ne.jp> <20180604174636.GA29016@FreeBSD.org> From: "Alex V. Petrov" Openpgp: preference=signencrypt Autocrypt: addr=alexvpetrov@gmail.com; prefer-encrypt=mutual; keydata= xsFNBFr3oA0BEADMSXiVd/IwYhJPMQ6LXbZ7jTA/RXuzrGYaR++UENx5QJ6/HJ/3myTeMnZE nNa0Zme+oKw/9s5x7rBTP6mL5ta7VSYpnPX932mAjT9J4nS7iW/wWNBqcXn7wDCog2TV8Ww3 13SUP2YaKoJKJLxddiZD6AJrkafB9EE/AycMQ8XxMao1lVS+/KAo0yciOsnSlIJCWhF00b3j xDlHLvehrDa4S3EB13bF6uE0XU5nFfMNHtBav2mwD9t01hNioCNTV1hXwmsS/L1n5PR5FyJJ yYtjeohrAUiGKGJU9lJJ6tROBhzV/k3OsOGPyajFOVsW0vUueYfgw+IAPYdOZIAONgNdxkvs tRLQxYPCBMN1FvQ7GlIhq7ob+mxuA1imXx3xzlYy5tu4QzB383qZtLqQnZpysjYooAbHl+eN vB2ldvH9TZxm3fxxNL6zgYAXE/pNgFoqg/ILmhDwvvHzApHqVCKU3g6yii0KPxD7susaUWcL JYgrmt2BIE0RuiQRGWyS0L277D/YGmVnPNHxPi58DBs2iexDm7jw7PhlmfOw44N9w+O09D2S gqmBHySAtsq9Z5LoM81F+LrOoVmpYczZWErS917Gua1X7K3wrXoqQC8qcSiHZpEcBl/Uohii QWzjQJot5LT7rvfFHpnSOXAKgN7enVM7KxTJAYK1U343GGdepQARAQABzTZBbGV4VlBldHJv diAoZmlyc3QgZ2xvYmFsIGtleSkgPGFsZXh2cGV0cm92QGdtYWlsLmNvbT7CwY4EEwEIADgW IQRvKPTT2TJuh37ANx313p8aVpVkcAUCWvegDQIbAwULCQgHAgYVCgkICwIEFgIDAQIeAQIX gAAKCRD13p8aVpVkcLLeEADClYAElEInGGjtLfH4jdjvTDaQTsrwT5/1E5/h8yxI4yn7hCt1 Dh+iCSUNLdPO88nZV2jP8bMQXFBKSbC0nAJXd8O+8t9AfSWoUC6IMzncxKTK/jZuJTCToCUR XZ+47+uJaBp51rpw3pFX8UrFlYSF6Dz97dI2cGHfx3xAOnowKxyHfthxS8waKWgbMOceds78 BP2+Q0iLCpoC9rO4KDc+w+h8z21eHIE9VHadTHpnKVF82voPH8XWvznTOCpYrdBwUtIyD/DV XRb0xcFsOSkvmReYX7u4QuOPLSc86sEWh4hXTFLAOdfeTjrDTDmBcmFpltmW1j+5t4mI1dK8 gptREM8gMJVJw3jjcO6jADeXX9q5C8/lX0sEGz9uC4oU5nkOMyfzd9Anb+9bCs7pMxhqAKjA 8tqJPPkmJU8WzMCs+uudIiQ8W9qIETwUJWxizQ3kvlzLfWRz5n93Y9kzSmjw81aiIJK/HFY8 wsW5zNo6JBn57cMPx8nBC4E2zM09ffmqSpjDwXfvZF2IIR8L4VTiKi3ovwLglJP+Qbs5HXNn 6K40cPNqfnHzPLwXwd/co04B/VVr+cKZuE58kYGty9Xs9q/SEpObDnxnLxMNHUNJJuRgOiti TKDkteHuKm6NA8v05o3TDQ5HU9szEoE5uoi/3pQ1ktfA/K3LkDwbotXL+87BTQRa96ANARAA w5+/xcaCP6iwsi2CFQ4pAWksdmPBEHA2VPn1ym3C6opjbyWUp6sn25eTWppdhA9rUqbM/zV/ hAFRT67oZJKBYNRaMoDdO8BsVZsg/u76QF/GuhbUjIk0tFFdpddMXl0zKAJJMCfDRxURRWv7 NW6sY/EZ4Dal5s4xOT+UrWGag3qoaIRdzw5bJRP+o75L90cE8pd7+Pd9cVJOOtTAwx0E4bPq dPSa6CPDSvzd9D3mw37dPzXysyQkQTy0OM7255E2wjYz3RbJxB3utybPVN3XJBD5EyA8IYeS ic1/03UrkRNv4XrLnlg7xLv96ZeCrf/BDNQW23iVwbISUAk4TXL7xs2TGYOmowZ89mMEcbfW ChX3YLAuAeWzgpMcrDC00izOxG0spkkrHL7/i1iSu2MKhv5qMTVgchlSktdd+KTba5keleHv ULQ3feGUKf9eTkKgES6q4rKrae0tIwByTLhhDVbkXqR6v8zrpJSscrvJ3tMNgquJKy5ATIUB nvUE2hMkSwtnJ2vQ/Z0zGt6c5KxI57/hsb148tXp1v3gAq9d6i8c8ChxSR/kUlqAvzl2QGcn CFVN6nfOzyNfBPZ61abNzkzjzyhOK4Gq4gQvx4QXhDp3jEME7rPM0Tqf0venb1Dp7SIHwggV yJglGApwoUvD4kKNIC7KDr+s/UjbBp4ExFMAEQEAAcLBdgQYAQgAIBYhBG8o9NPZMm6HfsA3 HfXenxpWlWRwBQJa96ANAhsMAAoJEPXenxpWlWRwAaEQAKm0imG5Fm37JZi+5faXJv/ZLZGl r4TVg4u1kMktdTQRrTXa3Qs0i3wTtOZe1p3xCCzPx+97iYETHragDTdAFUO+v+Llin26L1Zl z4huyIqgGSuTuekQfn6eoMZbcF+wzah4j/mvXQVpJBF2qQi1YdHSapWDlweuiuk01y8C3eHv 3qfFB/OJwXhwj0HKhkGkB2dLXuLtIk4GCXh4/g22tWz/SB0gsSXU7WhJFb0CyxETGR9YKxM8 CNl5tVRLqsBC6yQLvcAJgJci73PfMiHKnjxrz//+0xQO1TPeruWsd8nLYvziT38CyX42Mbaj 01WpvB0qOeTGtwGFmyyrnE8fYpd3CE0uAl9BnHqafAabl9+09x3wf+lEkkO2bK59akZz3BPU 8Lz2BAgskyS81WZCthQYUrUozFEx/31x8JJ95EQFNW9t8HBa51r4QhedSNKxLbT3Sx8hH0iq Z8wYkGw0og9U1DqgFzxE2HSGZSDG3I1DrPDqhcM/6Y0V98wS+XreuS88DYYck37+L7bTGiyZ WYFNZk1ChcIBk8hgKn5nFOCWO2rX06RI9zorzSpEg6lB2STae1Up5oEj8QqfYmfO3cp2Qhvj F3c2/i8KpWkJQkAgNrv428FIlx9SiPu9gvNTTYuLIOdZLQvInTmKs2uCoB6JDAW75axDhBbR FvM3Vpv/ Message-ID: <8a5853c7-47cd-5b1d-ebe3-9052d5e14cc0@gmail.com> Date: Tue, 5 Jun 2018 00:50:50 +0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <20180604174636.GA29016@FreeBSD.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2018 17:50:56 -0000 СпаÑибо ÐлекÑей! Thank you! 05.06.2018 00:46, Alexey Dokuchaev пишет: > On Sun, Jun 03, 2018 at 09:42:22PM +0900, Tomoaki AOKI wrote: >> This is caused by r334533 and/or r334534 (memset-related changes). >> sysutils/lsof is also affected. >> >> You should revert r334533 and r334534 temporarily until nvidia-driver >> support this change. > > nVidia driver port was fixed as of r471574. > > ./danfe > -- ----- Alex. From owner-freebsd-current@freebsd.org Mon Jun 4 19:03:53 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5F8F6FE2CC5 for ; Mon, 4 Jun 2018 19:03:53 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::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 CF2C0805C1; Mon, 4 Jun 2018 19:03:52 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-wm0-x22d.google.com with SMTP id r15-v6so325672wmc.1; Mon, 04 Jun 2018 12:03:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=p4Aqa2h4//uKeOebYtXgCGn9NI6R2mXHzqSEnhn1Rj0=; b=uFhSvsCAERNI/lXmFhzZL3Ge2+G5RjmeamItb+7BhlhWHbNUDlcKTVZD/bmIXuDTFK vYy+/y/Q2bztD6pCiOCHFYzRHZok6O3qWBw8m1BcL1Ik+K5ta+eL6wAlBGI+1l2/tY9k xFqJJtCgw0HOr9COmMZsxap060J1+sRyuRQVf0EAy9F15MxoNZbaNbi6P/WJGHn+RJkT E6TnRoXI8o0KN5QhqxNpfqHf0mYeG89mpE+EgstIFKBp7Mll5hpT3yWo+jide7dqm+Oj aBzUtlvF6nSZaJSYZxOYMqsOlLAz/bsUSudZi8vLGd5yYVolOsKM2KaMcMLt/ErnldUj dLMQ== 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=p4Aqa2h4//uKeOebYtXgCGn9NI6R2mXHzqSEnhn1Rj0=; b=jg/YjfARSjBlvIwyAD5kJ6NH4bPqVhsYcplWdHsX4NG0C4zixhYwKexoRHKsLuBdK5 uUUNMzAvTONAm+sorhOGcHcj+brna/oDlH4ZvkJXrWc1A8F+0Ekf/CFDpgZCCzfU3++o Jm0r1aMHxTAyCCR5mHE+wZiX8DZ0E8u7DgiYbfpITkYXcXkhiOHkRjmrQDqmQP/0kttc /XpwSG6eFF/lBXreCbTo2SJBJtIYVjfvGi7ReOe8PO9N3Y5plw0tNtyy18tUEFrqyh/V VUJI+l1B/8Umc7T7ZKz6YhXV7zmyJR6j7av7GYHvG7SFGnG8aFI8tkC/KWbszQPSGKTL ukIA== X-Gm-Message-State: APt69E1gDFGSoHAfKxtmG4e61JbyUFxZvbpr2GOqD6TQ+1zvYXC9Aucd NtQwf6+LpS8Phc5c4xhkekE4pT8AbfTLG4OyOmc= X-Google-Smtp-Source: ADUXVKJ+eggJ267NrKr1qUrpd8HXZIui18Tm8b+fOgulAKSrNi+rLT5qvZF5jm/UU4wLOHXdyg4a3Z4/dLM8BW0bExc= X-Received: by 2002:a1c:150:: with SMTP id 77-v6mr10676046wmb.3.1528139031821; Mon, 04 Jun 2018 12:03:51 -0700 (PDT) MIME-Version: 1.0 References: <20180524160234.GD68014@FreeBSD.org> <201805241610.w4OGAAGY041280@pdx.rh.CN85.dnsmgr.net> <20180530235156.310870d0@thor.intern.walstatt.dynvpn.de> <20180531101643.GV3789@kib.kiev.ua> In-Reply-To: From: Adrian Chadd Date: Mon, 4 Jun 2018 12:03:40 -0700 Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: jmaloney@ixsystems.com Cc: Daniel Eischen , Kostik Belousov , Johannes Lundberg , freebsd-current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2018 19:03:53 -0000 Hi, As a driver/framework developer - no, don't do that. It's worked mostly great for the video side of things because your touch points are "the VM system" and "linuxkpi". And they're all in one big driver pull from Linux. For wifi as an example - it has a bunch of userland components, a kernel framework component (net80211); it gets API churn from people who keep making networking API changes without making them opaque (i just got bitten by the STAILQ -> CK_STAILQ changes for multicast iteration, instead of us growing a multicast iterator function thing.) Having it be multiple drivers/firmware means that anyone doing wifi development here would have to install /all/ of the relevant packages and the net80211 stuff and userland just to get any work done and hope it stays in sync. It'd be nice if that was our stretch goal, but we ain't there yet. As for your intel NIC - I'm sorry that you've had issues getting that into the tree but you can just jump in #freebsd-wifi and whine at us until we commit it. That's what we're there for. -adrian From owner-freebsd-current@freebsd.org Mon Jun 4 19:34:54 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 63A20FE5C31 for ; Mon, 4 Jun 2018 19:34:54 +0000 (UTC) (envelope-from ian.freislich@capeaugusta.com) Received: from mail-yw0-x231.google.com (mail-yw0-x231.google.com [IPv6:2607:f8b0:4002:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DEE8881776 for ; Mon, 4 Jun 2018 19:34:53 +0000 (UTC) (envelope-from ian.freislich@capeaugusta.com) Received: by mail-yw0-x231.google.com with SMTP id v68-v6so10904042ywd.3 for ; Mon, 04 Jun 2018 12:34:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=capeaugusta-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=NVMHHv6bfrwdXK/5ZwcatCsyjgiYL4njONqnSUxZAds=; b=Hi04XHgaob31bhXMYwO3FN+GFPiGA00oAV4JQknzvEZfpgD80rOEMzj3UHK5Xyf7tp hMKAFzDSSVtqKsdZUdZcNMn/2q8zeL/9jF4eiuZ1uDrTund/Nsl0Ed1PEYiA5z4OQ8C7 mE5wc35fBcyOKJy4gjkayfHrCBXrGJ9i61wcks87l8eSwS0NJ0EEt87BZWQ+k46v1JG6 m8jnakCBZlrqWv5k73CrKS1HQnNJpNhjRsjQrHdQbHRiGcqY0cwNdhu9yod5PWSWPx11 kdowTZBolVwO3TEMQTl79cxtBZPAtzYCSvGThu0rQe+T9w4AwAdYPFza8XGGcYBIfeEy INTQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=NVMHHv6bfrwdXK/5ZwcatCsyjgiYL4njONqnSUxZAds=; b=TBovrWXpWGy4bh3Rxgbxmx8XcUx81K9x/DQfOIP0PR23CH2bA/tUfLWsYTjbhKl4IE UGJCC/9unIPwrnK0Zdj9veFwCOEzdub6Q4mA+Hy6nTsMhpBUuA6/pfDhWa433cXpTfsz BMkOs3vO8VKWSAwTm8nRtjXjZEu1ByewLTUjLBtFooEV+CZcbtzW8M5ycXZLSDaeni6q Ozj0ihJJBFoUhkb6Bi419kZrFKZU/+LGJ0r/9VFQ/SljUEA5Vjv80yQLMvLYQeKcOjWS TNBXXwkDi/9jkIZ5HZPoPNqjhOWUyTtlyDCJCUmyhWkf2RtkWyhUvY23ll04thHeN/4q C1bg== X-Gm-Message-State: ALKqPwcPQIEAdxrKAsn3nq/UcJYrC89nFCsHZEPO+LpKcvd5ks4aN3Pa YnyQ8dtADVzeRV+dtoISuS7QjVErJdg9fmpW6cD69+T/HyDfEOORRn8lbgeftWLJe6yPErNeog1 GMamabqeBwJyT/3RU X-Google-Smtp-Source: ADUXVKLTOoS/B09Sm400sEDW9loIO1DMqquyW4623zNKZSDKGX/HETGtANGhxs6RB/JvKBoy9HyPPQ== X-Received: by 2002:a81:2e91:: with SMTP id u139-v6mr11519936ywu.222.1528140892745; Mon, 04 Jun 2018 12:34:52 -0700 (PDT) Received: from [10.0.11.220] ([64.53.114.237]) by smtp.gmail.com with ESMTPSA id v7-v6sm513209ywv.91.2018.06.04.12.34.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 04 Jun 2018 12:34:52 -0700 (PDT) Subject: Re: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted To: Glen Barber , freebsd-stable@freebsd.org, freebsd-current@freebsd.org, Ed Maste References: <20180530155039.GE97814@FreeBSD.org> From: Ian FREISLICH Message-ID: <942c542c-9a4c-7fee-37c6-bf994f1079c4@capeaugusta.com> Date: Mon, 4 Jun 2018 15:34:51 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <20180530155039.GE97814@FreeBSD.org> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: quoted-printable Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2018 19:34:54 -0000 On 05/30/2018 11:50 AM, Glen Barber wrote: > Hi, > > Could folks please help boot-test the most recent 12.0-CURRENT amd64 > memstick images on various hardware? Note, this is not a request to > install 12.0-CURRENT, only a boot-test with various system knobs > tweaked. > > The most recent images are available at: > https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/Fr= eeBSD-12.0-CURRENT-amd64-20180529-r334337-mini-memstick.img > https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/Fr= eeBSD-12.0-CURRENT-amd64-20180529-r334337-memstick.img > > We are interested in testing both UEFI and CSM/BIOS/legacy mode, as we > would like to get this included in the upcoming 11.2-RELEASE if the > change that had been committed addresses several boot issues reported > recently. > > Please help test, and report back (both successes and failures). Coincidentally, I was trying to install these on a very old 10" Dell=20 Lattitude with an Atom N550 CPU.=A0 Both images booted to the beastie menu= =20 but hung loading the kernel.=A0 The only way I could get it to boot was to= =20 manually load the kernel at the loader prompt and boot. I was also=20 unsuccessful performing a network install due to what I think was the=20 download filesystem being read only.=A0 I was able to install from the=20 bundled distribution. Ian --=20 From owner-freebsd-current@freebsd.org Mon Jun 4 19:07:31 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 70D36FE2FC0 for ; Mon, 4 Jun 2018 19:07:31 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: from mail-it0-x244.google.com (mail-it0-x244.google.com [IPv6:2607:f8b0:4001:c0b::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F219580799; Mon, 4 Jun 2018 19:07:30 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: by mail-it0-x244.google.com with SMTP id n7-v6so301934itn.1; Mon, 04 Jun 2018 12:07:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=d1nuViUFuk62bR8tNvIRmEEXuax/P5cVOlYfc4UKqCY=; b=i6XvRQda8MkSViiyDzq1ltaaDf6FZ1O/uBMwnsjG33tL+HAkJV3Vu56qyEDHkd8ogN H3dbGG4hRyVJhq3Dww8lZTW6WpWhrcqEaSmpwPGdePE7cqqao9RI9+Fg9spKKM7xvx+/ GCWVmRypbddwQzCbmWU5MW+bsC5IwJrgpOVVsB6rTADEcIy8poHfJdYhK0CZ2Ur5+j7j qpboXS7htjpm8kz3YX8oI3r/VXhpRsso09Deg9I+nqL2wZ6fXRqy43Svgiuc7xL3Otwk CeFfF1gsJPDGCNscsrVD3T1BBnVjwn6JSEmvvpldACMoDhDQWxXWFs6wrQQULZ1OtLTs MhVw== 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=d1nuViUFuk62bR8tNvIRmEEXuax/P5cVOlYfc4UKqCY=; b=T+/QvgdD3+0kSNxj4uZv3+ipaQ04bALllOrAF1Pk5S1qZGjHbnNq/LEu7JllvX44hh brzn0FT8O8oK6LptEU4UqSIzFwsnAUstxXURXjioHuyHcHmo/droCmRUvH4qWEeSq7yY B0tHFIndiRgtbClIRsSgn4Ye6vsoBnjG2CJl07tF1Uv3H4O6eSMZywbYL/mKBa3//lQe UwCl13au/p3a1gtw9vWDvnWhkmYdac2OxLniwgaMuI2rxo+DiOpXPAVPiDqq3CSBYvvK riBMDJhfts/V3PlgRUp4g/+Xqqo5Qph9yPlMATxjZjQcuJ/f+EqsG/eErb45C61M45fA 3cCA== X-Gm-Message-State: APt69E0kFi4YC1JCZUYIov7sWbYy92qB6QQeRrHIhtqoEgRPnCWGOjAo yQnm6g5P17RcnIb+TTDVOQNsImxTx3IDeZp9IJs= X-Google-Smtp-Source: ADUXVKJN3Ul/ZRvJ/+9fb9SP0WM8I+4l82/kN+9jTYaPllNt7/4fpffC9FIR7UBOn13SrQ+p9WhsR+bOaOUiKJocwQM= X-Received: by 2002:a24:459f:: with SMTP id c31-v6mr8803246itd.132.1528139245589; Mon, 04 Jun 2018 12:07:25 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a02:8cd:0:0:0:0:0 with HTTP; Mon, 4 Jun 2018 12:07:25 -0700 (PDT) In-Reply-To: References: <20180524160234.GD68014@FreeBSD.org> <201805241610.w4OGAAGY041280@pdx.rh.CN85.dnsmgr.net> <20180530235156.310870d0@thor.intern.walstatt.dynvpn.de> <20180531101643.GV3789@kib.kiev.ua> From: Matthew Macy Date: Mon, 4 Jun 2018 12:07:25 -0700 Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: Adrian Chadd Cc: jmaloney@ixsystems.com, Daniel Eischen , Kostik Belousov , Johannes Lundberg , freebsd-current Content-Type: text/plain; charset="UTF-8" X-Mailman-Approved-At: Mon, 04 Jun 2018 19:37:33 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2018 19:07:31 -0000 On Mon, Jun 4, 2018 at 12:03 PM, Adrian Chadd wrote: > Hi, > > As a driver/framework developer - no, don't do that. > > It's worked mostly great for the video side of things because your > touch points are "the VM system" and "linuxkpi". And they're all in > one big driver pull from Linux. > > For wifi as an example - it has a bunch of userland components, a > kernel framework component (net80211); it gets API churn from people > who keep making networking API changes without making them opaque (i > just got bitten by the STAILQ -> CK_STAILQ changes for multicast > iteration, instead of us growing a multicast iterator function thing.) We've had one for several years. You're just not using it. > Having it be multiple drivers/firmware means that anyone doing wifi > development here would have to install /all/ of the relevant packages > and the net80211 stuff and userland just to get any work done and hope > it stays in sync. This is the same old saw of people who can't be bothered to use ports. It is more of a headache with ABI drift but it's certainly not a fundamental impediment. -M From owner-freebsd-current@freebsd.org Mon Jun 4 20:31:52 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DB73AFEEDAB for ; Mon, 4 Jun 2018 20:31:51 +0000 (UTC) (envelope-from Alexander@leidinger.net) Received: from mailgate.Leidinger.net (mailgate.leidinger.net [IPv6:2a00:1828:2000:375::1:5]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 770AF848AE for ; Mon, 4 Jun 2018 20:31:51 +0000 (UTC) (envelope-from Alexander@leidinger.net) Date: Mon, 04 Jun 2018 22:31:08 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=leidinger.net; s=outgoing-alex; t=1528144302; bh=abOEiFmE6AeFwI7EaFM+bYXUWE26CWLDH61Za6SSmsU=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=UhF3f7bzVZnpHQRSgjnT70sqH979UVHTESQFaOwkqxE/sbDVTZQsQhhRJRRYChHNF FtX+v3juzfiVAZ8gMjgulGkIa1FmXWJGAs3AWG/3uxOCynaDsB0J/nQRSsj2ceAxfs z/AC58j2bynyKKWSiPBQcB/wnXmqx2BCA6nZCWTZGjUjRVT8gPvmfEdgZbkOJXAc5R 167iwC3K1rUVRsR1pzzi+gE9FfxUgFgm0Alk4NxBKbK2xiEzvRzRtezzGowRCbe5bW dxr0HgiyTkUW9UK9Ji6QiXqgIYphfZ1QOFloxoH6Su5xYNUhz8U0BpsoDENs7dHzCI k1/y2LqVzik1Q== Message-ID: <20180604223108.Horde.RcVquaVKWdNzNidD_5aJz7E@webmail.leidinger.net> From: Alexander Leidinger To: Slawa Olhovchenkov Cc: Kirill Ponomarev , freebsd-current@freebsd.org Subject: Re: Deadlocks / hangs in ZFS References: <20180522101749.Horde.Wxz9gSxx1xArxkYMQqTL0iZ@webmail.leidinger.net> <20180522122924.GC1954@zxy.spb.ru> <20180522161632.Horde.ROSnBoZixBoE9ZBGp5VBQgZ@webmail.leidinger.net> <20180522144055.GD1954@zxy.spb.ru> <20180527194159.v54ox3vlthpuvx4q@jo> <20180527220612.GK1926@zxy.spb.ru> <20180528090201.Horde._E4JZcuEaZHfj_BNzWjci2O@webmail.leidinger.net> <20180603211450.Horde.pI-Fom6S1tUcaHvTF4MUjin@webmail.leidinger.net> <20180603192814.GP1926@zxy.spb.ru> In-Reply-To: <20180603192814.GP1926@zxy.spb.ru> User-Agent: Horde Application Framework 5 Content-Type: multipart/signed; boundary="=_qe-DcLRCIIZd1WsRly-W4dK"; protocol="application/pgp-signature"; micalg=pgp-sha1 MIME-Version: 1.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2018 20:31:52 -0000 This message is in MIME format and has been PGP signed. --=_qe-DcLRCIIZd1WsRly-W4dK Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Quoting Slawa Olhovchenkov (from Sun, 3 Jun 2018=20=20 22:28:14=20+0300): > On Sun, Jun 03, 2018 at 09:14:50PM +0200, Alexander Leidinger wrote: > >> Quoting Alexander Leidinger (from Mon, 28 >> May 2018 09:02:01 +0200): >> >> > Quoting Slawa Olhovchenkov (from Mon, 28 May 2018 >> > 01:06:12 +0300): >> > >> >> On Sun, May 27, 2018 at 09:41:59PM +0200, Kirill Ponomarev wrote: >> >> >> >>> On 05/22, Slawa Olhovchenkov wrote: >> >>>> > It has been a while since I tried Karl's patch the last time, and= I >> >>>> > stopped because it didn't apply to -current anymore at some point= . >> >>>> > Will what is provided right now in the patch work on -current? >> >>>> >> >>>> I am mean yes, after s/vm_cnt.v_free_count/vm_free_count()/g >> >>>> I am don't know how to have two distinct patch (for stable and >> >>>> current) in one review. >> >>> >> >>> I'm experiencing these issues sporadically as well, would you mind >> >>> to publish this patch for fresh current? >> >> >> >> Week ago I am adopt and publish patch to fresh current and stable, is >> >> adopt need again? >> > >> > I applied the patch in the review yesterday to rev 333966, it >> > applied OK (with some fuzz). I will try to reproduce my issue with >> > the patch. >> >> The behavior changed (or the system was long enough in this state >> without me noticing it). I have a panic now: >> panic: deadlkres: possible deadlock detected for 0xfffff803766db580, >> blocked for 1803003 ticks > > Hmm, may be first determinate locked function > > addr2line -ie /boot/kernel/kernel 0xfffff803766db580 > > or > > kgdb > x/10i 0xfffff803766db580 Both don'T produce any sensible output: (kgdb) x/10i 0xfffff803766db580 0xfffff803766db580: subb $0x80,-0x78(%rsi) 0xfffff803766db584: (bad) 0xfffff803766db585: (bad) 0xfffff803766db586: (bad) 0xfffff803766db587: incl -0x7f7792(%rax) 0xfffff803766db58d: (bad) 0xfffff803766db58e: (bad) 0xfffff803766db58f: incl -0x7f7792(%rax) 0xfffff803766db595: (bad) 0xfffff803766db596: (bad) Seems I need to provoke a real kernel dump instead of a textdump for this. Bye, Alexander. --=20 http://www.Leidinger.net=20Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_qe-DcLRCIIZd1WsRly-W4dK Content-Type: application/pgp-signature Content-Description: Digitale PGP-Signatur Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJbFaGMAAoJEKrxQhqFIICEf8MP/3MJ5+SyvKue3kRXrHQDc1WG AOhJc8YMrJUYkh8udbEbkDTCVT/4XrrZVUL9tzhe59WnWKYxei9Bs9Zjku+83+wm BlqUBQ99AhMOOgL+KiDHw98IaFrd0wvVKQFLc5MJN2bggpDxib/Vkytw+fxdnfNJ CbHqIJZ0KeLPbFzmwXsrumU66zcQwQ+dHISJ9DLM+8a3jzL7x/X4xSkJeNxKjJNi CEO1rtI+mE5ATd13UqqcUBdGfDiWLKt/3crXwGWdlvvnZng4oSDAsfWuyzSg8QeU jHNnP2/CWshOU7H0N7K0nisAw9b86UKJGA34rKAGACyONQ61/Vquc4wIpHJyLT+B 9wtywOhJipV2ZNFp48f5UZnaEHBh82ySGsZh4ZCGqKwmbbtNDAvbLDbrCEEV1Hu2 rd/vge3RmF1ZBtZQ8RnncTU8gDSJ1zdyiNOMZi4t4Tq7seZFmWQ3SiAt6ljCn87d d9Dl/EpIFCbS8Pr9/IonzMIKJVHakWOm0qRC7gsnTTkGO4PX9/N36lgp2FPV+Qe1 EqmMtdrLZC4SClCXV1EbC7sBrRS2ORa18aRD74v3xsYWjO/PaCaZbo5+h1uLdd6I Hc9aLB+KZCwhWaIQ4edNilxe3Z7DkuOZarLMmLI2lVtGIkEDdBEufdcsScU2rrf8 pJpx8t+WznZBxn92cbR5 =X5zV -----END PGP SIGNATURE----- --=_qe-DcLRCIIZd1WsRly-W4dK-- From owner-freebsd-current@freebsd.org Mon Jun 4 21:18:07 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 31468FF51DD for ; Mon, 4 Jun 2018 21:18:07 +0000 (UTC) (envelope-from freebsd@grem.de) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id A2D8C87323 for ; Mon, 4 Jun 2018 21:18:05 +0000 (UTC) (envelope-from freebsd@grem.de) Received: (qmail 6774 invoked by uid 89); 4 Jun 2018 21:17:57 -0000 Received: from unknown (HELO bsd64.grem.de) (mg@grem.de@194.97.158.70) by mail.grem.de with ESMTPA; 4 Jun 2018 21:17:57 -0000 Date: Mon, 4 Jun 2018 23:17:56 +0200 From: Michael Gmelin To: Konstantin Belousov Cc: Michael Gmelin , "freebsd-current@freebsd.org" , Matthias Apitz , jhb@freebsd.org Subject: Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy) Message-ID: <20180604231756.2ed2adb9@bsd64.grem.de> In-Reply-To: <20180604110654.GA2450@kib.kiev.ua> References: <20180603144840.44bfea41@bsd64.grem.de> <20180603132110.GP3789@kib.kiev.ua> <20180603165500.361ec894@bsd64.grem.de> <20180603150423.GQ3789@kib.kiev.ua> <20180603215020.452a81d8@bsd64.grem.de> <20180603205340.GS3789@kib.kiev.ua> <20180604004632.56ca6afa@bsd64.grem.de> <20180604110654.GA2450@kib.kiev.ua> X-Mailer: Claws Mail 3.15.1 (GTK+ 2.24.31; amd64-portbld-freebsd10.3) X-Face: $wrgCtfdVw_H9WAY?S&9+/F"!41z'L$uo*WzT8miX?kZ~W~Lr5W7v?j0Sde\mwB&/ypo^}> +a'4xMc^^KroE~+v^&^#[B">soBo1y6(TW6#UZiC]o>C6`ej+i Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEWJBwe5BQDl LASZU0/LTEWEfHbyj0Txi32+sKrp1Mv944X8/fm1rS+cAAAACXBIWXMAAAsTAAAL EwEAmpwYAAAAB3RJTUUH3wESCxwC7OBhbgAAACFpVFh0Q29tbWVudAAAAAAAQ3Jl YXRlZCB3aXRoIFRoZSBHSU1QbbCXAAAAAghJREFUOMu11DFvEzEUAGCfEhBVFzuq AKkLd0O6VrIQsLXVSZXoWE5N1K3DobBBA9fQpRWc8OkWouaIjedWKiyREOKs+3PY fvalCNjgLVHeF7/3bMtBzV8C/VsQ8tecEgCcDgrzjekwKZ7TwsJZd/ywEKwwP+ZM 8P3drTsAwWn2mpWuDDuYiK1bFs6De0KUUFw0tWxm+D4AIhuuvZqtyWYeO7jQ4Aea 7jUqI+ixhQoHex4WshEvSXdood7stlv4oSuFOC4tqGcr0NjEqXgV4mMJO38nld4+ xKNxRDon7khyKVqY7YR4d+Cg0OMrkWXZOM7YDkEfKiilCn1qYv4mighZiynuHHOA Wq9QJq+BIES7lMFUtcikMnkDGHUoncA+uHgrP0ctIEqfwLHzeSo+eUA66AqzwN6n 2ZHJhw6Qh/PoyC/QENyEyC/AyNjq74Bs+3UH0xYwzDUC4B97HgLocg1QLYgDDO1v f3UX9Y307Ew4AHh67YAFFsxEpkXwpXY3eIgMhAAE3R19L919nNnuD2wlPcDE3UeT L2ytEICQib9BXgS2fU8PrD82ToYO1OEmMSnYTjSqSv9wdC0tPYC+rQRQD9ESnldF CyqfmiYW+tlALt8gH2xrMdC/youbjzPXEun+/ReXsMCDyve3dZc09fn2Oas8oXGc Jj6/fOeK5UmSMPmf/jL+GD8BEj0k/Fn6IO4AAAAASUVORK5CYII= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2018 21:18:07 -0000 On Mon, 4 Jun 2018 14:06:55 +0300 Konstantin Belousov wrote: > On Mon, Jun 04, 2018 at 12:46:32AM +0200, Michael Gmelin wrote: > > > > > > On Sun, 3 Jun 2018 23:53:40 +0300 > > Konstantin Belousov wrote: > > > > > On Sun, Jun 03, 2018 at 09:50:20PM +0200, Michael Gmelin wrote: > > > > > > > > > > > > On Sun, 3 Jun 2018 18:04:23 +0300 > > > > Konstantin Belousov wrote: > > > > > > > > > On Sun, Jun 03, 2018 at 04:55:00PM +0200, Michael Gmelin > > > > > wrote: > > > > > > > > > > > > > > > > > > On Sun, 3 Jun 2018 16:21:10 +0300 > > > > > > Konstantin Belousov wrote: > > > > > > > > > > > > > On Sun, Jun 03, 2018 at 02:48:40PM +0200, Michael Gmelin > > > > > > > wrote: > > > > > > > > Hi, > > > > > > > > > > > > > > > > After upgrading CURRENT to r333992 (from something at > > > > > > > > least a year old, quite some changes in mp_machdep.c > > > > > > > > since), this machine crashes on boot: > > > > > > > > > > > > > > > > Copyright (c) 1992-2018 The FreeBSD Project. > > > > > > > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, > > > > > > > > 1992, 1993, 1994 The Regents of the University of > > > > > > > > California. All rights reserved. FreeBSD is a registered > > > > > > > > trademark of The FreeBSD Foundation. FreeBSD > > > > > > > > 12.0-CURRENT #1 r333992: Tue May 22 00:31:04 CEST 2018 > > > > > > > > root@flimsy:/usr/obj/usr/src/amd64.amd64/sys/flimsy > > > > > > > > amd64 FreeBSD clang version 6.0.0 > > > > > > > > (tags/RELEASE_600/final 326565) (based on LLVM 6.0.0) > > > > > > > > WARNING: WITNESS option enabled, expect reduced > > > > > > > > performance. VT(vga): resolution 640x480 CPU: Intel(R) > > > > > > > > Celeron(R) 2955U @ 1.40GHz (1396.80-MHz K8-class CPU) > > > > > > > > Origin="GenuineIntel" Id=0x40651 Family=0x6 > > > > > > > > Model=0x45 Stepping=1 > > > > > > > > Features=0xbfebfbff > > > > > > > CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > > > > > > > > Features2=0x4ddaebbf > > > > > > > xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,TSCDLT,XSAVE,OSXSAVE,RDRAND> > > > > > > > > AMD Features=0x2c100800 > > > > > > > > AMD Features2=0x21 Structured Extended > > > > > > > > Features=0x2603 > > > > > > > > XSAVE Features=0x1 VT-x: (disabled in BIOS) > > > > > > > > PAT,HLT,MTF,PAUSE,EPT,UG,VPID TSC: P-state invariant, > > > > > > > > performance statistics real memory = 4301258752 (4102 > > > > > > > > MB) avail memory = 1907572736 (1819 MB) Event timer > > > > > > > > "LAPIC" quality 600 ACPI APIC Table: > > > > > > > COREBOOT> > > > > > > > What does this mean ? Did you flashed coreboot ? > > > > > > > > > > > > This machine comes with it by default (my model was > > > > > > delivered with SeaBIOS 20131018_145217-build121-m2). So I > > > > > > didn't flash anything (didn't feel like bricking it). > > > > > > > > > > > > > > > > > > > > > kernel trap 12 with interrupts disabled > > > > > > > > > > > > > > > > Fatal trap 12: page fault while in kernel mode > > > > > > > > cpuid = 0; apic id = 00 > > > > > > > > fault virtual address = 0xfffff80001000000 > > > > > > > > fault code = supervisor write data, > > > > > > > > protection violation instruction pointer = > > > > > > > > 0x20:Oxffffffff8102955f stack pointer = > > > > > > > > 0x28:0xffffffff82a79be0 frame pointer = > > > > > > > > 0x28:0xffffffff82a79c10 code segment = base > > > > > > > > Ox0, limit Oxfffff, type Ox1b = DPL 0, pres 1, long 1, > > > > > > > > def32 0, gran 1 processor eflags = resume, IOPL > > > > > > > > = 0 current process = 0 () > > > > > > > > [ thread pid 0 tid 0 ] > > > > > > > > Stopped at native_start_all_aps+0x08f: movq > > > > > > > > %rax,(%rsi) > > > > > > > Look up the source line number for this address. > > > > > > > > > > > > > > > > > > > I guess that's sys/amd64/amd64/support.S line 854 (in > > > > > > rdmsr), called by native_start_all_aps. Any additional > > > > > > hints how I can track it down? > > > > > Why did you decided that this is rdmsr_safe() ? First, > > > > > native_start_all_aps() does not call rdmsr, second the ddb > > > > > report clearly indicates that the fault occured acessing DMAP > > > > > in native_start_all_aps(). > > > > > > > > > > Just look up the source line by the address > > > > > native_start_all_aps+0x08f. > > > > > > > > Okay, according to kgbd this should be here: > > > > > > > > https://svnweb.freebsd.org/base/head/sys/amd64/amd64/mp_machdep.c?revision=333368&view=markup#l369 > > > > > > > > 364 > > > > 365 /* Create the initial 1GB replicated page tables */ > > > > 366 for (i = 0; i < 512; i++) { > > > > 367 /* Each slot of the level 4 pages points to the > > > > same level 3 page */ 368 pt4[i] = > > > > (u_int64_t)(uintptr_t)(mptramp_pagetables + PAGE_SIZE); 369 > > > > pt4[i] |= PG_V | PG_RW | PG_U; 370 > > > > 371 /* Each slot of the level 3 pages points to the > > > > same level 2 page */ 372 pt3[i] = > > > > (u_int64_t)(uintptr_t)(mptramp_pagetables + (2 * PAGE_SIZE)); > > > > 373 pt3[i] |= PG_V | PG_RW | PG_U; 374 > > > > 375 /* The level 2 page slots are mapped with 2MB > > > > pages for 1GB. */ 376 pt2[i] = i * (2 * 1024 * 1024); > > > > 377 pt2[i] |= PG_V | PG_RW | PG_PS | PG_U; > > > > 378 } > > > > > > > > -m > > > You have fault on write due to read-only mapping of the portion of > > > the direct map, which maps the kernel text. It is consistent with > > > the faulting address. It is not clear if it is something new on > > > your machine, or before the kernel text was silently corrupted, > > > since ro protection is somewhat recent. > > > > > > It seems that mp_bootaddress() selected the bad place for the > > > bootstrap page tables. Even more, we do not include the kernel > > > text into the physmem[] array, so it is not clear how did it > > > happen. This code was also changed recently. > > > > > > Can you add the print of the physmap[] array somewhere before the > > > panic, to see what is the kernel idea of the available memory ? > > > It should be already done if you have serial console and set > > > debug.late_console tunable to 0. > > > > This is a sad little machine without any kind of serial console. > > > > Physmap looks like this after calling getmemsize(): > > > > [0]: 0x10000 > > [1]: 0x30000 > > [2]: 0x40000 > > [3]: 0x9e000 > > [4]: 0x100000 > > [5]: 0xf00000 > > [6]: 0x1003000 > > [7]: 0x7bf7a000 > > > > Physical memory chunks logged in cpu_startup are: > > > > 0x0000000000010000 - 0x000000000002ffff, 141072 bytes (32 pages) > > 0x0000000000040000 - 0x000000000009dfff, 385024 bytes (94 pages) > These two chunks reports are consistent with the physmap[0-1, 2-3]. > > > 0x0000000000100000 - 0x00000000001fffff, 1048576 bytes (256 pages) > > 0x0000000002c00000 - 0x0000000075467fff, 1921417216 bytes (469096 > > pages) 0x0000000100000000 - 0x00000001005e7fff, 6193152 bytes (1512 > > pages) > But these three looks completely unrelated to the rest of the physmap, > perhaps except the physmap[4]. We allocate boot pages from the top > of the last physmap chunk, but I am certain that we do not consume > that much memory for boot to make physmap[7] from the last reported > address. > > Are you sure that there are no typos in the values above ? Double checked the numbers. I changed it a bit more, so that debug output appears all on one page. Please see here for the results: https://gist.github.com/grembo/cebb9f7e2a98c37a51bee1e508f7d890 This is how I generated the output: Index: sys/amd64/amd64/machdep.c =================================================================== --- sys/amd64/amd64/machdep.c (revision 333992) +++ sys/amd64/amd64/machdep.c (working copy) @@ -1215,7 +1215,7 @@ * XXX first should be vm_paddr_t. */ static void -getmemsize(caddr_t kmdp, u_int64_t first) +getmemsize(caddr_t kmdp, u_int64_t first, int* physmap_idx_out, vm_paddr_t* physmap_out) { int i, physmap_idx, pa_indx, da_indx; vm_paddr_t pa, physmap[PHYSMAP_SIZE]; @@ -1482,6 +1482,10 @@ /* Map the message buffer. */ msgbufp = (struct msgbuf *)PHYS_TO_DMAP(phys_avail[pa_indx]); + + *physmap_idx_out = physmap_idx; + for (int i=0; i Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E2B44FD1CB5 for ; Tue, 5 Jun 2018 05:27:49 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 574C480AE9; Tue, 5 Jun 2018 05:27:49 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-wm0-x233.google.com with SMTP id x6-v6so2317699wmc.3; Mon, 04 Jun 2018 22:27:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=nYYh4mDOKIR1NNQOowiH31IheE7cxySO2nn4ATo5RPA=; b=uN5H5mLS1SFThGLcd3fBp+M+HlQSqgbgAlX9D9oP3xkuATMTj7HIMzev69hm0OkAaY ICOUWXVyfugHGxGo+veBSOVndIlhxkc9uHiAo/8STUTCE8ZJuYaIsVaalu5LvBli+BsD 2FdCd//wKDJCdvWbxAnKRX9sN2FYSPPgwI7RMeajQn2dqgv188mhfsPpabDW2APBKjED oTGQWltnVoJQg6TsNhdmarKMbY4KMdXrlHZ15M+0IKqG3zz3baIbAf2qTDOLig63qnqi UUNCoHbrNhy/eyLZiyPau7hy+Yw1SzOMDLkMxbOC4giEmthuYNT8MAADC0CbmQCrrnf7 IACQ== 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=nYYh4mDOKIR1NNQOowiH31IheE7cxySO2nn4ATo5RPA=; b=j4rkOeBRa+hm6YCi1Pi1PqMQ4811x333yHOm+AgEPghrrJm/sPcD4m+dkl9kFHQWTH XmsuRfuywx0wU2Dipwr2cGZVtn2EWknXw1jRwMeMCkVJ7zNUf7ph/6aZhjhgN/aeGzCZ siD8lI1TAz83d/eokuJmUe+mzeS3FfonI8fpR7YFoauyCPj1cvVFIHbuIe7AeI7r+/w2 jtgLzkkLVDw3lLqh602sosvn5zvKwWroLdu5d7pUKUfKOwkCaZwQxSP3da6VYi7Ee64z nhNlPOSADANwQ3YFTF4WRcQTS1CJKlSM7CjfE9THbRG/Q01VDCc27gwSPr9YJOG0VP68 cPdg== X-Gm-Message-State: APt69E1GyhBOTTrAh6Pxs4Esxpunlkpobqqm1IFtmo2/YNueU67nCd17 QubxIifWuXYaHIqwucZq2a6bzOlQS10k0slxZng= X-Google-Smtp-Source: ADUXVKJghUGnE7/d/XojXFP2AOr6s0EsO1DeAzPdj7w3rTvFdk2bYiF5xw+BZocpVt5O5SksCnUOKYO7H1Ani/FjmCg= X-Received: by 2002:a1c:110a:: with SMTP id 10-v6mr4748880wmr.130.1528176467867; Mon, 04 Jun 2018 22:27:47 -0700 (PDT) MIME-Version: 1.0 References: <20180524160234.GD68014@FreeBSD.org> <201805241610.w4OGAAGY041280@pdx.rh.CN85.dnsmgr.net> <20180530235156.310870d0@thor.intern.walstatt.dynvpn.de> <20180531101643.GV3789@kib.kiev.ua> In-Reply-To: From: Adrian Chadd Date: Mon, 4 Jun 2018 22:27:35 -0700 Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: Kip Macy Cc: jmaloney@ixsystems.com, Daniel Eischen , Kostik Belousov , Johannes Lundberg , freebsd-current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2018 05:27:50 -0000 Hi, If there's an API that isn't being used then great, I'll go find it and fix up pieces in my spare time to use it. But the last drive by cut/paste didn't do that; it just changed the code in place. :-) -adrian From owner-freebsd-current@freebsd.org Tue Jun 5 06:13:32 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CD5F3FDF34E for ; Tue, 5 Jun 2018 06:13:32 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic309-15.consmr.mail.bf2.yahoo.com (sonic309-15.consmr.mail.bf2.yahoo.com [74.6.129.125]) (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 7273982D31 for ; Tue, 5 Jun 2018 06:13:32 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: P4DuEqoVM1lvLrc00rcZ3Uji9BYFnQXRlDbhkM6tXZ7vlm3kgSY.6Avm_ngAWes BWozmLSico0v4tkW.ai6bIzS2R6Le0wH9AW1ZbD0rb5xySRol5WNPskXvLiFjxCX2yKX5gqJnBxn _AK5mYmj2UXsvfNAgmQMPM1bOuPQUmOhFxZNvcnp1wNRgo18vUGPPi5cHkmhXDciKhSADUGHH_dU jQvRoYaOGi5tJYQ2sMr3JWjy7qM_k_c7eg8Xz1MIU0YN_wJphz0koNMp9WNZ7kZF9hOfPEhNjMmw Dw7fGNJ1scwwfrYWG.x9_enm7HZssI3Dzn0zFojkcjJnTZce34RLT8lLMsw2IUiHeeys8Qrfs0iM HviT8dfht8Du1UorPuIe.ZHWQ_.9UQXEkT5hTQyIMPebwfPexWiVq3OCE4sZkJL.8mfG3Iria00S VA3uWU1IsKyzdHbgcpKS8xcEEI0ktXczJ.qU59YcF_IyIBTJGIoD8dZ7l9O6PKS88QBfc0_rEu77 sczzsNvXG0fZn6Q0TIN0LqSBE2d2RsS6Z8sZ6ATPEmAt2qET3DdGx.7PPq2uCd4vpBFWqQD2io1F h5WT9D2ozI0O.Vx.SNBpUfbr8zJkWOGBCyHCzWOCiT1POzqEaq6RnCY3ETZStWJcxFufeF0qYEzn 09PQ0Ucer1miH7J0JFGY5g5D0Y5t3M3Vwl4mvISTbKYY.ICoOcA1K1_BhijtSv.aS_.0_OSYKQax NAygMu8qaIwF5I68REpK5FeYBZ_ADCvg.gcybI4zvciYVpNllrwjwB_HEjMaSB000D.pPVcdvXxd dIXsnh_RGWHtV7vyjCpQJyYqTMcKDDwDGbyArOnwA3fbw_GQ8ZsKOlwqmPC_8t1mgNkOi8oL6UVO FhmbQZsPq3H_Ap1vKC9gNzAgOlzXq2HgTCEs.NI7U_NJxPZVW9f7iHo3iVZ.QqABz Received: from sonic.gate.mail.ne1.yahoo.com by sonic309.consmr.mail.bf2.yahoo.com with HTTP; Tue, 5 Jun 2018 06:13:26 +0000 Received: from ip70-189-131-151.lv.lv.cox.net (EHLO [192.168.0.109]) ([70.189.131.151]) by smtp418.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 3e73c57f710c39fcb84ed8cdb9e60688; Tue, 05 Jun 2018 06:13:24 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: Re: svn commit: r334626 - in head: . . . [brk_test fails to build for aarch64 and stops build: no brk or sbrk to test, so undefined symbols] Message-Id: <1731A84F-4278-43F5-B498-C3501081E783@yahoo.com> Date: Mon, 4 Jun 2018 23:13:22 -0700 To: Mark Johnston , freebsd-arm@freebsd.org, FreeBSD Current X-Mailer: Apple Mail (2.3445.8.2) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2018 06:13:33 -0000 =46rom ci.freebsd.org for a -r334626 + builds: --- brk_test.full --- cc -target aarch64-unknown-freebsd12.0 = --sysroot=3D/usr/obj/usr/src/arm64.aarch64/tmp = -B/usr/obj/usr/src/arm64.aarch64/tmp/usr/bin -O2 -pipe -g = -std=3Diso9899:1999 -fstack-protector-strong -Wsystem-headers -Werror = -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign = -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable = -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality = -Wno-unused-function -Wno-enum-conversion -Wno-unused-local-typedef = -Wno-address-of-packed-member -Wno-switch -Wno-switch-enum = -Wno-knr-promoted-parameter -Qunused-arguments -o brk_test.full = brk_test.o -lprivateatf-c /usr/obj/usr/src/arm64.aarch64/tmp/usr/bin/ld: error: undefined symbol: = brk >>> referenced by brk_test.c:52 = (/usr/src/lib/libc/tests/sys/brk_test.c:52) >>> brk_test.o:(atfu_brk_basic_body) /usr/obj/usr/src/arm64.aarch64/tmp/usr/bin/ld: error: undefined symbol: = sbrk >>> referenced by brk_test.c:55 = (/usr/src/lib/libc/tests/sys/brk_test.c:55) >>> brk_test.o:(atfu_brk_basic_body) . . . (and many more) . . . =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Tue Jun 5 05:36:59 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 44C47FD48B5 for ; Tue, 5 Jun 2018 05:36:59 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: from mail-it0-x232.google.com (mail-it0-x232.google.com [IPv6:2607:f8b0:4001:c0b::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C97CC814D0; Tue, 5 Jun 2018 05:36:58 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: by mail-it0-x232.google.com with SMTP id 144-v6so1911639iti.5; Mon, 04 Jun 2018 22:36:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=wFVOsIYKjOhKg4npPFdtVPRm9Fh9rD/Dgcp0+6a5wfs=; b=befQP4TNwRPADZnOSdWJ1vepg850fUGnnmOTallvKfp5q6308FxJtCr12+rRC5/miN xniuTqyWnJso5CqN4SQ5wBlv5ohQJQMHBqMUsjRSoEEv+imUBKnEy/t3K8cK5W7Epp5D g+QF4kzoYSk0WQXGL4D4iGBrxRT786H27N2x4tYF2S8yQ6aGN7bdszuECxaMWD3wERNb D75sGe0sfzGbgExS0W+SQDkwpJj/2cA2mE1aNWBr/1UUb0Dkf+xG/VRBlNM1ZBhGL3g1 VlTaND+mEKy2D9eghJmY68Va8/Kiz6MHK+Rtgo9K2UoMm6pjhSob7JiQN2HdOygGgpQH WF+A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=wFVOsIYKjOhKg4npPFdtVPRm9Fh9rD/Dgcp0+6a5wfs=; b=g2pTaqO1RWnbfZdu3EIxYiWmtUOIB40M87Z7Eqyq9Xql2t8sBQC6VVnzRSmeAePhMj X8wfubWIlLCy94KQRMy6SpFV7UsEcHvln6SPbHd0OFrpEro39VuJi8sqjCb3nnIzR4Zl dc2vL0HRUS8z0P0P1Ik/tCMyY7q15hsiBRdxHWTlWMjD46SrW4xCqb2korUzUmm4EHeE JdoYHguwgS1+ONVNv3s4V+Qvwgna2s5ynTruDzRy7vcrfZ2b3fdk++D4yOBLw/h/Nl1H pgSKYWWrLN4pLLhjgb2L3UCxO/XNu/V1odEftQfTyK+TRd0P6BWY2di1oCzf06qe2rJg U0QA== X-Gm-Message-State: APt69E0UOCt0+UriEDT/uP4K28BOr705h5ls3zxKU9FjEWdxCq8dPfO1 DTPwhI2iRM6WbEQ4FdGpc7jfdE5xZjopQrg0NoM= X-Google-Smtp-Source: ADUXVKKArbS53sqVk4wdOB0C8RiZXbgKOxV6/Nwm3Et+x9kNldmaS8m2ltXLPAKyrMw/35JjWK142t0AZM5aYxBwsnw= X-Received: by 2002:a24:459f:: with SMTP id c31-v6mr10392167itd.132.1528177018078; Mon, 04 Jun 2018 22:36:58 -0700 (PDT) MIME-Version: 1.0 References: <20180524160234.GD68014@FreeBSD.org> <201805241610.w4OGAAGY041280@pdx.rh.CN85.dnsmgr.net> <20180530235156.310870d0@thor.intern.walstatt.dynvpn.de> <20180531101643.GV3789@kib.kiev.ua> In-Reply-To: From: Matthew Macy Date: Mon, 4 Jun 2018 22:36:47 -0700 Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: Adrian Chadd Cc: Daniel Eischen , Johannes Lundberg , Kostik Belousov , freebsd-current , jmaloney@ixsystems.com X-Mailman-Approved-At: Tue, 05 Jun 2018 10:25:38 +0000 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2018 05:36:59 -0000 Implementing a callback in 140 different files for the sake of a handful of out of tree drivers and people not reading updating is pretty prohibitive. 11 may be more your cup of tea. On Mon, Jun 4, 2018 at 22:27 Adrian Chadd wrote: > Hi, > > If there's an API that isn't being used then great, I'll go find it > and fix up pieces in my spare time to use it. But the last drive by > cut/paste didn't do that; it just changed the code in place. :-) > > > > -adrian > From owner-freebsd-current@freebsd.org Tue Jun 5 12:02:35 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2A747FF0C86 for ; Tue, 5 Jun 2018 12:02:35 +0000 (UTC) (envelope-from ian.freislich@capeaugusta.com) Received: from mail-qk0-x22c.google.com (mail-qk0-x22c.google.com [IPv6:2607:f8b0:400d:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BBDDC731E6 for ; Tue, 5 Jun 2018 12:02:34 +0000 (UTC) (envelope-from ian.freislich@capeaugusta.com) Received: by mail-qk0-x22c.google.com with SMTP id g14-v6so1276367qkm.6 for ; Tue, 05 Jun 2018 05:02:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=capeaugusta-com.20150623.gappssmtp.com; s=20150623; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=dt8ZUF6wJqYdgSd9GAUgWbw6kKlddcBXsEfSqxZYG5E=; b=tL/6W1k/4NNUxTi/UPusGCpQKL2ie9aHECYua4BC/cp738+MrljXhwO9nD9oOeKwLC SM3WIE8CzNraXF7KdLnMWk3TE/IPwFIgRgFZohdYsSpjAqZ+SsLxSn7r+qUbnmGzFf60 GqIG1cinpxkuVDzaB1bT+6a2Z8gEjpM7EQbdRokmRwOBV8uoB7ewt3IpK8kieuCcSeqf Ju6R1cBs1uqwvnppX+0/6YPIUVfKA2FC8uXCLKLaKxi8bWL/u3UgB9+okis41zni3zWm fIjf6ySAsISN2nM9QgJm7BN7dku5LXmvO43VGkJN27iqIm74ZuuFMuqz4a64IWZkt7hp C42Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=dt8ZUF6wJqYdgSd9GAUgWbw6kKlddcBXsEfSqxZYG5E=; b=UQzm2vtTM3NT2v9p4P/B3cYQ0cbDrHSnWE5X7EOk2PrTSkGU89NAc24X4zk0yIh9pm MvhA9TzoQPdIKoYls9xwDRc2KTWjuwkj2a7Miq+SGwAf3ovMlPRQSWwVjOjue/hCO6Pr ylZ9nf4Vm0rLQOCPuACrQERH2G7HfF3IzMQLq3+f4Q1NTCQ6rtzZHD4JnKRsW/9CKm9E Q9hPEEw205Q6XJXWOgkekA4SpIsOfIV/NnfdZnJF1wTyEglfPsY3rkgBHbq2Q3IPiHP3 BoKhrBRX4hW89hmyNpr8VFNFwYQM/ZmFWEPGYyyNLsM1OMo0xhLKOQs2wvu5eeibrpUD M7lA== X-Gm-Message-State: APt69E3D7OIdKUNuxfpgHQOgTdCFFdk3FtVCV5MPNolZcuSEAsyPfui6 lWj0c3Dhkb+mOqXJ/k3nOToYxk/K32a3LLVMHpK/J/8QUR2+pJkgjw0j/wYi0aDgNPVxDwCLW7x eW5DEM72a+jgvb/qK X-Google-Smtp-Source: ADUXVKI23E1kqIhdl7CqcfhTfUuc3/LS7vm60Qk5FbSBtt71jKIATh1ZEkiDWI1t7Rocjp++VufPJg== X-Received: by 2002:a37:7d1:: with SMTP id 200-v6mr23192261qkh.393.1528200154059; Tue, 05 Jun 2018 05:02:34 -0700 (PDT) Received: from [10.0.11.220] ([64.53.114.237]) by smtp.gmail.com with ESMTPSA id e96-v6sm24836099qtb.69.2018.06.05.05.02.33 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 05 Jun 2018 05:02:33 -0700 (PDT) Subject: Re: uchcom update To: freebsd-usb@freebsd.org, FreeBSD Current Cc: freebsd-stable List References: From: Ian FREISLICH Message-ID: <83f7a6dd-5d7e-cfd2-e580-4db0c7134220@capeaugusta.com> Date: Tue, 5 Jun 2018 08:02:32 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: quoted-printable Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2018 12:02:35 -0000 On 05/22/2018 09:44 AM, Andriy Gapon wrote: > Yesterday I committed some changes to uchcom (so far, only in CURRENT). > Commits are r333997 - r334002. > > If you have a CH340/341 based USB<->RS232 adapter and it works for you, c= ould > you please test that it still does? > If you tried your adapter in the past and it did not work, there is a cha= nce it > might start working now. Could you please test that as well? ugen5.4: at usbus5, cfg=3D0 md=3DHOST spd=3DF= ULL=20 (12Mbps) pwr=3DON (96mA) ugen5.4.0: uchcom0: It's not made it any worse.=C2=A0 I'm not using this adapter by choice - it= 's=20 a USB to Maxim (Dallas) one-wire bus adapter.=C2=A0 The manual used to stat= e=20 that these are possibly the worst chips ever.=C2=A0 Is that still the=20 prevailing opinion? Ian --=20 From owner-freebsd-current@freebsd.org Tue Jun 5 12:09:33 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6A9F4FF2056; Tue, 5 Jun 2018 12:09:33 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D047C739CC; Tue, 5 Jun 2018 12:09:32 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id QAmAflFl45wO5QAmBfGBCb; Tue, 05 Jun 2018 06:09:25 -0600 X-Authority-Analysis: v=2.3 cv=SJtsqtnH c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=kj9zAlcOel0A:10 a=7mUfYlMuFuIA:10 a=CjxXgO3LAAAA:8 a=6I5d2MoRAAAA:8 a=YVOhz5M6AAAA:8 a=YxBL1-UpAAAA:8 a=ZEMpZlOG56c5PBaKjhMA:9 a=CjuIK1q_8ugA:10 a=IjZwj45LgO3ly-622nXo:22 a=sbbTL3E6IKcx-RquDtO-:22 a=Ia-lj3WSrqcvXOmTRaiG:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id 2F10DFB3; Tue, 5 Jun 2018 05:09:22 -0700 (PDT) Received: from slippy.cwsent.com (localhost [127.0.0.1]) by slippy.cwsent.com (8.15.2/8.15.2) with ESMTP id w55C9LrC039973; Tue, 5 Jun 2018 05:09:21 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Received: from slippy (cy@localhost) by slippy.cwsent.com (8.15.2/8.15.2/Submit) with ESMTP id w55C9L7f039970; Tue, 5 Jun 2018 05:09:21 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <201806051209.w55C9L7f039970@slippy.cwsent.com> X-Authentication-Warning: slippy.cwsent.com: cy owned process doing -bs X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Mark Millard cc: Mark Johnston , freebsd-arm@freebsd.org, FreeBSD Current Subject: Re: svn commit: r334626 - in head: . . . [brk_test fails to build for aarch64 and stops build: no brk or sbrk to test, so undefined symbols] In-Reply-To: Message from Mark Millard of "Mon, 04 Jun 2018 23:13:22 -0700." <1731A84F-4278-43F5-B498-C3501081E783@yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 05 Jun 2018 05:09:21 -0700 X-CMAE-Envelope: MS4wfKvYY+ujjVIWz030aqspTWwRuyF5xXXg9BttUMV2QhdbImSFKldFZ481mGKXRYCWpayEEyMUDUwp0wKMHDUpwlqUHKnwkqz+kluzS8NZ1Is2bE87tVF+ eUauEorscDqTEW3nAFMq5CpSArrhUJxjsFwNvxEISvYmYF0LBql4PP24sjcAclnobD7NYQUB0Bp6dHadDbqY9NI7W1yhIRLfbpd9JAfXr1sid/Jq6SDNnQq1 wmJRLeQAuwZtYLWMt8jq3rxmbPAejgV2a1oc+iP0LIc= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2018 12:09:33 -0000 In message <1731A84F-4278-43F5-B498-C3501081E783@yahoo.com>, Mark Millard write s: > >From ci.freebsd.org for a -r334626 + builds: > > --- brk_test.full --- > cc -target aarch64-unknown-freebsd12.0 --sysroot=/usr/obj/usr/src/arm64.aarch > 64/tmp -B/usr/obj/usr/src/arm64.aarch64/tmp/usr/bin -O2 -pipe -g -std=iso9899 > :1999 -fstack-protector-strong -Wsystem-headers -Werror -Wall -Wno-format-y2k > -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -W > no-unused-const-variable -Wno-tautological-compare -Wno-unused-value -Wno-par > entheses-equality -Wno-unused-function -Wno-enum-conversion -Wno-unused-local > -typedef -Wno-address-of-packed-member -Wno-switch -Wno-switch-enum -Wno-knr- > promoted-parameter -Qunused-arguments -o brk_test.full brk_test.o -lprivat > eatf-c > /usr/obj/usr/src/arm64.aarch64/tmp/usr/bin/ld: error: undefined symbol: brk > >>> referenced by brk_test.c:52 (/usr/src/lib/libc/tests/sys/brk_test.c:52) > >>> brk_test.o:(atfu_brk_basic_body) > > /usr/obj/usr/src/arm64.aarch64/tmp/usr/bin/ld: error: undefined symbol: sbrk > >>> referenced by brk_test.c:55 (/usr/src/lib/libc/tests/sys/brk_test.c:55) > >>> brk_test.o:(atfu_brk_basic_body) > > . . . (and many more) . . . Do a clean build or remove the libc directory from /usr/obj, then do your build. > > === > Mark Millard > marklmi at yahoo.com > ( dsl-only.net went > away in early 2018-Mar) -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. From owner-freebsd-current@freebsd.org Tue Jun 5 12:35:58 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0A390FF608A for ; Tue, 5 Jun 2018 12:35:58 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic311-13.consmr.mail.bf2.yahoo.com (sonic311-13.consmr.mail.bf2.yahoo.com [74.6.131.123]) (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 A33DA752C2 for ; Tue, 5 Jun 2018 12:35:57 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: mpgkS9kVM1nVjP4oNNl9tvAnwWF.9fB87iiIPwlAvG34t5slLw_1ky6AjVt0WBy RIAxl3YxwHwuMtww4r1wrU15a0MsoBWlolK5bgSlqlFNV6TkuJPOz03yOAKtEP0VWa0upxcZojXC mRguJS7N05zUnOjMpBhBVUdIUVqOkCV7N9yz1WDLTxiuQCK6q7q.Gs6bVx._qZ2g5EhW2WcfdliV hlaqdEzFviriek1q9e3I4cBhOkiQlkqfKiKW5Jr7HcarenGulWJUkII9vZyD80jkIV82N0zQ_LxN QLSrao3obGJmg3lLx8XwDEOWOKhO6X7fb2t1EDO7_ede8Q3jcHkqXbEsBGQBF11ufsg1A4NgYBx9 1zo6ganlWG1K8RaYI7.oDXFl_hDR6UMsxLCYQLr56A2_o4Z.wAa0HHIfZ2TBAfMrrG9Liv1w1bRz 6L8rVG0C8Jj12wAbNG0CMBoegRtIOPijk1LtiOgtz5UkBhyT7lRa2jgXwpD4sWgHjaLV8NU5U5zZ xtQ2p5TLmgiSvP401LYHojFM8Bl3vLiDJDtVyCLHS2QAITWHfjGirjJOAy6jtXAf6p0RO1FKCqB9 zkfcbN6AT.l.iADvgKfLC8pqppWYXYvkavTOGGhT0U08PG2JnO_g9f7KKwqFzr16cdUXGtfaGNA9 f0WME24uynSOZVrBz.S4Iv6LACaLQn.N3NsCnZCMr.k94bhdxKmQVosdv6gQzsk2lTv2Uo_MlkId xJvfLlHZrEMoWhAOrlw_ctFJ149uRZEY0xc4Z4B2tx49e6KU2.0BR.aW8lA6hWC76Ew4EnjIoraR 7e2y_MWU_fXcctw9mNbIX60WwTnSKfMUbBKd2_wXM8v34FZdvp1eVX8H6Kq9vr0ef3siV1HLUf3N 4mbeJpq_0zhON4hrkZbUybvRPMjLZqFfYiTTitnRNDKYIzB8HV6uiFrdtwlABi_OgBg-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic311.consmr.mail.bf2.yahoo.com with HTTP; Tue, 5 Jun 2018 12:35:56 +0000 Received: from ip70-189-131-151.lv.lv.cox.net (EHLO [192.168.0.109]) ([70.189.131.151]) by smtp432.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 7d34dac76abd681352c908d9f484ef9a; Tue, 05 Jun 2018 12:35:52 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: Re: svn commit: r334626 - in head: . . . [brk_test fails to build for aarch64 and stops build: no brk or sbrk to test, so undefined symbols] From: Mark Millard In-Reply-To: <201806051209.w55C9L7f039970@slippy.cwsent.com> Date: Tue, 5 Jun 2018 05:35:50 -0700 Cc: Mark Johnston , freebsd-arm@freebsd.org, FreeBSD Current Content-Transfer-Encoding: quoted-printable Message-Id: References: <201806051209.w55C9L7f039970@slippy.cwsent.com> To: Cy Schubert X-Mailer: Apple Mail (2.3445.8.2) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2018 12:35:58 -0000 On 2018-Jun-5, at 5:09 AM, Cy Schubert = wrote: > In message <1731A84F-4278-43F5-B498-C3501081E783@yahoo.com>, Mark=20 > Millard write > s: >>> =46rom ci.freebsd.org for a -r334626 + builds: >>=20 >> --- brk_test.full --- >> cc -target aarch64-unknown-freebsd12.0 = --sysroot=3D/usr/obj/usr/src/arm64.aarch >> 64/tmp -B/usr/obj/usr/src/arm64.aarch64/tmp/usr/bin -O2 -pipe -g = -std=3Diso9899 >> :1999 -fstack-protector-strong -Wsystem-headers -Werror -Wall = -Wno-format-y2k >> -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body = -Wno-string-plus-int -W >> no-unused-const-variable -Wno-tautological-compare -Wno-unused-value = -Wno-par >> entheses-equality -Wno-unused-function -Wno-enum-conversion = -Wno-unused-local >> -typedef -Wno-address-of-packed-member -Wno-switch -Wno-switch-enum = -Wno-knr- >> promoted-parameter -Qunused-arguments -o brk_test.full brk_test.o = -lprivat >> eatf-c >> /usr/obj/usr/src/arm64.aarch64/tmp/usr/bin/ld: error: undefined = symbol: brk >>>>> referenced by brk_test.c:52 = (/usr/src/lib/libc/tests/sys/brk_test.c:52) >>>>> brk_test.o:(atfu_brk_basic_body) >>=20 >> /usr/obj/usr/src/arm64.aarch64/tmp/usr/bin/ld: error: undefined = symbol: sbrk >>>>> referenced by brk_test.c:55 = (/usr/src/lib/libc/tests/sys/brk_test.c:55) >>>>> brk_test.o:(atfu_brk_basic_body) >>=20 >> . . . (and many more) . . . >=20 > Do a clean build or remove the libc directory from /usr/obj, then do=20= > your build. You missed the first line "=46rom ci.freebsd.org . . .": It was not my build, it was a ci.freebsd.org build of FreeBSD-head-aarch64-build . It was specifically #7944 (of -r334628 ) and later. The latest #7951 (of -r334651 ) is still broken the same way. #7943 (of -r334625 ) was the last good build. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Tue Jun 5 13:07:53 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7093FFD0DF6; Tue, 5 Jun 2018 13:07:53 +0000 (UTC) (envelope-from lwhsu.freebsd@gmail.com) Received: from mail-wm0-f68.google.com (mail-wm0-f68.google.com [74.125.82.68]) (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 E876C76DC6; Tue, 5 Jun 2018 13:07:52 +0000 (UTC) (envelope-from lwhsu.freebsd@gmail.com) Received: by mail-wm0-f68.google.com with SMTP id e16-v6so4828692wmd.0; Tue, 05 Jun 2018 06:07:52 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=KkC+bRowpioTBE4zI9XJYX/wDNbMwguRZjhQf667tro=; b=oIHOUgzcJ24dsf31xCegNsGFivV+WARmLYE/h6ApvlYE/EbjTcMMxPPsunbogZ7RtP Y8sRrWj3xe/W4eeri0tFtFhWRG9NiA3qFkSJsV+jIUZz3aGdW6dNXSGR8lUWpZb5X0kX pnBGEaeY2shXzKrwgOqrdCpovKE5QYFXQnBTGsxhbQncnLzZpi9STZI+EmrgUNbxCCO7 9isexaxS5c/WGh8y7I0Z0w/ErquqcfRWHg5ZtUMR+dT/E0bowUTyFRrCCHWpvH9mLhDI kBxRGdEkGP8TLLE4SqCsjpGRXtIw/cFp9a8quuRwAHvBm2v9crcUxVMLjIfZXbe3C3Y6 U4BA== X-Gm-Message-State: APt69E1Hc17/AMXieM8ejZlVyycc5pDF+zYxjAuwrvJC87HdxRUMsBmC JyO2w1ua/t/O8GLxACIXyRwYrNJYmIymYLDCcPvaBQ== X-Google-Smtp-Source: ADUXVKLkWcl9gll5CU7oZ/W9RQrHjJMe4o4qTNqYkjhkosAck4fLV1Hx6Vrz1q5LIPttg+AZmO5MbJvc97k9hi751us= X-Received: by 2002:a1c:ea4a:: with SMTP id i71-v6mr10040179wmh.158.1528204065615; Tue, 05 Jun 2018 06:07:45 -0700 (PDT) MIME-Version: 1.0 References: <1731A84F-4278-43F5-B498-C3501081E783@yahoo.com> <201806051209.w55C9L7f039970@slippy.cwsent.com> In-Reply-To: <201806051209.w55C9L7f039970@slippy.cwsent.com> From: Li-Wen Hsu Date: Tue, 5 Jun 2018 09:07:34 -0400 Message-ID: Subject: Re: svn commit: r334626 - in head: . . . [brk_test fails to build for aarch64 and stops build: no brk or sbrk to test, so undefined symbols] To: Cy Schubert Cc: FreeBSD Current , Mark Johnston , Mark Millard , freebsd-arm@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2018 13:07:53 -0000 On Tue, Jun 5, 2018 at 08:10 Cy Schubert wrote: > In message <1731A84F-4278-43F5-B498-C3501081E783@yahoo.com>, Mark > Millard write > s: > > >From ci.freebsd.org for a -r334626 + builds: > > > > --- brk_test.full --- > > cc -target aarch64-unknown-freebsd12.0 > --sysroot=/usr/obj/usr/src/arm64.aarch > > 64/tmp -B/usr/obj/usr/src/arm64.aarch64/tmp/usr/bin -O2 -pipe -g > -std=iso9899 > > :1999 -fstack-protector-strong -Wsystem-headers -Werror -Wall > -Wno-format-y2k > > -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body > -Wno-string-plus-int -W > > no-unused-const-variable -Wno-tautological-compare -Wno-unused-value > -Wno-par > > entheses-equality -Wno-unused-function -Wno-enum-conversion > -Wno-unused-local > > -typedef -Wno-address-of-packed-member -Wno-switch -Wno-switch-enum > -Wno-knr- > > promoted-parameter -Qunused-arguments -o brk_test.full brk_test.o > -lprivat > > eatf-c > > /usr/obj/usr/src/arm64.aarch64/tmp/usr/bin/ld: error: undefined symbol: > brk > > >>> referenced by brk_test.c:52 > (/usr/src/lib/libc/tests/sys/brk_test.c:52) > > >>> brk_test.o:(atfu_brk_basic_body) > > > > /usr/obj/usr/src/arm64.aarch64/tmp/usr/bin/ld: error: undefined symbol: > sbrk > > >>> referenced by brk_test.c:55 > (/usr/src/lib/libc/tests/sys/brk_test.c:55) > > >>> brk_test.o:(atfu_brk_basic_body) > > > > . . . (and many more) . . . > > Do a clean build or remove the libc directory from /usr/obj, then do > your build. Each build on ci.freebsd.org is a clean build from scratch. Li-Wen > -- Li-Wen Hsu https://lwhsu.org From owner-freebsd-current@freebsd.org Tue Jun 5 13:11:48 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E0053FD18C6 for ; Tue, 5 Jun 2018 13:11:47 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5781577289; Tue, 5 Jun 2018 13:11:47 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTP id w55DBaSx088275; Tue, 5 Jun 2018 16:11:39 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w55DBaSx088275 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w55DBZdm088274; Tue, 5 Jun 2018 16:11:35 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 5 Jun 2018 16:11:35 +0300 From: Konstantin Belousov To: Michael Gmelin Cc: "freebsd-current@freebsd.org" , Matthias Apitz , jhb@freebsd.org Subject: Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy) Message-ID: <20180605131135.GH2450@kib.kiev.ua> References: <20180603144840.44bfea41@bsd64.grem.de> <20180603132110.GP3789@kib.kiev.ua> <20180603165500.361ec894@bsd64.grem.de> <20180603150423.GQ3789@kib.kiev.ua> <20180603215020.452a81d8@bsd64.grem.de> <20180603205340.GS3789@kib.kiev.ua> <20180604004632.56ca6afa@bsd64.grem.de> <20180604110654.GA2450@kib.kiev.ua> <20180604231756.2ed2adb9@bsd64.grem.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180604231756.2ed2adb9@bsd64.grem.de> User-Agent: Mutt/1.10.0 (2018-05-17) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2018 13:11:48 -0000 On Mon, Jun 04, 2018 at 11:17:56PM +0200, Michael Gmelin wrote: > > > On Mon, 4 Jun 2018 14:06:55 +0300 > Konstantin Belousov wrote: > > > On Mon, Jun 04, 2018 at 12:46:32AM +0200, Michael Gmelin wrote: > > > > > > > > > On Sun, 3 Jun 2018 23:53:40 +0300 > > > Konstantin Belousov wrote: > > > > > > > On Sun, Jun 03, 2018 at 09:50:20PM +0200, Michael Gmelin wrote: > > > > > > > > > > > > > > > On Sun, 3 Jun 2018 18:04:23 +0300 > > > > > Konstantin Belousov wrote: > > > > > > > > > > > On Sun, Jun 03, 2018 at 04:55:00PM +0200, Michael Gmelin > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > On Sun, 3 Jun 2018 16:21:10 +0300 > > > > > > > Konstantin Belousov wrote: > > > > > > > > > > > > > > > On Sun, Jun 03, 2018 at 02:48:40PM +0200, Michael Gmelin > > > > > > > > wrote: > > > > > > > > > Hi, > > > > > > > > > > > > > > > > > > After upgrading CURRENT to r333992 (from something at > > > > > > > > > least a year old, quite some changes in mp_machdep.c > > > > > > > > > since), this machine crashes on boot: > > > > > > > > > > > > > > > > > > Copyright (c) 1992-2018 The FreeBSD Project. > > > > > > > > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, > > > > > > > > > 1992, 1993, 1994 The Regents of the University of > > > > > > > > > California. All rights reserved. FreeBSD is a registered > > > > > > > > > trademark of The FreeBSD Foundation. FreeBSD > > > > > > > > > 12.0-CURRENT #1 r333992: Tue May 22 00:31:04 CEST 2018 > > > > > > > > > root@flimsy:/usr/obj/usr/src/amd64.amd64/sys/flimsy > > > > > > > > > amd64 FreeBSD clang version 6.0.0 > > > > > > > > > (tags/RELEASE_600/final 326565) (based on LLVM 6.0.0) > > > > > > > > > WARNING: WITNESS option enabled, expect reduced > > > > > > > > > performance. VT(vga): resolution 640x480 CPU: Intel(R) > > > > > > > > > Celeron(R) 2955U @ 1.40GHz (1396.80-MHz K8-class CPU) > > > > > > > > > Origin="GenuineIntel" Id=0x40651 Family=0x6 > > > > > > > > > Model=0x45 Stepping=1 > > > > > > > > > Features=0xbfebfbff > > > > > > > > CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > > > > > > > > > Features2=0x4ddaebbf > > > > > > > > xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,TSCDLT,XSAVE,OSXSAVE,RDRAND> > > > > > > > > > AMD Features=0x2c100800 > > > > > > > > > AMD Features2=0x21 Structured Extended > > > > > > > > > Features=0x2603 > > > > > > > > > XSAVE Features=0x1 VT-x: (disabled in BIOS) > > > > > > > > > PAT,HLT,MTF,PAUSE,EPT,UG,VPID TSC: P-state invariant, > > > > > > > > > performance statistics real memory = 4301258752 (4102 > > > > > > > > > MB) avail memory = 1907572736 (1819 MB) Event timer > > > > > > > > > "LAPIC" quality 600 ACPI APIC Table: > > > > > > > > COREBOOT> > > > > > > > > What does this mean ? Did you flashed coreboot ? > > > > > > > > > > > > > > This machine comes with it by default (my model was > > > > > > > delivered with SeaBIOS 20131018_145217-build121-m2). So I > > > > > > > didn't flash anything (didn't feel like bricking it). > > > > > > > > > > > > > > > > > > > > > > > > kernel trap 12 with interrupts disabled > > > > > > > > > > > > > > > > > > Fatal trap 12: page fault while in kernel mode > > > > > > > > > cpuid = 0; apic id = 00 > > > > > > > > > fault virtual address = 0xfffff80001000000 > > > > > > > > > fault code = supervisor write data, > > > > > > > > > protection violation instruction pointer = > > > > > > > > > 0x20:Oxffffffff8102955f stack pointer = > > > > > > > > > 0x28:0xffffffff82a79be0 frame pointer = > > > > > > > > > 0x28:0xffffffff82a79c10 code segment = base > > > > > > > > > Ox0, limit Oxfffff, type Ox1b = DPL 0, pres 1, long 1, > > > > > > > > > def32 0, gran 1 processor eflags = resume, IOPL > > > > > > > > > = 0 current process = 0 () > > > > > > > > > [ thread pid 0 tid 0 ] > > > > > > > > > Stopped at native_start_all_aps+0x08f: movq > > > > > > > > > %rax,(%rsi) > > > > > > > > Look up the source line number for this address. > > > > > > > > > > > > > > > > > > > > > > I guess that's sys/amd64/amd64/support.S line 854 (in > > > > > > > rdmsr), called by native_start_all_aps. Any additional > > > > > > > hints how I can track it down? > > > > > > Why did you decided that this is rdmsr_safe() ? First, > > > > > > native_start_all_aps() does not call rdmsr, second the ddb > > > > > > report clearly indicates that the fault occured acessing DMAP > > > > > > in native_start_all_aps(). > > > > > > > > > > > > Just look up the source line by the address > > > > > > native_start_all_aps+0x08f. > > > > > > > > > > Okay, according to kgbd this should be here: > > > > > > > > > > https://svnweb.freebsd.org/base/head/sys/amd64/amd64/mp_machdep.c?revision=333368&view=markup#l369 > > > > > > > > > > 364 > > > > > 365 /* Create the initial 1GB replicated page tables */ > > > > > 366 for (i = 0; i < 512; i++) { > > > > > 367 /* Each slot of the level 4 pages points to the > > > > > same level 3 page */ 368 pt4[i] = > > > > > (u_int64_t)(uintptr_t)(mptramp_pagetables + PAGE_SIZE); 369 > > > > > pt4[i] |= PG_V | PG_RW | PG_U; 370 > > > > > 371 /* Each slot of the level 3 pages points to the > > > > > same level 2 page */ 372 pt3[i] = > > > > > (u_int64_t)(uintptr_t)(mptramp_pagetables + (2 * PAGE_SIZE)); > > > > > 373 pt3[i] |= PG_V | PG_RW | PG_U; 374 > > > > > 375 /* The level 2 page slots are mapped with 2MB > > > > > pages for 1GB. */ 376 pt2[i] = i * (2 * 1024 * 1024); > > > > > 377 pt2[i] |= PG_V | PG_RW | PG_PS | PG_U; > > > > > 378 } > > > > > > > > > > -m > > > > You have fault on write due to read-only mapping of the portion of > > > > the direct map, which maps the kernel text. It is consistent with > > > > the faulting address. It is not clear if it is something new on > > > > your machine, or before the kernel text was silently corrupted, > > > > since ro protection is somewhat recent. > > > > > > > > It seems that mp_bootaddress() selected the bad place for the > > > > bootstrap page tables. Even more, we do not include the kernel > > > > text into the physmem[] array, so it is not clear how did it > > > > happen. This code was also changed recently. > > > > > > > > Can you add the print of the physmap[] array somewhere before the > > > > panic, to see what is the kernel idea of the available memory ? > > > > It should be already done if you have serial console and set > > > > debug.late_console tunable to 0. > > > > > > This is a sad little machine without any kind of serial console. > > > > > > Physmap looks like this after calling getmemsize(): > > > > > > [0]: 0x10000 > > > [1]: 0x30000 > > > [2]: 0x40000 > > > [3]: 0x9e000 > > > [4]: 0x100000 > > > [5]: 0xf00000 > > > [6]: 0x1003000 > > > [7]: 0x7bf7a000 > > > > > > Physical memory chunks logged in cpu_startup are: > > > > > > 0x0000000000010000 - 0x000000000002ffff, 141072 bytes (32 pages) > > > 0x0000000000040000 - 0x000000000009dfff, 385024 bytes (94 pages) > > These two chunks reports are consistent with the physmap[0-1, 2-3]. > > > > > 0x0000000000100000 - 0x00000000001fffff, 1048576 bytes (256 pages) > > > 0x0000000002c00000 - 0x0000000075467fff, 1921417216 bytes (469096 > > > pages) 0x0000000100000000 - 0x00000001005e7fff, 6193152 bytes (1512 > > > pages) > > But these three looks completely unrelated to the rest of the physmap, > > perhaps except the physmap[4]. We allocate boot pages from the top > > of the last physmap chunk, but I am certain that we do not consume > > that much memory for boot to make physmap[7] from the last reported > > address. > > > > Are you sure that there are no typos in the values above ? > > Double checked the numbers. I changed it a bit more, > so that debug output appears all on one page. Please see here for the > results: > > https://gist.github.com/grembo/cebb9f7e2a98c37a51bee1e508f7d890 Ok, I have a guess what is going on. Does the result of the quirks end up as hw.physmem tunable passed to kernel ? It seems that there is physmap[] element pointing outside the DMAP-mapped region. Perhaps print the dmap limit too, to see whether I am on the right track. Try the following change. It lacks i386 bits. diff --git a/sys/amd64/amd64/machdep.c b/sys/amd64/amd64/machdep.c index e5c69ed91fa..bd6bbf04006 100644 --- a/sys/amd64/amd64/machdep.c +++ b/sys/amd64/amd64/machdep.c @@ -1254,7 +1254,7 @@ getmemsize(caddr_t kmdp, u_int64_t first) * in real mode mode (e.g. SMP bare metal). */ if (init_ops.mp_bootaddress) - init_ops.mp_bootaddress(physmap, &physmap_idx); + init_ops.mp_bootaddress(physmap, &physmap_idx, first); /* * Maxmem isn't the "maximum memory", it's one larger than the diff --git a/sys/amd64/amd64/mp_machdep.c b/sys/amd64/amd64/mp_machdep.c index 30146142087..292a6cefa91 100644 --- a/sys/amd64/amd64/mp_machdep.c +++ b/sys/amd64/amd64/mp_machdep.c @@ -103,7 +103,8 @@ static int start_ap(int apic_id); * Calculate usable address in base memory for AP trampoline code. */ void -mp_bootaddress(vm_paddr_t *physmap, unsigned int *physmap_idx) +mp_bootaddress(vm_paddr_t *physmap, unsigned int *physmap_idx, + vm_paddr_t dmap_limit) { unsigned int i; bool allocated; @@ -117,8 +118,9 @@ mp_bootaddress(vm_paddr_t *physmap, unsigned int *physmap_idx) * store the initial page tables. Note that it needs to be * aligned to a page boundary. */ - if (physmap[i] >= GiB(4) || - (physmap[i + 1] - round_page(physmap[i])) < (PAGE_SIZE * 3)) + if (physmap[i] >= GiB(4) || physmap[i + 1] - + round_page(physmap[i]) < PAGE_SIZE * 3 || + physmap[i + 1] - PAGE_SIZE * 3 > dmap_limit) continue; allocated = true; diff --git a/sys/amd64/include/smp.h b/sys/amd64/include/smp.h index 2ecfe62cf9f..24f0580fe51 100644 --- a/sys/amd64/include/smp.h +++ b/sys/amd64/include/smp.h @@ -58,7 +58,7 @@ void invlpg_pcid_handler(void); void invlrng_invpcid_handler(void); void invlrng_pcid_handler(void); int native_start_all_aps(void); -void mp_bootaddress(vm_paddr_t *, unsigned int *); +void mp_bootaddress(vm_paddr_t *, unsigned int *, vm_paddr_t); #endif /* !LOCORE */ #endif /* SMP */ diff --git a/sys/x86/include/init.h b/sys/x86/include/init.h index 880cabaa949..58bbe0a5fd6 100644 --- a/sys/x86/include/init.h +++ b/sys/x86/include/init.h @@ -41,7 +41,7 @@ struct init_ops { void (*early_clock_source_init)(void); void (*early_delay)(int); void (*parse_memmap)(caddr_t, vm_paddr_t *, int *); - void (*mp_bootaddress)(vm_paddr_t *, unsigned int *); + void (*mp_bootaddress)(vm_paddr_t *, unsigned int *, vm_paddr_t); int (*start_all_aps)(void); void (*msi_init)(void); }; From owner-freebsd-current@freebsd.org Tue Jun 5 13:42:34 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4B2CBFDCB8C; Tue, 5 Jun 2018 13:42:34 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9D83779063; Tue, 5 Jun 2018 13:42:33 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id QCEHflwCz5wO5QCEJfGMY6; Tue, 05 Jun 2018 07:42:31 -0600 X-Authority-Analysis: v=2.3 cv=SJtsqtnH c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=kj9zAlcOel0A:10 a=7mUfYlMuFuIA:10 a=xfDLHkLGAAAA:8 a=YxBL1-UpAAAA:8 a=CjxXgO3LAAAA:8 a=6I5d2MoRAAAA:8 a=2WlI2amiM7QyuENTnt0A:9 a=CjuIK1q_8ugA:10 a=IfaqVvZgccqrtc8gcwf2:22 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id 8D8C510A7; Tue, 5 Jun 2018 06:42:29 -0700 (PDT) Received: from slippy.cwsent.com (localhost [127.0.0.1]) by slippy.cwsent.com (8.15.2/8.15.2) with ESMTP id w55DgTFE053684; Tue, 5 Jun 2018 06:42:29 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Received: from slippy (cy@localhost) by slippy.cwsent.com (8.15.2/8.15.2/Submit) with ESMTP id w55DgTdF053558; Tue, 5 Jun 2018 06:42:29 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <201806051342.w55DgTdF053558@slippy.cwsent.com> X-Authentication-Warning: slippy.cwsent.com: cy owned process doing -bs X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Li-Wen Hsu cc: Cy Schubert , FreeBSD Current , Mark Johnston , Mark Millard , freebsd-arm@freebsd.org Subject: Re: svn commit: r334626 - in head: . . . [brk_test fails to build for aarch64 and stops build: no brk or sbrk to test, so undefined symbols] In-Reply-To: Message from Li-Wen Hsu of "Tue, 05 Jun 2018 09:07:34 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 05 Jun 2018 06:42:29 -0700 X-CMAE-Envelope: MS4wfMEU1metLZNBgtLUJIsxLJhlKnG2phVz7/qc4z+8sRniJlaJdElFh9/VG8xbU3BYRUfIcryivLpwkOsaUPOWCuPAJz/DW2JnK+uwAm3ahLmnFdxFpD9f iH8RqLMrb2Ebmw/EZF1ieSVPoIsPtbY1CSYanbSxhX0RHPLsLPrSp6lCfBLqDDBuDPiwL5oWkKYZtBLnspU4nNIFK04YQCAB5lpElgdI7Zzua2lyiHy7p2vM nwVXODdZYMZfuZHhCwKjHIjuM2Ncri5YP095ZWTj9mlsiDifTWrZFYcQBbwy0z6+ X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2018 13:42:34 -0000 In message , Li-Wen Hsu writes: > --00000000000079b474056de4bc0b > Content-Type: text/plain; charset="UTF-8" > > On Tue, Jun 5, 2018 at 08:10 Cy Schubert wrote: > > > In message <1731A84F-4278-43F5-B498-C3501081E783@yahoo.com>, Mark > > Millard write > > s: > > > >From ci.freebsd.org for a -r334626 + builds: > > > > > > --- brk_test.full --- > > > cc -target aarch64-unknown-freebsd12.0 > > --sysroot=/usr/obj/usr/src/arm64.aarch > > > 64/tmp -B/usr/obj/usr/src/arm64.aarch64/tmp/usr/bin -O2 -pipe -g > > -std=iso9899 > > > :1999 -fstack-protector-strong -Wsystem-headers -Werror -Wall > > -Wno-format-y2k > > > -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body > > -Wno-string-plus-int -W > > > no-unused-const-variable -Wno-tautological-compare -Wno-unused-value > > -Wno-par > > > entheses-equality -Wno-unused-function -Wno-enum-conversion > > -Wno-unused-local > > > -typedef -Wno-address-of-packed-member -Wno-switch -Wno-switch-enum > > -Wno-knr- > > > promoted-parameter -Qunused-arguments -o brk_test.full brk_test.o > > -lprivat > > > eatf-c > > > /usr/obj/usr/src/arm64.aarch64/tmp/usr/bin/ld: error: undefined symbol: > > brk > > > >>> referenced by brk_test.c:52 > > (/usr/src/lib/libc/tests/sys/brk_test.c:52) > > > >>> brk_test.o:(atfu_brk_basic_body) > > > > > > /usr/obj/usr/src/arm64.aarch64/tmp/usr/bin/ld: error: undefined symbol: > > sbrk > > > >>> referenced by brk_test.c:55 > > (/usr/src/lib/libc/tests/sys/brk_test.c:55) > > > >>> brk_test.o:(atfu_brk_basic_body) > > > > > > . . . (and many more) . . . > > > > Do a clean build or remove the libc directory from /usr/obj, then do > > your build. > > > Each build on ci.freebsd.org is a clean build from scratch. I overlooked that it was ci.freebsd.org. This is a different issue than on amd64. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. From owner-freebsd-current@freebsd.org Tue Jun 5 15:56:05 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7033FFF45D6 for ; Tue, 5 Jun 2018 15:56:05 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.not-for.work (onlyone.not-for.work [IPv6:2a01:4f8:201:6350::2]) by mx1.freebsd.org (Postfix) with ESMTP id F144381109 for ; Tue, 5 Jun 2018 15:56:04 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from [192.168.23.186] (unknown [89.113.128.32]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.not-for.work (Postfix) with ESMTPSA id 04D6C4DB for ; Tue, 5 Jun 2018 18:55:57 +0300 (MSK) To: FreeBSD current Reply-To: lev@FreeBSD.org From: Lev Serebryakov Subject: swapping is completely broken in -CURRENT r334649? Openpgp: preference=signencrypt Autocrypt: addr=lev@FreeBSD.org; prefer-encrypt=mutual; keydata= xsFNBFKbGksBEADeguVs+XyJc3mL3iiOBqDd16wSk97YTJYOi4VsHsINzJr09oFvNDiaDBIi fLn2p8XcJvehcsF2GSgrfXfw+uK4O1jyNIKJmiYA0EtE+ZbRtvDrrE0w6Q8+SDeKA21SWh3Y vSQ0DJUontbgW55ER2CbEiIUTIn34uQ0kmESAaw/v5p/9ue8yPTmURvv130FqPFz8VPzltqL NxyGt54TxPfKAzAHEIwxlEZ63JOwzloKh1UDBExcsf9nJO08/TAVgR5UZ5njFBPzaaquhRoP qPJLEQQDqxPIlvMNtHKf7iIebE4BHeqgCdJA0BoiR6gpa0wlsZtdrTPK3n4wYSphLvGbhfOZ YW/hbcu7HYS/FImkVxB3iY17kcC1UTnx4ZaYeASPBGOOPbXky1lLfmDGWIFT//70yx+G17qD OZzF1SvJJhGvh6ilFYaWMX7T+nIp6Mcafc4D7AakXM+XdubNXOMlCJhzPcZ0skgAEnYV587w V7em5fDVwQccwvtfezzqKeJAU5TGiywBHSR5Svzk2FwRNf6M//hWkpq0SRR63iOhkHGOAEBi 69GfEIwH2/w24rLxP0E+Hqq8n+EWNkPatw1Mhcl5PKkdvGCjJUaGNMkpBffjyYo254JXRscR eEnwdIkJt4ErDvjb2/UrOFq31wWMOiLzJeVchAgvTHBMRfP9aQARAQABzShMZXYgU2VyZWJy eWFrb3YgPGxldkBzZXJlYnJ5YWtvdi5zcGIucnU+wsGCBBMBCAAsAhsDBwsJCAcDAgEGFQgC CQoLBBYCAwECHgECF4ACGQEFAlKbP8wFCQlmJwEACgkQ6rA8WL/cR4/6VBAAjRMyyX3PBFx/ HxyiIZ698EfwlWUua8Ft4crtrdK52m0qNkbBB9BH8xQgBHG32A1CwyzQnzxHgZuoOWMjh+Qq WJv7dmpM/q/c1GCJHhlPgewXrciTwpAamZILN071u+1GCPWwGRPzfQ/U+k63KJWx9ozf4doM WTTom6Cqcssi4J1u5kkt52a5ZRhsCK9pEVGilk36XTP9BakGrnMSIxF/NK4xeZVX2q+Nuqvf RchyofKXVgLEDLwb1cd/baLtBpDzy0PTN2Zl2lX4kOA6jwTKsqRya9A1Vui1KXwPh2XViTQ1 7Y3l5qg/M+sR73DohezP6bO6huOnLhty17jAqHPNlD6RonDo+j8uIlEg4iMSTN3MhzkBAu0Q pe3ucQ0o1767JiXN3fsNvRzSFhLVNDqPLce4uKlMogsbreXWvdgHGTN1ybOHGbybZnP77yHz uNBacbmG3vL/OLXMqwLdL2JXoiec4DmXjjCdhTBl5xLV9Hz/6VWKqElteg8QFVvHB3tHWzJ4 /rpiVEixytCIII6DS33BXZ0h2EOkK/6AYA2SJxy1vgOH4SZBtDBHoezmHV2nFnq5O0c7AuAB 7WPWgQG0sEwHQPZmg/baRGitRJnaxf/Gvf1DeD1x1VrcoVke2vwBcgDM3kugP8L9hsqic2D3 dI+gP76haeuvNNZr3y9L9zvOwU0EUpsaSwEQALRr3B+OjY/cnJPstz5CVsVWyEZtJtrNviZr tBgbkhlkPm98sEWR4+gbpyeufdYJengDjeGzMDKcLB7h5fICS/j6A8XdlJ40TlbPfNgb6OHa ebaIYKTJpXKR9sD7ZyGivYMofm0em40wGUX7BIkdkomaWj+wUiS0CdXU0FWDj9wv73+Eim+X zZyXeFgIPv97v+pET7DfwKkADOfrkW9s4OfvGVjd+wm35wc8EngQEz0qdPBxx74X7vZFAxlA SXu8gDBJGYt2Bkc3QwULnfeXrZJWgqNPR5o44gGu96yaiOFaN/C6CJtev5ZEX+0ZxbvsHHB7 Z5AtsRURKpZ4w5HFHGhzHtDtoAKgeZ/gbhTVXPHvNQR818eN+Nl5BV8BRF/8yhR6VlJb8GYw h8oKDeVGVYC34+raHZQAM9WoBnN7jlt4T9zzPwtmw5mIahGFgvw1KDr7OItN2ZgtZ20UYC5m Go602nmHq0aPbU6SwGi1xohrliNsKaaciYiMaVIGRQq8iGr9Fe2HlvaA3BpB275i/gCVlUdG y5XLAv+yQMUvn5Z7XVsMroxDk/O+ae1ElyBvKiKyfWGJXTg5XUukkkyQmfWPxWUGoNA1P/P4 GMHSu7/Rqe/7m4uPu/RyTTqsSjjKJdP9kBwEzvqPtXsVoZuShtrptRQJDYflhgE4qmKSMKen ABEBAAHCwWUEGAECAA8FAlKbGksCGwwFCRLMAwAACgkQ6rA8WL/cR48RkA//SNzeW3CI8KHx rA0aeHW6Nb5ieoqVRBGLyjBM06RX6vHB9v4dJL6Z+yV2jGN2s+XZX2HILbuTOwcTxGkI3xTT e0cDXVaF5K8R/liigUjtwuC2v/sWgoWyUmK1Cy9CPYdcXmFq6nESfkUe8DYiGOUULdHq5w63 F53yOZ72iXRBQBZgkhPtRFu4lPYIzOsMag9DIJ9CthR1r0ziqU/keb94Qt3l+aXK7CwGdY7X T4zUIMHNYsuAuyX+NJIXfsN68TT6m7QmlUwxPs13nxmoVQzm4ruV+hlQKh1MtbsjWRkNgPxF IPiqoAEhy8QoddlSvRTwL5Z7zFQiwMdiXU7toL8pfzj/zJR1jELXKMipijrt5MLrV8XX3OPN yZZvh95VIl8mv+iAqwSZUufd2EJnvj5TObB0eH+a+34NWf/XqA3fPjE6KHzmdnw9PZjPEjlx JCPECSs+6gse1+GaEfKYuXzB/ENe2ctlcfx5iQJXFc+/+zG/uU/JX/pXJHA12CUfB5g7lH6X BZIHvRo3VTCDjXgbF5xxDAe5V4exf8d4oSNjQIFLYxxN7zkvH89EN6RPfRgsWN7bYArCwfS9 MOgs9pFeCOewR6qieK150aoqNENGfKFXJup+5VVl6I0mU+j0rgVDZDht2/QgP/Tb4lGBe+ai pOGaK/GYNR+Ad6bUmokKsx4= Organization: FreeBSD Message-ID: Date: Tue, 5 Jun 2018 18:55:52 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="UP323lhXGLFZ1NgqucdKyi934Rv3mw3le" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2018 15:56:05 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --UP323lhXGLFZ1NgqucdKyi934Rv3mw3le Content-Type: multipart/mixed; boundary="UJAPhb9PDEsF3ofuFiafkKQ7TFcjucEdc"; protected-headers="v1" From: Lev Serebryakov Reply-To: lev@FreeBSD.org To: FreeBSD current Message-ID: Subject: swapping is completely broken in -CURRENT r334649? --UJAPhb9PDEsF3ofuFiafkKQ7TFcjucEdc Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable I have 16G of free swap (out of 16G configured), but programs are killed due to "out of swap space"=E2=80=A6 --=20 // Lev Serebryakov --UJAPhb9PDEsF3ofuFiafkKQ7TFcjucEdc-- --UP323lhXGLFZ1NgqucdKyi934Rv3mw3le Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEE+W0coLX0MYtnSzMK6rA8WL/cR48FAlsWso1fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEY5 NkQxQ0EwQjVGNDMxOEI2NzRCMzMwQUVBQjAzQzU4QkZEQzQ3OEYACgkQ6rA8WL/c R48ZUg//TPfBscgEXD9V9SPr8cGDsZ9jjhAx8WFmnpT0iQemqYJSfFn0QG26nnHT BFTFOVG8wmv2IOXPaQKLMQBFworJUlCferrMlgg9AOcIdr3Fls4soD39DfM2BH9s ebIxYnYpyTYVehgo3n5E98BMz1bpH8qVIMTGw2tVl4qdsEuzl5Dgsx2EepYTy8d1 E/b469KwwcsLluGOZ+E8oFnloS8zvgKCRKAu/+7rg5a0Oq7CRS+FvNQB0ymBkNEe Xfxb17hWt23YOqEcDD++TK26gI4ASRkI7VER2EvxXnar0HEFda5JNBqpAw9MHgik xQyTa2F1zYJ/OSGhfoUUgB75oZPQlfQkJ60I1coq3fAyZqr+WzAVBO90Sfnps1GA RQXdPITPl9QvtvH4jO8Ai8sr2Z/5zBKHLXycsqvaUOcjnBi599rvnJQ2ZH2V5VpO EGpHB4OcTKZC8jvey1H8zTBG/6TcaJstvQk+gQUCJ9qV9YmhX+NBhBNrVhp/4HP9 nEvluMXJwcCwvE2Y0ISAFd9Vst8zoPtt7yb0DfwqovTSchvCKkCuXF4jrbe3O7G9 Ni9qs6Ls0XD7zuVtC7LdaNo3bruGzueTC7YNRPkqTDr5eXGqMJrlcGYATQAI0jDq kr5+DG8AMeM0H0NVtQrNDtXDCsNsSNGikc29sgWBPaAVWyi86SU= =BXu9 -----END PGP SIGNATURE----- --UP323lhXGLFZ1NgqucdKyi934Rv3mw3le-- From owner-freebsd-current@freebsd.org Tue Jun 5 16:17:21 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 85A09FF8989 for ; Tue, 5 Jun 2018 16:17:21 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F11C08203F; Tue, 5 Jun 2018 16:17:20 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wm0-x230.google.com with SMTP id j15-v6so6302453wme.0; Tue, 05 Jun 2018 09:17:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :mime-version:content-transfer-encoding; bh=MqFW/NuAek7dM//bD8irshenf8OXh4/5ViWGZzbQM+g=; b=bqAE9PSO04KOy9nDTEznWTOzb+WAWb+4rIH9lxr/WL4wR76mfY+cZyY9TanxFg5ddp s7Tt7U+9vP8QnBLdd8LK0nQlyE8AFaV+shOrKGl0/1kSEhyeSw14AJaM+Yzk65bvJpaP 9q+jSBJKF1PC4xiSZkMWeW65wSiR2bHz+14Msm637qgmyMc74S4GrTF6Zso6VwGfS4Ji 0UxM/0h4M95UBpyJNJk7vsirbBbtjgpeC3yLSGV8gH5bJ9TNUDGZ/nqQvldne+vKxJs8 XusKSZwwKLyCflyVP9Liw/eB42TaFhLeoQB2PprFPQ6vGEZDZiwdUMRX6vXirApT+CBv oFlg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:reply-to:mime-version:content-transfer-encoding; bh=MqFW/NuAek7dM//bD8irshenf8OXh4/5ViWGZzbQM+g=; b=GjXCRV7QY00eayASA1VnR5+xPMBNGNtlRhL1ZX+X4irnP7JIAolkdZpdJ4kgfjenTt bHK80SqRmTrdxkFZ8NEH7i/T+YWJMJL8H/bzgAo7PYoHA4v7GZbmzcmCko7mjVLGStLv MWNKCXcrXXfZRh3gp3Grrq9+omi7bPrDWvJwJRTQHEKFl6B02/aRon0MUOpU/jsaAjG7 PnNGveeQxL2F4iCQ1vqSKIgq2qnM7Qzzveng9k8SZOWAKoXps/VGCsMlmDIVk/m57IFy uJNBUfoq9lkClTyI/1EdfsOS3ETKdFzgK6gqUV4afc7fo2zhkv0WMGttazizuvag+Ly5 i15Q== X-Gm-Message-State: APt69E0FH0FFCzlzCtODX4p9Y6+wZfysOsH4HJD22UiYP+Zln8RhM3LB f3A4rYj47/jxNhDy4BdgwChc2Q== X-Google-Smtp-Source: ADUXVKKlmwiECeMtY3L7c0pFqUnr6gREudXXnI09qS/cm7epNV+7rxmo02rXzF/MYsQsIGME/GR2Ng== X-Received: by 2002:a1c:3282:: with SMTP id y124-v6mr12975272wmy.33.1528215439732; Tue, 05 Jun 2018 09:17:19 -0700 (PDT) Received: from ernst.home (p5B02337A.dip0.t-ipconnect.de. [91.2.51.122]) by smtp.gmail.com with ESMTPSA id 12-v6sm2499591wmn.27.2018.06.05.09.17.18 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 05 Jun 2018 09:17:18 -0700 (PDT) Date: Tue, 5 Jun 2018 18:17:16 +0200 From: Gary Jennejohn To: Lev Serebryakov Cc: FreeBSD current Subject: Re: swapping is completely broken in -CURRENT r334649? Message-ID: <20180605181716.73b8ea91@ernst.home> In-Reply-To: References: Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2018 16:17:21 -0000 On Tue, 5 Jun 2018 18:55:52 +0300 Lev Serebryakov wrote: > I have 16G of free swap (out of 16G configured), but programs are > killed due to "out of swap space" > I complained about this also and alc@ gave me this hint: sysctl vm.pageout_update_period=0 I don't whether it will help, but you can give it a try. -- Gary Jennejohn From owner-freebsd-current@freebsd.org Tue Jun 5 17:25:56 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AE6A8FE4C79 for ; Tue, 5 Jun 2018 17:25:56 +0000 (UTC) (envelope-from clbuisson@orange.fr) Received: from smtp.smtpout.orange.fr (smtp12.smtpout.orange.fr [80.12.242.134]) by mx1.freebsd.org (Postfix) with ESMTP id 3883A85F28 for ; Tue, 5 Jun 2018 17:25:55 +0000 (UTC) (envelope-from clbuisson@orange.fr) Received: from localhost ([92.134.115.95]) by mwinf5d23 with ME id v5JH1x00P23Zv9G035JHZy; Tue, 05 Jun 2018 19:18:18 +0200 X-ME-Helo: localhost X-ME-Auth: Y2xidWlzc29uQHdhbmFkb28uZnI= X-ME-Date: Tue, 05 Jun 2018 19:18:18 +0200 X-ME-IP: 92.134.115.95 Subject: Re: error building libpmc_events.c From: Claude Buisson To: FreeBSD Current References: <517b70cf-c5dc-db7b-7887-43cd74f3e10c@orange.fr> Cc: bdrewery@freebsd.org, mmacy@freebsd.org Message-ID: <8a2bdd46-f3f2-61e7-d757-5187156f7ac5@orange.fr> Date: Tue, 5 Jun 2018 19:18:16 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <517b70cf-c5dc-db7b-7887-43cd74f3e10c@orange.fr> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2018 17:25:56 -0000 Replying to my own mail for more details, and ccing potential commiters On 06/04/2018 17:34, Claude Buisson wrote: > Hi, > > During a buildworld of head on amd64, from 332518 to 334590, the build > stops with: > > --- all_subdir_lib/libpmc --- > ===> lib/libpmc (all) > --- libpmc_events.c --- > ./pmu-events/jevents "x86" /home/src/lib/libpmc/pmu-events/arch > libpmc_events.c > sh: ./pmu-events/jevents: not found > *** [libpmc_events.c] Error code 127 > ... > This was during the lib32 build: jevents is not built in this context The same error has been described by kevans@ on svn-src-all@ as a consequence of svn 334226 (by bdrewery), pmu-events having since been moved in svn r334242 (by mmacy) CBu From owner-freebsd-current@freebsd.org Tue Jun 5 21:09:52 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 07ABFFF6F92 for ; Tue, 5 Jun 2018 21:09:52 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.not-for.work (onlyone.not-for.work [IPv6:2a01:4f8:201:6350::2]) by mx1.freebsd.org (Postfix) with ESMTP id 7663072E07 for ; Tue, 5 Jun 2018 21:09:51 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from [192.168.23.186] (unknown [89.113.128.32]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.not-for.work (Postfix) with ESMTPSA id 6918B557; Wed, 6 Jun 2018 00:09:50 +0300 (MSK) Reply-To: lev@FreeBSD.org Subject: Re: swapping is completely broken in -CURRENT r334649? To: gljennjohn@gmail.com Cc: FreeBSD current References: <20180605181716.73b8ea91@ernst.home> From: Lev Serebryakov Openpgp: preference=signencrypt Autocrypt: addr=lev@FreeBSD.org; prefer-encrypt=mutual; keydata= xsFNBFKbGksBEADeguVs+XyJc3mL3iiOBqDd16wSk97YTJYOi4VsHsINzJr09oFvNDiaDBIi fLn2p8XcJvehcsF2GSgrfXfw+uK4O1jyNIKJmiYA0EtE+ZbRtvDrrE0w6Q8+SDeKA21SWh3Y vSQ0DJUontbgW55ER2CbEiIUTIn34uQ0kmESAaw/v5p/9ue8yPTmURvv130FqPFz8VPzltqL NxyGt54TxPfKAzAHEIwxlEZ63JOwzloKh1UDBExcsf9nJO08/TAVgR5UZ5njFBPzaaquhRoP qPJLEQQDqxPIlvMNtHKf7iIebE4BHeqgCdJA0BoiR6gpa0wlsZtdrTPK3n4wYSphLvGbhfOZ YW/hbcu7HYS/FImkVxB3iY17kcC1UTnx4ZaYeASPBGOOPbXky1lLfmDGWIFT//70yx+G17qD OZzF1SvJJhGvh6ilFYaWMX7T+nIp6Mcafc4D7AakXM+XdubNXOMlCJhzPcZ0skgAEnYV587w V7em5fDVwQccwvtfezzqKeJAU5TGiywBHSR5Svzk2FwRNf6M//hWkpq0SRR63iOhkHGOAEBi 69GfEIwH2/w24rLxP0E+Hqq8n+EWNkPatw1Mhcl5PKkdvGCjJUaGNMkpBffjyYo254JXRscR eEnwdIkJt4ErDvjb2/UrOFq31wWMOiLzJeVchAgvTHBMRfP9aQARAQABzShMZXYgU2VyZWJy eWFrb3YgPGxldkBzZXJlYnJ5YWtvdi5zcGIucnU+wsGCBBMBCAAsAhsDBwsJCAcDAgEGFQgC CQoLBBYCAwECHgECF4ACGQEFAlKbP8wFCQlmJwEACgkQ6rA8WL/cR4/6VBAAjRMyyX3PBFx/ HxyiIZ698EfwlWUua8Ft4crtrdK52m0qNkbBB9BH8xQgBHG32A1CwyzQnzxHgZuoOWMjh+Qq WJv7dmpM/q/c1GCJHhlPgewXrciTwpAamZILN071u+1GCPWwGRPzfQ/U+k63KJWx9ozf4doM WTTom6Cqcssi4J1u5kkt52a5ZRhsCK9pEVGilk36XTP9BakGrnMSIxF/NK4xeZVX2q+Nuqvf RchyofKXVgLEDLwb1cd/baLtBpDzy0PTN2Zl2lX4kOA6jwTKsqRya9A1Vui1KXwPh2XViTQ1 7Y3l5qg/M+sR73DohezP6bO6huOnLhty17jAqHPNlD6RonDo+j8uIlEg4iMSTN3MhzkBAu0Q pe3ucQ0o1767JiXN3fsNvRzSFhLVNDqPLce4uKlMogsbreXWvdgHGTN1ybOHGbybZnP77yHz uNBacbmG3vL/OLXMqwLdL2JXoiec4DmXjjCdhTBl5xLV9Hz/6VWKqElteg8QFVvHB3tHWzJ4 /rpiVEixytCIII6DS33BXZ0h2EOkK/6AYA2SJxy1vgOH4SZBtDBHoezmHV2nFnq5O0c7AuAB 7WPWgQG0sEwHQPZmg/baRGitRJnaxf/Gvf1DeD1x1VrcoVke2vwBcgDM3kugP8L9hsqic2D3 dI+gP76haeuvNNZr3y9L9zvOwU0EUpsaSwEQALRr3B+OjY/cnJPstz5CVsVWyEZtJtrNviZr tBgbkhlkPm98sEWR4+gbpyeufdYJengDjeGzMDKcLB7h5fICS/j6A8XdlJ40TlbPfNgb6OHa ebaIYKTJpXKR9sD7ZyGivYMofm0em40wGUX7BIkdkomaWj+wUiS0CdXU0FWDj9wv73+Eim+X zZyXeFgIPv97v+pET7DfwKkADOfrkW9s4OfvGVjd+wm35wc8EngQEz0qdPBxx74X7vZFAxlA SXu8gDBJGYt2Bkc3QwULnfeXrZJWgqNPR5o44gGu96yaiOFaN/C6CJtev5ZEX+0ZxbvsHHB7 Z5AtsRURKpZ4w5HFHGhzHtDtoAKgeZ/gbhTVXPHvNQR818eN+Nl5BV8BRF/8yhR6VlJb8GYw h8oKDeVGVYC34+raHZQAM9WoBnN7jlt4T9zzPwtmw5mIahGFgvw1KDr7OItN2ZgtZ20UYC5m Go602nmHq0aPbU6SwGi1xohrliNsKaaciYiMaVIGRQq8iGr9Fe2HlvaA3BpB275i/gCVlUdG y5XLAv+yQMUvn5Z7XVsMroxDk/O+ae1ElyBvKiKyfWGJXTg5XUukkkyQmfWPxWUGoNA1P/P4 GMHSu7/Rqe/7m4uPu/RyTTqsSjjKJdP9kBwEzvqPtXsVoZuShtrptRQJDYflhgE4qmKSMKen ABEBAAHCwWUEGAECAA8FAlKbGksCGwwFCRLMAwAACgkQ6rA8WL/cR48RkA//SNzeW3CI8KHx rA0aeHW6Nb5ieoqVRBGLyjBM06RX6vHB9v4dJL6Z+yV2jGN2s+XZX2HILbuTOwcTxGkI3xTT e0cDXVaF5K8R/liigUjtwuC2v/sWgoWyUmK1Cy9CPYdcXmFq6nESfkUe8DYiGOUULdHq5w63 F53yOZ72iXRBQBZgkhPtRFu4lPYIzOsMag9DIJ9CthR1r0ziqU/keb94Qt3l+aXK7CwGdY7X T4zUIMHNYsuAuyX+NJIXfsN68TT6m7QmlUwxPs13nxmoVQzm4ruV+hlQKh1MtbsjWRkNgPxF IPiqoAEhy8QoddlSvRTwL5Z7zFQiwMdiXU7toL8pfzj/zJR1jELXKMipijrt5MLrV8XX3OPN yZZvh95VIl8mv+iAqwSZUufd2EJnvj5TObB0eH+a+34NWf/XqA3fPjE6KHzmdnw9PZjPEjlx JCPECSs+6gse1+GaEfKYuXzB/ENe2ctlcfx5iQJXFc+/+zG/uU/JX/pXJHA12CUfB5g7lH6X BZIHvRo3VTCDjXgbF5xxDAe5V4exf8d4oSNjQIFLYxxN7zkvH89EN6RPfRgsWN7bYArCwfS9 MOgs9pFeCOewR6qieK150aoqNENGfKFXJup+5VVl6I0mU+j0rgVDZDht2/QgP/Tb4lGBe+ai pOGaK/GYNR+Ad6bUmokKsx4= Organization: FreeBSD Message-ID: <34ee04a3-6455-baa2-09c3-f3c67b11a525@FreeBSD.org> Date: Wed, 6 Jun 2018 00:09:43 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <20180605181716.73b8ea91@ernst.home> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="qXqr0WwznP3v3aZpvTTf2xEHY5jeuYt5X" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2018 21:09:52 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --qXqr0WwznP3v3aZpvTTf2xEHY5jeuYt5X Content-Type: multipart/mixed; boundary="sPJSsxZEFAgllXCVKpqUzl3IYiKft3Abr"; protected-headers="v1" From: Lev Serebryakov Reply-To: lev@FreeBSD.org To: gljennjohn@gmail.com Cc: FreeBSD current Message-ID: <34ee04a3-6455-baa2-09c3-f3c67b11a525@FreeBSD.org> Subject: Re: swapping is completely broken in -CURRENT r334649? References: <20180605181716.73b8ea91@ernst.home> In-Reply-To: <20180605181716.73b8ea91@ernst.home> --sPJSsxZEFAgllXCVKpqUzl3IYiKft3Abr Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 05.06.2018 19:17, Gary Jennejohn wrote: >> I have 16G of free swap (out of 16G configured), but programs are >> killed due to "out of swap space" >> >=20 > I complained about this also and alc@ gave me this hint: > sysctl vm.pageout_update_period=3D0 >=20 > I don't whether it will help, but you can give it a try. Looks like it helps a little. Very resource-hungry operation have been completed, but after ~10 minutes, when compilation have been finished, and swap is clear again, system starts to kill processes. WTF?! --=20 // Lev Serebryakov --sPJSsxZEFAgllXCVKpqUzl3IYiKft3Abr-- --qXqr0WwznP3v3aZpvTTf2xEHY5jeuYt5X Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEE+W0coLX0MYtnSzMK6rA8WL/cR48FAlsW/BdfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEY5 NkQxQ0EwQjVGNDMxOEI2NzRCMzMwQUVBQjAzQzU4QkZEQzQ3OEYACgkQ6rA8WL/c R49DUBAAvH49iq4NA/2XdQ2bJRlAMV5y+EFY6jVyamzLMnJfohHY54zvLRYH5q4k MLg09c40xwT9Ds+BjiK2po9HE5FaT2KFidfn3eIJQCEKCN8nAf+Qtce3VVDye6Mq GxFj9aZwJnvt+J0y1GGI82fMYYqbU/LwH5W4/GUhof3zy39+hoH5Ox0vb5USkFQF hkniwRn1EVSIMnR1vWWi7ZT0lgwj/+lMKt0ikh41VeXDef9jbLZEmhQRFoEYKtBV toCHGvSU5ZpkldyQd9dlyBjw6fNNzrOP9mg0nA69n9SiUKyyhfU9Kb/GiZ7Q6bnp MSaBxvf46kyLNQlnBUXoCBqikfitTelH6z5zCy1ufyVkd0C4EMdPNCZCSfpvwp1m lzXziuU8x4D757DDY6sPcYGt85E6qQWN2nE+kAf8txwvFTL++RaZu/pB1+WOaJLt dJtwBgOMXab4gEw5rg1NelzV/+HSYxTkJPSPU+VyiQ1hPrdsptHaewes+xRqHtCu qKjkOWLaSoCx07xl+blas2mlw1oGbhJ5vZwKwlq9KhWMPV3Vmd9BeEHO+95Ku2ez MRarrwyrivqKVvxuUHC1ELnhZbJeZ+Yj62rOMQV49cukQErSmVUaSug+k65sfL4/ 9PUWuXKaENAKUqB+6lljlKjrtKgC53DAZxnWhz9Bh4HSHuDd+R4= =5+Zu -----END PGP SIGNATURE----- --qXqr0WwznP3v3aZpvTTf2xEHY5jeuYt5X-- From owner-freebsd-current@freebsd.org Tue Jun 5 21:22:10 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A94EBFF766A for ; Tue, 5 Jun 2018 21:22:10 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.not-for.work (onlyone.not-for.work [IPv6:2a01:4f8:201:6350::2]) by mx1.freebsd.org (Postfix) with ESMTP id 2B07D73977 for ; Tue, 5 Jun 2018 21:22:10 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from [192.168.23.186] (unknown [89.113.128.32]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.not-for.work (Postfix) with ESMTPSA id C13BB55D; Wed, 6 Jun 2018 00:22:08 +0300 (MSK) Reply-To: lev@FreeBSD.org Subject: Re: swapping is completely broken in -CURRENT r334649? To: gljennjohn@gmail.com Cc: FreeBSD current References: <20180605181716.73b8ea91@ernst.home> From: Lev Serebryakov Openpgp: preference=signencrypt Autocrypt: addr=lev@FreeBSD.org; prefer-encrypt=mutual; keydata= xsFNBFKbGksBEADeguVs+XyJc3mL3iiOBqDd16wSk97YTJYOi4VsHsINzJr09oFvNDiaDBIi fLn2p8XcJvehcsF2GSgrfXfw+uK4O1jyNIKJmiYA0EtE+ZbRtvDrrE0w6Q8+SDeKA21SWh3Y vSQ0DJUontbgW55ER2CbEiIUTIn34uQ0kmESAaw/v5p/9ue8yPTmURvv130FqPFz8VPzltqL NxyGt54TxPfKAzAHEIwxlEZ63JOwzloKh1UDBExcsf9nJO08/TAVgR5UZ5njFBPzaaquhRoP qPJLEQQDqxPIlvMNtHKf7iIebE4BHeqgCdJA0BoiR6gpa0wlsZtdrTPK3n4wYSphLvGbhfOZ YW/hbcu7HYS/FImkVxB3iY17kcC1UTnx4ZaYeASPBGOOPbXky1lLfmDGWIFT//70yx+G17qD OZzF1SvJJhGvh6ilFYaWMX7T+nIp6Mcafc4D7AakXM+XdubNXOMlCJhzPcZ0skgAEnYV587w V7em5fDVwQccwvtfezzqKeJAU5TGiywBHSR5Svzk2FwRNf6M//hWkpq0SRR63iOhkHGOAEBi 69GfEIwH2/w24rLxP0E+Hqq8n+EWNkPatw1Mhcl5PKkdvGCjJUaGNMkpBffjyYo254JXRscR eEnwdIkJt4ErDvjb2/UrOFq31wWMOiLzJeVchAgvTHBMRfP9aQARAQABzShMZXYgU2VyZWJy eWFrb3YgPGxldkBzZXJlYnJ5YWtvdi5zcGIucnU+wsGCBBMBCAAsAhsDBwsJCAcDAgEGFQgC CQoLBBYCAwECHgECF4ACGQEFAlKbP8wFCQlmJwEACgkQ6rA8WL/cR4/6VBAAjRMyyX3PBFx/ HxyiIZ698EfwlWUua8Ft4crtrdK52m0qNkbBB9BH8xQgBHG32A1CwyzQnzxHgZuoOWMjh+Qq WJv7dmpM/q/c1GCJHhlPgewXrciTwpAamZILN071u+1GCPWwGRPzfQ/U+k63KJWx9ozf4doM WTTom6Cqcssi4J1u5kkt52a5ZRhsCK9pEVGilk36XTP9BakGrnMSIxF/NK4xeZVX2q+Nuqvf RchyofKXVgLEDLwb1cd/baLtBpDzy0PTN2Zl2lX4kOA6jwTKsqRya9A1Vui1KXwPh2XViTQ1 7Y3l5qg/M+sR73DohezP6bO6huOnLhty17jAqHPNlD6RonDo+j8uIlEg4iMSTN3MhzkBAu0Q pe3ucQ0o1767JiXN3fsNvRzSFhLVNDqPLce4uKlMogsbreXWvdgHGTN1ybOHGbybZnP77yHz uNBacbmG3vL/OLXMqwLdL2JXoiec4DmXjjCdhTBl5xLV9Hz/6VWKqElteg8QFVvHB3tHWzJ4 /rpiVEixytCIII6DS33BXZ0h2EOkK/6AYA2SJxy1vgOH4SZBtDBHoezmHV2nFnq5O0c7AuAB 7WPWgQG0sEwHQPZmg/baRGitRJnaxf/Gvf1DeD1x1VrcoVke2vwBcgDM3kugP8L9hsqic2D3 dI+gP76haeuvNNZr3y9L9zvOwU0EUpsaSwEQALRr3B+OjY/cnJPstz5CVsVWyEZtJtrNviZr tBgbkhlkPm98sEWR4+gbpyeufdYJengDjeGzMDKcLB7h5fICS/j6A8XdlJ40TlbPfNgb6OHa ebaIYKTJpXKR9sD7ZyGivYMofm0em40wGUX7BIkdkomaWj+wUiS0CdXU0FWDj9wv73+Eim+X zZyXeFgIPv97v+pET7DfwKkADOfrkW9s4OfvGVjd+wm35wc8EngQEz0qdPBxx74X7vZFAxlA SXu8gDBJGYt2Bkc3QwULnfeXrZJWgqNPR5o44gGu96yaiOFaN/C6CJtev5ZEX+0ZxbvsHHB7 Z5AtsRURKpZ4w5HFHGhzHtDtoAKgeZ/gbhTVXPHvNQR818eN+Nl5BV8BRF/8yhR6VlJb8GYw h8oKDeVGVYC34+raHZQAM9WoBnN7jlt4T9zzPwtmw5mIahGFgvw1KDr7OItN2ZgtZ20UYC5m Go602nmHq0aPbU6SwGi1xohrliNsKaaciYiMaVIGRQq8iGr9Fe2HlvaA3BpB275i/gCVlUdG y5XLAv+yQMUvn5Z7XVsMroxDk/O+ae1ElyBvKiKyfWGJXTg5XUukkkyQmfWPxWUGoNA1P/P4 GMHSu7/Rqe/7m4uPu/RyTTqsSjjKJdP9kBwEzvqPtXsVoZuShtrptRQJDYflhgE4qmKSMKen ABEBAAHCwWUEGAECAA8FAlKbGksCGwwFCRLMAwAACgkQ6rA8WL/cR48RkA//SNzeW3CI8KHx rA0aeHW6Nb5ieoqVRBGLyjBM06RX6vHB9v4dJL6Z+yV2jGN2s+XZX2HILbuTOwcTxGkI3xTT e0cDXVaF5K8R/liigUjtwuC2v/sWgoWyUmK1Cy9CPYdcXmFq6nESfkUe8DYiGOUULdHq5w63 F53yOZ72iXRBQBZgkhPtRFu4lPYIzOsMag9DIJ9CthR1r0ziqU/keb94Qt3l+aXK7CwGdY7X T4zUIMHNYsuAuyX+NJIXfsN68TT6m7QmlUwxPs13nxmoVQzm4ruV+hlQKh1MtbsjWRkNgPxF IPiqoAEhy8QoddlSvRTwL5Z7zFQiwMdiXU7toL8pfzj/zJR1jELXKMipijrt5MLrV8XX3OPN yZZvh95VIl8mv+iAqwSZUufd2EJnvj5TObB0eH+a+34NWf/XqA3fPjE6KHzmdnw9PZjPEjlx JCPECSs+6gse1+GaEfKYuXzB/ENe2ctlcfx5iQJXFc+/+zG/uU/JX/pXJHA12CUfB5g7lH6X BZIHvRo3VTCDjXgbF5xxDAe5V4exf8d4oSNjQIFLYxxN7zkvH89EN6RPfRgsWN7bYArCwfS9 MOgs9pFeCOewR6qieK150aoqNENGfKFXJup+5VVl6I0mU+j0rgVDZDht2/QgP/Tb4lGBe+ai pOGaK/GYNR+Ad6bUmokKsx4= Organization: FreeBSD Message-ID: <2925b27f-43cf-8813-eaa7-4f3d12bef8f0@FreeBSD.org> Date: Wed, 6 Jun 2018 00:22:08 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <20180605181716.73b8ea91@ernst.home> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="HzPjevfK0Nq4N3CX1HCqSIzUiMfUlB7Qa" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2018 21:22:10 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --HzPjevfK0Nq4N3CX1HCqSIzUiMfUlB7Qa Content-Type: multipart/mixed; boundary="fO7oDtvPWOgxFW2x2Gu9lt2FVyvL3tOtr"; protected-headers="v1" From: Lev Serebryakov Reply-To: lev@FreeBSD.org To: gljennjohn@gmail.com Cc: FreeBSD current Message-ID: <2925b27f-43cf-8813-eaa7-4f3d12bef8f0@FreeBSD.org> Subject: Re: swapping is completely broken in -CURRENT r334649? References: <20180605181716.73b8ea91@ernst.home> In-Reply-To: <20180605181716.73b8ea91@ernst.home> --fO7oDtvPWOgxFW2x2Gu9lt2FVyvL3tOtr Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 05.06.2018 19:17, Gary Jennejohn wrote: > I complained about this also and alc@ gave me this hint: > sysctl vm.pageout_update_period=3D0 Really, situation is worse than stated in subject, because processes are being killed AFTER memory pressure, when here are a lot of free memory already! It looks like very serious bug. --=20 // Lev Serebryakov --fO7oDtvPWOgxFW2x2Gu9lt2FVyvL3tOtr-- --HzPjevfK0Nq4N3CX1HCqSIzUiMfUlB7Qa Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEE+W0coLX0MYtnSzMK6rA8WL/cR48FAlsW/wBfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEY5 NkQxQ0EwQjVGNDMxOEI2NzRCMzMwQUVBQjAzQzU4QkZEQzQ3OEYACgkQ6rA8WL/c R4+01g/9HDUN5q4UJDsWRpk1xWO42VxnT4dDA7f6DuuoPerr9d9Ktf3vVYPUXPwq VUJYWac8xwe5IP1xyk6okDr3lthA1dfyAX8Mymi9fhAj+KC2IUAnMTGtS214jOIf A2iJKT9SpdYIaQF+pcWv+GvjMzTvTygk93g9htU4YC4GYBCSzv5+cZcIifjgkeC4 jSxkIjVrFGh+aiXYElVKUOiSTSDxbNSdF8QiWjDL7RBJvHDBHn3c7tuSvI1DZMXu 0RwAOEulzadzgt4Jmy0nEIgxeE7PKETIlxm952mznrw4plh3DPjQbLvhaXAmYMuB aWC+oA/8d5qtNsE4wRjPcaqHlGTU1JauF7Spm87FX2rUQjczBb+BMy9B8hq5Il1S Pm3yjCOslB4qNqfhZkf5auaEnUknEXiF8YB11+CdW5ZDM6OVyYWsSjxnuRg4Yf4S daEr5pIx2ACPduRPYedQA62ojSGmEfYUDdUrwHJyNmBtlXgUtLhZHS7wVt1TyYaR 3tQ5Lge+ZoE3F4eoyDAQZoxrKf1NSj0iJB+pcEt5MIQ2ETQAFDk8j6cfYUe/iX3h kAv5flBWJ09Oh8fZzRBf27Vf3wFi+8FnzIxIQtpCSKqYnqlujQVhKUfnpVYxoUlz 5XxdW4rFVa1c6SsFJOaMQeevBHCg5e5UGlLecQA8C4Zspqf+iDM= =/38C -----END PGP SIGNATURE----- --HzPjevfK0Nq4N3CX1HCqSIzUiMfUlB7Qa-- From owner-freebsd-current@freebsd.org Tue Jun 5 21:49:06 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6F28FFF8B34 for ; Tue, 5 Jun 2018 21:49:06 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-io0-x236.google.com (mail-io0-x236.google.com [IPv6:2607:f8b0:4001:c06::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 027FC76840; Tue, 5 Jun 2018 21:49:06 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-io0-x236.google.com with SMTP id d22-v6so5204466iof.13; Tue, 05 Jun 2018 14:49:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=Rb2IpsyQeqoMYr5FlUPMHnG5puOsYPpCf9fCQE6Scns=; b=CNSzFLs8sdeTZwg5N/7/1u/bOJgP7L4ahNWiOEsZeITJGn0+TIrP3FFIzIyMWypvxs O56YoVJSJCR/3SoQKQgTFh8LXjKJisNOQ4NuSO8tpMpxwG3FoZHw7FJxiL2OWIfHZgxp 1c+Hj3P2sRpsBTRe3cNq/gbyCM/ADC2u0tnTwAq7atL4jj9cq7ZTI+i/KYoIbXVN5hRq hyFAwHQ3dv5ad87jRgd64hg6y68H60Qkd88i4DOcmG1WhhizqS0KbpO8J0v9RfNs4ywp nLCH2XY4f6L31QDAUDNyKlowgvRFnIw8zZYBRdZGEcxbhzi7DTz3ey4UHoxGugMvbkgV MXvQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=Rb2IpsyQeqoMYr5FlUPMHnG5puOsYPpCf9fCQE6Scns=; b=U0DCjUXlEu5Im4rwgwxp7eSwSgQRP8b+6t1gI+erP/YiwILtf/m/CoJ3UgnfCZGzvx Q2UA1WlO4wM91L7VTiRR6lZKiWiItDXg61mcw7FnkZyrtVd7NGV4nn7eliLjdzf48O9s hE7mpi1JDeYIdM4V9z97iiBG39uSwq/dyaiEupmbK9W6J4FOz6PWXX3iJgKHqSjdxv6o HKeFZIoI8cUKHEdQ+LFHrMuLuPgm2Q5DPnqLlX4X+y0Qo/38r7Aj2Qb6v2j4Lzi69R0/ D1Fa8vjXoPiUOgmA/yoemMXgCnGEJPVTq/ruWWf7yJRE2GysSQDue5+gOr4ODQ6nBML4 G0LQ== X-Gm-Message-State: APt69E2ijT5z23MZ8Tt0XEJWdnoKg7IRugRYVkxqyzOk14OabTNl1V+U EiK8Ttj+Y+o6pdf9bA/1VK5xKQ== X-Google-Smtp-Source: ADUXVKJlMv/HyFJwulCgeZNq/lLSfDIYR7BOGRRx5QmQSKl9Q/NS4eCHLiBp86TFkgoWtu3LMB2foA== X-Received: by 2002:a6b:3e56:: with SMTP id l83-v6mr394571ioa.75.1528235345226; Tue, 05 Jun 2018 14:49:05 -0700 (PDT) Received: from pesky ([75.98.19.133]) by smtp.gmail.com with ESMTPSA id m14-v6sm1244263iti.36.2018.06.05.14.49.03 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 05 Jun 2018 14:49:04 -0700 (PDT) Sender: Mark Johnston Date: Tue, 5 Jun 2018 17:48:08 -0400 From: Mark Johnston To: Lev Serebryakov Cc: gljennjohn@gmail.com, FreeBSD current Subject: Re: swapping is completely broken in -CURRENT r334649? Message-ID: <20180605214808.GA94301@pesky> References: <20180605181716.73b8ea91@ernst.home> <2925b27f-43cf-8813-eaa7-4f3d12bef8f0@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2925b27f-43cf-8813-eaa7-4f3d12bef8f0@FreeBSD.org> User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2018 21:49:06 -0000 On Wed, Jun 06, 2018 at 12:22:08AM +0300, Lev Serebryakov wrote: > On 05.06.2018 19:17, Gary Jennejohn wrote: > > > > I complained about this also and alc@ gave me this hint: > > sysctl vm.pageout_update_period=0 > > Really, situation is worse than stated in subject, because processes > are being killed AFTER memory pressure, when here are a lot of free > memory already! > > It looks like very serious bug. The issue was identified earlier this week and is being worked on. It's a regression from r329882 which appears only on certain hardware. You can probably work around it by setting vm.pageout_oom_seq to a large value (try 1000 for instance), though this will make the "true" OOM killer take longer to kick in. The problem is unrelated to the pageout_update_period. From owner-freebsd-current@freebsd.org Tue Jun 5 22:04:59 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C30B2FF935C for ; Tue, 5 Jun 2018 22:04:59 +0000 (UTC) (envelope-from as@cmplx.uk) Received: from jail0199.vps.exonetric.net (jail0199.vps.exonetric.net [IPv6:2a02:1658:1::199:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "jail0199.vps.exonetric.net", Issuer "jail0199.vps.exonetric.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 106E577326 for ; Tue, 5 Jun 2018 22:04:57 +0000 (UTC) (envelope-from as@cmplx.uk) Received: from jail0199.vps.exonetric.net (jail0199.vps.exonetric.net [178.250.76.108]) by jail0199.vps.exonetric.net (8.15.2/8.15.2) with ESMTPS id w55M4uQU083160 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Tue, 5 Jun 2018 22:04:56 GMT (envelope-from as@jail0199.vps.exonetric.net) Received: (from as@localhost) by jail0199.vps.exonetric.net (8.15.2/8.15.2/Submit) id w55M4uFc083159 for freebsd-current@freebsd.org; Tue, 5 Jun 2018 22:04:56 GMT (envelope-from as) Date: Tue, 5 Jun 2018 22:04:56 GMT From: Anton Shterenlikht Message-Id: <201806052204.w55M4uFc083159@jail0199.vps.exonetric.net> To: freebsd-current@freebsd.org Subject: intel graphics regression? between r332432 and r333982 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2018 22:04:59 -0000 I'm looking for help to make graphics work on Dell Precision 3520. This did work in r332432: http://freebsd.1045724.x6.nabble.com/Dell-Precision-3520-laptop-help-with-dual-graphics-card-td6249818.html I now updated to: # uname -a FreeBSD z.net 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r333982: Thu May 24 21:24:22 BST 2018 root@z.net:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 and I cannot get graphics anymore. Some details: # pciconf -lv | grep -A3 vga vgapci1@pci0:0:2:0: class=0x030000 card=0x07a91028 chip=0x191b8086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' device = 'HD Graphics 530' class = display -- vgapci0@pci0:1:0:0: class=0x030200 card=0x07a91028 chip=0x13b410de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'GM107GLM [Quadro M620 Mobile]' class = display Somebody in questions@ suggested https://github.com/ahacking/freebsd-gpu-off to disable one of the 2 devices. Not sure if this worked as expected. I now have: # cat /usr/local/etc/gpu-off.conf export methods="\_SB.PCI0.PEG0.PEGP._OFF" I built graphics/drm-next-kmod and added kld_list="/boot/modules/i915kms.ko" to /etc/rc.conf. However, on boot I see: KLD drm.ko: depends on kernel - not available or version mismatch linker_load_file: /boot/modules/drm.ko - unsupported file type KLD i915kms.ko: depends on drmn - not available or version mismatch linker_load_file: /boot/modules/i915kms.ko - unsupported file type I can still load these modules manually: root@z:~ # kldload drm root@z:~ # kldload i915kms info: [drm] Initialized drm 1.1.0 20060810 root@z:~ # kldstat Id Refs Address Size Name 1 44 0xffffffff80200000 23fad18 kernel 2 1 0xffffffff825fc000 29bc8 if_iwm.ko 3 1 0xffffffff82626000 1bb438 iwm8265fw.ko 4 1 0xffffffff831fa000 be5c geom_bde.ko 6 1 0xffffffff83206000 210 acpi_call.ko 7 1 0xffffffff83207000 2388 ums.ko 8 1 0xffffffff8320a000 1780 uhid.ko 9 1 0xffffffff8320c000 10c70 drm.ko 10 1 0xffffffff8321d000 7d0e0 i915kms.ko 11 1 0xffffffff8329b000 40eb0 drm2.ko 12 4 0xffffffff832dc000 1ef0 iicbus.ko 13 1 0xffffffff832de000 ec0 iic.ko 14 1 0xffffffff832df000 1570 iicbb.ko Still, starting X I get in /var/log/Xorg.0.log [ 429.258] (EE) open /dev/dri/card0: No such file or directory Give me a hint Anton From owner-freebsd-current@freebsd.org Tue Jun 5 23:06:29 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E50A0FD1351 for ; Tue, 5 Jun 2018 23:06:28 +0000 (UTC) (envelope-from freebsd@grem.de) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id 6179379B24 for ; Tue, 5 Jun 2018 23:06:28 +0000 (UTC) (envelope-from freebsd@grem.de) Received: (qmail 24240 invoked by uid 89); 5 Jun 2018 23:06:27 -0000 Received: from unknown (HELO bsd64.grem.de) (mg@grem.de@194.97.158.70) by mail.grem.de with ESMTPA; 5 Jun 2018 23:06:27 -0000 Date: Wed, 6 Jun 2018 01:06:25 +0200 From: Michael Gmelin To: Konstantin Belousov Cc: Michael Gmelin , "freebsd-current@freebsd.org" , Matthias Apitz , jhb@freebsd.org Subject: Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy) Message-ID: <20180606010625.62632920@bsd64.grem.de> In-Reply-To: <20180605131135.GH2450@kib.kiev.ua> References: <20180603144840.44bfea41@bsd64.grem.de> <20180603132110.GP3789@kib.kiev.ua> <20180603165500.361ec894@bsd64.grem.de> <20180603150423.GQ3789@kib.kiev.ua> <20180603215020.452a81d8@bsd64.grem.de> <20180603205340.GS3789@kib.kiev.ua> <20180604004632.56ca6afa@bsd64.grem.de> <20180604110654.GA2450@kib.kiev.ua> <20180604231756.2ed2adb9@bsd64.grem.de> <20180605131135.GH2450@kib.kiev.ua> X-Mailer: Claws Mail 3.15.1 (GTK+ 2.24.31; amd64-portbld-freebsd10.3) X-Face: $wrgCtfdVw_H9WAY?S&9+/F"!41z'L$uo*WzT8miX?kZ~W~Lr5W7v?j0Sde\mwB&/ypo^}> +a'4xMc^^KroE~+v^&^#[B">soBo1y6(TW6#UZiC]o>C6`ej+i Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEWJBwe5BQDl LASZU0/LTEWEfHbyj0Txi32+sKrp1Mv944X8/fm1rS+cAAAACXBIWXMAAAsTAAAL EwEAmpwYAAAAB3RJTUUH3wESCxwC7OBhbgAAACFpVFh0Q29tbWVudAAAAAAAQ3Jl YXRlZCB3aXRoIFRoZSBHSU1QbbCXAAAAAghJREFUOMu11DFvEzEUAGCfEhBVFzuq AKkLd0O6VrIQsLXVSZXoWE5N1K3DobBBA9fQpRWc8OkWouaIjedWKiyREOKs+3PY fvalCNjgLVHeF7/3bMtBzV8C/VsQ8tecEgCcDgrzjekwKZ7TwsJZd/ywEKwwP+ZM 8P3drTsAwWn2mpWuDDuYiK1bFs6De0KUUFw0tWxm+D4AIhuuvZqtyWYeO7jQ4Aea 7jUqI+ixhQoHex4WshEvSXdood7stlv4oSuFOC4tqGcr0NjEqXgV4mMJO38nld4+ xKNxRDon7khyKVqY7YR4d+Cg0OMrkWXZOM7YDkEfKiilCn1qYv4mighZiynuHHOA Wq9QJq+BIES7lMFUtcikMnkDGHUoncA+uHgrP0ctIEqfwLHzeSo+eUA66AqzwN6n 2ZHJhw6Qh/PoyC/QENyEyC/AyNjq74Bs+3UH0xYwzDUC4B97HgLocg1QLYgDDO1v f3UX9Y307Ew4AHh67YAFFsxEpkXwpXY3eIgMhAAE3R19L919nNnuD2wlPcDE3UeT L2ytEICQib9BXgS2fU8PrD82ToYO1OEmMSnYTjSqSv9wdC0tPYC+rQRQD9ESnldF CyqfmiYW+tlALt8gH2xrMdC/youbjzPXEun+/ReXsMCDyve3dZc09fn2Oas8oXGc Jj6/fOeK5UmSMPmf/jL+GD8BEj0k/Fn6IO4AAAAASUVORK5CYII= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2018 23:06:29 -0000 On Tue, 5 Jun 2018 16:11:35 +0300 Konstantin Belousov wrote: > On Mon, Jun 04, 2018 at 11:17:56PM +0200, Michael Gmelin wrote: > > > > > > On Mon, 4 Jun 2018 14:06:55 +0300 > > Konstantin Belousov wrote: > > > > > On Mon, Jun 04, 2018 at 12:46:32AM +0200, Michael Gmelin wrote: > > > > > > > > > > > > On Sun, 3 Jun 2018 23:53:40 +0300 > > > > Konstantin Belousov wrote: > > > > > > > > > On Sun, Jun 03, 2018 at 09:50:20PM +0200, Michael Gmelin > > > > > wrote: > > > > > > > > > > > > > > > > > > On Sun, 3 Jun 2018 18:04:23 +0300 > > > > > > Konstantin Belousov wrote: > > > > > > > > > > > > > On Sun, Jun 03, 2018 at 04:55:00PM +0200, Michael Gmelin > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > On Sun, 3 Jun 2018 16:21:10 +0300 > > > > > > > > Konstantin Belousov wrote: > > > > > > > > > > > > > > > > > On Sun, Jun 03, 2018 at 02:48:40PM +0200, Michael > > > > > > > > > Gmelin wrote: > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > > > > > After upgrading CURRENT to r333992 (from something > > > > > > > > > > at least a year old, quite some changes in > > > > > > > > > > mp_machdep.c since), this machine crashes on boot: > > > > > > > > > > > > > > > > > > > > Copyright (c) 1992-2018 The FreeBSD Project. > > > > > > > > > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, > > > > > > > > > > 1991, 1992, 1993, 1994 The Regents of the > > > > > > > > > > University of California. All rights reserved. > > > > > > > > > > FreeBSD is a registered trademark of The FreeBSD > > > > > > > > > > Foundation. FreeBSD 12.0-CURRENT #1 r333992: Tue > > > > > > > > > > May 22 00:31:04 CEST 2018 > > > > > > > > > > root@flimsy:/usr/obj/usr/src/amd64.amd64/sys/flimsy > > > > > > > > > > amd64 FreeBSD clang version 6.0.0 > > > > > > > > > > (tags/RELEASE_600/final 326565) (based on LLVM > > > > > > > > > > 6.0.0) WARNING: WITNESS option enabled, expect > > > > > > > > > > reduced performance. VT(vga): resolution 640x480 > > > > > > > > > > CPU: Intel(R) Celeron(R) 2955U @ 1.40GHz > > > > > > > > > > (1396.80-MHz K8-class CPU) Origin="GenuineIntel" > > > > > > > > > > Id=0x40651 Family=0x6 Model=0x45 Stepping=1 > > > > > > > > > > Features=0xbfebfbff > > > > > > > > > CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > > > > > > > > > > Features2=0x4ddaebbf > > > > > > > > > xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,TSCDLT,XSAVE,OSXSAVE,RDRAND> > > > > > > > > > > AMD > > > > > > > > > > Features=0x2c100800 > > > > > > > > > > AMD Features2=0x21 Structured Extended > > > > > > > > > > Features=0x2603 > > > > > > > > > > XSAVE Features=0x1 VT-x: (disabled in > > > > > > > > > > BIOS) PAT,HLT,MTF,PAUSE,EPT,UG,VPID TSC: P-state > > > > > > > > > > invariant, performance statistics real memory = > > > > > > > > > > 4301258752 (4102 MB) avail memory = 1907572736 > > > > > > > > > > (1819 MB) Event timer "LAPIC" quality 600 ACPI APIC > > > > > > > > > > Table: > > > > > > > > > COREBOOT> > > > > > > > > > What does this mean ? Did you flashed > > > > > > > > > coreboot ? > > > > > > > > > > > > > > > > This machine comes with it by default (my model was > > > > > > > > delivered with SeaBIOS 20131018_145217-build121-m2). So > > > > > > > > I didn't flash anything (didn't feel like bricking it). > > > > > > > > > > > > > > > > > > > > > > > > > > > kernel trap 12 with interrupts disabled > > > > > > > > > > > > > > > > > > > > Fatal trap 12: page fault while in kernel mode > > > > > > > > > > cpuid = 0; apic id = 00 > > > > > > > > > > fault virtual address = 0xfffff80001000000 > > > > > > > > > > fault code = supervisor write data, > > > > > > > > > > protection violation instruction pointer = > > > > > > > > > > 0x20:Oxffffffff8102955f stack pointer = > > > > > > > > > > 0x28:0xffffffff82a79be0 frame pointer = > > > > > > > > > > 0x28:0xffffffff82a79c10 code segment = > > > > > > > > > > base Ox0, limit Oxfffff, type Ox1b = DPL 0, pres 1, > > > > > > > > > > long 1, def32 0, gran 1 processor eflags = > > > > > > > > > > resume, IOPL = 0 current process = 0 () > > > > > > > > > > [ thread pid 0 tid 0 ] > > > > > > > > > > Stopped at native_start_all_aps+0x08f: > > > > > > > > > > movq %rax,(%rsi) > > > > > > > > > Look up the source line number for this address. > > > > > > > > > > > > > > > > > > > > > > > > > I guess that's sys/amd64/amd64/support.S line 854 (in > > > > > > > > rdmsr), called by native_start_all_aps. Any additional > > > > > > > > hints how I can track it down? > > > > > > > Why did you decided that this is rdmsr_safe() ? First, > > > > > > > native_start_all_aps() does not call rdmsr, second the ddb > > > > > > > report clearly indicates that the fault occured acessing > > > > > > > DMAP in native_start_all_aps(). > > > > > > > > > > > > > > Just look up the source line by the address > > > > > > > native_start_all_aps+0x08f. > > > > > > > > > > > > Okay, according to kgbd this should be here: > > > > > > > > > > > > https://svnweb.freebsd.org/base/head/sys/amd64/amd64/mp_machdep.c?revision=333368&view=markup#l369 > > > > > > > > > > > > 364 > > > > > > 365 /* Create the initial 1GB replicated page tables */ > > > > > > 366 for (i = 0; i < 512; i++) { > > > > > > 367 /* Each slot of the level 4 pages points to > > > > > > the same level 3 page */ 368 pt4[i] = > > > > > > (u_int64_t)(uintptr_t)(mptramp_pagetables + PAGE_SIZE); 369 > > > > > > pt4[i] |= PG_V | PG_RW | PG_U; 370 > > > > > > 371 /* Each slot of the level 3 pages points to > > > > > > the same level 2 page */ 372 pt3[i] = > > > > > > (u_int64_t)(uintptr_t)(mptramp_pagetables + (2 * > > > > > > PAGE_SIZE)); 373 pt3[i] |= PG_V | PG_RW | PG_U; > > > > > > 374 375 /* The level 2 page slots are mapped > > > > > > with 2MB pages for 1GB. */ 376 pt2[i] = i * (2 * > > > > > > 1024 * 1024); 377 pt2[i] |= PG_V | PG_RW | PG_PS > > > > > > | PG_U; 378 } > > > > > > > > > > > > -m > > > > > You have fault on write due to read-only mapping of the > > > > > portion of the direct map, which maps the kernel text. It is > > > > > consistent with the faulting address. It is not clear if it > > > > > is something new on your machine, or before the kernel text > > > > > was silently corrupted, since ro protection is somewhat > > > > > recent. > > > > > > > > > > It seems that mp_bootaddress() selected the bad place for the > > > > > bootstrap page tables. Even more, we do not include the kernel > > > > > text into the physmem[] array, so it is not clear how did it > > > > > happen. This code was also changed recently. > > > > > > > > > > Can you add the print of the physmap[] array somewhere before > > > > > the panic, to see what is the kernel idea of the available > > > > > memory ? It should be already done if you have serial console > > > > > and set debug.late_console tunable to 0. > > > > > > > > This is a sad little machine without any kind of serial console. > > > > > > > > Physmap looks like this after calling getmemsize(): > > > > > > > > [0]: 0x10000 > > > > [1]: 0x30000 > > > > [2]: 0x40000 > > > > [3]: 0x9e000 > > > > [4]: 0x100000 > > > > [5]: 0xf00000 > > > > [6]: 0x1003000 > > > > [7]: 0x7bf7a000 > > > > > > > > Physical memory chunks logged in cpu_startup are: > > > > > > > > 0x0000000000010000 - 0x000000000002ffff, 141072 bytes (32 pages) > > > > 0x0000000000040000 - 0x000000000009dfff, 385024 bytes (94 > > > > pages) > > > These two chunks reports are consistent with the physmap[0-1, > > > 2-3]. > > > > 0x0000000000100000 - 0x00000000001fffff, 1048576 bytes (256 > > > > pages) 0x0000000002c00000 - 0x0000000075467fff, 1921417216 > > > > bytes (469096 pages) 0x0000000100000000 - 0x00000001005e7fff, > > > > 6193152 bytes (1512 pages) > > > But these three looks completely unrelated to the rest of the > > > physmap, perhaps except the physmap[4]. We allocate boot pages > > > from the top of the last physmap chunk, but I am certain that we > > > do not consume that much memory for boot to make physmap[7] from > > > the last reported address. > > > > > > Are you sure that there are no typos in the values above ? > > > > Double checked the numbers. I changed it a bit more, > > so that debug output appears all on one page. Please see here for > > the results: > > > > https://gist.github.com/grembo/cebb9f7e2a98c37a51bee1e508f7d890 > Ok, I have a guess what is going on. Does the result of the quirks > end up as hw.physmem tunable passed to kernel ? It seems that there > is physmap[] element pointing outside the DMAP-mapped region. > > Perhaps print the dmap limit too, to see whether I am on the right > track. I didn't print the dmap limit yet, but I tested your patch: > > Try the following change. It lacks i386 bits. > > diff --git a/sys/amd64/amd64/machdep.c b/sys/amd64/amd64/machdep.c > index e5c69ed91fa..bd6bbf04006 100644 > --- a/sys/amd64/amd64/machdep.c > +++ b/sys/amd64/amd64/machdep.c > @@ -1254,7 +1254,7 @@ getmemsize(caddr_t kmdp, u_int64_t first) > * in real mode mode (e.g. SMP bare metal). > */ > if (init_ops.mp_bootaddress) > - init_ops.mp_bootaddress(physmap, &physmap_idx); > + init_ops.mp_bootaddress(physmap, &physmap_idx, > first); > /* > * Maxmem isn't the "maximum memory", it's one larger than > the diff --git a/sys/amd64/amd64/mp_machdep.c > b/sys/amd64/amd64/mp_machdep.c index 30146142087..292a6cefa91 100644 > --- a/sys/amd64/amd64/mp_machdep.c > +++ b/sys/amd64/amd64/mp_machdep.c > @@ -103,7 +103,8 @@ static int start_ap(int apic_id); > * Calculate usable address in base memory for AP trampoline code. > */ > void > -mp_bootaddress(vm_paddr_t *physmap, unsigned int *physmap_idx) > +mp_bootaddress(vm_paddr_t *physmap, unsigned int *physmap_idx, > + vm_paddr_t dmap_limit) > { > unsigned int i; > bool allocated; > @@ -117,8 +118,9 @@ mp_bootaddress(vm_paddr_t *physmap, unsigned int > *physmap_idx) > * store the initial page tables. Note that it needs > to be > * aligned to a page boundary. > */ > - if (physmap[i] >= GiB(4) || > - (physmap[i + 1] - round_page(physmap[i])) < > (PAGE_SIZE * 3)) > + if (physmap[i] >= GiB(4) || physmap[i + 1] - > + round_page(physmap[i]) < PAGE_SIZE * 3 || > + physmap[i + 1] - PAGE_SIZE * 3 > dmap_limit) > continue; > > allocated = true; > diff --git a/sys/amd64/include/smp.h b/sys/amd64/include/smp.h > index 2ecfe62cf9f..24f0580fe51 100644 > --- a/sys/amd64/include/smp.h > +++ b/sys/amd64/include/smp.h > @@ -58,7 +58,7 @@ void invlpg_pcid_handler(void); > void invlrng_invpcid_handler(void); > void invlrng_pcid_handler(void); > int native_start_all_aps(void); > -void mp_bootaddress(vm_paddr_t *, unsigned int *); > +void mp_bootaddress(vm_paddr_t *, unsigned int *, vm_paddr_t); > > #endif /* !LOCORE */ > #endif /* SMP */ > diff --git a/sys/x86/include/init.h b/sys/x86/include/init.h > index 880cabaa949..58bbe0a5fd6 100644 > --- a/sys/x86/include/init.h > +++ b/sys/x86/include/init.h > @@ -41,7 +41,7 @@ struct init_ops { > void (*early_clock_source_init)(void); > void (*early_delay)(int); > void (*parse_memmap)(caddr_t, vm_paddr_t *, int *); > - void (*mp_bootaddress)(vm_paddr_t *, unsigned int *); > + void (*mp_bootaddress)(vm_paddr_t *, unsigned int *, > vm_paddr_t); int (*start_all_aps)(void); > void (*msi_init)(void); > }; With the patch I could boot without problems and the machine appears to be stable (ran some high load & memory intensive tests - by the way, the machine only has 2gb of ram [even though 4g are reported on boot - usable memory appears to be reported ok]). Thanks, Michael -- Michael Gmelin From owner-freebsd-current@freebsd.org Wed Jun 6 00:47:21 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 58A81FD517F for ; Wed, 6 Jun 2018 00:47:21 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from CAN01-QB1-obe.outbound.protection.outlook.com (mail-eopbgr660064.outbound.protection.outlook.com [40.107.66.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT TLS CA 4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 863447C563 for ; Wed, 6 Jun 2018 00:47:20 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from YTOPR0101MB0953.CANPRD01.PROD.OUTLOOK.COM (52.132.44.24) by YTOPR0101MB2266.CANPRD01.PROD.OUTLOOK.COM (52.132.51.18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.820.14; Wed, 6 Jun 2018 00:47:17 +0000 Received: from YTOPR0101MB0953.CANPRD01.PROD.OUTLOOK.COM ([fe80::a860:9237:2e9f:f87f]) by YTOPR0101MB0953.CANPRD01.PROD.OUTLOOK.COM ([fe80::a860:9237:2e9f:f87f%3]) with mapi id 15.20.0820.015; Wed, 6 Jun 2018 00:47:17 +0000 From: Rick Macklem To: "freebsd-current@freebsd.org" Subject: how do I use the make universe machines? Thread-Topic: how do I use the make universe machines? Thread-Index: AQHT/S+/hTGXEeL5mkihoTOoY7p6XA== Date: Wed, 6 Jun 2018 00:47:17 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=rmacklem@uoguelph.ca; x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; YTOPR0101MB2266; 7:+ox1lJFQMBqzmeiEFrIDscgcUvchpP/uspOG6NDeR3mdcWT0iPUXIwJL0F6isM5gFRXJRGtTBob7hZxwu4WvbDkZT2qP1dd6lqMT0xbzPjM/wiurIPyEpH7ZM+gxlesJm3Zhb+fHNnOm+zz1Kt4CJqSNFdA+OO3HhIehKNQ5twy0W1plfWZxuztqO8xSG+jI4ePXZVRPDEK4xbjKxxG0tToxz3ecknRmHFQFhROg7ZRyIg3kS+rRFKKrkroUkWyg x-ms-exchange-antispam-srfa-diagnostics: SOS; x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(8989080)(5600026)(4534165)(4627221)(201703031133081)(201702281549075)(8990040)(2017052603328)(7153060)(7193020); SRVR:YTOPR0101MB2266; x-ms-traffictypediagnostic: YTOPR0101MB2266: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-ms-exchange-senderadcheck: 1 x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(93006095)(93001095)(10201501046)(3002001)(3231254)(944501410)(52105095)(149027)(150027)(6041310)(201703131423095)(201702281529075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123562045)(20161123558120)(20161123564045)(6072148)(201708071742011)(7699016); SRVR:YTOPR0101MB2266; BCL:0; PCL:0; RULEID:; SRVR:YTOPR0101MB2266; x-forefront-prvs: 06952FC175 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(39380400002)(376002)(366004)(396003)(39860400002)(199004)(189003)(3660700001)(2906002)(97736004)(68736007)(3280700002)(2351001)(99286004)(53936002)(86362001)(316002)(9686003)(25786009)(2900100001)(5660300001)(2501003)(5640700003)(55016002)(786003)(305945005)(558084003)(6916009)(33656002)(74316002)(102836004)(74482002)(8676002)(186003)(106356001)(7696005)(8936002)(81156014)(6506007)(486006)(81166006)(476003)(105586002)(478600001)(6436002)(14454004)(26005)(5250100002); DIR:OUT; SFP:1101; SCL:1; SRVR:YTOPR0101MB2266; H:YTOPR0101MB0953.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: uoguelph.ca does not designate permitted sender hosts) x-microsoft-antispam-message-info: lKNPYvvCjaigYl+oiGRB+MHXIcbUNMDtz8bJK3iH79iITE/8+Qzcsagu6Gf/hZwd7pjbsapIzg/PavOr0R5mVA3Yp+a0O2lBE30VUVgtbVgXxj5zk4OVopNTn0QdHuC+x79Ltz7luVHm+tY/K0VInZwYJb2YXAyj3xYIrZXzXf7gzGPr2BYe+QCZgDVfaIOa spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-MS-Office365-Filtering-Correlation-Id: 7af58713-6d34-4739-d378-08d5cb470d66 X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-Network-Message-Id: 7af58713-6d34-4739-d378-08d5cb470d66 X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Jun 2018 00:47:17.0283 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTOPR0101MB2266 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jun 2018 00:47:21 -0000 I've heard mention of "make universe" machines multiple times, but have no idea how to use them? Is there doc on this? Thanks, rick ps: I'll admit I haven't looked at the developer's guide in a long time. From owner-freebsd-current@freebsd.org Wed Jun 6 01:17:30 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 36512FDB246 for ; Wed, 6 Jun 2018 01:17:30 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-5.mit.edu (dmz-mailsec-scanner-5.mit.edu [18.7.68.34]) (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 B9BD77D4D4 for ; Wed, 6 Jun 2018 01:17:29 +0000 (UTC) (envelope-from kaduk@mit.edu) X-AuditID: 12074422-5f1ff700000032a5-11-5b1734f738dd Received: from mailhub-auth-1.mit.edu ( [18.9.21.35]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-5.mit.edu (Symantec Messaging Gateway) with SMTP id 62.65.12965.7F4371B5; Tue, 5 Jun 2018 21:12:23 -0400 (EDT) Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11]) by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id w561CLgZ018028; Tue, 5 Jun 2018 21:12:22 -0400 Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id w561CI5r028066 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 5 Jun 2018 21:12:21 -0400 Date: Tue, 5 Jun 2018 20:12:18 -0500 From: Benjamin Kaduk To: Rick Macklem Cc: "freebsd-current@freebsd.org" Subject: Re: how do I use the make universe machines? Message-ID: <20180606011218.GA72167@kduck.kaduk.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.1 (2017-09-22) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrBIsWRmVeSWpSXmKPExsUixCmqrPvdRDza4NlcZYs5bz4wWTxcdo3J gcljxqf5LB6/N+9lCmCK4rJJSc3JLEst0rdL4Mo4dXwJS8F35orlTTdYGxgnMXcxcnJICJhI zHv8HMjm4hASWMwkse/felYIZwOjxN21C9lBqoQErjBJTDgsBWKzCKhInN34lQ3EZgOyG7ov g00SEVCX2Ly6H8xmFrCXaLuznbGLkYNDWMBU4ugEB5AwL9Cyf5OWsEGMTJA4fOUMK0RcUOLk zCcsEK1aEjf+vWQCaWUWkJZY/o8DxOQUSJTYM0MLpEJUQFlib98h9gmMArOQNM9C0jwLoXkB I/MqRtmU3Crd3MTMnOLUZN3i5MS8vNQiXVO93MwSvdSU0k2MoABld1HawTjxn9chRgEORiUe 3hXdYtFCrIllxZW5hxglOZiURHkPColHC/El5adUZiQWZ8QXleakFh9ilOBgVhLhTbwEVM6b klhZlVqUD5OS5mBREufNXcQYLSSQnliSmp2aWpBaBJOV4eBQkuD9aww0VLAoNT21Ii0zpwQh zcTBCTKcB2i4IjCihXiLCxJzizPTIfKnGBWlxHk7QJoFQBIZpXlwvaAEIpG9v+YVozjQK8K8 T0CqeIDJB677FdBgJqDBzyqEQQaXJCKkpBoYdW4/XrVoVn7sLKaoso7EFRufKWnHKe/7Zzz9 mr3/X701J2WsPkU/0Cvdu3/y69aEdcuLmViPf5L4w/xae49x+pR1BvWZzSo3m9R5b+3UjL77 SiW6ZeJckQVzeK8u+jc1aotQy+20nVFSH45N/rL/dML3H0mSv+9NeqG99rzp4iiGrJlzmtWm dimxFGckGmoxFxUnAgArKvBc+wIAAA== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jun 2018 01:17:30 -0000 On Wed, Jun 06, 2018 at 12:47:17AM +0000, Rick Macklem wrote: > I've heard mention of "make universe" machines multiple times, > but have no idea how to use them? > Is there doc on this? > > Thanks, rick > ps: I'll admit I haven't looked at the developer's guide in a long time. I think https://www.freebsd.org/internal/machines.html sounds like the page you're looking for. (universe is just a top-level make target like buildworld, but will take a while on non-beefy hardware.) -Ben From owner-freebsd-current@freebsd.org Wed Jun 6 02:50:12 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 93134FDDAC6 for ; Wed, 6 Jun 2018 02:50:12 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 08D1B7F8C5 for ; Wed, 6 Jun 2018 02:50:11 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id w562oHxV031321; Tue, 5 Jun 2018 19:50:23 -0700 (PDT) (envelope-from bsd-lists@BSDforge.com) X-Mailer: UDNSMS MIME-Version: 1.0 Cc: "freebsd-current@freebsd.org>" , "Rick Macklem" In-Reply-To: <20180606011218.GA72167@kduck.kaduk.org> From: "Chris H" Reply-To: bsd-lists@BSDforge.com To: "Benjamin Kaduk" Subject: Re: how do I use the make universe machines? Date: Tue, 05 Jun 2018 19:50:23 -0700 Message-Id: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jun 2018 02:50:12 -0000 On Tue, 5 Jun 2018 20:12:18 -0500 "Benjamin Kaduk" said > On Wed, Jun 06, 2018 at 12:47:17AM +0000, Rick Macklem wrote: > > I've heard mention of "make universe" machines multiple times, > > but have no idea how to use them? > > Is there doc on this? > >=20 > > Thanks, rick > > ps: I'll admit I haven't looked at the developer's guide in a long time= =2E >=20 > I think https://www=2Efreebsd=2Eorg/internal/machines=2Ehtml sounds like > the page you're looking for=2E (universe is just a top-level make > target like buildworld, but will take a while on non-beefy > hardware=2E) >=20 > -Ben I was surprised to discover there was no mention in /usr/src/UPDATING, nor /usr/src/README=2E So in case anyone might be wondering; /usr/src/Makefile # universe - *Really* build *everything* (buildworld and # all kernels on all architectures)=2E # tinderbox - Same as universe, but presents a list of failed bui= ld # targets and exits with an error if there were any=2E following, an excerpt by Allan Jude (FreeBSD developer && bsdnow=2Etv): Testing is Tricky and Rigorous, so FreeBSD Came Out with the Universe Build Further complicating things, ZFS has its own upstream repo with its own rul= es and testing requirements: e=2Eg=2E, a pull request has to be in a ZFS-running operating system like FreeBSD or Linux and used in production for a minimum= of three months before actually being committed=2E =E2=80=9CThe ZFS repo has to be in production quality at all times,= =E2=80=9D Allan elaborated=2E =E2=80=9CFreeBSD itself has a test suite, a set of regression tests, and th= en continuous integration with Jenkins=2E=E2=80=9D The trick there is the multiple platform= conundrum=2E You make a commit, the code is seemingly perfect, but then you realize you = only know how it runs on your x86 hardware=2E Maybe its functionality on ARM is a different story=2E =E2=80=9CWe have this concept called the Universe Build where you build Fre= eBSD for every different processor environment that=E2=80=99s supported,=E2=80=9D Al= lan shared=2E That way no matter how well it works on your system, you also know it=E2=80=99ll wor= k for everyone else=2E As is to be expected, Allan told us the Universe Build can take a while to develop to perfection =E2=80=94 =E2=80=9Cespecially if you don=E2=80=99t ha= ve all the hardware, but the FreeBSD Foundation provides servers to the developers of the project=2E= =E2=80=9D So thankfully, they=E2=80=99ve got access to really big servers, some 36 cores= , and a boat load of RAM=2E =E2=80=9CIf you had to do a Universe Build on your laptop, it = might take a day and a half,=E2=80=9D Allan added, with a laugh=2E --Chris From owner-freebsd-current@freebsd.org Wed Jun 6 07:37:35 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5202DFEB049; Wed, 6 Jun 2018 07:37:35 +0000 (UTC) (envelope-from maurizio1018@gmail.com) Received: from mail-pl0-x243.google.com (mail-pl0-x243.google.com [IPv6:2607:f8b0:400e:c01::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C70C068B10; Wed, 6 Jun 2018 07:37:34 +0000 (UTC) (envelope-from maurizio1018@gmail.com) Received: by mail-pl0-x243.google.com with SMTP id c23-v6so3256302plz.12; Wed, 06 Jun 2018 00:37:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=2BY8PvenIZchaoLRY0q2A1hlyfXUCa5FG65/VgR+6zE=; b=hhjC4wZ7LsQMfWQVsoCWGd9HInivJIq9u4xnwiFz2f9LmNGSm4+wGfJYI/kyumMHdX SQGm7XQD3mpJrtCwx7GtxzhU6yHVh3fuYWbwAokGDpCgIeCxStaDOGKMO3OzkASd5B5C zG1az7HuyNbBoCETrTF35W0xm7BPKkOqXroM2m+oyHrH7R3p/qAv9OgWg7QPEyN1+H/t aS75/ze2Mc/x4yHenrBbFl0KbLHNPWf8Lu6KjKRPvTsWwobtzIFCIbNjunpTM+SMjZ0m lh87PviokpWJJqF957CR05wuItY6jzUnXJi1H7cqTRJeWy/MHzKwj6UYbz9SqbJvY0/1 t0jg== 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=2BY8PvenIZchaoLRY0q2A1hlyfXUCa5FG65/VgR+6zE=; b=ofBzVii+/DSWEHFhDESABEidp2aSw4pZziC5dxYKphq0NKmJhJ7Vzt0poTGjtzEp54 KBsp9iLv3Zc0He4zkF++JFDMpPp9qSCpPFhAwPqVRVvqyZ4iEv6F5fTfB+8TXHyeF03v 5Sm6ZGjcqx1skd94tyzoTRIFskd9wQyflYKTtbXg6oBVFDQY6iHQqH/mz41U+Pr/geBf 0O8GInwVgHGss/vhtK0Sx7HncYaiTYtj8yZRW6w6wpTYCWRnL+Wn9/W9+nON1/Ie0UmA fRcNmsPP0MnxHLcJKqi5PG97hfSEnFf/ni3pvQVzZ+vmT994nKRVsn05QAajk4YcMuSI FiSA== X-Gm-Message-State: APt69E0u3EZ3JdX/T412VH4W6a1f3YFIxZU3e9IesX5/rPwJi61jKp8y ZW2xsNL0ezuOZK0HYjnf5tXlYHhCnhSf6PyVmaO3cQ== X-Google-Smtp-Source: ADUXVKJw3lhzYGtOZRAxwL4iLSBXHv3Rr3exNu0y+eZ5mVQXB+LwukqgbJ55Dsb8Tfu41YEJ+J4Prn19FJFZwD3SKuA= X-Received: by 2002:a17:902:b611:: with SMTP id b17-v6mr2103486pls.284.1528270653696; Wed, 06 Jun 2018 00:37:33 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a17:90a:ad94:0:0:0:0 with HTTP; Wed, 6 Jun 2018 00:37:33 -0700 (PDT) In-Reply-To: <20180530155039.GE97814@FreeBSD.org> References: <20180530155039.GE97814@FreeBSD.org> From: Maurizio Vairani Date: Wed, 6 Jun 2018 09:37:33 +0200 Message-ID: Subject: Re: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted To: freebsd-current , freebsd-stable@freebsd.org Cc: Ed Maste Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jun 2018 07:37:35 -0000 2018-05-30 17:50 GMT+02:00 Glen Barber : > Hi, > > Could folks please help boot-test the most recent 12.0-CURRENT amd64 > memstick images on various hardware? Note, this is not a request to > install 12.0-CURRENT, only a boot-test with various system knobs > tweaked. > > The most recent images are available at: > https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO- > IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-mini-memstick.img > https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO- > IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-memstick.img > > We are interested in testing both UEFI and CSM/BIOS/legacy mode, as we > would like to get this included in the upcoming 11.2-RELEASE if the > change that had been committed addresses several boot issues reported > recently. > > Please help test, and report back (both successes and failures). > > Thanks, > > Glen > > Hi, successfully tested the memstick.img on: Mac mini Mid 2011, BIOS and UEFI Desktop based on Asus H81M-K mainboard, BIOS and UEFI -- Maurizio From owner-freebsd-current@freebsd.org Wed Jun 6 09:37:02 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 05A54FEEA16 for ; Wed, 6 Jun 2018 09:37:02 +0000 (UTC) (envelope-from ed@nuxi.nl) 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 70A5C6C896 for ; Wed, 6 Jun 2018 09:37:01 +0000 (UTC) (envelope-from ed@nuxi.nl) Received: by mail-wm0-x22c.google.com with SMTP id p126-v6so10259335wmb.2 for ; Wed, 06 Jun 2018 02:37:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nuxi-nl.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=lXzhGIn8u7FkhIzvlsTOqHTLfWOg7+sBlMFcem7zaUk=; b=ODMitodL5ONiRSKc1EsxjVdrCnimS4Ng5fXrHycKnHeSN0VXd4efFczARv0F6iUvEJ 3FjQp6VLjG4/SvwF/AjUINQ/Q8xI+TdkgSpZiwbv5wm9E1heWofLULr2UmR4Pz0vSgZp N1UUVte7e7m20YneqNCOfOmn/BJQMJTvwaEk+GFYe4dj1XkWCbfpzRVZRixNAR7f1kgy q4gqkz/S/4u/7Dp5SltYT0W6uwx1aUeXa5vOWwYKmvfH4aABmfiP2xYQfQ71fwPp2XEC JGfyCPS2rYFuwktDyF+ZSFvEhkIV1XGWSM7Spawe0HqlHQN5yH6egtJEFiJfCKOS8s5e Ia6w== 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=lXzhGIn8u7FkhIzvlsTOqHTLfWOg7+sBlMFcem7zaUk=; b=nq618etY36G0/P+k8obfx48S112DHp7Ad/AYZAi2ey9PNEVoVKdh4QG4RieSus5WtR mPjTGrotFuR75AXU2OiGHxIV3zDKa465FhI/bzGj/bsZVh9dkvk9/GEdWsA8/p6wADIf YdoCRoYNzVFKBHYvM35JQqXvKMGiPmMqNVhYfmvOXplRE4aqYlfzZiPYSLsFQMnp76Ir GupBzAOssn++ccRsNbvM9U1mOw03SsLSwfkJud5f4NLtYZWrmwgfOoFvvIipCyKUHW8u BVYwfPpi12TjYlWNCTvpuOPMkdAmouNM5d89SGCQJC5ypp2Bw2A5rqnwEGIwMsc51Cct zThA== X-Gm-Message-State: APt69E138/05KhHyIpOUHLrQembF7ptg8ALv/y/a8st9nNqSmDVZRXyj 8wgAHVmjKYH0MgBsz65IJh5mCIln+0ROMJlbdv40Ug== X-Google-Smtp-Source: ADUXVKIjc0h1zVFvPkLdMelNZL9ALj1v2wn6DBaPNxn5LGFPHi5IrEo5oA2UlpfrcNu6EIteQVeFwfD+M9fBj1ZJJds= X-Received: by 2002:aa7:c588:: with SMTP id g8-v6mr2881819edq.200.1528277820380; Wed, 06 Jun 2018 02:37:00 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a50:8e0d:0:0:0:0:0 with HTTP; Wed, 6 Jun 2018 02:36:29 -0700 (PDT) In-Reply-To: References: From: Ed Schouten Date: Wed, 6 Jun 2018 11:36:29 +0200 Message-ID: Subject: Re: Odd w/who behavior for the last 12 years To: "Timur I. Bakeyev" Cc: FreeBSD Current , Ed Schouten , Robert Watson , Alan Jude , Michal Mertl Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jun 2018 09:37:02 -0000 Hi Timur, 2018-05-28 5:26 GMT+02:00 Timur I. Bakeyev : > So I propose to remove the said patch(or make it verify only "pts/" > devices). any objections? Sounds good! Changes like the ones made in r155875 were simply workarounds to deal with processes silly enough not to write DEAD_PROCESS entries. Instead of patching up w, wall, who, etc. we should spend effort to fix these problems at the root instead. Be sure to cc me on code reviews! -- Ed Schouten Nuxi, 's-Hertogenbosch, the Netherlands From owner-freebsd-current@freebsd.org Wed Jun 6 05:00:51 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 74608FE169F for ; Wed, 6 Jun 2018 05:00:51 +0000 (UTC) (envelope-from o.hartmann@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 B89A8835D0 for ; Wed, 6 Jun 2018 05:00:50 +0000 (UTC) (envelope-from o.hartmann@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 0MHX4u-1fRWPf24fU-003Ltx for ; Wed, 06 Jun 2018 06:55:31 +0200 Date: Wed, 6 Jun 2018 06:55:25 +0200 From: "O. Hartmann" To: freebsd-current Subject: CAM/ growisofs: Segmentation fault, SCSI sense: ILLEGAL REQUEST asc:21,0 (Logical block address out of range) Message-ID: <20180606065520.1b927cdf@freyja.zeit4.iv.bundesimmobilien.de> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:Gff/q+tzm5DDM1VrAA5mUiQV+zJEc/wizm9UOKZa/8e4Qz16djk GzKDqgObMHEYY4xyMnGt3baIPVGu92w0LdfBtr+5EPYKf5O4Lf/oc1Y45uMMwEupXTRmgzl HaYcQBmdYkv2/coissrwbipEa8M2cLf4DBuQRSQd78/Ey1UmfsuA5ZkIonu2zTDAOXtmSZS G2WTM0yZ2hWZ87f+Hyoyg== X-UI-Out-Filterresults: notjunk:1;V01:K0:pkA/rsJiiGo=:r6yAXthOZ5Q6jcO0qdrlK2 T8KeeRqGmdv3yABIHnP8QC3EFAl09F1Jlcbc2MyzK1n02CReuUcA8asariUEg5BJnO+248eKy p9nRMkPUxJnD5MD+5fxJDHUUOlaO6dQcnpiQzvr/r5Yf1cAq/MgwU6WHnRopIF+ysA/K7eeSg VIVvO1VY2CuYuiQrnD14obuZE15iSXYSEfWDiN3QgmgAo+tGPM5LltrsbfWRYRSeXnbUjfN+O O41h/rE/TaICYsRd5IWx3G9D8752/ACg6ajv7lmRT5dJragUsX8l44mGBPBJ4RhDfQbf6ejgX MUyPi+/zoP6dtRCXDkrIhKQR+1Gf8X7pilEMgmLfYcshxPex9t9F71E7jlDWJkVFBe1jEcV9k UCygB3IvvUcTV21vRiNAl7GDK4oOh1uDBh2p5T/HU3cHw0kIsMdWDEGU2YX9zoWQ+XmTDOYt0 VvnadPWG4wZo2hltIS0SPLp2ZsjuNY4id/hcbvRlkSZXMpY//rzaaJEk66h8HXPQviQ+14mOp g1QBGzb7gCWOtQ3NwB5HlTh9nk8JxnURdFyJeZPduU24TsMvQH3Hq5TuoyvBvZxD4acfcHXja 8++m8JRW8bjcTowpadbML0+Dm+0Cw11RhPHC36swJdJxL446ZP9O1SBvXxggzJSXC7n31P2oB K0cGw1xAFSV21PUILNIf7FCSh1klVr/dWi/oCMFJ44melnUgz3A0hq/4drPJMbkMPpswFKKK5 GLfrpv4B3/4fUu6m3ytpWdjCur3oi43ftH+4pR2yvTYVnEBmyf1cQ3/65HLH2wgWX//AeyqMd 67IbDGC X-Mailman-Approved-At: Wed, 06 Jun 2018 10:10:01 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jun 2018 05:00:51 -0000 Hello, my desperate call for help is according to PR 225291, https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225291. On one of our Workstations (Fujitsu Celsius M740 with Haswell XEON 6-core CPU) I face the inability to burn larger DVDs, using the port sysutils/dvd+rw-tools. The recent status of the OS is FreeBSD 12.0-CURRENT #38 r334651: Tue Jun 5 13:33:18 CEST 2018 amd64, but this problem has been present since January, see PR citet above. The fact is, that with several DVD burner (all older models), burning DVDs of larger sizes (> 4 GB) started to fail around December/January and I thought that might be due to a defect of the hardware. After switching to other exchange burner models, the same error occured. While I was able to finish the job in January after the Seg fault occured, this is now impossible, even with the DVD burner it worked prior. Please have a look at the PR cited above for more details. Thanks in advance, Oliver From owner-freebsd-current@freebsd.org Wed Jun 6 10:21:15 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 41FCBFEFB4F for ; Wed, 6 Jun 2018 10:21:15 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x230.google.com (mail-io0-x230.google.com [IPv6:2607:f8b0:4001:c06::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C672A6DBE4 for ; Wed, 6 Jun 2018 10:21:14 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x230.google.com with SMTP id t6-v6so6973492iob.10 for ; Wed, 06 Jun 2018 03:21:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=ClCdjHEgVFZV3/WA32WnwHlDa6X1Ncb4kx4fYeEcBTQ=; b=krDzjVPbxBoIozYcsZF3k7TsBB6qSjz6C5wMG21xK/M8zaKQXA2cfSUp243cK2q1rD 9W3nva2ESEm9cgLYPZBhdTCnYE9WOMnF26uYBFvkzUJAd8gwah/2aj8NtApOyACDE+AW vRDRqQ5EebRhUd+XGgB5hXc9fZ8bWTAk32VP6Ltjsy3e4HLgsaZnqQEuanar4UWur/Kj Jw9Pi+ij1dqU5/pv9MxBn1hR+P7UXC4WrNZpIon51DwnWt+oxO6M6aS1dUM7X+hBeabm n974o+HqCqGRlOhHJjWBc+kkOtgvuzcGbqnTu3kiOgO2ur8jsSC8tVAGL00QreVKYkBd 2O/A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=ClCdjHEgVFZV3/WA32WnwHlDa6X1Ncb4kx4fYeEcBTQ=; b=dymBk0xc0je+BAiSLGeCaJcueQyU/sHh5THEMpxeRFXNxMBIAqf/2zQsv4d/espT3E dqFXBNlPKEC+EehMlDbHnoUMfmVhnVNUNJSbqAuTLAoU24Rs8Ll8TDuH291KnaIMMdmv p3foZwtRwhL68VNJ6JNw6lKXHYTAL23LL+l97S3lrcjHLLIYTQw25o5rmgo5kF+cuDBx o7MNLkeZ0yCBlx7CGSVIIVL58hiaqU2jLvnqraG5+sML1VY19ktsromP0tFFGlUlfSiV 2E67Uz7En/q7SPTYFzUvNqZ+2LdC36oSz+I0ZxRgiLwE7il8E6nZMy/s88sw7pG0r2DC k/Lg== X-Gm-Message-State: APt69E2gA+cWFl6Hs+ZCZjZH/bOBBtwm7k3hpjNyB+ad1knrhyeHtXTS wy2tbkhI7qwUNoqpHH6+3TbBzkC8lkCfl5PvkII+1g== X-Google-Smtp-Source: ADUXVKLK+EKMX215e/Vy7sYkNO9lXzRM1jwZ5s9xsT+t6DFWjuxRZ7ZLrNZDPKyzf6BzAEzag45KtAvAIarQE6vNkVU= X-Received: by 2002:a5e:9817:: with SMTP id s23-v6mr2233081ioj.117.1528280474053; Wed, 06 Jun 2018 03:21:14 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:d028:0:0:0:0:0 with HTTP; Wed, 6 Jun 2018 03:21:13 -0700 (PDT) X-Originating-IP: [38.64.177.126] In-Reply-To: <20180606065520.1b927cdf@freyja.zeit4.iv.bundesimmobilien.de> References: <20180606065520.1b927cdf@freyja.zeit4.iv.bundesimmobilien.de> From: Warner Losh Date: Wed, 6 Jun 2018 06:21:13 -0400 X-Google-Sender-Auth: ki_TJxb-wrxRkCc07s4F8uLF7qM Message-ID: Subject: Re: CAM/ growisofs: Segmentation fault, SCSI sense: ILLEGAL REQUEST asc:21,0 (Logical block address out of range) To: "O. Hartmann" Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jun 2018 10:21:15 -0000 On Wed, Jun 6, 2018 at 12:55 AM, O. Hartmann wrote: > Hello, > > my desperate call for help is according to PR 225291, > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225291. > > On one of our Workstations (Fujitsu Celsius M740 with Haswell XEON 6-core > CPU) > I face the inability to burn larger DVDs, using the port > sysutils/dvd+rw-tools. > > The recent status of the OS is FreeBSD 12.0-CURRENT #38 r334651: Tue Jun 5 > 13:33:18 CEST 2018 amd64, but this problem has been present since January, > see > PR citet above. > > The fact is, that with several DVD burner (all older models), burning DVDs > of > larger sizes (> 4 GB) started to fail around December/January and I thought > that might be due to a defect of the hardware. After switching to other > exchange burner models, the same error occured. > > While I was able to finish the job in January after the Seg fault occured, > this > is now impossible, even with the DVD burner it worked prior. > > Please have a look at the PR cited above for more details. > Without more details, I'm at a loss. I took a quick look at the bug report. I'm thinking that a lot of this is 'effect' not cause. The drive is getting some kind of bad request (or is just nuts, but we'll hold hardware breaking in reserve for the moment) and we're reacting appropriately to it (though the userland growisofs program segment faulting is clearly bad -- likely an untested error path). So I'm unsure what to do next... Any chance at all you can bisect the revision where this started happening? Warner From owner-freebsd-current@freebsd.org Wed Jun 6 14:20:56 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 41254FF7B4A for ; Wed, 6 Jun 2018 14:20:56 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E2B6B767E5; Wed, 6 Jun 2018 14:20:55 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (unknown [127.0.1.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id ADF052B13; Wed, 6 Jun 2018 14:20:55 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [172.31.3.2]) by mail.xzibition.com (Postfix) with ESMTP id 649FF5C21; Wed, 6 Jun 2018 14:20:54 +0000 (UTC) X-Virus-Scanned: amavisd-new at mail.xzibition.com Received: from mail.xzibition.com ([172.31.3.2]) by mail.xzibition.com (mail.xzibition.com [172.31.3.2]) (amavisd-new, port 10026) with LMTP id NEXA0U-Dz5zB; Wed, 6 Jun 2018 14:20:52 +0000 (UTC) Content-Type: text/plain; charset=us-ascii DKIM-Filter: OpenDKIM Filter v2.10.3 mail.xzibition.com E77935C1D Mime-Version: 1.0 (1.0) Subject: Re: error building libpmc_events.c From: Bryan Drewery X-Mailer: iPhone Mail (15E302) In-Reply-To: <8a2bdd46-f3f2-61e7-d757-5187156f7ac5@orange.fr> Date: Wed, 6 Jun 2018 10:20:49 -0400 Cc: FreeBSD Current , mmacy@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <4D71D6AB-C715-4BC4-8A84-E20C86E2A519@FreeBSD.org> References: <517b70cf-c5dc-db7b-7887-43cd74f3e10c@orange.fr> <8a2bdd46-f3f2-61e7-d757-5187156f7ac5@orange.fr> To: Claude Buisson X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jun 2018 14:20:56 -0000 I think I know the issue. Will try looking later today or tomorrow. Regards, Bryan Drewery > On Jun 5, 2018, at 13:18, Claude Buisson wrote: >=20 > Replying to my own mail for more details, and ccing potential commiters >=20 >> On 06/04/2018 17:34, Claude Buisson wrote: >> Hi, >> During a buildworld of head on amd64, from 332518 to 334590, the build st= ops with: >> --- all_subdir_lib/libpmc --- >> =3D=3D=3D> lib/libpmc (all) >> --- libpmc_events.c --- >> ./pmu-events/jevents "x86" /home/src/lib/libpmc/pmu-events/arch libpmc_ev= ents.c >> sh: ./pmu-events/jevents: not found >> *** [libpmc_events.c] Error code 127 >> ... >=20 > This was during the lib32 build: jevents is not built in this context >=20 > The same error has been described by kevans@ on svn-src-all@ as a conseque= nce of svn 334226 (by bdrewery), pmu-events having since been moved in svn r= 334242 (by mmacy) >=20 > CBu From owner-freebsd-current@freebsd.org Wed Jun 6 15:03:04 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1AFFCFF8DFB; Wed, 6 Jun 2018 15:03:04 +0000 (UTC) (envelope-from dsamms@nw-ds.com) Received: from web.nwds.us (web2.nwds.us [135.84.180.41]) (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 A86F5781B6; Wed, 6 Jun 2018 15:03:03 +0000 (UTC) (envelope-from dsamms@nw-ds.com) Received: from localhost (localhost [127.0.0.1]) by web.nwds.us (Postfix) with ESMTP id 198CD218C6; Wed, 6 Jun 2018 09:02:57 -0600 (MDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nw-ds.com; h= content-transfer-encoding:content-language:content-type :content-type:in-reply-to:mime-version:user-agent:date:date :message-id:reply-to:from:from:references:subject:subject; s= default; t=1528297376; x=1530111777; bh=fshxLCv6jpO8IETryg8a6z8m kLse5Da73DzJLbz4ZwQ=; b=K4kCV+sAF137/RpdPJSgbzTeQ3ssz3VPwZbeLl99 QIGKsd//A2MazgvhUQ738PnZLBI/FU5PG2WBuREn0pu9/7oeltkowLRqLyK/aWWO aR9fHTd4msJ5O/Tgdk8It7Jwu4zUhEnBz+1AnvD/Lh6bK9lnOn+2bnekVN03m+o7 pOoU6SDTM21h1yWNgde5rQSIPJ+uX0dZkli5IxT3Hp7m3l64sGHJ/vPA5W8UR18Y jDV4pfs+2vEJyOXQkXIdNZp6/5plJSHwjo0CER4mccKiuxtEHim4emxgPFPpc6zq LJbWfwnqG1Ev5whnA4RlgblP7GOnSmhsBsRwuNS70BBl6Q== X-Virus-Scanned: Debian amavisd-new at web.nwds.us Received: from web.nwds.us ([127.0.0.1]) by localhost (smtp-1.nwds.us [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id uCszplUruJEm; Wed, 6 Jun 2018 09:02:56 -0600 (MDT) Received: from xeon.localdomain (host-98-127-45-240.grf-mt.client.bresnan.net [98.127.45.240]) (Authenticated sender: dsamms@nw-ds.com) by web.nwds.us (Postfix) with ESMTPSA id B79DE20852; Wed, 6 Jun 2018 09:02:56 -0600 (MDT) Subject: Re: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted To: Glen Barber , freebsd-current@freebsd.org, freebsd-stable@freebsd.org References: <20180530155039.GE97814@FreeBSD.org> From: David Samms Reply-To: 2yt@gmx.com Message-ID: <92949769-94c2-8b5c-5c34-08e0f3c6a753@nw-ds.com> Date: Wed, 6 Jun 2018 09:02:55 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <20180530155039.GE97814@FreeBSD.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Wed, 06 Jun 2018 15:09:56 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jun 2018 15:03:04 -0000 Hi Tested both images in both modes on: Intel=AE Server Board S1200KP E3-1230 CPU BIOS/legacy mode work perfectly UEFI failed. Not surprising as I have never gotten FreeBSD UEFI to work=20 on this motherboard. Console displayed: ------------------------- /boot/kernel/kernel.... Booting... Start... EFI frame... addr, size... dimensions... stride... masks... _ Required power to be cycled --=20 David Samms From owner-freebsd-current@freebsd.org Wed Jun 6 15:30:22 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D3294FD1521 for ; Wed, 6 Jun 2018 15:30:22 +0000 (UTC) (envelope-from clbuisson@orange.fr) Received: from smtp.smtpout.orange.fr (smtp05.smtpout.orange.fr [80.12.242.127]) by mx1.freebsd.org (Postfix) with ESMTP id 570A179EC1 for ; Wed, 6 Jun 2018 15:30:22 +0000 (UTC) (envelope-from clbuisson@orange.fr) Received: from localhost ([92.134.115.95]) by mwinf5d10 with ME id vTNj1x00B23Zv9G03TNjWj; Wed, 06 Jun 2018 17:22:44 +0200 X-ME-Helo: localhost X-ME-Auth: Y2xidWlzc29uQHdhbmFkb28uZnI= X-ME-Date: Wed, 06 Jun 2018 17:22:44 +0200 X-ME-IP: 92.134.115.95 Subject: Re: error building libpmc_events.c [solved (sort of)] To: Bryan Drewery Cc: FreeBSD Current , mmacy@freebsd.org References: <517b70cf-c5dc-db7b-7887-43cd74f3e10c@orange.fr> <8a2bdd46-f3f2-61e7-d757-5187156f7ac5@orange.fr> <4D71D6AB-C715-4BC4-8A84-E20C86E2A519@FreeBSD.org> From: Claude Buisson Message-ID: Date: Wed, 6 Jun 2018 17:22:42 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <4D71D6AB-C715-4BC4-8A84-E20C86E2A519@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.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jun 2018 15:30:23 -0000 On 06/06/2018 16:20, Bryan Drewery wrote: > I think I know the issue. Will try looking later today or tomorrow. > > Regards, > Bryan Drewery > >> On Jun 5, 2018, at 13:18, Claude Buisson wrote: >> >> Replying to my own mail for more details, and ccing potential commiters >> >>> On 06/04/2018 17:34, Claude Buisson wrote: >>> Hi, >>> During a buildworld of head on amd64, from 332518 to 334590, the build stops with: >>> --- all_subdir_lib/libpmc --- >>> ===> lib/libpmc (all) >>> --- libpmc_events.c --- >>> ./pmu-events/jevents "x86" /home/src/lib/libpmc/pmu-events/arch libpmc_events.c >>> sh: ./pmu-events/jevents: not found >>> *** [libpmc_events.c] Error code 127 >>> ... >> >> This was during the lib32 build: jevents is not built in this context >> >> The same error has been described by kevans@ on svn-src-all@ as a consequence of svn 334226 (by bdrewery), pmu-events having since been moved in svn r334242 (by mmacy) >> >> CBu > After further investigations, I found that jevents was effectively built, but in the src directory, instead of obj-lib32 Commenting WITHOUT_AUTO_OBJ in src-env.conf has been sufficient to get a successful buildword ! So the question becomes: must WITHOUT_AUTO_OBJ be supported by the build infrastructure ? Thanks for your time CBu From owner-freebsd-current@freebsd.org Wed Jun 6 15:36:03 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EE35AFD1A38 for ; Wed, 6 Jun 2018 15:36:02 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8B0E77A5C2; Wed, 6 Jun 2018 15:36:02 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (unknown [127.0.1.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id 5F6694CB8; Wed, 6 Jun 2018 15:36:02 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [172.31.3.2]) by mail.xzibition.com (Postfix) with ESMTP id 3A2695E6F; Wed, 6 Jun 2018 15:36:01 +0000 (UTC) X-Virus-Scanned: amavisd-new at mail.xzibition.com Received: from mail.xzibition.com ([172.31.3.2]) by mail.xzibition.com (mail.xzibition.com [172.31.3.2]) (amavisd-new, port 10026) with LMTP id dY3mwBGO5fbO; Wed, 6 Jun 2018 15:35:58 +0000 (UTC) Subject: Re: error building libpmc_events.c [solved (sort of)] DKIM-Filter: OpenDKIM Filter v2.10.3 mail.xzibition.com 4119C5E69 To: Claude Buisson Cc: FreeBSD Current , mmacy@freebsd.org References: <517b70cf-c5dc-db7b-7887-43cd74f3e10c@orange.fr> <8a2bdd46-f3f2-61e7-d757-5187156f7ac5@orange.fr> <4D71D6AB-C715-4BC4-8A84-E20C86E2A519@FreeBSD.org> From: Bryan Drewery Openpgp: preference=signencrypt Autocrypt: addr=bdrewery@FreeBSD.org; prefer-encrypt=mutual; keydata= xsBNBFJphmsBCADiFgmS4bIzwZijrS31SjEMzg+n5zNellgM+HkShwehpqCiyhXdWrvH6dTZ a6u50pbUIX7doTR7W7PQHCjCTqtpwvcj0eulZva+iHFp+XrbgSFHn+VVXgkYP2MFySyZRFab D2qqzJBEJofhpv4HvY6uQI5K99pMqKr1Z/lHqsijYYu4RH2OfwB5PinId7xeldzWEonVoCr+ rfxzO/UrgA6v/3layGZcKNHFjmc3NqoN1DXtdaEHqtjIozzbndVkH6lkFvIpIrI6i5ox8pwp VxsxLCr/4Musd5CWgHiet5kSw2SzNeA8FbxdLYCpXNVu+uBACEbCUP+CSNy3NVfEUxsBABEB AAHNJEJyeWFuIERyZXdlcnkgPGJkcmV3ZXJ5QEZyZWVCU0Qub3JnPsLAgAQTAQoAKgIbAwUL CQgHAwUVCgkICwUWAwIBAAIeAQIXgAIZAQUCWujOIgUJCmB7NwAKCRA113G7bkaXz/xpB/9b /UWIPbieY1IeIuHF2pyYPE7Hytkh3HVsxMA0F5Ma2AYQsXZZeKNKWrF7RPyDyDwUklLHJkhm k3EfClBbHxf08kMIm1vWCJRtgxic9knY/bzYGiWMpHjg3cSd1XfrYH1autYqTZAjDwIkgOjU dR//Tbn4V36sY7y2jz+kdMVWvK53U32aZqiwBbCn4DPe1wSZcUs17mV/0uZdIoGdj74B1orN A/0py5vHYo6HcbBNoaR8pKRLf5VZNRsxqGIMhTucx4SJWcHpuRBWYyvJSFzwvxdK4ZD4Yqoc kFGPVtOXktVMai9exrLvP3G77fKMu8DI6j4QRU4wCesnHuIfRPFuzsBNBFJphmsBCACiVFPf kNfaFtUSuY0395ueo/rMyHPGPQ2iwvERFCpeFGSQSgagpenNHLpFQKTg/dl6FOoST5tqyxMq fyHGHDzzU51bvA/IfaGoNi/BIhTe/toZNMRvpcI3PLjiGcnJnuwCCbAVOAGdb+t5cZtpNdOI cKYmrYG3u9RiBpe6dTF+qLrD/8Bs1wjhduQ8fcNNgnkXu8xDH4ZxY0lIc3QgvYWp9vimlQe6 iKjUd2/DX28ETZcD5h6pYV331KMPTrEI0p0yvFijUZce8c1XHFyL1j9sBAha5qpszJl6Uq5i LolhKRcGfcdmtD72vHQjUYglUyudSJUVyo2gMYjdbiFKzJulABEBAAHCwGUEGAEKAA8FAlJp hmsCGwwFCQlmAYAACgkQNddxu25Gl89UPggA2mGQp28yCUKsJ6KHFVy/lpHfoQrKF+s7HfKT U2ObVeVNX4I8ZdW1UO48mRqxEOwY8r5YSH6X06OmiqCX2aSMXg3N06/l+ztlB0+UGGlkXBjv l9/nii+bC6b8XWuu0X7Qpb9oYBK9YtoaoyuVplAmjdj/cPou65meKIaS1yDTjHh450DrW8Qg he6l0bFX4BHKTSm99U90ML7EY19B6iI2BZSqWutVsyD71oAREY6NGgDpCOIO6FS41+WeYCDR j8vsa/BiaoX2d2SBDsCwsEwe9fg5PYMi2uVIhvL6OrxnwOdB+TkgvOy5zZSNO29UG/JilZKo Ndz2wpEaUzChGGqLvcLAZQQYAQoADwIbDAUCWujOKAUJCmB7PQAKCRA113G7bkaXz6bkB/9H dUR3E0wBwMh6z0AOFDKh+PbRI9Xd4IncdhE55tNK410650a3gADIDwqz3i72GIinkgaxzpEO xP1bs7a+BeF3p5Xd6Jjk6J/nEshisgNW7VjUbJHFGs8Sf9A6oM3q4VkI/ArVo5qkZxgKs72U HSAy5NV+AdqdTrWuAL20xfQ6gA7JF35Xf8zyUM2GMl0X8ik7dJ1jMp+TB27LipqbDgamFzH9 F9hC9gur94OQ/x3nQ+mFZ1uipYHA1EdrKuhb/Ts4bN/Ezl8nmYGxc9Bw7ZBxGOTId/rEIzoe LWpAvg6dcw0T9lNfSWc6PX+kf3dOXNIdkw9NqKID8wEPe8axcGYG Organization: FreeBSD Message-ID: Date: Wed, 6 Jun 2018 11:35:55 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="dgJ6HBNxzCZqLjhLnD9ci78lW83uuXpHJ" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jun 2018 15:36:03 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --dgJ6HBNxzCZqLjhLnD9ci78lW83uuXpHJ Content-Type: multipart/mixed; boundary="Z3RCZzetWUq3g5ZFmdNFpCGXRiZgi9FBQ"; protected-headers="v1" From: Bryan Drewery To: Claude Buisson Cc: FreeBSD Current , mmacy@freebsd.org Message-ID: Subject: Re: error building libpmc_events.c [solved (sort of)] References: <517b70cf-c5dc-db7b-7887-43cd74f3e10c@orange.fr> <8a2bdd46-f3f2-61e7-d757-5187156f7ac5@orange.fr> <4D71D6AB-C715-4BC4-8A84-E20C86E2A519@FreeBSD.org> In-Reply-To: --Z3RCZzetWUq3g5ZFmdNFpCGXRiZgi9FBQ Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 6/6/18 11:22 AM, Claude Buisson wrote: > On 06/06/2018 16:20, Bryan Drewery wrote: >> I think I know the issue. Will try looking later today or tomorrow. >> >> Regards, >> Bryan Drewery >> >>> On Jun 5, 2018, at 13:18, Claude Buisson wrote:= >>> >>> Replying to my own mail for more details, and ccing potential commite= rs >>> >>>> On 06/04/2018 17:34, Claude Buisson wrote: >>>> Hi, >>>> During a buildworld of head on amd64, from 332518 to 334590, the >>>> build stops with: >>>> --- all_subdir_lib/libpmc --- >>>> =3D=3D=3D> lib/libpmc (all) >>>> --- libpmc_events.c --- >>>> ./pmu-events/jevents "x86" /home/src/lib/libpmc/pmu-events/arch >>>> libpmc_events.c >>>> sh: ./pmu-events/jevents: not found >>>> *** [libpmc_events.c] Error code 127 >>>> ... >>> >>> This was during the lib32 build: jevents is not built in this context= >>> >>> The same error has been described by kevans@ on svn-src-all@ as a >>> consequence of svn 334226 (by bdrewery), pmu-events having since been= >>> moved in svn r334242 (by mmacy) >>> >>> CBu >> >=20 > After further investigations, I found that jevents was effectively > built, but in the src directory, instead of obj-lib32 >=20 > Commenting WITHOUT_AUTO_OBJ in src-env.conf has been sufficient to get = a > successful buildword ! >=20 > So the question becomes: must WITHOUT_AUTO_OBJ be supported by the buil= d > infrastructure ? Well it's exactly why WITH_AUTO_OBJ is a thing. There's no reason jevents should be in your source tree when using buildworld. If you were building manually in the directories then that's why WITH_AUTO_OBJ is there, to prevent the binary from being written to the source tree later leading to build problems like this. WITHOUT_AUTO_OBJ is "supported" as much as it was before, expect problems like this. I don't recommend setting WITHOUT_AUTO_OBJ. Feedback on why you were using it would help. >=20 > Thanks for your time >=20 > CBu --=20 Regards, Bryan Drewery --Z3RCZzetWUq3g5ZFmdNFpCGXRiZgi9FBQ-- --dgJ6HBNxzCZqLjhLnD9ci78lW83uuXpHJ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEE+Rc8ssOq6npcih8JNddxu25Gl88FAlsX/1wACgkQNddxu25G l8+Higf/SISLVowZlWayQ6SPFzilXN5E1oCnzUs3g3bdaN0ifPKqgxvFwVMCvHce O1l3A3O+YCbt83e2pUf6wmmB+HMAeAPkEFRsqTIkkiMrw6815U/QbB+NjS5fkwjB dnM3ezevYHzl/GPwbEFwWlc+3EUIFZcuOXnSXK4sItXq0qRUEO3ieA/9jNsUdL8o shq9qAxqJdRNzdcK8WDXUKJPJq/eaWpVdqnY1IRbjLV8YQtkPO9CIIOFKL0Oaglq BoRmaUGuCboPIY/pTbKQcSvjkyo+leDR/kZcQWatFBp5bt+UDS+6OOndjEee3IgB NgI6H0NFKLaar8vLOyqjS7jsG2w1bQ== =uPcr -----END PGP SIGNATURE----- --dgJ6HBNxzCZqLjhLnD9ci78lW83uuXpHJ-- From owner-freebsd-current@freebsd.org Wed Jun 6 16:26:23 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 35E0FFD45E9 for ; Wed, 6 Jun 2018 16:26:23 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-io0-f174.google.com (mail-io0-f174.google.com [209.85.223.174]) (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 C80F67C527 for ; Wed, 6 Jun 2018 16:26:22 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-io0-f174.google.com with SMTP id r24-v6so8290785ioh.9 for ; Wed, 06 Jun 2018 09:26:22 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=RN74gV13qn/TvWitDti1pzmTiJiW42FQvwr16ZwF/pM=; b=Nu6/M4iGXK3X58Mlfsx4WRggQUeRhCKXjLIDloC65mMasRffWeInpkFJil6KXtgHa6 oWDCi92r94T8+09YJ1rz4xbi+9FXdA/6D1f1r+zxsJXRVqzTbHG465g+q7eDQk1aye18 ELPrfl7HcYI4MlskzyLEyLH++LV3uRWpWbsq+d74Qx26SxsxDOJacnh8w6OYk0rNPncD hj7D3p985XBKb0/spoxYyWaS3TDuZ0JZy3ViSbS1fhy7AEHgziSTl/ZO32Ig2uRwargN LpabjBjiBIlq24JmEz6O6uFejPZ6Qc7xJPcXYAMzafPDl3JkzGOW2+qvS1yJ5os4p8H1 Zv3A== X-Gm-Message-State: APt69E2ZP3DfxnL1JaJ+IuRzZpLw271B2jUIkgMWJgFVkCBBhQ/EDL0s gZcbm3iY4Bp5M4jW4FUsOC/iaZit X-Google-Smtp-Source: ADUXVKLa78bC10AlQZJPw56u2SJUMbqeBg14EBxdidB9pzXALLis38haz+wLdgyZLjroc2FpRmVopg== X-Received: by 2002:a6b:3110:: with SMTP id j16-v6mr3532635ioa.249.1528302000007; Wed, 06 Jun 2018 09:20:00 -0700 (PDT) Received: from mail-io0-f172.google.com (mail-io0-f172.google.com. [209.85.223.172]) by smtp.gmail.com with ESMTPSA id s9-v6sm4516500ioa.66.2018.06.06.09.19.59 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 Jun 2018 09:19:59 -0700 (PDT) Received: by mail-io0-f172.google.com with SMTP id e15-v6so8301197iog.1 for ; Wed, 06 Jun 2018 09:19:59 -0700 (PDT) X-Received: by 2002:a6b:b5c1:: with SMTP id e184-v6mr3673706iof.267.1528301999735; Wed, 06 Jun 2018 09:19:59 -0700 (PDT) MIME-Version: 1.0 Reply-To: cem@freebsd.org Received: by 2002:a02:5995:0:0:0:0:0 with HTTP; Wed, 6 Jun 2018 09:19:59 -0700 (PDT) In-Reply-To: <20180606011218.GA72167@kduck.kaduk.org> References: <20180606011218.GA72167@kduck.kaduk.org> From: Conrad Meyer Date: Wed, 6 Jun 2018 09:19:59 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: how do I use the make universe machines? To: Rick Macklem Cc: "freebsd-current@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jun 2018 16:26:23 -0000 On Tue, Jun 5, 2018 at 6:12 PM, Benjamin Kaduk wrote: > On Wed, Jun 06, 2018 at 12:47:17AM +0000, Rick Macklem wrote: >> I've heard mention of "make universe" machines multiple times, >> but have no idea how to use them? >> Is there doc on this? >> >> Thanks, rick >> ps: I'll admit I haven't looked at the developer's guide in a long time. > > I think https://www.freebsd.org/internal/machines.html sounds like > the page you're looking for. (universe is just a top-level make > target like buildworld, but will take a while on non-beefy > hardware.) Hi Rick, Yep, those are the machines you want. Note those host names listed are subdomains below the top-level freebsd.org domain. All of the 'universeNNa' hostnames are jails on a single, relatively beefy server running CURRENT, and the 'universeNNb' hostnames are all jails on a different, relatively beefy server running CURRENT. SSH credentials are the same as for freefall. Conveniently, motd on these machines contains the usual convention for running the universe target on them: Hint: env MAKEOBJDIRPREFIX=/scratch/tmp/$USER/obj \ make -s -j8 __MAKE_CONF=/dev/null tinderbox I would modify that slightly, replacing -j8 with -j$(sysctl -n hw.ncpu), in the usual case that no one else is utilizing the machine at the same time. -DNO_CLEAN might be quite useful for incremental polishing work on a patch for any previously failed arches. The clean build should finish in under an hour, IIRC. Best, Conrad From owner-freebsd-current@freebsd.org Wed Jun 6 16:50:44 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C1A05FD54F4 for ; Wed, 6 Jun 2018 16:50:44 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from smtp.fagskolen.gjovik.no (smtp.fagskolen.gjovik.no [IPv6:2001:700:1100:1:200:ff:fe00:b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.fagskolen.gjovik.no", Issuer "Fagskolen i Gj??vik" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 34FDD7D466 for ; Wed, 6 Jun 2018 16:50:43 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from mail.fig.ol.no (localhost [127.0.0.1]) by mail.fig.ol.no (8.15.2/8.15.2) with ESMTPS id w56GocFK096204 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Wed, 6 Jun 2018 18:50:38 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) Received: from localhost (trond@localhost) by mail.fig.ol.no (8.15.2/8.15.2/Submit) with ESMTP id w56GocIp096201 for ; Wed, 6 Jun 2018 18:50:38 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) X-Authentication-Warning: mail.fig.ol.no: trond owned process doing -bs Date: Wed, 6 Jun 2018 18:50:37 +0200 (CEST) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Sender: Trond.Endrestol@fagskolen.gjovik.no To: FreeBSD current Subject: r334533 renders head unbootable on XenServer 7.4 Message-ID: User-Agent: Alpine 2.21.999 (BSF 260 2018-02-26) Organization: Fagskolen Innlandet OpenPGP: url=http://fig.ol.no/~trond/trond.key MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.fig.ol.no X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jun 2018 16:50:44 -0000 After trial and error, I found r334533 to be responsible for rendering head unbootable on XenServer 7.4. Neither of the two available XenServer patches has been applied on the host server. Normal and verbose boot messages stops non-deterministically at: hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Or at: granttable0: on xenpv0 This is on a non-critical VM, but I think this issue should be resolved by the time stable/12 becomes available, or if stable/11 will be impacted by a MFH of r334533 in the near future. The host server will be upgraded to XenServer 7.5 by the end of the week, in case that makes the issue go away. -- Trond. From owner-freebsd-current@freebsd.org Wed Jun 6 18:55:45 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 54187FDE9D9; Wed, 6 Jun 2018 18:55:45 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DB3E6820EC; Wed, 6 Jun 2018 18:55:44 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.110.112]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1fQdat-0004aE-Ty; Wed, 06 Jun 2018 20:55:40 +0200 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "bob prohaska" Cc: freebsd-arm@freebsd.org, "FreeBSD Current" Subject: Re: panic: Assertion td->td_lock == TDQ_LOCKPTR(tdq) failed at /usr/src/sys/kern/sched_ule.c:2137 References: <20180601154153.GA62632@www.zefox.net> Date: Wed, 06 Jun 2018 20:55:39 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.4.0 X-Scan-Signature: a6d9551f4f6a9cf0aa9f9bf7e32696d9 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jun 2018 18:55:45 -0000 On Sat, 02 Jun 2018 13:40:27 +0200, Ronald Klop wrote: > This happened again. Now I have a crashdump. > Anyone interested? > > Some more answers below. > > > On Fri, 01 Jun 2018 17:41:54 +0200, bob prohaska > wrote: > >> On Thu, May 31, 2018 at 05:53:12PM +0200, Ronald Klop wrote: >>> I had a crash on my RPI-3B+ running freebsd 12/aarch64 from the 29 may >>> snapshot. >>> It was building world -j4 and portsnap extract. >>> >>> I will keep it in the debugger for about an hour so if I need to >>> provide >>> more information, please mail me. >>> >>> >>> db> show panic >>> panic: Assertion td->td_lock == TDQ_LOCKPTR(tdq) failed at >>> /usr/src/sys/kern/sched_ule.c:2137 >>> >> This used to be a fairly common error on my RPI3, but I haven't seen >> it in some time. >> >> As a matter of curiosity, have you been able to run a -j4 buildworld >> to completion on your RPI3? If so, please post your setup. For several >> months now all my attempts at j4 buildworld have failed with "killed, >> out of swap" even though top seems to report minimal swap usage. It >> even happens with no -j value set at all, but usually restarting with >> -DNO_CLEAN allowed progress to pick up where it left off. How do you ever run a -j4 buildworld? My RPI3 starts building clang/llvm with sometimes 500 MB+ per process so everything starts swapping like hell and takes forever to run. Regards, Ronald. >> >> Alas, as I write this, the kernel just reported >> >> Jun 1 08:34:34 www kernel: pid 19399 (c++), uid 0, was killed: out of >> swap space >> >> top is showing >> Swap: 4096M Total, 17M Used, 4079M Free >> but since top is alive the value is stale. Nonetheless, I have seen top >> killed while still showing minimal swap usage. >> >> It seems as if the "out of swap" kills are being issued in error.. >> >> Thanks for reading, >> >> bob prohaska >> > > > I just received my RPI3 this week. It is running GENERIC with debug > options still. Building a -NODEBUG kernel from src didn't succeed yet > because of the mentioned panic. > I'm now building with -j2 to be on the safe side. > > After I have the -NODEBUG kernel it will be a bit faster and I will try > -j4 again. > > Regards, > Ronald. From owner-freebsd-current@freebsd.org Wed Jun 6 23:57:57 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 51944FE7CD4; Wed, 6 Jun 2018 23:57:57 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A6B6172675; Wed, 6 Jun 2018 23:57:56 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w56Nw2eg091352 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 6 Jun 2018 16:58:03 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w56Nw2fY091351; Wed, 6 Jun 2018 16:58:02 -0700 (PDT) (envelope-from fbsd) Date: Wed, 6 Jun 2018 16:58:01 -0700 From: bob prohaska To: Ronald Klop Cc: freebsd-arm@freebsd.org, FreeBSD Current , bob prohaska Subject: Re: panic: Assertion td->td_lock == TDQ_LOCKPTR(tdq) failed at /usr/src/sys/kern/sched_ule.c:2137 Message-ID: <20180606235801.GA87339@www.zefox.net> References: <20180601154153.GA62632@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jun 2018 23:57:57 -0000 On Wed, Jun 06, 2018 at 08:55:39PM +0200, Ronald Klop wrote: > On Sat, 02 Jun 2018 13:40:27 +0200, Ronald Klop > wrote: > > > How do you ever run a -j4 buildworld? My RPI3 starts building clang/llvm > with sometimes 500 MB+ per process so everything starts swapping like hell > and takes forever to run. > Lately, never 8-) When I started playing with an RPI3, in late 2016, -j4 buildworlds worked usably well. Early in 2018 problems appeared, including Assertion td->td_lock == TDQ_LOCKPTR(tdq) failed, among others. Things didn't really go to pot until somewhat later when the swap frenzy issue reared its head and haven't improved much. Sadly, when the swap frenzy workaround of using sysctl vm.pageout_update_period=0 was suggested, a -j4 buildworld then resorted to the old td_lock issue, so it looks as if both bugs are alive and kicking. Just to complicate matters, I was in the habit of using a USB flash drive as both an outboard file system (/usr/, /var/ and /tmp/) and as a swap device. A very common reaction was to blame the flash device for the trouble, though so far as I can tell a Sandisk Extreme USB flash drive isn't much slower, if any, than a mechanical hard disk for random writes. The same USB flash devices on a Pi2 running 11-Stable seems to be fine. However, turning off the USB flash swap device does seem to reduce the number of "indefinite wait buffer" messages on the console (they're usually not fatal) so I think there is still something amiss. Whether it's the flash, the USB or the VM system is unclear to me. For now the workarounds are to run buildworld with no explicit -j value (presumably equivalent to -j1), to use only swap on the microSD card and to use the -DNO_CLEAN option for most buildworld sessions, doing an explict "make clean" or "rm -rf /usr/obj/usr" when necessary. In a few cases it seemed helpful to start with "make kernel-toolchain" then follow with make -DNO_CLEAN buildworld" but I didn't keep good enough records to be certain of the benefits. Apologies for the length, HTH bob prohaska From owner-freebsd-current@freebsd.org Thu Jun 7 05:29:11 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 90F97FF8184 for ; Thu, 7 Jun 2018 05:29:11 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic317-22.consmr.mail.gq1.yahoo.com (sonic317-22.consmr.mail.gq1.yahoo.com [98.137.66.148]) (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 1CCC17EAE7 for ; Thu, 7 Jun 2018 05:29:11 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: NZZngb8VM1k_pUjOUZx6dlc_T.Ys5uXI5Th_dvBXhv3pNx5Tzk5zvzfrKU6rKpM V7nevM8ITO0aePjYJSN33k8LAsAjov_aBRRKsKQcBb3cOzF6J6p9S.U35upmdUa6TbAMC519xJ7u FY3b0FLbiNCL_mkt4Ylzhq.UKS7vd2eg03SF.NWYR5y3V2qHk8NZJTEAZ46MNy7_roBiBYo_u92G 4egkrZVNa8bmwx5pC.AWO2ph94ZQMTiVHJbEYFtv53u7RxkPaIUnso5YqIXuwIg4ahBvPx3yOY3r KAW7pEm9CDCnA31Obh6rlRde8IqFNSPN33_TZADqoMNVcEMHGeHg_sQ5rMRnu6eG3Te1Fxbo2RdX D2RzP7w0fZaBUDPcy8rfld.SlQu5uclLfiRSRWRzcGP2N106hwmQbhHa5eq5wrEwe0YGO6tckdIF oOV0PRi3MTu3tMkNFG8m263pC_jTOkdHrwH44OuTJerTqGzl5fqpcGLfHW7Ef1vVvIBms.z7bYvk P7LXbWL31RxCvpyx0jlS2WVkHx6dIxNhk_nUuqy6t3NaiSs6yYF807wjLu6oKPu8FMcJfUYryxYY n_denswacdpDWd2qodyT4iKe71_p1m1d2lGLKWBDXyErRmftbPOA8whQblU_eW1bSrChRa43DFFQ Wygmnmc.AwtSM_bWK11dtR6wl.pUblNRRE3mEcR0ATFAlLPOJgnRshQLln7y5q1g0PNL4WhS5CEU BCuxLxZPecuJfvC5AqC6AqzZEB_ruLHWM.KCpJjwlWTgebSyUwvDVEVltWQfv8FK5RWpZzAjFpp8 zKvst9C6f4QLQaMLrry43nNyLNy2caz9owCdE6iVHQyVEi47BiaAPQt6braghK5SJIptZSdMwb67 2SIZKQ5OASg.mLY4dauj8aSkP7EUvRweYq08IbAz9Osvv3SVKFDbqtVZBHCzENlCfx82aEA-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic317.consmr.mail.gq1.yahoo.com with HTTP; Thu, 7 Jun 2018 05:29:03 +0000 Received: from ip70-189-131-151.lv.lv.cox.net (EHLO [192.168.0.109]) ([70.189.131.151]) by smtp411.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID eca1213dae89f799cd55944fbd3f215f; Thu, 07 Jun 2018 05:29:00 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: Re: panic: Assertion td->td_lock == TDQ_LOCKPTR(tdq) failed at /usr/src/sys/kern/sched_ule.c:2137 Message-Id: <6CEF9465-3908-4D5E-BC9E-967B9D1DD6AA@yahoo.com> Date: Wed, 6 Jun 2018 22:28:58 -0700 To: bob prohaska , FreeBSD Current , freebsd-arm@freebsd.org X-Mailer: Apple Mail (2.3445.8.2) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jun 2018 05:29:11 -0000 bob prohaska fbsd at www.zefox.net wrote on Wed Jun 6 23:57:57 UTC 2018 :=20 > On Wed, Jun 06, 2018 at 08:55:39PM +0200, Ronald Klop wrote: > > On Sat, 02 Jun 2018 13:40:27 +0200, Ronald Klop > =20 > > wrote: > >=20 > >=20 > > How do you ever run a -j4 buildworld? My RPI3 starts building = clang/llvm =20 > > with sometimes 500 MB+ per process so everything starts swapping = like hell =20 > > and takes forever to run. > > >=20 > Lately, never 8-) Looks like there has been another stab at avoiding some unnecessary Out Of Memory killing of processes: Author: alc Date: Thu Jun 7 02:54:11 2018 New Revision: 334752 URL: https://svnweb.freebsd.org/changeset/base/334752 Log: . . . One visible effect of this error was that processes were being killed by the virtual memory system's OOM killer when in fact there was plentiful free memory. (I do not have access to an appropriate test context at this time.) =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Thu Jun 7 11:28:20 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F33F4FE1F78 for ; Thu, 7 Jun 2018 11:28:19 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from CAN01-TO1-obe.outbound.protection.outlook.com (mail-eopbgr670057.outbound.protection.outlook.com [40.107.67.57]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT TLS CA 4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8EE208B92C for ; Thu, 7 Jun 2018 11:28:19 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from YTOPR0101MB0953.CANPRD01.PROD.OUTLOOK.COM (52.132.44.24) by YTOPR0101MB2283.CANPRD01.PROD.OUTLOOK.COM (52.132.51.23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.820.13; Thu, 7 Jun 2018 11:28:18 +0000 Received: from YTOPR0101MB0953.CANPRD01.PROD.OUTLOOK.COM ([fe80::a860:9237:2e9f:f87f]) by YTOPR0101MB0953.CANPRD01.PROD.OUTLOOK.COM ([fe80::a860:9237:2e9f:f87f%3]) with mapi id 15.20.0820.015; Thu, 7 Jun 2018 11:28:18 +0000 From: Rick Macklem To: Benjamin Kaduk CC: "freebsd-current@freebsd.org" Subject: Re: how do I use the make universe machines? Thread-Topic: how do I use the make universe machines? Thread-Index: AQHT/S+/hTGXEeL5mkihoTOoY7p6XKRSbHMAgAI9YYQ= Date: Thu, 7 Jun 2018 11:28:18 +0000 Message-ID: References: , <20180606011218.GA72167@kduck.kaduk.org> In-Reply-To: <20180606011218.GA72167@kduck.kaduk.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=rmacklem@uoguelph.ca; x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; YTOPR0101MB2283; 7:VmREn99gnc/IdNHEk6bLy4YMT4Hs9a9IPUk4vcQN21nuBCngP1LJ8zXeFI4vB2HoSrN2xsF6NDIJ/pGPUoV7Xoe/XGmC/UIEYmA38Xxia+iIJ/MKqIm6zBw1kLw3F045nnWQdxXlKZUroLor6Wx2OKoE5rFp3cmHvVQAj+nNdBVZyA9QAjENjePQm0i4XJm1gx+oFOoE2cE5lo2HaQLSHrEsBjuN07L2IXshDlVCoTV5Y3T+5t+fXoniHko/xblB x-ms-exchange-antispam-srfa-diagnostics: SOS; x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(8989080)(5600026)(4534165)(4627221)(201703031133081)(201702281549075)(8990040)(2017052603328)(7153060)(7193020); SRVR:YTOPR0101MB2283; x-ms-traffictypediagnostic: YTOPR0101MB2283: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-ms-exchange-senderadcheck: 1 x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(93006095)(93001095)(3002001)(10201501046)(3231254)(944501410)(52105095)(149027)(150027)(6041310)(201703131423095)(201702281529075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123562045)(20161123558120)(20161123564045)(6072148)(201708071742011)(7699016); SRVR:YTOPR0101MB2283; BCL:0; PCL:0; RULEID:; SRVR:YTOPR0101MB2283; x-forefront-prvs: 06968FD8C4 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(376002)(346002)(396003)(39860400002)(39380400002)(199004)(189003)(8936002)(316002)(25786009)(6246003)(4326008)(2171002)(97736004)(33656002)(53936002)(2906002)(6306002)(105586002)(5660300001)(9686003)(2900100001)(106356001)(74482002)(476003)(786003)(3280700002)(6916009)(5250100002)(3660700001)(99286004)(446003)(11346002)(68736007)(14454004)(8676002)(81166006)(81156014)(86362001)(229853002)(6436002)(74316002)(26005)(6506007)(305945005)(55016002)(186003)(478600001)(966005)(102836004)(7696005)(486006)(76176011); DIR:OUT; SFP:1101; SCL:1; SRVR:YTOPR0101MB2283; H:YTOPR0101MB0953.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: uoguelph.ca does not designate permitted sender hosts) x-microsoft-antispam-message-info: Xo6wnysAjLES2qQbp6OAkNtzXnBlnoSOCno1x5ZjkajFED9PtvymqU6ucrfnftTHRcCWwQWTGEme5kmYbPhHmi3jrX+DFFgxxkzWROQGfq0QhLCw904GeDHwf27ETwwscHOp1TfTpRlHAs7bYAdKYGSeZh0DNEnJZ5dyhVI1S50HzJz36t4Yp/lXZu2HBNU2 spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-MS-Office365-Filtering-Correlation-Id: 158b29af-44de-4082-bba0-08d5cc69c47c X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-Network-Message-Id: 158b29af-44de-4082-bba0-08d5cc69c47c X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Jun 2018 11:28:18.2309 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTOPR0101MB2283 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jun 2018 11:28:20 -0000 Just replying to one of the messages at random... Benjamin Kaduk wrote: [stuff snipped] >I think https://www.freebsd.org/internal/machines.html sounds like >the page you're looking for. (universe is just a top-level make >target like buildworld, but will take a while on non-beefy >hardware.) Yea, the last time I tried it on an i386 was FreeBSD9 and even then it took a week to complete.;-) Thanks everyone, it is working fine. In particular, I;d like to thank cem@ = for the hint about reading "motd" to see what the command is. Thanks again, rick From owner-freebsd-current@freebsd.org Thu Jun 7 15:44:56 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 28EFFFE1D73 for ; Thu, 7 Jun 2018 15:44:56 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [IPv6:2001:470:8d59:1::8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.protected-networks.net", Issuer "Protected Networks CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C2EE070630 for ; Thu, 7 Jun 2018 15:44:55 +0000 (UTC) (envelope-from imb@protected-networks.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= protected-networks.net; h=content-transfer-encoding :content-language:content-type:content-type:mime-version :user-agent:date:date:message-id:subject:subject:from:from; s= 201508; t=1528386294; bh=NGaKHtDpPqkEnOicBYGrgoRG8+hjIBAXNkxFZQp oGBs=; b=ij4e9GmuYeKaR0XaL/m3EJa/pvIRtYnHvKmKW9ZCxLBFfWPNQV31CGk OP8oJlFQHdnO2JBjDCgKDZkgrthr0gCxn2IJAvla/AkKakADDbPwHTeGl7YbBYgd gAvdHTnrGEVJwvn4IJLiLVTU6GtJyarw3NoGBKsafp2HgiqAYrvQ= Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [192.168.1.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: imb@mail.protected-networks.net) by mail.protected-networks.net (Postfix) with ESMTPSA id 0148C387AE for ; Thu, 7 Jun 2018 11:44:53 -0400 (EDT) To: freebsd-current From: Michael Butler Subject: rust broken? Openpgp: preference=signencrypt Message-ID: Date: Thu, 7 Jun 2018 11:44:53 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jun 2018 15:44:56 -0000 In response to a Firefox update, I tried to build the new version. However, rust now fails with a core-dump in the build process. checking for libffi > 3.0.9... yes checking MOZ_FFI_CFLAGS... -I/usr/local/lib/libffi-3.2.1/include checking MOZ_FFI_LIBS... -L/usr/local/lib -lffi checking for rustc... /usr/local/bin/rustc checking for cargo... /usr/local/bin/cargo checking rustc version... DEBUG: Executing: `/usr/local/bin/rustc --version --verbose` DEBUG: The command returned non-zero exit status -12. DEBUG: Its output was: DEBUG: | rustc 1.26.0 DEBUG: | binary: rustc DEBUG: | commit-hash: unknown DEBUG: | commit-date: unknown DEBUG: | host: x86_64-unknown-freebsd DEBUG: | release: 1.26.0 ERROR: Command `/usr/local/bin/rustc --version --verbose` failed with exit status -12. Attempts to rebuild rust (and cargo) from the bootstrap files fail in similar fashion. On a machine running a SVN r334538 kernel but more recent user-land, it builds successfully. With (the only difference being) a kernel at SVN r334748, it does not. Any hints/thoughts? imb From owner-freebsd-current@freebsd.org Thu Jun 7 17:11:08 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 03095FE4D87 for ; Thu, 7 Jun 2018 17:11:08 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lf0-x241.google.com (mail-lf0-x241.google.com [IPv6:2a00:1450:4010:c07::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6101074CCC for ; Thu, 7 Jun 2018 17:11:07 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lf0-x241.google.com with SMTP id q11-v6so15830396lfc.7 for ; Thu, 07 Jun 2018 10:11:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=2tVCVIeXBMKrEmFthPBvy1YPE5U1e5wGXSOZ3i/fvYY=; b=gh6BYeUc6Hf/SGaUNTszaGAMYKsfgFFkCuYacacptC9efUQGyzxpx4nnpbEofKnqD4 G9UbLFfBxpegevj6CcEmCX8z7+yRlnt8UksrnGGwseQngGafW+dA7pHyHGuJUmXGEBDD YcxldeHUJ+hpLIBWMX59ZWGAOoS1hWbKx70O6MiQ6tL6rgP0kc80ds2tOiVEJ14mp++a Mff5JPnX4xyPYjBmnUKBBkcHJzEsHCmlPUzdH0wHoQs+pCC+zjVivs6V5x3XePthQ05X Krahl68NwTQKxo41N2uG6iCyYT9x0BSS7fmwJ1u4ZJnrS5aOWeUWmH6ppOtGNUaatxFz q0ww== 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=2tVCVIeXBMKrEmFthPBvy1YPE5U1e5wGXSOZ3i/fvYY=; b=cRRvM5zFwiu1+OYdkS8b8uc2a6rrQd6ubQAK51ZeuFU53uLIjF98Oc1bNB8zcN6QsE o/1g/jugLgYpaGXABDYi7CDXsiXnMm76UEXnkDrryhPcMiD89YMci9gv4jBd9YflVbIM kNZPHcuByJgq92pPTcsR+IuyqTlhfhgK0VdvDsvjPgIv59gWXWAbBvrP3cUP/81XUjwd THx+ZnZmKBOb0rnSgx85V4roDJe2Hz5ONFPXEqg/w0QnkrFWMGOJcoET4pkz0WkcjBqQ VvYpvcx7UKPBO8fUt+baha6/BGjwyx3sJZf+Gn+a+Wz+ifcji+lrKZHhfT08To2PnjZ3 Z76Q== X-Gm-Message-State: APt69E20Nn+Arr9qTCvpsFjyoOP6Gm7OIMb9fKQkBln8t29mUHtdyGOR 2hT06CL4mCyM/NQKjOXS/563HT5REkmxuvkY6wI= X-Google-Smtp-Source: ADUXVKKMtOef7/gZi5xJwUlqD6XL4pkwlvx6WOwx5L1HB02ZeOLrHRN3PMSY8uhzUacD7nTOLpb8RLA8GDIRJ+id8hM= X-Received: by 2002:a2e:5111:: with SMTP id f17-v6mr2103408ljb.16.1528391465932; Thu, 07 Jun 2018 10:11:05 -0700 (PDT) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 2002:ab3:7206:0:0:0:0:0 with HTTP; Thu, 7 Jun 2018 10:11:05 -0700 (PDT) In-Reply-To: References: From: Alan Somers Date: Thu, 7 Jun 2018 11:11:05 -0600 X-Google-Sender-Auth: 45n5I8KQ6RatcgIVRG6HOxK3sxo Message-ID: Subject: Re: rust broken? To: Michael Butler Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jun 2018 17:11:08 -0000 Can you reproduce the problem using rust installed from rustup instead of from Ports? If so, you should file a bug report with the Rust developers. Hint: when using Rustup, you'll have to use vresion 1.26.1 instead of 1.26.0. -Alan On Thu, Jun 7, 2018 at 9:44 AM, Michael Butler wrote: > In response to a Firefox update, I tried to build the new version. > However, rust now fails with a core-dump in the build process. > > checking for libffi > 3.0.9... yes > checking MOZ_FFI_CFLAGS... -I/usr/local/lib/libffi-3.2.1/include > checking MOZ_FFI_LIBS... -L/usr/local/lib -lffi > checking for rustc... /usr/local/bin/rustc > checking for cargo... /usr/local/bin/cargo > checking rustc version... > DEBUG: Executing: `/usr/local/bin/rustc --version --verbose` > DEBUG: The command returned non-zero exit status -12. > DEBUG: Its output was: > DEBUG: | rustc 1.26.0 > DEBUG: | binary: rustc > DEBUG: | commit-hash: unknown > DEBUG: | commit-date: unknown > DEBUG: | host: x86_64-unknown-freebsd > DEBUG: | release: 1.26.0 > ERROR: Command `/usr/local/bin/rustc --version --verbose` failed with > exit status -12. > > Attempts to rebuild rust (and cargo) from the bootstrap files fail in > similar fashion. > > On a machine running a SVN r334538 kernel but more recent user-land, it > builds successfully. With (the only difference being) a kernel at SVN > r334748, it does not. > > Any hints/thoughts? > > imb > _______________________________________________ > 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 Jun 7 17:14:21 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E4B00FE4ED6 for ; Thu, 7 Jun 2018 17:14:20 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f50.google.com (mail-lf0-f50.google.com [209.85.215.50]) (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 515F575094; Thu, 7 Jun 2018 17:14:20 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f50.google.com with SMTP id g21-v6so13874571lfb.4; Thu, 07 Jun 2018 10:14:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:from:to:cc:references:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=fT6d7hXyqv1CjB3bwHa0p/ESFHlxkfQjXGnVdfdgZuQ=; b=TMK+sT+jaykwEezzzxRwSUZ5sKeH6dGghbUZ0isSKtX/6Wwar2NtGo1L5CsA3McpA0 NJ2dwbUUvuQI8fHWnu9y1wQBqvAq7+WJVL4HWBdTlLB7pvNnyXxxJF38wDSBGSFCbscb V7wsZBL/gelRQXW8MWQNO26s8rXT5imbi7OfMeWL4ZdCbaODD0QzO8JfaA3BpWk3qMBW Sm6dqG+D0uFsYSaApat2EgBaryLxvqmes8L61pp/7HdV4JfxI6YAYtRrT9lITKZTmCWa 7tLisYxw4ZLKR5n45YCml2SbKBaqAtO5i+Bmj5OKHj3316q44eXsskVEMCbPeJAjWezt PeZg== X-Gm-Message-State: APt69E0y7SN5r5lWpChGwya/k9DgoRGcm1fT2IJJslh7tLQAtGZWih4x gIWse166y/pF0n4+tqgX6WqUcHeL X-Google-Smtp-Source: ADUXVKI45JeeSYNcrqkmn1tTRtK9YFP5LFGl9XFJRHvl5oZXndqIrrkHRhuRglKGpMFrj+nw/PdffA== X-Received: by 2002:a19:f24e:: with SMTP id d14-v6mr1463980lfk.18.1528391652714; Thu, 07 Jun 2018 10:14:12 -0700 (PDT) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id p16-v6sm6903921lji.20.2018.06.07.10.14.11 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Jun 2018 10:14:11 -0700 (PDT) Subject: Re: Is kern.sched.preempt_thresh=0 a sensible default? From: Andriy Gapon To: FreeBSD Current Cc: Stefan Esser , "M. Warner Losh" References: <1d188cb0-ebc8-075f-ed51-57641ede1fd6@freebsd.org> <49fa8de4-e164-0642-4e01-a6188992c32e@freebsd.org> <32d6305b-3d57-4d37-ba1b-51631e994520@FreeBSD.org> <93efc3e1-7ac3-fedc-a71e-66c99f8e8c1e@freebsd.org> <9aaec961-e604-303a-52f3-ee24e3a435d0@FreeBSD.org> Openpgp: preference=signencrypt Autocrypt: addr=avg@FreeBSD.org; prefer-encrypt=mutual; keydata= xsFNBFm4LIgBEADNB/3lT7f15UKeQ52xCFQx/GqHkSxEdVyLFZTmY3KyNPQGBtyvVyBfprJ7 mAeXZWfhat6cKNRAGZcL5EmewdQuUfQfBdYmKjbw3a9GFDsDNuhDA2QwFt8BmkiVMRYyvI7l N0eVzszWCUgdc3qqM6qqcgBaqsVmJluwpvwp4ZBXmch5BgDDDb1MPO8AZ2QZfIQmplkj8Y6Z AiNMknkmgaekIINSJX8IzRzKD5WwMsin70psE8dpL/iBsA2cpJGzWMObVTtCxeDKlBCNqM1i gTXta1ukdUT7JgLEFZk9ceYQQMJJtUwzWu1UHfZn0Fs29HTqawfWPSZVbulbrnu5q55R4PlQ /xURkWQUTyDpqUvb4JK371zhepXiXDwrrpnyyZABm3SFLkk2bHlheeKU6Yql4pcmSVym1AS4 dV8y0oHAfdlSCF6tpOPf2+K9nW1CFA8b/tw4oJBTtfZ1kxXOMdyZU5fiG7xb1qDgpQKgHUX8 7Rd2T1UVLVeuhYlXNw2F+a2ucY+cMoqz3LtpksUiBppJhw099gEXehcN2JbUZ2TueJdt1FdS ztnZmsHUXLxrRBtGwqnFL7GSd6snpGIKuuL305iaOGODbb9c7ne1JqBbkw1wh8ci6vvwGlzx rexzimRaBzJxlkjNfMx8WpCvYebGMydNoeEtkWldtjTNVsUAtQARAQABzR5BbmRyaXkgR2Fw b24gPGF2Z0BGcmVlQlNELm9yZz7CwZQEEwEIAD4WIQS+LEO7ngQnXA4Bjr538m7TUc1yjwUC WbgsiAIbIwUJBaOagAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRB38m7TUc1yj+JAEACV l9AK/nOWAt/9cufV2fRj0hdOqB1aCshtSrwHk/exXsDa4/FkmegxXQGY+3GWX3deIyesbVRL rYdtdK0dqJyT1SBqXK1h3/at9rxr9GQA6KWOxTjUFURsU7ok/6SIlm8uLRPNKO+yq0GDjgaO LzN+xykuBA0FlhQAXJnpZLcVfPJdWv7sSHGedL5ln8P8rxR+XnmsA5TUaaPcbhTB+mG+iKFj GghASDSfGqLWFPBlX/fpXikBDZ1gvOr8nyMY9nXhgfXpq3B6QCRYKPy58ChrZ5weeJZ29b7/ QdEO8NFNWHjSD9meiLdWQaqo9Y7uUxN3wySc/YUZxtS0bhAd8zJdNPsJYG8sXgKjeBQMVGuT eCAJFEYJqbwWvIXMfVWop4+O4xB+z2YE3jAbG/9tB/GSnQdVSj3G8MS80iLS58frnt+RSEw/ psahrfh0dh6SFHttE049xYiC+cM8J27Aaf0i9RflyITq57NuJm+AHJoU9SQUkIF0nc6lfA+o JRiyRlHZHKoRQkIg4aiKaZSWjQYRl5Txl0IZUP1dSWMX4s3XTMurC/pnja45dge/4ESOtJ9R 8XuIWg45Oq6MeIWdjKddGhRj3OohsltKgkEU3eLKYtB6qRTQypHHUawCXz88uYt5e3w4V16H lCpSTZV/EVHnNe45FVBlvK7k7HFfDDkryM7BTQRZuCyIARAAlq0slcsVboY/+IUJdcbEiJRW be9HKVz4SUchq0z9MZPX/0dcnvz/gkyYA+OuM78dNS7Mbby5dTvOqfpLJfCuhaNYOhlE0wY+ 1T6Tf1f4c/uA3U/YiadukQ3+6TJuYGAdRZD5EqYFIkreARTVWg87N9g0fT9BEqLw9lJtEGDY EWUE7L++B8o4uu3LQFEYxcrb4K/WKmgtmFcm77s0IKDrfcX4doV92QTIpLiRxcOmCC/OCYuO jB1oaaqXQzZrCutXRK0L5XN1Y1PYjIrEzHMIXmCDlLYnpFkK+itlXwlE2ZQxkfMruCWdQXye syl2fynAe8hvp7Mms9qU2r2K9EcJiR5N1t1C2/kTKNUhcRv7Yd/vwusK7BqJbhlng5ZgRx0m WxdntU/JLEntz3QBsBsWM9Y9wf2V4tLv6/DuDBta781RsCB/UrU2zNuOEkSixlUiHxw1dccI 6CVlaWkkJBxmHX22GdDFrcjvwMNIbbyfQLuBq6IOh8nvu9vuItup7qemDG3Ms6TVwA7BD3j+ 3fGprtyW8Fd/RR2bW2+LWkMrqHffAr6Y6V3h5kd2G9Q8ZWpEJk+LG6Mk3fhZhmCnHhDu6CwN MeUvxXDVO+fqc3JjFm5OxhmfVeJKrbCEUJyM8ESWLoNHLqjywdZga4Q7P12g8DUQ1mRxYg/L HgZY3zfKOqcAEQEAAcLBfAQYAQgAJhYhBL4sQ7ueBCdcDgGOvnfybtNRzXKPBQJZuCyIAhsM BQkFo5qAAAoJEHfybtNRzXKPBVwQAKfFy9P7N3OsLDMB56A4Kf+ZT+d5cIx0Yiaf4n6w7m3i ImHHHk9FIetI4Xe54a2IXh4Bq5UkAGY0667eIs+Z1Ea6I2i27Sdo7DxGwq09Qnm/Y65ADvXs 3aBvokCcm7FsM1wky395m8xUos1681oV5oxgqeRI8/76qy0hD9WR65UW+HQgZRIcIjSel9vR XDaD2HLGPTTGr7u4v00UeTMs6qvPsa2PJagogrKY8RXdFtXvweQFz78NbXhluwix2Tb9ETPk LIpDrtzV73CaE2aqBG/KrboXT2C67BgFtnk7T7Y7iKq4/XvEdDWscz2wws91BOXuMMd4c/c4 OmGW9m3RBLufFrOag1q5yUS9QbFfyqL6dftJP3Zq/xe+mr7sbWbhPVCQFrH3r26mpmy841ym dwQnNcsbIGiBASBSKksOvIDYKa2Wy8htPmWFTEOPRpFXdGQ27awcjjnB42nngyCK5ukZDHi6 w0qK5DNQQCkiweevCIC6wc3p67jl1EMFY5+z+zdTPb3h7LeVnGqW0qBQl99vVFgzLxchKcl0 R/paSFgwqXCZhAKMuUHncJuynDOP7z5LirUeFI8qsBAJi1rXpQoLJTVcW72swZ42IdPiboqx NbTMiNOiE36GqMcTPfKylCbF45JNX4nF9ElM0E+Y8gi4cizJYBRr2FBJgay0b9Cp Message-ID: Date: Thu, 7 Jun 2018 20:14:10 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <9aaec961-e604-303a-52f3-ee24e3a435d0@FreeBSD.org> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jun 2018 17:14:21 -0000 On 03/05/2018 12:41, Andriy Gapon wrote: > I think that we need preemption policies that might not be expressible as one or > two numbers. A policy could be something like this: > - interrupt threads can preempt only threads from "lower" classes: real-time, > kernel, timeshare, idle; > - interrupt threads cannot preempt other interrupt threads > - real-time threads can preempt other real-time threads and threads from "lower" > classes: kernel, timeshare, idle > - kernel threads can preempt only threads from lower classes: timeshare, idle > - interactive timeshare threads can only preempt batch and idle threads > - batch threads can only preempt idle threads Here is a sketch of the idea: https://reviews.freebsd.org/D15693 -- Andriy Gapon From owner-freebsd-current@freebsd.org Thu Jun 7 17:33:32 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1290FFE57DC for ; Thu, 7 Jun 2018 17:33:32 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [202.12.127.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.protected-networks.net", Issuer "Protected Networks CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id AA56775BF5; Thu, 7 Jun 2018 17:33:31 +0000 (UTC) (envelope-from imb@protected-networks.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= protected-networks.net; h=content-transfer-encoding :content-language:content-type:content-type:in-reply-to :mime-version:user-agent:date:date:message-id:from:from :references:subject:subject; s=201508; t=1528392803; bh=bPpw+/zK rUUwuT4g71MC4GEZaDWBmBLW4r62u6oqw4Q=; b=Uym0fdO/7tVKLykMYh63+daJ RmITEHmjVHTL/dsE1GiKeBBBAey75tmvAx8qArCQ9m0/VxgaLoe+eNBIQnykjm2S lf2VfQakgtMdLqrLL4vVH6JCYF7UhPE1vbfNbmO5wWLVoRLh53stzAaet0h6tl7E sQHMcq3frXrPTWgRpeA= Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [192.168.1.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: imb@mail.protected-networks.net) by mail.protected-networks.net (Postfix) with ESMTPSA id AC1F03B427; Thu, 7 Jun 2018 13:33:23 -0400 (EDT) Subject: Re: rust broken? To: Matthew Macy , Alan Somers Cc: freebsd-current References: From: Michael Butler Openpgp: preference=signencrypt Message-ID: <1e32764d-c202-6ad0-4c1b-0b0951cd6602@protected-networks.net> Date: Thu, 7 Jun 2018 13:33:22 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jun 2018 17:33:32 -0000 Ah - I'll re-enable that to see if it makes a difference .. I missed that in the comparison between my two build environments :-( Michael On 06/07/18 13:21, Matthew Macy wrote: > > Rustup uses the 11 ABI. > > On Thu, Jun 7, 2018 at 10:11 Alan Somers > wrote: > > Can you reproduce the problem using rust installed from rustup > instead of > from Ports?  If so, you should file a bug report with the Rust > developers. > Hint: when using Rustup, you'll have to use vresion 1.26.1 instead of > 1.26.0. > -Alan > > On Thu, Jun 7, 2018 at 9:44 AM, Michael Butler > > > wrote: > > > In response to a Firefox update, I tried to build the new version. > > However, rust now fails with a core-dump in the build process. > > > > checking for libffi > 3.0.9... yes > > checking MOZ_FFI_CFLAGS... -I/usr/local/lib/libffi-3.2.1/include > > checking MOZ_FFI_LIBS... -L/usr/local/lib -lffi > > checking for rustc... /usr/local/bin/rustc > > checking for cargo... /usr/local/bin/cargo > > checking rustc version... > > DEBUG: Executing: `/usr/local/bin/rustc --version --verbose` > > DEBUG: The command returned non-zero exit status -12. > > DEBUG: Its output was: > > DEBUG: | rustc 1.26.0 > > DEBUG: | binary: rustc > > DEBUG: | commit-hash: unknown > > DEBUG: | commit-date: unknown > > DEBUG: | host: x86_64-unknown-freebsd > > DEBUG: | release: 1.26.0 > > ERROR: Command `/usr/local/bin/rustc --version --verbose` failed with > > exit status -12. > > > > Attempts to rebuild rust (and cargo) from the bootstrap files fail in > > similar fashion. > > > > On a machine running a SVN r334538 kernel but more recent > user-land, it > > builds successfully. With (the only difference being) a kernel at SVN > > r334748, it does not. > > > > Any hints/thoughts? > > > >         imb > > _______________________________________________ > > freebsd-current@freebsd.org > mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org > " > > > _______________________________________________ > freebsd-current@freebsd.org > mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org > " > From owner-freebsd-current@freebsd.org Thu Jun 7 17:50:28 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7266BFE6203 for ; Thu, 7 Jun 2018 17:50:28 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [IPv6:2001:470:8d59:1::8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.protected-networks.net", Issuer "Protected Networks CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 10DC376587; Thu, 7 Jun 2018 17:50:28 +0000 (UTC) (envelope-from imb@protected-networks.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= protected-networks.net; h=content-transfer-encoding :content-language:content-type:content-type:in-reply-to :mime-version:user-agent:date:date:message-id:from:from :references:subject:subject; s=201508; t=1528393826; bh=XA2RcNbo nu7yQC8pxV1Zfpbx5DMyqg5PuKjp26jXjgw=; b=RqIKDP14bt+WgDp5GUdrGWec 24RjzRle7dwDCqZ6KUZ19YWUSPmADDqtOXGH5k15Fav6GKmHlA0LTYvh0NM1XwAo mbBn6pwwpbdMAc3kgfJ1IyHKLDPvByhR1nZuZETpsiqVVJzha3rEvCkIIwZjTeDF 6J7Zy1Fhs3vYsKc+7vw= Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [192.168.1.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: imb@mail.protected-networks.net) by mail.protected-networks.net (Postfix) with ESMTPSA id B68363B566; Thu, 7 Jun 2018 13:50:26 -0400 (EDT) Subject: Re: rust broken? To: Matthew Macy Cc: Alan Somers , freebsd-current References: <1e32764d-c202-6ad0-4c1b-0b0951cd6602@protected-networks.net> From: Michael Butler Openpgp: preference=signencrypt Message-ID: Date: Thu, 7 Jun 2018 13:50:25 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jun 2018 17:50:28 -0000 On 06/07/18 13:36, Matthew Macy wrote: > On Thu, Jun 7, 2018 at 10:33 Michael Butler > wrote: > > Ah - I'll re-enable that to see if it makes a difference .. > > > > It's not a question of enabling. It doesn't explicitly use the 11 > symbols. Rust developers assume that every OS has a frozen ABI like > Linux. The rust from rustup will only work on 11. This is why you need > to use the port / pkg. I commented out this line in my kernel config .. nooption COMPAT_FREEBSD11 .. and the port's bootstrap files now run as they should :-) Sorry for the noise - self-inflicted wound :-( imb From owner-freebsd-current@freebsd.org Thu Jun 7 17:52:32 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4AD6BFE63CE for ; Thu, 7 Jun 2018 17:52:32 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: from smtp.freebsd.org (unknown [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E8A6D768EC; Thu, 7 Jun 2018 17:52:31 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: from mail-io0-f173.google.com (mail-io0-f173.google.com [209.85.223.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) (Authenticated sender: mmacy) by smtp.freebsd.org (Postfix) with ESMTPSA id B431010D7D; Thu, 7 Jun 2018 17:52:31 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: by mail-io0-f173.google.com with SMTP id s26-v6so12828677ioj.4; Thu, 07 Jun 2018 10:52:31 -0700 (PDT) X-Gm-Message-State: APt69E18mAc6NjEHdrg2P4rm2qNgStdR9BvpLI7Ell8/dXKy5LN/WCuB //uhF+k+P2ynQIZVsYt31OvxjP7KVDCEzvPzJwk= X-Google-Smtp-Source: ADUXVKJWRluirB2l3G3g2gY8aq3HdLLqNZ98keDpsw8JIN/cagr4NvWCiFDTfg8wyDbTMWKhZynXYUhYhkLj0LRdsqI= X-Received: by 2002:a6b:d00c:: with SMTP id x12-v6mr2495322ioa.5.1528393951307; Thu, 07 Jun 2018 10:52:31 -0700 (PDT) MIME-Version: 1.0 References: <1e32764d-c202-6ad0-4c1b-0b0951cd6602@protected-networks.net> In-Reply-To: From: Matthew Macy Date: Thu, 7 Jun 2018 10:52:20 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: rust broken? To: Michael Butler Cc: Alan Somers , freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jun 2018 17:52:32 -0000 On Thu, Jun 7, 2018 at 10:50 Michael Butler wrote: > On 06/07/18 13:36, Matthew Macy wrote: > > On Thu, Jun 7, 2018 at 10:33 Michael Butler > > wrote: > > > > Ah - I'll re-enable that to see if it makes a difference .. > > > > > > > > It's not a question of enabling. It doesn't explicitly use the 11 > > symbols. Rust developers assume that every OS has a frozen ABI like > > Linux. The rust from rustup will only work on 11. This is why you need > > to use the port / pkg. > > I commented out this line in my kernel config .. > > nooption COMPAT_FREEBSD11 Ah. Yes. The port uses the 11 ABI symbols explicitly. > > > .. and the port's bootstrap files now run as they should :-) > > Sorry for the noise - self-inflicted wound :-( > > imb > From owner-freebsd-current@freebsd.org Thu Jun 7 20:21:17 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4CC9EFEA79E for ; Thu, 7 Jun 2018 20:21:17 +0000 (UTC) (envelope-from as@cmplx.uk) Received: from jail0199.vps.exonetric.net (jail0199.vps.exonetric.net [IPv6:2a02:1658:1::199:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "jail0199.vps.exonetric.net", Issuer "jail0199.vps.exonetric.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E200C7D3DB for ; Thu, 7 Jun 2018 20:21:16 +0000 (UTC) (envelope-from as@cmplx.uk) Received: from jail0199.vps.exonetric.net (jail0199.vps.exonetric.net [178.250.76.108]) by jail0199.vps.exonetric.net (8.15.2/8.15.2) with ESMTPS id w57KLFeH090700 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Thu, 7 Jun 2018 20:21:15 GMT (envelope-from as@jail0199.vps.exonetric.net) Received: (from as@localhost) by jail0199.vps.exonetric.net (8.15.2/8.15.2/Submit) id w57KLFle090699 for freebsd-current@freebsd.org; Thu, 7 Jun 2018 20:21:15 GMT (envelope-from as) Date: Thu, 7 Jun 2018 20:21:15 GMT From: Anton Shterenlikht Message-Id: <201806072021.w57KLFle090699@jail0199.vps.exonetric.net> To: freebsd-current@freebsd.org Subject: cannot get touchpad mouse, no psm device, on Dell Precision 3520 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jun 2018 20:21:17 -0000 Please help get touchpad mouse on Dell Precision 3520. The usb mouse works fine. z> pciconf -lv hostb0@pci0:0:0:0: class=0x060000 card=0x07a91028 chip=0x19108086 rev=0x07 hdr=0x00 vendor = 'Intel Corporation' device = 'Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers' class = bridge subclass = HOST-PCI pcib1@pci0:0:1:0: class=0x060400 card=0x07a91028 chip=0x19018086 rev=0x07 hdr=0x01 vendor = 'Intel Corporation' device = 'Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16)' class = bridge subclass = PCI-PCI vgapci1@pci0:0:2:0: class=0x030000 card=0x07a91028 chip=0x191b8086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' device = 'HD Graphics 530' class = display subclass = VGA none0@pci0:0:4:0: class=0x118000 card=0x07a91028 chip=0x19038086 rev=0x07 hdr=0x00 vendor = 'Intel Corporation' device = 'Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem' class = dasp xhci0@pci0:0:20:0: class=0x0c0330 card=0x07a91028 chip=0xa12f8086 rev=0x31 hdr=0x00 vendor = 'Intel Corporation' device = 'Sunrise Point-H USB 3.0 xHCI Controller' class = serial bus subclass = USB none1@pci0:0:20:2: class=0x118000 card=0x07a91028 chip=0xa1318086 rev=0x31 hdr=0x00 vendor = 'Intel Corporation' device = 'Sunrise Point-H Thermal subsystem' class = dasp none2@pci0:0:21:0: class=0x118000 card=0x07a91028 chip=0xa1608086 rev=0x31 hdr=0x00 vendor = 'Intel Corporation' device = 'Sunrise Point-H Serial IO I2C Controller' class = dasp none3@pci0:0:21:1: class=0x118000 card=0x07a91028 chip=0xa1618086 rev=0x31 hdr=0x00 vendor = 'Intel Corporation' device = 'Sunrise Point-H Serial IO I2C Controller' class = dasp none4@pci0:0:22:0: class=0x078000 card=0x07a91028 chip=0xa13a8086 rev=0x31 hdr=0x00 vendor = 'Intel Corporation' device = 'Sunrise Point-H CSME HECI' class = simple comms ahci0@pci0:0:23:0: class=0x010601 card=0x07a91028 chip=0xa1028086 rev=0x31 hdr=0x00 vendor = 'Intel Corporation' device = 'Sunrise Point-H SATA controller [AHCI mode]' class = mass storage subclass = SATA pcib2@pci0:0:28:0: class=0x060400 card=0x07a91028 chip=0xa1118086 rev=0xf1 hdr=0x01 vendor = 'Intel Corporation' device = 'Sunrise Point-H PCI Express Root Port' class = bridge subclass = PCI-PCI pcib3@pci0:0:28:2: class=0x060400 card=0x07a91028 chip=0xa1128086 rev=0xf1 hdr=0x01 vendor = 'Intel Corporation' device = 'Sunrise Point-H PCI Express Root Port' class = bridge subclass = PCI-PCI pcib4@pci0:0:28:4: class=0x060400 card=0x07a91028 chip=0xa1148086 rev=0xf1 hdr=0x01 vendor = 'Intel Corporation' device = 'Sunrise Point-H PCI Express Root Port' class = bridge subclass = PCI-PCI pcib5@pci0:0:29:0: class=0x060400 card=0x07a91028 chip=0xa1188086 rev=0xf1 hdr=0x01 vendor = 'Intel Corporation' device = 'Sunrise Point-H PCI Express Root Port' class = bridge subclass = PCI-PCI isab0@pci0:0:31:0: class=0x060100 card=0x07a91028 chip=0xa1548086 rev=0x31 hdr=0x00 vendor = 'Intel Corporation' device = 'Sunrise Point-H LPC Controller' class = bridge subclass = PCI-ISA none5@pci0:0:31:2: class=0x058000 card=0x07a91028 chip=0xa1218086 rev=0x31 hdr=0x00 vendor = 'Intel Corporation' device = 'Sunrise Point-H PMC' class = memory hdac0@pci0:0:31:3: class=0x040300 card=0x07a91028 chip=0xa1718086 rev=0x31 hdr=0x00 vendor = 'Intel Corporation' device = 'CM238 HD Audio Controller' class = multimedia subclass = HDA none6@pci0:0:31:4: class=0x0c0500 card=0x07a91028 chip=0xa1238086 rev=0x31 hdr=0x00 vendor = 'Intel Corporation' device = 'Sunrise Point-H SMBus' class = serial bus subclass = SMBus em0@pci0:0:31:6: class=0x020000 card=0x07a91028 chip=0x15e38086 rev=0x31 hdr=0x00 vendor = 'Intel Corporation' device = 'Ethernet Connection (5) I219-LM' class = network subclass = ethernet vgapci0@pci0:1:0:0: class=0x030200 card=0x07a91028 chip=0x13b410de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'GM107GLM [Quadro M620 Mobile]' class = display subclass = 3D iwm0@pci0:2:0:0: class=0x028000 card=0x00508086 chip=0x24fd8086 rev=0x78 hdr=0x00 vendor = 'Intel Corporation' device = 'Wireless 8265 / 8275' class = network none7@pci0:3:0:0: class=0xff0000 card=0x07a91028 chip=0x525a10ec rev=0x01 hdr=0x00 vendor = 'Realtek Semiconductor Co., Ltd.' device = 'RTS525A PCI Express Card Reader' nvme0@pci0:61:0:0: class=0x010802 card=0x00001c5c chip=0x12841c5c rev=0x00 hdr=0x00 vendor = 'SK hynix' class = mass storage subclass = NVM z> Thanks Anton From owner-freebsd-current@freebsd.org Thu Jun 7 20:34:35 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7586FFEB021 for ; Thu, 7 Jun 2018 20:34:35 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EE9677DE89 for ; Thu, 7 Jun 2018 20:34:34 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.106] (cpe-75-82-194-8.socal.res.rr.com [75.82.194.8]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 37067f3c TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Thu, 7 Jun 2018 13:34:31 -0700 (PDT) Subject: Re: cannot get touchpad mouse, no psm device, on Dell Precision 3520 To: Anton Shterenlikht , freebsd-current@freebsd.org References: <201806072021.w57KLFle090699@jail0199.vps.exonetric.net> From: Pete Wright Message-ID: Date: Thu, 7 Jun 2018 13:34:31 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <201806072021.w57KLFle090699@jail0199.vps.exonetric.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jun 2018 20:34:35 -0000 On 06/07/2018 13:21, Anton Shterenlikht wrote: > Please help get touchpad mouse on > Dell Precision 3520. > The usb mouse works fine. pciconf isn't really applicable here i think.  does your dmesg buffer reference any PS/2 devices being detected?  here is CURRENT detecting my synaptics touchpad: $ dmesg|grep psm psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Synaptics Touchpad, device ID 0 assuming it is being detected, have you set: moused_enable="YES" in /etc/rc.conf? If you have set that but do not see your touchpad being detected, and assuming it's a synaptics device, have you set the following in /boot/loader.conf? hw.psm.synaptics_support="1" Cheers, -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Thu Jun 7 21:01:20 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2C0DAFEBAA3 for ; Thu, 7 Jun 2018 21:01:20 +0000 (UTC) (envelope-from as@cmplx.uk) Received: from jail0199.vps.exonetric.net (jail0199.vps.exonetric.net [IPv6:2a02:1658:1::199:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "jail0199.vps.exonetric.net", Issuer "jail0199.vps.exonetric.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B5BA27ECD5 for ; Thu, 7 Jun 2018 21:01:19 +0000 (UTC) (envelope-from as@cmplx.uk) Received: from jail0199.vps.exonetric.net (jail0199.vps.exonetric.net [178.250.76.108]) by jail0199.vps.exonetric.net (8.15.2/8.15.2) with ESMTPS id w57L1IDa094541 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 7 Jun 2018 21:01:18 GMT (envelope-from as@jail0199.vps.exonetric.net) Received: (from as@localhost) by jail0199.vps.exonetric.net (8.15.2/8.15.2/Submit) id w57L1IKU094540; Thu, 7 Jun 2018 21:01:18 GMT (envelope-from as) Date: Thu, 7 Jun 2018 21:01:18 +0000 From: Anton Shterenlikht To: Pete Wright Cc: Anton Shterenlikht , freebsd-current@freebsd.org Subject: Re: cannot get touchpad mouse, no psm device, on Dell Precision 3520 Message-ID: <20180607210118.GA94139@jail0199.vps.exonetric.net> Mail-Followup-To: Pete Wright , Anton Shterenlikht , freebsd-current@freebsd.org References: <201806072021.w57KLFle090699@jail0199.vps.exonetric.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jun 2018 21:01:20 -0000 On Thu, Jun 07, 2018 at 01:34:31PM -0700, Pete Wright wrote: > > > On 06/07/2018 13:21, Anton Shterenlikht wrote: > > Please help get touchpad mouse on > > Dell Precision 3520. > > The usb mouse works fine. > > > pciconf isn't really applicable here i think.  does your dmesg buffer > reference any PS/2 devices being detected?  here is CURRENT detecting my > synaptics touchpad: > > $ dmesg|grep psm > psm0: irq 12 on atkbdc0 > psm0: [GIANT-LOCKED] > psm0: model Synaptics Touchpad, device ID 0 z> dmesg|grep psm z> Perhaps this relatively modern laptop uses a different device for its touchpad? Thanks Anton From owner-freebsd-current@freebsd.org Fri Jun 8 00:13:39 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A04871009260; Fri, 8 Jun 2018 00:13:39 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 008BB87CED; Fri, 8 Jun 2018 00:13:38 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w580DklN096285 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 7 Jun 2018 17:13:47 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w580DjXR096284; Thu, 7 Jun 2018 17:13:45 -0700 (PDT) (envelope-from fbsd) Date: Thu, 7 Jun 2018 17:13:45 -0700 From: bob prohaska To: Mark Millard Cc: FreeBSD Current , freebsd-arm@freebsd.org Subject: Re: panic: Assertion td->td_lock == TDQ_LOCKPTR(tdq) failed at /usr/src/sys/kern/sched_ule.c:2137 Message-ID: <20180608001345.GA96201@www.zefox.net> References: <6CEF9465-3908-4D5E-BC9E-967B9D1DD6AA@yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6CEF9465-3908-4D5E-BC9E-967B9D1DD6AA@yahoo.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jun 2018 00:13:39 -0000 On Wed, Jun 06, 2018 at 10:28:58PM -0700, Mark Millard wrote: > > Looks like there has been another stab at avoiding some > unnecessary Out Of Memory killing of processes: > > Author: alc > Date: Thu Jun 7 02:54:11 2018 > New Revision: 334752 > URL: https://svnweb.freebsd.org/changeset/base/334752 > > > Log: > . . . One visible > effect of this error was that processes were being killed by the > virtual memory system's OOM killer when in fact there was plentiful > free memory. > An RPI3 kernel at 334800 still reported Jun 7 16:28:21 www kernel: pid 71329 (c++), uid 0, was killed: out of swap space during a -j4 buildworld. I wasn't watching top at the time, so I don't know how much swap was in use. Total available was 4 GB, which certainly seems like it ought to be enough. The swap was on both microSD and USB flash. I've run make clean in /usr/src/lib/clang/libllvm and restarted a -j4 buildworld with the -DNO_CLEAN option, and also set sysctl vm.pageout_update_period=0 to see what would happen. Within a few minutes buildworld stopped, the tail of the log file contained --- X86GenEVEX2VEXTables.inc --- llvm-tblgen -gen-x86-EVEX2VEX-tables -I /usr/src/contrib/llvm/include -I /usr/src/contrib/llvm/lib/Target/X86 -d X86GenEVEX2VEXTables.inc.d -o X86GenEVEX2VEXTables.inc /usr/src/contrib/llvm/lib/Target/X86/X86.td --- X86GenFastISel.inc --- llvm-tblgen -gen-fast-isel -I /usr/src/contrib/llvm/include -I /usr/src/contrib/llvm/lib/Target/X86 -d X86GenFastISel.inc.d -o X86GenFastISel.inc /usr/src/contrib/llvm/lib/Target/X86/X86.td --- X86GenDAGISel.inc --- Killed *** [X86GenDAGISel.inc] Error code 137 make[6]: stopped in /usr/src/lib/clang/libllvm 1 error make[6]: stopped in /usr/src/lib/clang/libllvm *** [all_subdir_lib/clang/libllvm] Error code 2 make[5]: stopped in /usr/src/lib/clang I'll try again, this time with USB swap turned off. Thanks for reading! bob prohaska From owner-freebsd-current@freebsd.org Fri Jun 8 00:51:08 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8076B100A09B for ; Fri, 8 Jun 2018 00:51:08 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-qt0-x22d.google.com (mail-qt0-x22d.google.com [IPv6:2607:f8b0:400d:c0d::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 1BA5069219 for ; Fri, 8 Jun 2018 00:51:08 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: by mail-qt0-x22d.google.com with SMTP id s9-v6so11891090qtg.2 for ; Thu, 07 Jun 2018 17:51:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=lZAwPuUUGAQFBIs5sXJ7FHC+3MulH20WetQgYi+NaHI=; b=UpV6I3RFCyZbzYZgYL0xWwLPhGKOSR/hZiO8WfATaCNPV7UhNIWHOsP1MLWHr001jw x2dKZPVF/++FehdDT9SxJNqhIOUH7wVEybAPOTrqki3e3TEoGd0QjI1uJ/9/XtyMz2ub tGg7qsg+o9GTWaziEvtdsQ8g1zeyOfYNvdcn9Im3JYvDbcUugF5x8qYVBI23wFe+vd96 lMybQMhyDU6uEpx7pauZEPWCtMWSVQRdy0VxQQdT3PKkGDo6v+YuRqdLeiWi+VI7QQil ATyLkOEf8v4HvREi5r5IvzEGR9opAqzNtgm1aB3qDbOAvmbnwSA+ZR3MxyvC6exqAUuW khtA== 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=lZAwPuUUGAQFBIs5sXJ7FHC+3MulH20WetQgYi+NaHI=; b=SF+JNTnsnbiSvmuBqtqUvd2qiZN3rXMA/Z0nbNKQuvJittHD4dHPtoLW39YgIpl+ms xs8a/NMycSFyNqrAMPGFPiJ4J2/SGQGapXZkJZfgGz0S9DiOvEkDo7Z/H4pmVXmoZGJr X7k/haL51CE4p/Hdq9k8ncPiMxOSIgDzRf2sVg4B7gpet/bu0zyLY04pYnc34513s9J0 /i2N7Z65mftzt6Uqo0ZTRTgMXY/DqnHI5AEs+YTJZMIUxchm/PQ++qkmPDbW0zrTXDr4 JQnxae9L8UOtFczuE0lrl+YeZbeDV5M6KFyU449KLAzqZMZgZhewRTD2pgsRSqSIKlVn SGWQ== X-Gm-Message-State: APt69E3XzGYX3+m6sPRVYVvhZojOHl3x6wSTQfxNrFgLGdfsfoOnfHMx 3wBbKacVHTmeADeeDAPZkQrMYrSOuCqiSmjzKEwHPA== X-Google-Smtp-Source: ADUXVKIGZ2krxC/QF6XmBDBc4+9CcdIwxeTfwCMFi6s0EQnbnu6kGhfBKH3d+VR5MVU0SU2vt8XapYS9TkQYnl+It2U= X-Received: by 2002:ac8:358a:: with SMTP id k10-v6mr3924207qtb.248.1528419067817; Thu, 07 Jun 2018 17:51:07 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ac8:1c4e:0:0:0:0:0 with HTTP; Thu, 7 Jun 2018 17:51:07 -0700 (PDT) In-Reply-To: References: From: Mateusz Guzik Date: Fri, 8 Jun 2018 02:51:07 +0200 Message-ID: Subject: Re: r334533 renders head unbootable on XenServer 7.4 To: =?UTF-8?Q?Trond_Endrest=C3=B8l?= Cc: FreeBSD current Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jun 2018 00:51:08 -0000 On Wed, Jun 6, 2018 at 6:50 PM, Trond Endrest=C3=B8l < Trond.Endrestol@fagskolen.gjovik.no> wrote: > After trial and error, I found r334533 to be responsible for rendering > head unbootable on XenServer 7.4. Neither of the two available > XenServer patches has been applied on the host server. > > Normal and verbose boot messages stops non-deterministically at: > > hpet0: iomem 0xfed00000-0xfed003ff on acpi0 > > Or at: > > granttable0: on xenpv0 > > This is on a non-critical VM, but I think this issue should be > resolved by the time stable/12 becomes available, or if stable/11 > will be impacted by a MFH of r334533 in the near future. > > The host server will be upgraded to XenServer 7.5 by the end of the > week, in case that makes the issue go away. > Thanks for the report. Next time if you identify the culprit please cc: the committer - not everyone watches mailing lists too closely. I set it up on FreeBSD as dom0 and verified the problem exists. I fixed it with the following: https://svnweb.freebsd.org/changeset/base/334820 --=20 Mateusz Guzik From owner-freebsd-current@freebsd.org Thu Jun 7 17:22:11 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C8650FE52C6 for ; Thu, 7 Jun 2018 17:22:11 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: from mail-it0-x243.google.com (mail-it0-x243.google.com [IPv6:2607:f8b0:4001:c0b::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 575637564C; Thu, 7 Jun 2018 17:22:11 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: by mail-it0-x243.google.com with SMTP id j186-v6so13601193ita.5; Thu, 07 Jun 2018 10:22:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=X/VLuHXR849fGmLB2agCCoX1YzbkK1Ix83ql+oPeuKE=; b=IehiABclf0Wntj7ZsiBqluUFFLp27tyZnef9uYaXcwBIcbxOIPQsMuxoH7VAQILJeQ dBSbuWSOQyzTLfcXX1bh8ZIi9jEBRz5H4/EcCW7epRGPupySyhFuVHIiNyIv1bz2LA9Q BAo2luXf+UOj860IxYOiuyA8AqWt1VeU7AiqfjrICgRTpk9eqrZs+RLOmHUeiar5JKdO zfuKibLeDLC7x7X3upG/kFMn6P+D/UkCgl/O6TP1BMdQBQdRIjS8pbxmatnkityfv1Xq p6kod4xMOB4M5Y0CVOX3n+4ieUn+pb+b3E7o1XJSTy+PfPLOROuUKaTNNCgACYjkjPdV aWBA== 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=X/VLuHXR849fGmLB2agCCoX1YzbkK1Ix83ql+oPeuKE=; b=SqVCXplj6bPd+7e0qyOO3xTiBG+WqFhTRGMWX6ko4WhZzSNL6DxtLkkGO4o3EYcp/l WLJFBiQtgjMYMbmr5XW1v2x9EbjS9r9OrjJZ9C8LA+okL/OQxOT4ofk2Ocfs0+izl4l0 kQXsRlKkmMZLWNSuH5Flrx4JsyupTIrZuQbzNwFknRxUFe/+apw8+ievV+NLGNRh6j9s oIzR99PHBaMWoe3QmrtCf1yVkjA2T0T16VSrPEIl6mIpQxFKTM5PG7znigknPsJWvk9I YyTvxv1wK0lu1PifYR4HrBDYHo8pUepYgcBWefFN8dJRUDcCN0XDgWfA522Ue/GAp89c B/SA== X-Gm-Message-State: APt69E2z9M59sivc/fpu8pz4mFmWGBFTsB31Ftntr2JKZ5jsnq1ExOzP NNzWLqDqp/WGVeEFnJskefLuaSdKOVjVFPRA5KE= X-Google-Smtp-Source: ADUXVKJjUoEJ0lhHenHDpNs6QoHTrw3aDnQhgrM8SITH5DyAxPiiljqN91Pby63IW7YttR5j8X3eFItNCa/kAJCjoIc= X-Received: by 2002:a24:2745:: with SMTP id g66-v6mr2735440ita.77.1528392130494; Thu, 07 Jun 2018 10:22:10 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Matthew Macy Date: Thu, 7 Jun 2018 10:21:59 -0700 Message-ID: Subject: Re: rust broken? To: Alan Somers Cc: Michael Butler , freebsd-current X-Mailman-Approved-At: Fri, 08 Jun 2018 01:35:24 +0000 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jun 2018 17:22:12 -0000 Rustup uses the 11 ABI. On Thu, Jun 7, 2018 at 10:11 Alan Somers wrote: > Can you reproduce the problem using rust installed from rustup instead of > from Ports? If so, you should file a bug report with the Rust developers. > Hint: when using Rustup, you'll have to use vresion 1.26.1 instead of > 1.26.0. > -Alan > > On Thu, Jun 7, 2018 at 9:44 AM, Michael Butler > > wrote: > > > In response to a Firefox update, I tried to build the new version. > > However, rust now fails with a core-dump in the build process. > > > > checking for libffi > 3.0.9... yes > > checking MOZ_FFI_CFLAGS... -I/usr/local/lib/libffi-3.2.1/include > > checking MOZ_FFI_LIBS... -L/usr/local/lib -lffi > > checking for rustc... /usr/local/bin/rustc > > checking for cargo... /usr/local/bin/cargo > > checking rustc version... > > DEBUG: Executing: `/usr/local/bin/rustc --version --verbose` > > DEBUG: The command returned non-zero exit status -12. > > DEBUG: Its output was: > > DEBUG: | rustc 1.26.0 > > DEBUG: | binary: rustc > > DEBUG: | commit-hash: unknown > > DEBUG: | commit-date: unknown > > DEBUG: | host: x86_64-unknown-freebsd > > DEBUG: | release: 1.26.0 > > ERROR: Command `/usr/local/bin/rustc --version --verbose` failed with > > exit status -12. > > > > Attempts to rebuild rust (and cargo) from the bootstrap files fail in > > similar fashion. > > > > On a machine running a SVN r334538 kernel but more recent user-land, it > > builds successfully. With (the only difference being) a kernel at SVN > > r334748, it does not. > > > > Any hints/thoughts? > > > > imb > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to " > freebsd-current-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@freebsd.org Fri Jun 8 01:55:34 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 348FD100B855; Fri, 8 Jun 2018 01:55:34 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 83E9B6B63E; Fri, 8 Jun 2018 01:55:33 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w581tkbC096632 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 7 Jun 2018 18:55:47 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w581tkt4096631; Thu, 7 Jun 2018 18:55:46 -0700 (PDT) (envelope-from fbsd) Date: Thu, 7 Jun 2018 18:55:45 -0700 From: bob prohaska To: Mark Millard Cc: FreeBSD Current , freebsd-arm@freebsd.org Subject: Re: panic: Assertion td->td_lock == TDQ_LOCKPTR(tdq) failed at /usr/src/sys/kern/sched_ule.c:2137 Message-ID: <20180608015545.GA96590@www.zefox.net> References: <6CEF9465-3908-4D5E-BC9E-967B9D1DD6AA@yahoo.com> <20180608001345.GA96201@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180608001345.GA96201@www.zefox.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jun 2018 01:55:34 -0000 On Thu, Jun 07, 2018 at 05:13:45PM -0700, bob prohaska wrote: > > I'll try again, this time with USB swap turned off. The circle closed, back to the original panic in the subject line. Console, top and buildworld.log files are at http://www.zefox.net/~fbsd/rpi3/crashes/20180607 Thanks for reading, bob prohaska From owner-freebsd-current@freebsd.org Thu Jun 7 17:36:37 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EE588FE59A7 for ; Thu, 7 Jun 2018 17:36:36 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7FB4175DD0; Thu, 7 Jun 2018 17:36:36 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: by mail-it0-x233.google.com with SMTP id v83-v6so13679203itc.3; Thu, 07 Jun 2018 10:36:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=trvNDXOGHjsSniiU7sAkMzJiOBLkjqtU0m78AyD90A0=; b=dZ/vBGkHCEFYBJosxxe0YMeFUDmwYnMWMLJKSqtOHIgeDfq2Ct8Z6mPNl0JXwID9ja ZpVEAp54JzZwZvSIZnnGjQEe4rvRQJHMfCJ5WPrnQkBG2x4BNrGQoZpvxS+lgzBQywaz MoiDKFA+RbzC6YdqPC7FKBkF0vJBHjM/Mf5ihvLeG5xJcngFEdGv0p+KbJfXaSd8MhKP oJCUBhwcrv3JX5CCvNXHWenNMIhRiRROS9WGgm/yFf1Wwix/irazE7ytZ04AI6Vni1SZ XVqNASUn8PQbT6rS49z4Je+8+M9tRUGgY4XuKljRutt0MDCsKFMZAVt8ZHOai4RWAb/A Tw1w== 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=trvNDXOGHjsSniiU7sAkMzJiOBLkjqtU0m78AyD90A0=; b=SJbrI7LoAaYXVQfUWspwav5TA4BXK3GaSV338WukWUrLth6EEJa32tB9IetBOnhRQB OijfacAZj1jqstAsqDc1Xv1eEUAUcKTbhiJ01XK0y+nO74WPrabeSGgMZBMtCnne+c5/ xsCZbT5oibNp848eZtNhdTJJbd7J1DdbJHEZOwlQAdpyOecON6Pr3xNMIPhN33DZ824L MFUyrsP6RI0EdCb/VIg0k4MBJJGbwoCbRGbHDNKzZnXSBvKRjx3SOHcNn59bl66iYSQB DahG4IwoS36303Vfj8/+7r7eeSjj7x2APCduJgjicH7iYPv2UAjC9yla/qNouNVx0q8I UNrA== X-Gm-Message-State: APt69E2Dhxz5ITRQPPLFJP9tOld8R64lv4xtQgMkbXnLYbq7VXfOrgHh Q/QiolXQfQXbqseeHPj15u3JV1dh8YANrgMZ/iI= X-Google-Smtp-Source: ADUXVKJqBzbbPIH5bFoGHLO7I7335guRvnQrOij82pmJUK/4+pWyWcLx5uHwCVj+b6QU7dDNvdqN49tYpD3G9Fp5Yzc= X-Received: by 2002:a24:6c8a:: with SMTP id w132-v6mr2747312itb.4.1528392995738; Thu, 07 Jun 2018 10:36:35 -0700 (PDT) MIME-Version: 1.0 References: <1e32764d-c202-6ad0-4c1b-0b0951cd6602@protected-networks.net> In-Reply-To: <1e32764d-c202-6ad0-4c1b-0b0951cd6602@protected-networks.net> From: Matthew Macy Date: Thu, 7 Jun 2018 10:36:24 -0700 Message-ID: Subject: Re: rust broken? To: Michael Butler Cc: Alan Somers , freebsd-current X-Mailman-Approved-At: Fri, 08 Jun 2018 01:58:36 +0000 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jun 2018 17:36:37 -0000 On Thu, Jun 7, 2018 at 10:33 Michael Butler wrote: > Ah - I'll re-enable that to see if it makes a difference .. > It's not a question of enabling. It doesn't explicitly use the 11 symbols. Rust developers assume that every OS has a frozen ABI like Linux. The rust from rustup will only work on 11. This is why you need to use the port / pkg. -M > I missed that in the comparison between my two build environments :-( > > Michael > > On 06/07/18 13:21, Matthew Macy wrote: > > > > Rustup uses the 11 ABI. > > > > On Thu, Jun 7, 2018 at 10:11 Alan Somers > > wrote: > > > > Can you reproduce the problem using rust installed from rustup > > instead of > > from Ports? If so, you should file a bug report with the Rust > > developers. > > Hint: when using Rustup, you'll have to use vresion 1.26.1 instead of > > 1.26.0. > > -Alan > > > > On Thu, Jun 7, 2018 at 9:44 AM, Michael Butler > > > > > wrote: > > > > > In response to a Firefox update, I tried to build the new version. > > > However, rust now fails with a core-dump in the build process. > > > > > > checking for libffi > 3.0.9... yes > > > checking MOZ_FFI_CFLAGS... -I/usr/local/lib/libffi-3.2.1/include > > > checking MOZ_FFI_LIBS... -L/usr/local/lib -lffi > > > checking for rustc... /usr/local/bin/rustc > > > checking for cargo... /usr/local/bin/cargo > > > checking rustc version... > > > DEBUG: Executing: `/usr/local/bin/rustc --version --verbose` > > > DEBUG: The command returned non-zero exit status -12. > > > DEBUG: Its output was: > > > DEBUG: | rustc 1.26.0 > > > DEBUG: | binary: rustc > > > DEBUG: | commit-hash: unknown > > > DEBUG: | commit-date: unknown > > > DEBUG: | host: x86_64-unknown-freebsd > > > DEBUG: | release: 1.26.0 > > > ERROR: Command `/usr/local/bin/rustc --version --verbose` failed > with > > > exit status -12. > > > > > > Attempts to rebuild rust (and cargo) from the bootstrap files fail > in > > > similar fashion. > > > > > > On a machine running a SVN r334538 kernel but more recent > > user-land, it > > > builds successfully. With (the only difference being) a kernel at > SVN > > > r334748, it does not. > > > > > > Any hints/thoughts? > > > > > > imb > > > _______________________________________________ > > > freebsd-current@freebsd.org > > mailing list > > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > > To unsubscribe, send any mail to > > "freebsd-current-unsubscribe@freebsd.org > > " > > > > > _______________________________________________ > > freebsd-current@freebsd.org > > mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to > > "freebsd-current-unsubscribe@freebsd.org > > " > > > > From owner-freebsd-current@freebsd.org Fri Jun 8 02:43:33 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 61053100CF68 for ; Fri, 8 Jun 2018 02:43:33 +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 CF4866D7B1 for ; Fri, 8 Jun 2018 02:43:32 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.190] (cpe-23-243-162-239.socal.res.rr.com [23.243.162.239]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id c691d308 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Thu, 7 Jun 2018 19:43:26 -0700 (PDT) Subject: Re: cannot get touchpad mouse, no psm device, on Dell Precision 3520 To: Anton Shterenlikht , freebsd-current@freebsd.org References: <201806072021.w57KLFle090699@jail0199.vps.exonetric.net> <20180607210118.GA94139@jail0199.vps.exonetric.net> From: Pete Wright Message-ID: Date: Thu, 7 Jun 2018 19:43:25 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <20180607210118.GA94139@jail0199.vps.exonetric.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jun 2018 02:43:33 -0000 On 06/07/2018 14:01, Anton Shterenlikht wrote: > On Thu, Jun 07, 2018 at 01:34:31PM -0700, Pete Wright wrote: >> >> On 06/07/2018 13:21, Anton Shterenlikht wrote: >>> Please help get touchpad mouse on >>> Dell Precision 3520. >>> The usb mouse works fine. >> >> pciconf isn't really applicable here i think.  does your dmesg buffer >> reference any PS/2 devices being detected?  here is CURRENT detecting my >> synaptics touchpad: >> >> $ dmesg|grep psm >> psm0: irq 12 on atkbdc0 >> psm0: [GIANT-LOCKED] >> psm0: model Synaptics Touchpad, device ID 0 > z> dmesg|grep psm > z> > > Perhaps this relatively modern laptop > uses a different device for its touchpad? hrm, looks like it should be a pretty well supported touchpad.  did you try updating loader.conf and rebooting to see if it shows up? it looks like this is the touchpad vendor according to the dell/ubuntu docs: Aquantia Corp. DLL07A9:01 044E:120B -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Fri Jun 8 06:24:17 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 987BA1012064 for ; Fri, 8 Jun 2018 06:24:17 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic316-15.consmr.mail.bf2.yahoo.com (sonic316-15.consmr.mail.bf2.yahoo.com [74.6.130.125]) (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 42228757AE for ; Fri, 8 Jun 2018 06:24:17 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: ND.8.UAVM1mDLiprl9gKzuzw1XefngNSw8Y_MW23zD8MMXy9ToxwYAmCKyNQjXn Sokrq1Q9L8tC9HOu1A.9szsy.dB5_VkkgB9FtnbWmwqri8mKj4mO7bpZG6MChUWFUxp33m7a5.dU p3I8bqEfldRR10GlObXegkmoSpfz18kTcb9eiWVNpnekp_1DyZAEGQ4N4GC.nTUuaK2E.ZIEHO4V YuFI3LiJugX6y5nRiphM373oSuQ6QS_xkjinxrGZ6z6djAX_OmyTyOmCTQTgKixaggdejGjnxA.1 n_AKgMwBEePEf1PNcJzwO7sKLIetTWxS0mnCSu12DgPMSPH1oSdSLbl.m.0aeyvSLEM27D0AXG9u pI4vmvsHysqSKQiAZZkVJY0_Bwi6_Omw6MPQuEsUD2JKte6aMCuNIlH_B_jUD082aon9CyHFK49o zIuocTieSrBxSlLCxJnR8AC0.7TXbWphB7KRbDGgvwfDKufEFlr7tyjB4fbAvC8XgKj8h_Qck.Ej hPLgJDnsfjRCRDOJ4b43VeRuYSU5yNVAYPWrA5HmtgZjDzbkpJven5oNmJGHVsIIMR9CP33Bnxiw yPkBMkmBqPc6D_bjXQPUegwZ_rz6AFwvzUu0iFamkzR_Qnp7YV3IH9ljL_5xYkNfVBsTmh8Zfzwd 1in_u8HIPgY9nyjuvHjulCWFUxcpaIxoGI.DT2WIWEHN4xJSYSB81y0yHmyVABpLyTISqbnw25LI 1xvZrx6gnVlcSjEhpQ9BaYbhyAKmY0AGuZ.z1jcUSjDfavxHhvGUY5akc.h2NFXOGvqut.D1S3hJ xVbeo9qqKjAKoGQHD1lwbLQUTp9jrxw8O6qkSN45MWBcj7A5YdCAY7DTI5CGDuUCHzaPmUkkgow_ nJ0asGKW1.v2D5pU0v2_CEZG_cvCEIWzjdQ.nNB6npjLt2N8_apT0YIEtybThpQFB6Vmc6o_hRA- - Received: from sonic.gate.mail.ne1.yahoo.com by sonic316.consmr.mail.bf2.yahoo.com with HTTP; Fri, 8 Jun 2018 06:24:16 +0000 Received: from ip70-189-131-151.lv.lv.cox.net (EHLO [192.168.0.109]) ([70.189.131.151]) by smtp415.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 90f939cc8fb1a6c61a3c934d084819ac; Fri, 08 Jun 2018 06:24:12 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: head -r334827 broke powerpc* and mips builds on ci.freebsd.org Message-Id: <1F8CCFA1-6449-47F4-8D61-995F5E177AB0@yahoo.com> Date: Thu, 7 Jun 2018 23:24:09 -0700 To: mmacy@FreeBSD.org, FreeBSD PowerPC ML , FreeBSD Current X-Mailer: Apple Mail (2.3445.8.2) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jun 2018 06:24:17 -0000 powerpc 64, powerpc, powerpcspe gets things like: --- all_subdir_hwpmc --- cc1: warnings being treated as errors /usr/src/sys/dev/hwpmc/hwpmc_e500.c: In function 'e500_intr': /usr/src/sys/dev/hwpmc/hwpmc_e500.c:611: warning: passing argument 3 of = 'pmc_process_interrupt' from incompatible pointer type /usr/src/sys/dev/hwpmc/hwpmc_e500.c:611: error: too many arguments to = function 'pmc_process_interrupt' /usr/src/sys/dev/hwpmc/hwpmc_e500.c: In function 'pmc_e500_initialize': /usr/src/sys/dev/hwpmc/hwpmc_e500.c:658: warning: assignment from = incompatible pointer type mips gets: --- hwpmc_mips.o --- cc1: warnings being treated as errors /usr/src/sys/dev/hwpmc/hwpmc_mips.c: In function 'pmc_mips_initialize': /usr/src/sys/dev/hwpmc/hwpmc_mips.c:458: warning: assignment from = incompatible pointer type =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Fri Jun 8 06:32:59 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A8E721012785 for ; Fri, 8 Jun 2018 06:32:59 +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 EFF7F75DB9; Fri, 8 Jun 2018 06:32:58 +0000 (UTC) (envelope-from greg@unrelenting.technology) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=unrelenting.technology; h=date:from:to:subject:message-id; s=default; bh=KCvMDIBQR9vfP/jUyQ84tuTKho1ORVFCp9Ko5u0k8oY=; b=Vj3myjfWQZrdGlRY6jI8+3h7vNaifLoAqHQenHlY9l7hrmpvn/yxee46Wm0fsvORYmtgnvETNGjBoeKXKdLB//Sjb9TMU3bSebZMoqK0nLD1fc22GK0ocwc0IKt4HCC5JMtLbCzU8LHRcZLe2TlmebFoTCbrSDC/WWuU7rL5btM= Received: by hraggstad.unrelenting.technology (OpenSMTPD) with ESMTPSA id 30b6907e TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Fri, 8 Jun 2018 06:26:15 +0000 (UTC) Received: from localhost (markarth.lan [local]) by markarth.lan (OpenSMTPD) with ESMTPA id 750ac54a; Fri, 8 Jun 2018 09:26:35 +0300 (MSK) Date: Fri, 8 Jun 2018 09:26:35 +0300 From: Greg To: Matthew Macy Cc: Michael Butler , Alan Somers , freebsd-current Subject: Re: rust broken? Message-ID: <20180608062635.veqhgksicoulkiyf@unrelenting.technology> References: <1e32764d-c202-6ad0-4c1b-0b0951cd6602@protected-networks.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline In-Reply-To: OpenPGP: url=https://unrelenting.technology/pub/3B011BAF.asc User-Agent: the one that sucks less X-Hashcash: 1:20:180608:freebsd-current@freebsd.org::yjgt9uqP6s7FZaPq:/RQ X-Hashcash: 1:20:180608:imb@protected-networks.net::7++62VTWjpRlX0O6:1iTE X-Hashcash: 1:20:180608:asomers@freebsd.org::5ZT/5yWFovgmpInk:c/P X-Hashcash: 1:20:180608:mat.macy@gmail.com::VA6eB1Y4zn4yHWOV:0WBh X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jun 2018 06:32:59 -0000 On 06/07, Matthew Macy wrote: >On Thu, Jun 7, 2018 at 10:33 Michael Butler >wrote: > >> Ah - I'll re-enable that to see if it makes a difference .. >> > > >It's not a question of enabling. It doesn't explicitly use the 11 symbols. >Rust developers assume that every OS has a frozen ABI like Linux. The rust >from rustup will only work on 11. This is why you need to use the port / >pkg. It does use the 11 (pre-ino64) symbols. Rust from rustup has worked fine on CURRENT for a few months already. From owner-freebsd-current@freebsd.org Fri Jun 8 07:18:59 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 44C9F1013196 for ; Fri, 8 Jun 2018 07:18:59 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from smtp.fagskolen.gjovik.no (smtp.fagskolen.gjovik.no [IPv6:2001:700:1100:1:200:ff:fe00:b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.fagskolen.gjovik.no", Issuer "Fagskolen i Gj??vik" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B0F7B76FDD for ; Fri, 8 Jun 2018 07:18:58 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from mail.fig.ol.no (localhost [127.0.0.1]) by mail.fig.ol.no (8.15.2/8.15.2) with ESMTPS id w587IqxK092697 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 8 Jun 2018 09:18:52 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) Received: from localhost (trond@localhost) by mail.fig.ol.no (8.15.2/8.15.2/Submit) with ESMTP id w587IqVE092693; Fri, 8 Jun 2018 09:18:52 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) X-Authentication-Warning: mail.fig.ol.no: trond owned process doing -bs Date: Fri, 8 Jun 2018 09:18:51 +0200 (CEST) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Sender: Trond.Endrestol@fagskolen.gjovik.no To: FreeBSD current cc: Mateusz Guzik Subject: Re: r334533 renders head unbootable on XenServer 7.4 In-Reply-To: Message-ID: References: User-Agent: Alpine 2.21.999 (BSF 260 2018-02-26) Organization: Fagskolen Innlandet OpenPGP: url=http://fig.ol.no/~trond/trond.key MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, score=-2.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.fig.ol.no X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jun 2018 07:18:59 -0000 On Fri, 8 Jun 2018 02:51+0200, Mateusz Guzik wrote: > Thanks for the report. Next time if you identify the culprit please cc: > the committer - not everyone watches mailing lists too closely. Wilco. > I set it up on FreeBSD as dom0 and verified the problem exists. > I fixed it with the following: > https://svnweb.freebsd.org/changeset/base/334820 Thanks. I'll try to build r334820+. -- Trond. From owner-freebsd-current@freebsd.org Fri Jun 8 12:27:23 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D1D0F1019E18 for ; Fri, 8 Jun 2018 12:27:22 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wm0-x244.google.com (mail-wm0-x244.google.com [IPv6:2a00:1450:400c:c09::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49F9F804EE; Fri, 8 Jun 2018 12:27:22 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wm0-x244.google.com with SMTP id n5-v6so3362837wmc.5; Fri, 08 Jun 2018 05:27:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :mime-version:content-transfer-encoding; bh=PQ59KKZIhyzOMryYyFS2kirF0OXHwtZ4qZsBZPq7CDc=; b=Dgbu5tE0fXy9vkT5vKmSToSzWV1fU32GgTR1mEKzxQgb3eed+SsUmWcZJ0TJ44uFIW 5mxq1kD0u0D58mE9ALivIgohYzeDB/r7MPqVtNpvL3ITzbPvSY4gpAz18CqJpFGQVdgq dXWBXA7mJ/ytM3psvtsv86WIRpeSZ6rm2W4tRDw2vOGh+4Le2RZFq3lXa6x2K2yGJN1b KoL2PNZIkCsMhTwA/sPJ3pi3X/9Id6+ER0kgHYsX8KyV0y7wkUdDnaY9VScgTHYKAOgT lIgqNVdz19Dmj0XSanm1hXiGs/KyUWEZbg+U36PrNY83h+5SxCRw3NkuCxrfTNT8jnfh lYOg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:reply-to:mime-version:content-transfer-encoding; bh=PQ59KKZIhyzOMryYyFS2kirF0OXHwtZ4qZsBZPq7CDc=; b=GcMTbNQL5dKmQm6D6dTdkUGEWakKBcnR5RdOAuIBqW6Q/R7I7AaV8KWT1pLTpaYtE4 x2YycdvzX9x+6XzA9icJzTr9eLwaUAhxIEw/GRT+bcXUq2jcOI2DclmMGnoJ1yvEijpm cMxtbRqKrQylxfm0hbA19Xe3w7Ej3l01/9VIkPduPEA4ZDSCHtrrtmfGkRv5fT5H2hk6 9wq4j+XHRTZ3R7rButLildE0Ik8mItXa+Qbyhk/JIZykyD8YSyovjeTRj5wqznC6msS+ Svy8812/qtREyydkRmVGzi58xePwx2o6ftNzWkDcceVky4OQpUS360Uu44nT2o94HTPf UTQw== X-Gm-Message-State: APt69E3rdyBcAFHOxwfFypF6ueb5OLPYL+ec98HTvIv27qWPHfUMhJF4 jBT1Rhk7xkE1tT185ZERHlWr0A== X-Google-Smtp-Source: ADUXVKKcoINLsnx3QbEOkPLare08WwceG8bpiuJm7bMAHOmZD+uCmvIb+ivuV5VfP9PD19O6fmCjig== X-Received: by 2002:a1c:3ac6:: with SMTP id h189-v6mr1575504wma.64.1528460841190; Fri, 08 Jun 2018 05:27:21 -0700 (PDT) Received: from ernst.home (p5B02381D.dip0.t-ipconnect.de. [91.2.56.29]) by smtp.gmail.com with ESMTPSA id 194-v6sm2265974wml.20.2018.06.08.05.27.19 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 08 Jun 2018 05:27:20 -0700 (PDT) Date: Fri, 8 Jun 2018 14:27:19 +0200 From: Gary Jennejohn To: Andriy Gapon Cc: FreeBSD Current , Stefan Esser , "M. Warner Losh" Subject: Re: Is kern.sched.preempt_thresh=0 a sensible default? Message-ID: <20180608142719.32104c84@ernst.home> In-Reply-To: References: <1d188cb0-ebc8-075f-ed51-57641ede1fd6@freebsd.org> <49fa8de4-e164-0642-4e01-a6188992c32e@freebsd.org> <32d6305b-3d57-4d37-ba1b-51631e994520@FreeBSD.org> <93efc3e1-7ac3-fedc-a71e-66c99f8e8c1e@freebsd.org> <9aaec961-e604-303a-52f3-ee24e3a435d0@FreeBSD.org> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jun 2018 12:27:23 -0000 On Thu, 7 Jun 2018 20:14:10 +0300 Andriy Gapon wrote: > On 03/05/2018 12:41, Andriy Gapon wrote: > > I think that we need preemption policies that might not be expressible as one or > > two numbers. A policy could be something like this: > > - interrupt threads can preempt only threads from "lower" classes: real-time, > > kernel, timeshare, idle; > > - interrupt threads cannot preempt other interrupt threads > > - real-time threads can preempt other real-time threads and threads from "lower" > > classes: kernel, timeshare, idle > > - kernel threads can preempt only threads from lower classes: timeshare, idle > > - interactive timeshare threads can only preempt batch and idle threads > > - batch threads can only preempt idle threads > > > Here is a sketch of the idea: https://reviews.freebsd.org/D15693 > What about SCHED_4BSD? Or is this just an example and you chose SCHED_ULE for it? -- Gary Jennejohn From owner-freebsd-current@freebsd.org Fri Jun 8 13:38:47 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6A930101B1C3 for ; Fri, 8 Jun 2018 13:38:47 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id EB7638254E for ; Fri, 8 Jun 2018 13:38:46 +0000 (UTC) (envelope-from david@catwhisker.org) Received: by mailman.ysv.freebsd.org (Postfix) id A1364101B1C2; Fri, 8 Jun 2018 13:38:46 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8D1D2101B1C1 for ; Fri, 8 Jun 2018 13:38:46 +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 DA61B8254D for ; Fri, 8 Jun 2018 13:38:45 +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 w58DcaZn094566 for ; Fri, 8 Jun 2018 13:38:36 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id w58DcaKW094565 for current@freebsd.org; Fri, 8 Jun 2018 06:38:36 -0700 (PDT) (envelope-from david) Date: Fri, 8 Jun 2018 06:38:36 -0700 From: David Wolfskill To: current@freebsd.org Subject: Panic from ipfw_alloc_rule() after r334769 -> r334832 Message-ID: <20180608133836.GM1389@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="Hvu36a0Kt9AtMNDI" Content-Disposition: inline User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jun 2018 13:38:47 -0000 --Hvu36a0Kt9AtMNDI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Sorry for lack of much analysis; am at BSDCan. jtl@ suggested that a sequence of changes involving memory allocation and ipfw counters is likely to be at issue. I tried grabbing some screen shots, the last of which has a backtrace (that isn't cut off, as the middle one is); they are available at . Peace, david --=20 David H. Wolfskill david@catwhisker.org Note that the presence of a pardon implies prior conviction for a crime. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --Hvu36a0Kt9AtMNDI Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEzLfO+ReoAfQwZNd7FTnMQKBJ7hcFAlsahtxfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEND QjdDRUY5MTdBODAxRjQzMDY0RDc3QjE1MzlDQzQwQTA0OUVFMTcACgkQFTnMQKBJ 7hctcgf/Y3EUaKfunr09LCuirGBMQQXr+13v0zsEE1Q+SM+HOW3WuTN+tKrgs1id fZpKXLVi2ZRSTHppcBEgWcRud/zQ5sDyjqwRvUPDCd1KLIaFOtTd3sx1Wg1H+dLK CRtVui6lCq5t+ahDkCU37xF9UEqKdUK0XhEj0g4ie+1kfkLJ/pQVuiPUJGtqGy8D kVq5NyK3ErtbSkxITL/N4kShq+17PWynVP+tkgeEMZtFNJ8gYZsJcPxkH+mhfnYS 4LhBC5VuU4LDPgB2YhZL3jDQbPixZZ2akQE/UO+yNhpac9hI1I7axFBd0CQgto61 8LvB9tvy021l3isRv37P3ppRzB/Ciw== =3uFE -----END PGP SIGNATURE----- --Hvu36a0Kt9AtMNDI-- From owner-freebsd-current@freebsd.org Fri Jun 8 14:18:53 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C0B8C101BBBE for ; Fri, 8 Jun 2018 14:18:53 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f68.google.com (mail-lf0-f68.google.com [209.85.215.68]) (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 2DD1D83B19 for ; Fri, 8 Jun 2018 14:18:53 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f68.google.com with SMTP id d24-v6so20311373lfa.8 for ; Fri, 08 Jun 2018 07:18:53 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:openpgp:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=SREXyr2kXPON1OW7BWYZJ3vovP/HhduZRTHoac9zSpM=; b=hzVyNGiyaMap1RTBLiYR2rVppjlsYww/oIgMphkvFuB/U5kxPjF1nocyFZ7QfzHtNp nTuRvNxOpt0sc1NBDEhAfY2OkLuSxzBCbN1kY/efbE/FRl1eku00IYrEch7/C+mqrU9u MMY7c+CFzVe3ylauxC9BC7/0nFfqv3Fla1TQy32+aXd2Rd9Wd/BLlP50dpXx+mrKTNqn D5mFn1stdned0xP5FbNDb1NNsa8qGyze6qBRizzCZJfRpDf6k9J4mawKJdkRP4apZCD1 bgzDREB1Rpg4YEvO25XnjefatumDSgdWeNSS0dg7njd7N5WdrP1ZYN19dTbp8IrVuGdw Txuw== X-Gm-Message-State: APt69E3Cmy0okgj3nyjgHmnUNygQJ3pmxDenAzqDfL2msdda/Cp7UMet de6PdwBe1F9kJw8AfPj2rsY/Xo9A X-Google-Smtp-Source: ADUXVKKwjW0k1mI7sQL1yjiXgnVZgmeMp2pfiFoMVkBfb/H9RWRGsVKvEXBL4TKLRa6zZvBSW7y2eA== X-Received: by 2002:a19:944f:: with SMTP id w76-v6mr4279274lfd.90.1528467525453; Fri, 08 Jun 2018 07:18:45 -0700 (PDT) Received: from [10.141.167.20] ([130.180.212.184]) by smtp.googlemail.com with ESMTPSA id j11-v6sm4344866lja.42.2018.06.08.07.18.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 08 Jun 2018 07:18:44 -0700 (PDT) Subject: Re: Is kern.sched.preempt_thresh=0 a sensible default? To: gljennjohn@gmail.com Cc: FreeBSD Current References: <1d188cb0-ebc8-075f-ed51-57641ede1fd6@freebsd.org> <49fa8de4-e164-0642-4e01-a6188992c32e@freebsd.org> <32d6305b-3d57-4d37-ba1b-51631e994520@FreeBSD.org> <93efc3e1-7ac3-fedc-a71e-66c99f8e8c1e@freebsd.org> <9aaec961-e604-303a-52f3-ee24e3a435d0@FreeBSD.org> <20180608142719.32104c84@ernst.home> From: Andriy Gapon Openpgp: preference=signencrypt Message-ID: Date: Fri, 8 Jun 2018 17:18:43 +0300 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <20180608142719.32104c84@ernst.home> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jun 2018 14:18:53 -0000 On 08/06/2018 15:27, Gary Jennejohn wrote: > On Thu, 7 Jun 2018 20:14:10 +0300 > Andriy Gapon wrote: > >> On 03/05/2018 12:41, Andriy Gapon wrote: >>> I think that we need preemption policies that might not be expressible as one or >>> two numbers. A policy could be something like this: >>> - interrupt threads can preempt only threads from "lower" classes: real-time, >>> kernel, timeshare, idle; >>> - interrupt threads cannot preempt other interrupt threads >>> - real-time threads can preempt other real-time threads and threads from "lower" >>> classes: kernel, timeshare, idle >>> - kernel threads can preempt only threads from lower classes: timeshare, idle >>> - interactive timeshare threads can only preempt batch and idle threads >>> - batch threads can only preempt idle threads >> >> >> Here is a sketch of the idea: https://reviews.freebsd.org/D15693 >> > > What about SCHED_4BSD? Or is this just an example and you chose > SCHED_ULE for it? I haven't looked at SCHED_4BSD code at all. -- Andriy Gapon From owner-freebsd-current@freebsd.org Fri Jun 8 14:40:37 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E9552101C8E4 for ; Fri, 8 Jun 2018 14:40:36 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wr0-x242.google.com (mail-wr0-x242.google.com [IPv6:2a00:1450:400c:c0c::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5CB5D85288; Fri, 8 Jun 2018 14:40:36 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wr0-x242.google.com with SMTP id v13-v6so13649543wrp.13; Fri, 08 Jun 2018 07:40:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :mime-version:content-transfer-encoding; bh=4/Z8GVljJFFLKgeXceBL6UHcaCFM/LsC2m96dyfhpIs=; b=q3iMod3XJVAS/COr4do2pRtbfKAB+BHvLj3hoi5ifz3yH15Q0MwlwH/YKaaIaPZF7s ItnOSTxpBQ1X6+Cy4IpeFDEmFUUcGjR5lxYpFBrj0nqJP2CSnnmKS8h7SXD0gyGmWWe8 B5ZFSSUdXgeD7Ejali5nC1U4KeWj60UjLE5o/o4+mXg6VYoty4UjeIoaxH5YY+uz67DZ WB6JNJ+3i7wbaxX5NjVylEF/HhN3sKaiixE0k1jY1yNBoj3DdLMAC6eoy+ranDVriYHn KWQ2SuldcYhniJvKHWXyVmHje1+MN2CSJu9L6ip3NZBhfCF/z6mr11E0qjiYw9bYfJz7 EYWA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:reply-to:mime-version:content-transfer-encoding; bh=4/Z8GVljJFFLKgeXceBL6UHcaCFM/LsC2m96dyfhpIs=; b=Lrun7apkfCclSSZKu+vLH/8U+Oy1ni0WokK5goreBHv7qI4o5tvrwpNeKWabPtCm+F rwJhu+Xjvw5VdVhIuRAKu+YI/4vrdLZ45WanaA7vJjLAks9ivz87jO+MspvNps8pBWMs blkuDRMcs6q2p+PIUQmjmVL8oTDb+d9virJf55MuZY3swPEUzzOngCFTZLudULswKnLb F1xCmYrwKOlBbO3Ja3WQQmAfpB2P86hAcpSPYDJQY943TtvGYIPypwBzDyABxVJdqutq KcqMM1PhiQ7endZab5H5sQwKyaMvMhfP6oWEFTNWDzRm9k9UVuEbflHLQftK9/8T+Dar XR4g== X-Gm-Message-State: APt69E2qifFVlcbqZ1//MQQj2ND8IX9Peqf+6Iz5YWb2kHe/OCRI5qTy Vf2KUwtExpOe8wK6rfWSwJSsEQ== X-Google-Smtp-Source: ADUXVKLA6/vPZb47sDmoOU1l0WjfkRocQJRNkTusVjkecsE8yAbSGqT1/sL3Y/MZJXOzCLbBFlJhXA== X-Received: by 2002:adf:ea0f:: with SMTP id q15-v6mr5736303wrm.9.1528468835254; Fri, 08 Jun 2018 07:40:35 -0700 (PDT) Received: from ernst.home (p5B02381D.dip0.t-ipconnect.de. [91.2.56.29]) by smtp.gmail.com with ESMTPSA id l84-v6sm2318824wmi.3.2018.06.08.07.40.34 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 08 Jun 2018 07:40:34 -0700 (PDT) Date: Fri, 8 Jun 2018 16:40:33 +0200 From: Gary Jennejohn To: Andriy Gapon Cc: FreeBSD Current Subject: Re: Is kern.sched.preempt_thresh=0 a sensible default? Message-ID: <20180608164033.5ff948f9@ernst.home> In-Reply-To: References: <1d188cb0-ebc8-075f-ed51-57641ede1fd6@freebsd.org> <49fa8de4-e164-0642-4e01-a6188992c32e@freebsd.org> <32d6305b-3d57-4d37-ba1b-51631e994520@FreeBSD.org> <93efc3e1-7ac3-fedc-a71e-66c99f8e8c1e@freebsd.org> <9aaec961-e604-303a-52f3-ee24e3a435d0@FreeBSD.org> <20180608142719.32104c84@ernst.home> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jun 2018 14:40:37 -0000 On Fri, 8 Jun 2018 17:18:43 +0300 Andriy Gapon wrote: > On 08/06/2018 15:27, Gary Jennejohn wrote: > > On Thu, 7 Jun 2018 20:14:10 +0300 > > Andriy Gapon wrote: > > > >> On 03/05/2018 12:41, Andriy Gapon wrote: > >>> I think that we need preemption policies that might not be expressible as one or > >>> two numbers. A policy could be something like this: > >>> - interrupt threads can preempt only threads from "lower" classes: real-time, > >>> kernel, timeshare, idle; > >>> - interrupt threads cannot preempt other interrupt threads > >>> - real-time threads can preempt other real-time threads and threads from "lower" > >>> classes: kernel, timeshare, idle > >>> - kernel threads can preempt only threads from lower classes: timeshare, idle > >>> - interactive timeshare threads can only preempt batch and idle threads > >>> - batch threads can only preempt idle threads > >> > >> > >> Here is a sketch of the idea: https://reviews.freebsd.org/D15693 > >> > > > > What about SCHED_4BSD? Or is this just an example and you chose > > SCHED_ULE for it? > > I haven't looked at SCHED_4BSD code at all. > I hope you will eventually because that's what I use. I find its scheduling of interactive processes much better than ULE. -- Gary Jennejohn From owner-freebsd-current@freebsd.org Fri Jun 8 14:52:18 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 48512101D0FC for ; Fri, 8 Jun 2018 14:52:18 +0000 (UTC) (envelope-from jonlooney@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 CEDAE85FE4 for ; Fri, 8 Jun 2018 14:52:17 +0000 (UTC) (envelope-from jonlooney@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 887AB101D0FA; Fri, 8 Jun 2018 14:52:17 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 75C41101D0F9 for ; Fri, 8 Jun 2018 14:52:17 +0000 (UTC) (envelope-from jonlooney@gmail.com) Received: from mail-wm0-f45.google.com (mail-wm0-f45.google.com [74.125.82.45]) (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 0697685FD9 for ; Fri, 8 Jun 2018 14:52:16 +0000 (UTC) (envelope-from jonlooney@gmail.com) Received: by mail-wm0-f45.google.com with SMTP id r15-v6so3832456wmc.1 for ; Fri, 08 Jun 2018 07:52:16 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=Oa/NrJ+OJ+Cswye3miF8qNyEVWsujg8u0FSil0S0Ix0=; b=W/fZjxSv/9ohhWDYjq2yM8tkXLcnYt9EXMjvdR/wDRqhijAJ/G2YZsRVjKWFvaHAjO PXc64XXHpN5EGnQp9Fbv8Q62lfWkmFuKqppXzLdFVQruESqJm+KdJu7IrFL+zgf9o9CP TFQHlzITPoCBdxKl90VdFlskhUz9itHCxRBpvZv4kXcFGgTe4hzl8cVrNLQj+3ht8mjp 2AowvIAdoawoI0v+wOGgOcBX5wJXKdAjAVzaJ5eHsGVWNt3GfkonkyEs85cQ8togh1Vz jwvdyFFh2zrO37USV4WSF6tp3nXHd65BbaCzpzF3W9VF3F8MTKENpIUWR1YGoE1MGiCK MrEg== X-Gm-Message-State: APt69E3wdh6FgiOuc2KXEh6mam8zsv+aMOLr0471+6l02m3YcNgXL9qo WnhzAHwlXY9nL45EyQiJ5F+g5lNH X-Google-Smtp-Source: ADUXVKLvMZd+YyktKe5ZmrIqQ9Ow0ro9QR88k/MLrImsABzaBMDwqdL2jYmxJexs2KP5LYdZo0RYvA== X-Received: by 2002:a50:b7fc:: with SMTP id i57-v6mr7506902ede.284.1528469529814; Fri, 08 Jun 2018 07:52:09 -0700 (PDT) Received: from mail-wm0-f47.google.com (mail-wm0-f47.google.com. [74.125.82.47]) by smtp.gmail.com with ESMTPSA id e46-v6sm15622386edd.80.2018.06.08.07.52.09 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 08 Jun 2018 07:52:09 -0700 (PDT) Received: by mail-wm0-f47.google.com with SMTP id n5-v6so4247147wmc.5 for ; Fri, 08 Jun 2018 07:52:09 -0700 (PDT) X-Received: by 2002:a1c:8cc8:: with SMTP id o191-v6mr1802878wmd.75.1528469529458; Fri, 08 Jun 2018 07:52:09 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:adf:98e2:0:0:0:0:0 with HTTP; Fri, 8 Jun 2018 07:52:08 -0700 (PDT) In-Reply-To: <20180608133836.GM1389@albert.catwhisker.org> References: <20180608133836.GM1389@albert.catwhisker.org> From: "Jonathan T. Looney" Date: Fri, 8 Jun 2018 10:52:08 -0400 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Panic from ipfw_alloc_rule() after r334769 -> r334832 To: David Wolfskill , FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jun 2018 14:52:18 -0000 On Fri, Jun 8, 2018 at 9:38 AM, David Wolfskill wrote: > > Sorry for lack of much analysis; am at BSDCan. jtl@ suggested that a > sequence of changes involving memory allocation and ipfw counters is > likely to be at issue. Just to be clear, I speculated that this seemed like it could be caused by r334824. And, screen_1.jpg does indeed seem to point at that commit. Jonathan From owner-freebsd-current@freebsd.org Fri Jun 8 15:40:46 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BB912101DFBB for ; Fri, 8 Jun 2018 15:40:46 +0000 (UTC) (envelope-from jonlooney@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 4AE5687E68 for ; Fri, 8 Jun 2018 15:40:46 +0000 (UTC) (envelope-from jonlooney@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 097D1101DFBA; Fri, 8 Jun 2018 15:40:46 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C12C3101DFB9 for ; Fri, 8 Jun 2018 15:40:45 +0000 (UTC) (envelope-from jonlooney@gmail.com) Received: from mail-wm0-f48.google.com (mail-wm0-f48.google.com [74.125.82.48]) (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 3EB7387E63; Fri, 8 Jun 2018 15:40:45 +0000 (UTC) (envelope-from jonlooney@gmail.com) Received: by mail-wm0-f48.google.com with SMTP id e16-v6so4107016wmd.0; Fri, 08 Jun 2018 08:40:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=9lhnUd40WTIK2Av7hNHrSuAALLx9jKted4xeXTS0Hfc=; b=Ax8IrquehfHH2lUoDJiTq7vmBERu83P+V7tvu3j87KZQNhrP52B2mQvinhy1/kSr9r yBfW7dkaZGXRduOPbS+/1wlR93/8uS0ATBnELeuo3xoLMLUsxBzziEEk0Z7HeukcxWbg 3zbpGn2y8+qCEGcD3MCjNH3rRfKmicT33GVX9Sk5V08XekEhY9yrkAcBMGjU7tuTETjo kGQSeONvgGZTMjNSmP4ZTrM1igGmIzAwdglxunTOaaD4c80HcXy7cLiNpO0QmLK6YqkJ Rqeb/OgXJVe6fcwe17cygRNV8PmTV1m49MFbbJhOpA7ArsWRFOlomCiWC3ws6IB8unhg 7pkg== X-Gm-Message-State: APt69E18PIvY/l1/rcggsZ1t+q/KKCccoaBo7gDSXAH1v4ySBsn5CwDN AyXj1DMAPLGeJry9xFRHyklpChD3 X-Google-Smtp-Source: ADUXVKKlCjZBMJ7WlnNXQY8+TMwPsbIDwZYmZ5NjSyg/KolwQlHAYmoRVdh7vI+/rD2gqNjWq3pUsg== X-Received: by 2002:a50:fa03:: with SMTP id b3-v6mr7661214edq.26.1528472438141; Fri, 08 Jun 2018 08:40:38 -0700 (PDT) Received: from mail-wm0-f54.google.com (mail-wm0-f54.google.com. [74.125.82.54]) by smtp.gmail.com with ESMTPSA id w10-v6sm4481056eda.50.2018.06.08.08.40.37 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 08 Jun 2018 08:40:37 -0700 (PDT) Received: by mail-wm0-f54.google.com with SMTP id r125-v6so4549339wmg.2; Fri, 08 Jun 2018 08:40:37 -0700 (PDT) X-Received: by 2002:a1c:2dd5:: with SMTP id t204-v6mr2041546wmt.94.1528472437413; Fri, 08 Jun 2018 08:40:37 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:adf:98e2:0:0:0:0:0 with HTTP; Fri, 8 Jun 2018 08:40:36 -0700 (PDT) In-Reply-To: References: <20180608133836.GM1389@albert.catwhisker.org> From: "Jonathan T. Looney" Date: Fri, 8 Jun 2018 11:40:37 -0400 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Panic from ipfw_alloc_rule() after r334769 -> r334832 To: David Wolfskill , FreeBSD Current , Mateusz Guzik Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jun 2018 15:40:47 -0000 On Fri, Jun 8, 2018 at 10:52 AM, Jonathan T. Looney wrote: > > On Fri, Jun 8, 2018 at 9:38 AM, David Wolfskill wrote: > > > > Sorry for lack of much analysis; am at BSDCan. jtl@ suggested that a > > sequence of changes involving memory allocation and ipfw counters is > > likely to be at issue. > > Just to be clear, I speculated that this seemed like it could be caused by r334824. > > And, screen_1.jpg does indeed seem to point at that commit. Yes, it is clear that this is hitting r334824. V_ipfw_cntr_zone is defined with UMA_ZONE_PCPU. ipfw_alloc_rule() allocates from V_ipfw_cntr_zone with M_ZERO. That clearly violates the assertion added in r334824, as well as the assumption behind the commit: "Nothing in the tree uses it..." It seems like something will need to be changed here to resolve the mismatch in assumptions/expectations... :-/ If anyone is hitting this bug and needs to get a working system in the meantime, you'll need to revert the following commits which implemented (or updated) this change: r334830 r334829 r334824 Jonathan From owner-freebsd-current@freebsd.org Fri Jun 8 15:54:06 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 767B4101E6E3 for ; Fri, 8 Jun 2018 15:54:06 +0000 (UTC) (envelope-from mjguzik@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 F3BEF688B7 for ; Fri, 8 Jun 2018 15:54:05 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id B7632101E6E1; Fri, 8 Jun 2018 15:54:05 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 94FC4101E6E0 for ; Fri, 8 Jun 2018 15:54:05 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-qt0-x22d.google.com (mail-qt0-x22d.google.com [IPv6:2607:f8b0:400d:c0d::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 14C98688B4; Fri, 8 Jun 2018 15:54:05 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: by mail-qt0-x22d.google.com with SMTP id s9-v6so13898908qtg.2; Fri, 08 Jun 2018 08:54:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=g9Qz3QfzRZtxVfTmBYik00YuD5SsnCbQaxeH84wg0pA=; b=mAktZHmnSVJZJuBw4BqAYRPu8HAdU8fFei0zSzTrU7JggRCcqktvlJedyMFEwc40T6 n4KE/t1iyb3npF8jkFu8UJ1LH4eP0GF+AI6rsOhq6pTgJr6+yfs3lJiQL/am+hS4k8zi S+LcJ1s4bmwQ1F3GMRmyGdM4vVqn1f/pCi3imm1NJYNk8bOYUwkwBeanhHz7JGDYSxTB pjW6Kx2OfIFANjthuPXoJJMMsXFCd6MDFyMq2Rn2PcnhkrIHi7sulhYD5C0D1FwiZ62P oy0LooKYgNfTbTRYif2fYi7/Mrt4Q+y5u0VURIcURtBHmvgQRuKNNz7OvpZMpqJ0qwnJ wWmQ== 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=g9Qz3QfzRZtxVfTmBYik00YuD5SsnCbQaxeH84wg0pA=; b=Ljcs3U13BZD/mKfXOnSVRuu7v2YP74VC2KfhidMMSTSLM73hsajJ5ibdCTMUwu4/sz 8JbYWWbOIVpjL9LnSc3xlXbNXdL+81kOk6t3c38DPDVFeH0WRlFUlLmE+hS6+e1xXxJW d7ILv/8c5zOKzrajaGZ0C858pykiLysCM1S7Ds2AuEE6Szfj7DDb+iD78KNcExH66E3G oOaocAf3D7DxrMTmup1HIQWEu+CKp6pc67oGV+H9tpvTk5fcRm2ma+6gL/op0UqVB3+p ItM4VtOmdDjJHVh6Ot2AMerpnF61F3sj1DQFeN1Xjx0KyixNv6Co0cats4/WSiiSj79E ByQQ== X-Gm-Message-State: APt69E38g0WMSvLxSKmeKRSNRSaM3gyIm910otpJ85AhKEfTgR9yh6vb 6VHGShl8rhkrYTIR9ZB0GMkyHotTG5lqtCLfXyC3wQ== X-Google-Smtp-Source: ADUXVKInzDKrdA9mla+PH1VxPYAZW4Pgyc/GzllBxv4+WnY70ekf9a6WgrsOO+b2QaJSPy83kBZKQUaWhQzf3YPhWjg= X-Received: by 2002:ac8:358a:: with SMTP id k10-v6mr6286346qtb.248.1528473244501; Fri, 08 Jun 2018 08:54:04 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ac8:1c4e:0:0:0:0:0 with HTTP; Fri, 8 Jun 2018 08:54:03 -0700 (PDT) In-Reply-To: References: <20180608133836.GM1389@albert.catwhisker.org> From: Mateusz Guzik Date: Fri, 8 Jun 2018 17:54:03 +0200 Message-ID: Subject: Re: Panic from ipfw_alloc_rule() after r334769 -> r334832 To: "Jonathan T. Looney" Cc: David Wolfskill , FreeBSD Current , Mateusz Guzik Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jun 2018 15:54:06 -0000 weird, my grep-fu failed me hardcore i guess. Will fix shortly. On Fri, Jun 8, 2018 at 5:40 PM, Jonathan T. Looney wrote: > On Fri, Jun 8, 2018 at 10:52 AM, Jonathan T. Looney > wrote: > > > > On Fri, Jun 8, 2018 at 9:38 AM, David Wolfskill > wrote: > > > > > > Sorry for lack of much analysis; am at BSDCan. jtl@ suggested that a > > > sequence of changes involving memory allocation and ipfw counters is > > > likely to be at issue. > > > > Just to be clear, I speculated that this seemed like it could be caused > by r334824. > > > > And, screen_1.jpg does indeed seem to point at that commit. > > Yes, it is clear that this is hitting r334824. > > V_ipfw_cntr_zone is defined with UMA_ZONE_PCPU. > > ipfw_alloc_rule() allocates from V_ipfw_cntr_zone with M_ZERO. > > That clearly violates the assertion added in r334824, as well as the > assumption behind the commit: "Nothing in the tree uses it..." > > It seems like something will need to be changed here to resolve the > mismatch in assumptions/expectations... :-/ > > If anyone is hitting this bug and needs to get a working system in the > meantime, you'll need to revert the following commits which implemented (or > updated) this change: > > r334830 > r334829 > r334824 > > Jonathan > -- Mateusz Guzik From owner-freebsd-current@freebsd.org Fri Jun 8 16:27:08 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 97E5C101EF3A for ; Fri, 8 Jun 2018 16:27:08 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: from mail-ot0-x22c.google.com (mail-ot0-x22c.google.com [IPv6:2607:f8b0:4003:c0f::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 2842D69B02; Fri, 8 Jun 2018 16:27:08 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: by mail-ot0-x22c.google.com with SMTP id l15-v6so15330608oth.6; Fri, 08 Jun 2018 09:27:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=H9l3Fx3KBWvjMS6wKU4Iisf4kafc/SksGz1HB/w7Ubw=; b=mkpccahP6imtinhPu3WuuAchkmZ1S/KBCnkj74GKpGq7EHbdRdtyMeEahvaR+oADV1 7WdLsIlI4hLgLUTjrzeFe4/CpndGVLG5Ngyg4mDH/hHNqGQfLnlgyb+Xyub0WWP2zQJ7 skWK+4crUivmcTRmuOmRsTLkSH29Qkjqfxpst3mWpbAXaE37auyfVm7FVND1ZcPeS2eJ 8BhmDpzBABoxSHDi8eghKXyutntUeRtDLERwRDA2NIUAdVzj49VLvVcurSB61U5kS3zB zVvD3e22HMFnpnjfQwcYqkbb0CUHG9lKTqIhUJDivuKNcUC71O4+7Pu7cFs0i0QQdabd 9G8g== 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=H9l3Fx3KBWvjMS6wKU4Iisf4kafc/SksGz1HB/w7Ubw=; b=LTsZ2SnZ63KXXQ1NP6IZ5SKmurZKLpaXuN3KrWXkCKtqpxSbjh/HoQD7lMIbnVAgZN zCz0AehWxB19trgwy9DgxcOR5pzpnkFlkGe0naP8mTQqpX688bM741NMgeBPaGuO7SPn OJcS7YJBy4P/acsy0ZRJA8l6VTXdu7hc52EcB+XV802Gt89g8tGXMTPjKvyM03Ao7c2q z9t3Ph27PQclVF2hcSpXgUSHDLRSGnAvI1LletRVV+gg5dX26amiBPYxwWaUACyP2coK F45iykmrc7sWdHx3gxHqZl/aF+t8rqgJnLygOZWee//NZuXcVGqOw320CucjR7fRynNv JnNA== X-Gm-Message-State: APt69E0z+2nXqhfWjGjK5Ojvhed5OotACNfjwzbmbXz4xijkYBlhzVKc kWFLT1k1tCCNOGT5CT33wj2T812723iGG6/qBj02yg== X-Google-Smtp-Source: ADUXVKJf5TkiyPX5R4DBhazTUo9kYwtxu7FCdiloxw8fyNDAlYzXBJ5UJKeHfrz48I9VFAT+/O+hP3Xj9Vm35G6SX7M= X-Received: by 2002:a9d:3e4c:: with SMTP id h12-v6mr3844349otg.150.1528475227351; Fri, 08 Jun 2018 09:27:07 -0700 (PDT) MIME-Version: 1.0 Sender: kmacybsd@gmail.com Received: by 2002:a9d:5885:0:0:0:0:0 with HTTP; Fri, 8 Jun 2018 09:27:06 -0700 (PDT) In-Reply-To: <20180608062635.veqhgksicoulkiyf@unrelenting.technology> References: <1e32764d-c202-6ad0-4c1b-0b0951cd6602@protected-networks.net> <20180608062635.veqhgksicoulkiyf@unrelenting.technology> From: "K. Macy" Date: Fri, 8 Jun 2018 09:27:06 -0700 X-Google-Sender-Auth: N6XLH2uv6Lj6tAcIfvfaQvXqFy8 Message-ID: Subject: Re: rust broken? To: Greg Cc: Matthew Macy , Michael Butler , Alan Somers , freebsd-current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jun 2018 16:27:08 -0000 On Thu, Jun 7, 2018 at 11:26 PM, Greg wrote: > On 06/07, Matthew Macy wrote: >> >> On Thu, Jun 7, 2018 at 10:33 Michael Butler >> wrote: >> >>> Ah - I'll re-enable that to see if it makes a difference .. >>> >> >> >> It's not a question of enabling. It doesn't explicitly use the 11 symbols. >> Rust developers assume that every OS has a frozen ABI like Linux. The rust >> from rustup will only work on 11. This is why you need to use the port / >> pkg. > > > It does use the 11 (pre-ino64) symbols. > Rust from rustup has worked fine on CURRENT for a few months already. > There's also kevent and who knows what else. But that's cool. There was no sign of movement there when last I used Rust in October. -M From owner-freebsd-current@freebsd.org Fri Jun 8 22:13:49 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E4C20FDC0F2 for ; Fri, 8 Jun 2018 22:13:48 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 8405775531 for ; Fri, 8 Jun 2018 22:13:48 +0000 (UTC) (envelope-from david@catwhisker.org) Received: by mailman.ysv.freebsd.org (Postfix) id 47770FDC0ED; Fri, 8 Jun 2018 22:13:48 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 36149FDC0EC for ; Fri, 8 Jun 2018 22:13:48 +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 799AC7552E; Fri, 8 Jun 2018 22:13:47 +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 w58MDjO3004106; Fri, 8 Jun 2018 22:13:45 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id w58MDjtN004105; Fri, 8 Jun 2018 15:13:45 -0700 (PDT) (envelope-from david) Date: Fri, 8 Jun 2018 15:13:45 -0700 From: David Wolfskill To: "Jonathan T. Looney" Cc: FreeBSD Current , Mateusz Guzik Subject: Re: Panic from ipfw_alloc_rule() after r334769 -> r334832 Message-ID: <20180608221345.GG1389@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , "Jonathan T. Looney" , FreeBSD Current , Mateusz Guzik References: <20180608133836.GM1389@albert.catwhisker.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="k1rsTFzI2vU/DXCC" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jun 2018 22:13:49 -0000 --k1rsTFzI2vU/DXCC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jun 08, 2018 at 11:40:37AM -0400, Jonathan T. Looney wrote: > ... > If anyone is hitting this bug and needs to get a working system in the > meantime, you'll need to revert the following commits which implemented (= or > updated) this change: >=20 > r334830 > r334829 > r334824 >=20 > Jonathan I confirm that, having reverted the above (via: svn merge -c -334830 -c -334829 -c -334824 . then rebuilding the kernel allowed the laptop to boot successfully. (My laptop's kernel has IPFIREWALL wired in and explicitly does not have IPFIREWALL_DEFAULT_TO_ACCEPT.) Peace, david --=20 David H. Wolfskill david@catwhisker.org Note that the presence of a pardon implies prior conviction for a crime. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --k1rsTFzI2vU/DXCC Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEzLfO+ReoAfQwZNd7FTnMQKBJ7hcFAlsa/5lfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEND QjdDRUY5MTdBODAxRjQzMDY0RDc3QjE1MzlDQzQwQTA0OUVFMTcACgkQFTnMQKBJ 7heKlgf/TZzqNqYZpDZxxzklgyttnsCpBwpQYUGPN2fGIVVa0rPcfNT60Y8kL8zU xuvYqDQoMn2j/tw1RB2mtg5ts+je9/+JbY9ta/MDKC6uqSoJ0gOSeAWXOYkyghHz Z0vPFJMzS8ZAgkQILW0LY0ahBgK80mHF4V71jDmxJbRwyF3jsy8X7KWb8lPZFH9E hC9hr3anuFPDf4QpT9wwFqBvcfOFhji2IGwyw3CwRLteS38jSWPHS+jAub1gMPiH Vg/03yfwRwWX1LGO4veebVEw1zRJVr7OCxxgS3YWKsd8YSXzXSfDBxnhZJP/1zbJ uG661gXlsUgDJRzcgj+0KkRDn2MFGA== =aYf3 -----END PGP SIGNATURE----- --k1rsTFzI2vU/DXCC-- From owner-freebsd-current@freebsd.org Fri Jun 8 23:08:28 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7E94EFDD0BE for ; Fri, 8 Jun 2018 23:08:28 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic307-10.consmr.mail.gq1.yahoo.com (sonic307-10.consmr.mail.gq1.yahoo.com [98.137.64.34]) (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 EAEEA768D7 for ; Fri, 8 Jun 2018 23:08:27 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: 5I6pL_cVM1mehT8hGmBEY.eTIkgpwvy6Jy2fISbYW4L0WBjPpIdg023XpbQOI05 2h_ZnVwamKDqm4Xp8dtzglki75YQwO0jfNBpDSddFDK0NJND5dgV6IhzW9XC78dFLasR__1axXWS deQosDhYOTcEBcZmcPQcBcWsKuB4PiA8Pqk50hqsJn102IBRsfKP3JWktktjt5MPj6tJo5rHzHdA sBXcO0y5yuzlGgohQ11RIP9Dd2rGy7e6QwzR1hvbqbM6CM9W8PhMnDP3tf99gPZO.Fwz4Wu.4DLo HNT2xn4CNkz3PhqKEFgQnjCB46W8uvd_REWAArJFyS9.OQ0uFbtzSdvz3zWq3aqh_buKe0Nmmp9C lJV1R31pDVq1XPtKNb7X0WJbpKZI1kUslib7rf34HeyipfKwMu_5GQBZu3s6qu7hxnikKNNr86Z7 wpXbGFo3S9xNViKjo6sJy3lasPKp3fSOAsxWdksA9YHM0OdvQy5pj3o1RLfwtAFMfKHVqtutLm6X Hd4VNQDvMm1XvVaMgzUgRv7kM6Kaw54ycqOIiktcRyVnqGJy5VjdLPriEwOeQrITZ3sEvJvQ4Qkm wGZ3SdFCQ263BNQ9ortNQ238RgZFJgFqKPY67dHWIumfOH4.9lb3NI2tor2NMPJOv4qTJdvszXbu GoPIyWzO4W407jvJrFnEbxh6jWzKrizfW5NFeyb9NL_TwH1OuwwDZ.0Q6ky8m_AqEmxuN1_mHdLz LHMbeQzNDdliTDO5OfYK6f9Zhq8DpINZotXo7B_cbSD6_qi2XbSMCF9YFt1HbfZUaM0SOjNC5ai1 pA1sEt7p6CJ4YgZMtSyV.28YTmxnrWR0HqiKWyqy4Yz5W01hF4F_tYs2gTu9uwfodZLcVUTbbj.A VZxgoHRLcdJnYAoGtyLteZ7PNAAjGbXQ5CdfWYeCvPWkwjKEANN1tzgQks57G6.7EKz0Rs.jx9pl PlA_a_gfhEIQ- Received: from sonic.gate.mail.ne1.yahoo.com by sonic307.consmr.mail.gq1.yahoo.com with HTTP; Fri, 8 Jun 2018 23:08:21 +0000 Received: from ip70-189-131-151.lv.lv.cox.net (EHLO [192.168.0.109]) ([70.189.131.151]) by smtp419.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 11ec90c7def69534568e6d8a26998e49; Fri, 08 Jun 2018 23:08:18 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: head -r334749 breaks the FreeBSD-head-amd64-gcc ci.freebsd.org build [via pmc.h struct's having constructors in C++] Message-Id: Date: Fri, 8 Jun 2018 16:08:16 -0700 To: mmacy@FreeBSD.org, FreeBSD Current X-Mailer: Apple Mail (2.3445.8.2) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jun 2018 23:08:28 -0000 [Note other build failures stopped builds before the below before this was run into. Now those pass to reach the below.] ci.free.bsd.org has FreeBSD-head-amd64-gcc failing for: --- libpmc_json.o --- In file included from /workspace/src/lib/libpmc/libpmc_json.cc:39:0: /workspace/src/lib/libpmc/pmc.h:102:53: error: 'int pmc_cpuinfo(const = pmc_cpuinfo**)' hides constructor for 'struct pmc_cpuinfo' = [-Werror=3Dshadow] int pmc_cpuinfo(const struct pmc_cpuinfo **_cpu_info); ^ /workspace/src/lib/libpmc/pmc.h:103:57: error: 'int pmc_pmcinfo(int, = pmc_pmcinfo**)' hides constructor for 'struct pmc_pmcinfo' = [-Werror=3Dshadow] int pmc_pmcinfo(int _cpu, struct pmc_pmcinfo **_pmc_info); ^ With the .cc (so C++ context) the name of a struct is also the name of the constructor for the struct. Having subroutines with that name name ends up with the name shadowing the C++ constructor. The builds are set up to reject such. The struct's in pmc.h are: struct pmc_cpuinfo { enum pmc_cputype pm_cputype; /* the kind of CPU */ uint32_t pm_ncpu; /* number of CPUs */ uint32_t pm_npmc; /* #PMCs per CPU */ uint32_t pm_nclass; /* #classes of PMCs */ struct pmc_classinfo pm_classes[PMC_CLASS_MAX]; }; and: struct pmc_pmcinfo { int32_t pm_cpu; /* CPU number */ struct pmc_info pm_pmcs[]; /* NPMC structs */ }; =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Sat Jun 9 17:15:20 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1CFD11010B35 for ; Sat, 9 Jun 2018 17:15:20 +0000 (UTC) (envelope-from se@freebsd.org) Received: from mailout06.t-online.de (mailout06.t-online.de [194.25.134.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1732077953; Sat, 9 Jun 2018 11:53:59 +0000 (UTC) (envelope-from se@freebsd.org) Received: from fwd35.aul.t-online.de (fwd35.aul.t-online.de [172.20.27.145]) by mailout06.t-online.de (Postfix) with SMTP id 2DE9641C52F7; Sat, 9 Jun 2018 13:53:51 +0200 (CEST) Received: from Stefans-MBP-23.fritz.box (rCYz4+Zcgh9PIrZU88+4RFENdVoNZX9BDwdaA+C1A5BxNOH-4mYL+5jMDkgN9RzgSA@[84.154.104.94]) by fwd35.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384 encrypted) esmtp id 1fRcRJ-1O0BMW0; Sat, 9 Jun 2018 13:53:49 +0200 Subject: Re: Is kern.sched.preempt_thresh=0 a sensible default? To: Andriy Gapon , FreeBSD Current Cc: "M. Warner Losh" References: <1d188cb0-ebc8-075f-ed51-57641ede1fd6@freebsd.org> <49fa8de4-e164-0642-4e01-a6188992c32e@freebsd.org> <32d6305b-3d57-4d37-ba1b-51631e994520@FreeBSD.org> <93efc3e1-7ac3-fedc-a71e-66c99f8e8c1e@freebsd.org> <9aaec961-e604-303a-52f3-ee24e3a435d0@FreeBSD.org> From: Stefan Esser Openpgp: preference=signencrypt Autocrypt: addr=se@freebsd.org; prefer-encrypt=mutual; keydata= xsBNBFVxiRIBCADOLNOZBsqlplHUQ3tG782FNtVT33rQli9EjNt2fhFERHIo4NxHlWBpHLnU b0s4L/eItx7au0i7Gegv01A9LUMwOnAc9EFAm4EW3Wmoa6MYrcP7xDClohg/Y69f7SNpEs3x YATBy+L6NzWZbJjZXD4vqPgZSDuMcLU7BEdJf0f+6h1BJPnGuwHpsSdnnMrZeIM8xQ8PPUVQ L0GZkVojHgNUngJH6e21qDrud0BkdiBcij0M3TCP4GQrJ/YMdurfc8mhueLpwGR2U1W8TYB7 4UY+NLw0McThOCLCxXflIeF/Y7jSB0zxzvb/H3LWkodUTkV57yX9IbUAGA5RKRg9zsUtABEB AAHNKVN0ZWZhbiBFw59lciAoWWFob28hKSA8c3QuZXNzZXJAeWFob28uZGU+wsCWBBMBCgBA AhsDBwsJCAcDAgEGFQgCCQoLBBYCAwECHgECF4AWIQSjceplnAvsyCtxUxNH67XvWv31RAUC WvLvqwUJCyUBEwAKCRBH67XvWv31REySCACc6vqcSFQCRyBRc2CV5ZBjbbnTy7VBoXbUS3/c 4Hn8I0YQ39q7//2z8vYsgLeM1mMXL4PUIU/0f0dBAFBLpxV7bntGzyCJls6SeGS/qcQKhqaI 6I7NcWg8OkIJIhUL6q238cS1ql9pU65fyHe0PP8JS08m81PDpX2/4wTE6h2jgYUy55eXRzoF MEjr1S8SSnidsBem27o7iWu9ltJsUtE86071iZlLzbuHv2nvucrjAV9cK9tHrxYT/YiY8QhT L48iWj2xIjLjg1ebmgIFZ2k881we/KTIoUugqOOR1gDSc4qwM8CA388cN3frjtl98CwhAT5T UV8tIDqri+/Z1AKwzsBNBFVxiRIBCACxI/aglzGVbnI6XHd0MTP05VK/fJub4hHdc+LQpz1M kVnCAhFbY9oecTB/togdKtfiloavjbFrb0nJhJnx57K+3SdSuu+znaQ4SlWiZOtXnkbpRWNU eMm+gtTDMSvloGAfr76RtFHskdDOLgXsHD70bKuMhlBxUCrSwGzHaD00q8iQPhJZ5itb3WPq z3B4IjiDAWTO2obD1wtAvSuHuUj/XJRsiKDKW3x13cfavkad81bZW4cpNwUv8XHLv/vaZPSA ly+hkY7NrDZydMMXVNQ7AJQufWuTJ0q7sImRcEZ5EIa98esJPey4O7C0vY405wjeyxpVZkpq ThDMurqtQFn1ABEBAAHCwHwEGAEKACYCGwwWIQSjceplnAvsyCtxUxNH67XvWv31RAUCWvLv qwUJCyUBGQAKCRBH67XvWv31RLnrB/9gzcRlpx71sDMosoZULWn7wysBJ/8AIEfIByRaHQe3 pn/KwE57pB+zFbbQqB7YzeZb7/UUgR4zU2ZbOcEfwDZcHUbj0B3fGRsS3t0uiLlAd8w0sBZb SxrqzjdpDjIbOZkxssqUmvrsN67UG1AFWH9aD24keBS7YjPBS8hLxPeYV+Xz6vUL8fRZje/Z JgiBMIwyj6g2lH/zkdnxBdC0iG1xxJOLTaghMMeQyCdH6ef8+VMyAlAJsMckbOTvx63tY8z7 DFcrnTJfbe1EziRilVsEaK8tTzJzhcTfos+f3eBYWEilxe5HzIhYKJeC7lmsSUcGwa6+9VRg a0ctmi9Z8OgX Message-ID: Date: Sat, 9 Jun 2018 13:53:48 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit X-ID: rCYz4+Zcgh9PIrZU88+4RFENdVoNZX9BDwdaA+C1A5BxNOH-4mYL+5jMDkgN9RzgSA X-TOI-MSGID: 62d0694b-abd3-4c82-8ade-eac6f48c8717 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Jun 2018 17:15:20 -0000 Am 07.06.18 um 19:14 schrieb Andriy Gapon: > On 03/05/2018 12:41, Andriy Gapon wrote: >> I think that we need preemption policies that might not be expressible as one or >> two numbers. A policy could be something like this: >> - interrupt threads can preempt only threads from "lower" classes: real-time, >> kernel, timeshare, idle; >> - interrupt threads cannot preempt other interrupt threads >> - real-time threads can preempt other real-time threads and threads from "lower" >> classes: kernel, timeshare, idle >> - kernel threads can preempt only threads from lower classes: timeshare, idle >> - interactive timeshare threads can only preempt batch and idle threads >> - batch threads can only preempt idle threads > > Here is a sketch of the idea: https://reviews.freebsd.org/D15693 Hi Andriy, I highly appreciate your effort to improve the scheduling in SCHED_ULE. But I'm afraid, that your scheme will not fix the problem. As you may know, there are a number of problems with SCHED_ULE, which let quite a number of users prefer SCHED_4BSD even on multi-core systems. The problems I'm aware of: 1) On UP systems, I/O intensive applications may be starved by compute intensive processes that are allowed to consume their full quantum of time (limiting reads to some 10 per second worst case). 2) Similarly, on SMP systems with load higher than the number of cores (virtual cores in case of HT), the compute bound cores can slow down a cp of a large file from 100s of MB/s to 100s of KB/s, under certain circumstances. 3) Programs that evenly split the load on all available cores have been suffering from sub-optimal assignment of threads to cores. E.g. on a CPU with 8 (virtual) cores, this resulted in 6 cores running the load in nominal time, 1 core taking twice as long because 2 threads were scheduled to run on it, while 1 core was mostly idle. Even if the load was initially evenly distributed, a woken up process that ran on one core destroyed the symmetry and it was not recovered. (This was a problem e.g. for parallel programs using MPI or the like.) 4) The real time behavior of SCHED_ULE is weak due to interactive processes (e.g. the X server) being put into the "time-share" class and then suffering from the problems described as 1) or 2) above. (You distinguish time-share and batch processes, which both are allowed to consume their full quanta even of a higher priority process in their class becomes runnable. I think this will not give the required responsiveness e.g. for an X server.) They should be considered I/O intensive, if they often don't use their full quantum, without taking the significant amount of CPU time they may use at times into account. (I.e. the criterion for time-sharing should not be the CPU time consumed, but rather some fraction of the quanta not being fully used due to voluntarily giving up the CPU.) With many real-time threads it may be hard to identify interactive threads, since they are non-voluntarily disrupted too often - this must be considered in the sampling of voluntary vs. non-voluntary context switches. 5) The NICE parameter has hardly any effect on the scheduling. Processes started with nice 19 get nearly the same share of the CPU as processes at nice 0, while they should traditionally only run when a core was idle, otherwise. Nice values between 0 and 19 have even less effect (hardly any). I have not had time to try the patch in that review, but I think that the cause of scheduling problems is not localized in that function. And a solution should be based on typical use cases or sample scenarios being applied to a scheduling policy. There are some easy cases (e.g. a "random" load of independent processes like a parallel make run), where only cache effects are relevant (try to keep a thread on its CPU as long as possible and, if interrupted, continue it on that CPU if you can assume there is still significant cached state). There have been excessive KTR traces that showed the scheduler behavior under specific loads, especially MPI, and there have been attempts to fix the uneven distribution of processes for that case (but AFAIR not with good success). Your patches may be part of the solution, with at least 3 other parts remaining: 1) The classification of interactive and time-share should be separate. Interactive means that the process does not use its full quantum in a non-negligible fraction of cases. The X server or a DBMS server should not be considered compute intensive, or request rates will be as low as 10 per second (if the time-share quantum is in the order of 100 ms). 2) The scheduling should guarantee symmetric distribution of the load for scenarios as parallel programs with MPI. Since OpenMP and other mechanism have similar requirements, this will become more relevant over time. 3) The nice-ness of a process should be relevant, to give the user or admin a way to adjust priorities. Each of those points will require changes in different parts of the scheduler, but I think those changes should not be considered in isolation. Best regards, STefan From owner-freebsd-current@freebsd.org Sat Jun 9 17:16:26 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8FAFD1011A9F for ; Sat, 9 Jun 2018 17:16:26 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [IPv6:2001:8b0:151:1:c4ea:bd49:619b:6cb3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 33A078227E for ; Sat, 9 Jun 2018 12:39:58 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from liminal.local (135-23-114-22.cpe.pppoe.ca [135.23.114.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id 94BE4DB2A for ; Sat, 9 Jun 2018 12:39:55 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none (p=none dis=none) header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/94BE4DB2A; dkim=none; dkim-atps=neutral To: freebsd-current@freebsd.org From: Matthew Seaman Subject: Base FreeBSD-lld package dependency problems... Openpgp: preference=signencrypt Autocrypt: addr=matthew@FreeBSD.org; prefer-encrypt=mutual; keydata= xsFNBFJIL80BEADi7/VbnnErDU6pjEhI/SzEZ/HbDRkJ5g7HroAtqIRm6nj8ZwOAgZ/2ZnWn 5F+fXTuLsG0FLNtkd17FoVcuCi5e/GPliXI5cmamV7E1Yz4T8UsJ7RQolimyxVexccKd16Tc AA7B9bFlJSKkBUSD0buj7VjT07xWhRzu6Vgi5r0UjLALYJz977uZA0F1aOGOXREDEAOhdcNc kSNjynqAwDA6dCT1Elpi4key1fYjv4jyDF+GU/YXul2Y/rguA8FCkHd9vyym5eAsLQ5mG00V V9fkEHIpH5KorNVnl/ufHXnkZqmHAZVpFDcrshb7aZ/pL45PXyWgLj+e6etelgj3a2bZi0JF cVdXCnBZVP2oIyYblM11ugTbfCwodORU8a5KfPeztMdAtDr4e+32NTrPdPi5rLT+GUsYz+PL 3A3m3u8bdsFp40DlIrBtSByVjqERxcfhphrEB4J8BXHUG7OAtXkZMlW/PGKDwXJq0O6Z5Tcg YHAoEiSWbXiexHgXNJyP+sqnIlhLWhSJGeJ+C83wqI6oYlZUCW00NkPxcIHnQPV/z+5wQVci TMyaWC2YCIHz4Ljs+TnwWMz0E8PNFDfHVbQ0W4PRGV7gRAqxfL+yKufauIEGbEq8rNDbSwL3 bcUCxR4ZDlaUEUwT4J8naf7rjdgiEYHs2Ig3jeK1+ER4FPG1sQARAQABzTBNYXR0aGV3IFNl YW1hbiA8bS5zZWFtYW5AaW5mcmFjYW5pbm9waGlsZS5jby51az7CwZcEEwEKAEECGwMFCwkI BwMFFQoJCAsFFgIDAQACHgECF4ACGQEWIQRyz6whebywJLW1RZADb2ye5/OevwUCWttU4QUJ DFmAlAAKCRADb2ye5/Oevwb5EACipbOazgwl5IbqkQI4gELpCh5dqDASS9DQqAD35n/cI91P 0lrYcdyCQbOXadQi5bswnP4AcJqX83mITXbcApDdxVxHujw7VODI069eV3/I9Qz72mHYYAAj w0CHNx4bKED2YCSVS6+jV5hq2sywNEUxL+4I218Oc+IsLts62m4tQ8UxX9fQ2H1kQOvdrYpj x7je5qJX/yujLc+9WWZ8ZBSdP/HVJUEdRgQotwAlgfMp3mRQEE73MAJisG/olj/dSxd+oHIP NbJt1yxMqhZekuEGqZpm3tWvqYgpGcEXdhphJSxeK6oLpTLghuAb7/WdOBrpfL7c2OQYBgOw DK+7Io9NBt/d/rCxL39jmUONW8ohrhnNQ2SALnyYTvZgruxA4tXxOOyM9up0/8mB5E8YC9ML 5YuxRPNTXYeWCexa0zktnkCgT7PhS33evf5gsA0B9Snv7TFCFN9adPAdHlsppZIWfTHDG8e2 Jik8PmvsUG34XNif5k6Ui3++2ZA8ZoKvOyLeomuno1hN8yk1APw8SbX1SPNz9UVbl8W/YgGj 3GhYOuQt4HcMiLyTby6R4lC4nsBaHS1MX+57f6Zxzf2wNjSKxiJK9qS7azbu/GxpafNhbz1Z +iUDIaJkRWA1Gs8C7SMcfVsI5zDtvqHGYtTCgooVMYJ6vRyB68M4bljUYMxRTs7BTQRSUUK4 ARAA1FhWoOejtwmsnGshoIbda2FmM+z/f97OzpagLhACHfP5Es/I18wG/0G+rdNuO2tjA9IM Z44GUMtjokDrDk63N9S+rVKy1QEy+UN6CiIfYTpTTAPnEY7IGN1JjGksPhn7aeuBCQwUMAV1 k+wklBCcOD6s8DD4kx0ZJqkH83XzWoBSVamdHvnM56C8yPVr5HHMC1tZInAWBMrF+cjl1EPf z3CqkVnG8Sxc5ydeibMS9Q3lHLeVkVlMRAmNqzNLfgJDUWtzac7JIjFEsxYYhpiaPcsstUUu Ha4zIRJ/yHDNbDttWRf1lrlFZLpeuap4BZ2hQw0UOZVNwGoFoS4ZqaZiv8mm0lX6s9/AdQD6 AVrpXWKa7JU2wDiay9sRbYh+5vVWGz9mhncK/Vfwtu5IjVp5v5WMz/WfnUxZMcNlfgTo4i1s www+qRBO2A4Yj8qKKWnTsl7aCX92itTiPgwbt6YgQPwgww72r67jPt5o8VMXDqPMPKzGicw1 AyxtMjsoSlnn91FuZctwil3vPpvzGXtBmrzQSbdDmy0KT5p5/W9pD/8UtLLLM6PLs5X0jIho vQHnQKEUO7xV3yNDAW9DPICeh7f/o9W+QJfQAXngNz0brvmgScAUXRaeAFeQbAmtEG92qlSV D7gb7WOemllgfbEn0Nanrv5aEcZCWx4WjybMLHEAEQEAAcLBZQQYAQoADwUCUlFCuAIbDAUJ Adf5AAAKCRADb2ye5/Oev8CLD/40aQCRpHTfydtq6sEVHFdpQCgGIE/47r46kr2x15C2wYPY m9JJ1lHvjpKt6N2gGfmiMfq8+PX1ppWp+qkZP4KF2PSxJJ6sjPNMne9+UhPEX5Xn3Z1vjRXJ t7BV0vhsB7WrI8jI9arpYkwVOkQyyjFxWeL0jvfGYYABttvlG/hjxuwI01vipuTfr89zjRYc C5hY1sg2bOn/tIe/V15Sj13Uo/JuFn7Aim91iEYrp5668qbWbLM/8hNqtECH6qLEhtoeoLlL bq6D3HIi00bYvcbBpig/azUasHio3gf4GNklQ5bVvWgIwV0Ue4TjXMCokpaLCq+CNaIqEO9v qJcEa4t0d7oXFHj6U9l6iSVPYRgXsCj/pBgYFPrdV6V8WNGHqa+yQBBtV9bSPNKF8xAjHQ5B KGardo1fBsF7P1CVE3SSr5IzZwk5DIeyCWGJjB8NGGaPWNPIvNyC9v5N9KpFe7WAOyAdEjR7 81ly0veYnFEFcVAmvW3FgzlEXQXw4M4FuniETd3idSJZpRBmq2jvxyfF3b69AdiLddcOAffR jGOBTezLtqxJstJhj7/s4yCuwQhUTpJzwoNBbPLqxmQ/THmdwx6VYAPIqOHBkSQj14nGyX5R vkfvZFq9OBKiVBSQi94jaaWZswqMfGeqZIOuZit+Q2TFTyS8b0R0dDaUUw32DMLBZQQYAQoA DwIbDAUCVCEGdQUJA7D3PQAKCRADb2ye5/Oev1gnD/4wJs6iWJrm2p7/7A0vt+ldL7j/ZaLw dl6XGiTvDY13qISfRwsl6yhsKgwqeAM5zOm1E6gzIdf7VwWx2/4KnQJ83nfBmU8KReUX3udT bVIk8Jo3sMYvPsWtNjRIHCLcXn54/Ajljp1cXihzQ0oXpFxn9sbZll4iE6TcKbPuBBFEsrbI xbjdtG7PNzjnhKkkwrORp2JsScWMcpvqq0/AvPeMKMbQ8SAkOZH20aWdw4wDbcm1bTrxSGYf bFsDmMXxueySeIWbDCwimeMFdWSItsCvHTKX8BIwDM6NP2sQY9Qya3p48HCmFGDpmHdZoU4f xp9+lZFvbNlG+gtY1up3HNYZ9pIbOOdKDjkKtymYX+F2gNflgD/Jp/Fa2EXDzk/iQ73gdT66 2TP9C0WOkFiM17bv5HmmFMGxG0Ap6Ntt8dcqZb2/XoBjR88ssrgDaSbFtpDkUIMy6OarXCii ioMF+bgpPDIffOFPRSFsB+jmMcGu2r3q5I6C3fpTgHh9towgJLhw0pfl08Vr+q3oODcOcXwk NbTrBtM3T5SrLv/lQqWtZmCppWDuRuFt02/jbMaVmWCnpQJN89Z+44H+Fu2ZL+sZSDhsBE0w O7iGAfgP1yIIiK/zunx6IMuNMf5v1y6StOHO/PqJ4+q8IWKBLzjWzEnpNiT5CA/Hdk7v+Va1 Ypd9XsLBfAQYAQoAJgIbDBYhBHLPrCF5vLAktbVFkANvbJ7n856/BQJa21VJBQkMUG4RAAoJ EANvbJ7n856/mAcP/0ybQAvXfxWEEBykIP0DhJHAC/EMeBwNkiAp4Sqr+uIz3GCFGKHDjvEG sofiFQ2ujBpG7FncHlBbnsTLFvte3ahE30I1AKcd9k1MBeOFoCBHwES1ts0XUXF37E+ANrEC QrzSayZx95csIiYvlfOPEOLAt7EiURKXCXdO6HNo8UimcmGdQwT3ytTMosHAbdrhQk13chTI WptmmCwz9iWLxT9PLY01ACCoXuAdGz07ZXQn+bB+avMa6Wh5yh39J+6jJiuzbRlv/Uelogq7 ojbC5zveX5rNbcyinwOEFyGAhFpfF7ESsKedR2Q40LvysT7I5ugS+Hk4Z2nvbd2bOSdC4j8a BWzfqVu2p37d2AnnswfPoLrOyNUZ+ciTEcmEUVR7WWUwQ0H6A6h4C2NeBmLRRjk9CEfzrgM2 DNQqDL1RMYKlVosQ8BeUR9ThztUwDakxnK0ZtZb2rAliKYaaEFbZDePz1xmvjYc7EZq/3OTl GMUDa6BPHHbCvJjiAUc/Q9iaRe3dp69V/rwOM5NiS+tWgp3OtgX0mDWVoQnDjyWVIRU/QagJ HsNJJCc0N48BxgIX3H6M0x6BbA9PKgFtDlK4hLR/hDl5fnWG45TVIxT4ybuPXGW7af9U6bGD gXTBNUCzNUz2p2F2u7W/iK0WTfjovYvVVcptegyu6ttZN49KkQtL Message-ID: <931bb5f2-b4f3-ad8a-9189-e307b9f5e6c5@FreeBSD.org> Date: Sat, 9 Jun 2018 08:39:52 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="sUFewhUu3t1KH8a3LF1np8V3fDNcAOIk9" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Jun 2018 17:16:26 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --sUFewhUu3t1KH8a3LF1np8V3fDNcAOIk9 Content-Type: multipart/mixed; boundary="cRJmX9D4ICCA9DgweTfvq08udmYj8yfD6"; protected-headers="v1" From: Matthew Seaman To: freebsd-current@freebsd.org Message-ID: <931bb5f2-b4f3-ad8a-9189-e307b9f5e6c5@FreeBSD.org> Subject: Base FreeBSD-lld package dependency problems... --cRJmX9D4ICCA9DgweTfvq08udmYj8yfD6 Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: quoted-printable Here's a little glitch with packaged base I stumbled upon. On a freshly pkg upgrade'd 12-current machine, I see: codling:/usr/home/matthew:# pkg info -dr FreeBSD-lld-12.0.s20180609030436= FreeBSD-lld-12.0.s20180609030436 Depends on : FreeBSD-runtime-12.0.s20180609030436 So, no dependencies except the runtime. But look at this: codling:/usr/home/matthew:# pkg autoremove Checking integrity... done (0 conflicting) Deinstallation has been requested for the following 2 packages: Installed packages to be REMOVED: FreeBSD-libefivar-12.0.s20180609030436 FreeBSD-libregex-12.0.s20180609030436 Number of packages to be removed: 2 Proceed with deinstalling packages? [y/N]: y [1/2] Deinstalling FreeBSD-libefivar-12.0.s20180609030436... [1/2] Deleting files for FreeBSD-libefivar-12.0.s20180609030436: 100% [2/2] Deinstalling FreeBSD-libregex-12.0.s20180609030436... [2/2] Deleting files for FreeBSD-libregex-12.0.s20180609030436: 100% codling:/usr/home/matthew:# pkg install -f FreeBSD-lld Updating base repository catalogue... base repository is up to date. Updating ports repository catalogue... ports repository is up to date. All repositories are up to date. Checking integrity... done (0 conflicting) The following 3 package(s) will be affected (of 0 checked): New packages to be INSTALLED: FreeBSD-libefivar: 12.0.s20180609030436 [base] FreeBSD-libregex: 12.0.s20180609030436 [base] Installed packages to be REINSTALLED: FreeBSD-lld-12.0.s20180609030436 [base] Number of packages to be installed: 2 Number of packages to be reinstalled: 1 Proceed with this action? [y/N]: y [1/3] Reinstalling FreeBSD-lld-12.0.s20180609030436... [1/3] Extracting FreeBSD-lld-12.0.s20180609030436: 100% [2/3] Installing FreeBSD-libefivar-12.0.s20180609030436... [2/3] Extracting FreeBSD-libefivar-12.0.s20180609030436: 100% [3/3] Installing FreeBSD-libregex-12.0.s20180609030436... [3/3] Extracting FreeBSD-libregex-12.0.s20180609030436: 100% Looks like FreeBSD-lld might need to register dependencies on FreeBSD-libefivar and FreeBSD-libregex? Or perhaps its some other package that needs libefivar and libregex? Cheers, Matthew --cRJmX9D4ICCA9DgweTfvq08udmYj8yfD6-- --sUFewhUu3t1KH8a3LF1np8V3fDNcAOIk9 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEEGfFU7L8RLlBUTj8wAFE/EOCp5OcFAlsbyplfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDE5 RjE1NEVDQkYxMTJFNTA1NDRFM0YzMDAwNTEzRjEwRTBBOUU0RTcACgkQAFE/EOCp 5Of8SA//R8vg1Af85H/vkIbsezEeblgd8Ws3Cvx1WTgZOdpfXcE/BziDquSFH9ke /5nkOuaxAIB5R/ovhv77Q6DFdHMVWksmhT3GpDlRxrhhBGRh3pYgZoL7LyXIeTv2 /nGMbU1Sqop7eIh7H6JBbwSP1KhaQGyhV7d05Uu/3Ok957buwZCFrTc9EZVtHpMW G3LYgZkQ0A6LTZCYbpdH/11bEjSnchHg/Xpi9gLbhq5TlEYQplN2nTgQ41wHVTKi bf511RQZXA2P3AL6e48ZDaSEUTVV11JrEZqfTqfzLu/GunTct42FdxufihNr51UO /zmcrCngfSmIKYrEfsWOGowOlmJap2ILtU6xqy9rEPWQcFUZ3ptTMmISeBgOKjyw demtNW5ji9KYEyT7s7ZdX7PQPvDtB/zIA3pHDXQnoWGMbsSz37sZLfzS+YxQKepQ x/3BArFF47h3xzMkAX1qJFzFcKl8DL+0y8H/3Hq3wYx5NwrRGakDp2IEF0wmD5UB yq8siGK27mcS7CC4qd+FwGrIHhd51qrJoAJ4vAV+XZUrP44xskqhEPfg5ikJ2uL/ 4SyruxZXaN6LZpV0yzeEN41O4YBlIb/sKyK6+hOoND4WqpLXGxbuutrAsNLtqfq8 Zs4SgeyDsUXhuV/KDLFc6o2ErNExvCVKQA0frcCeLBzPdDsAr7Q= =SjPR -----END PGP SIGNATURE----- --sUFewhUu3t1KH8a3LF1np8V3fDNcAOIk9-- From owner-freebsd-current@freebsd.org Sat Jun 9 17:16:08 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2164C1011741 for ; Sat, 9 Jun 2018 17:16:08 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A995E7A766 for ; Sat, 9 Jun 2018 16:12:01 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([78.55.173.237]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MVNWU-1fltxJ1AI2-00Yk4M for ; Sat, 09 Jun 2018 18:11:59 +0200 Date: Sat, 9 Jun 2018 18:11:30 +0200 From: "O. Hartmann" To: FreeBSD CURRENT Subject: r334885: dwarf.c:1980:8: error: use of undeclared identifier 'DW_LANG_C11' case DW_LANG_C11: Message-ID: <20180609181157.742eb122@thor.intern.walstatt.dynvpn.de> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 X-Provags-ID: V03:K1:Cwry4KILWM1snWkeWtqhz457XmiLJjY3EyAdgCREjuOXZozrbdP qXDDL3FQxyzWv57hYx4PjioFB/4EGQYKgvQ7ciJzRIyOYX3hPJIAj2ImM7wIrmsTxLxc8Wz pxCS+hft3Ti5fbniCCv3m3wlLohjtZ1JGEALfvQLVlHmptPEO3ucEcRWXLCm+IOHBEOMG2M ye9PsRio44vTBJOmiC6TA== X-UI-Out-Filterresults: notjunk:1;V01:K0:xyYybjL36Fs=:7PBqz8JRwC2MsfOrFwBbug OEhGYRDrmfiTo5Y5enGZ959d29QgScd/pJlSrMXbuC4REMifHjwymlGH6EGdDuyXJkKZc600s wonBqqmTHW5VCwsBmWvaeVmOgIP7lnWLLtU8Vdavfy4HpCDckZcHvMbfYb+KwoPn8HX55YKhP Y/OSkjnyxsKXc7wcsYCHxADgtVFV8qF70hIVlQBtGDVtyjobUvC2rXBuIpf1NE2/BkLFj3en4 IBXbqqEw9YVXAKSaUfD+KV+ONgKXRDAqj3CixblplRGWOfNZHbVtLfhTQ5nq3JD9DkVe2nsQy cumBdHIn2J90YR0oxKe1ZaYsTsKfK9FvTvjCFTpLdAzAgPz6C2qz6PmxSNbL05klPWM4FyXop ZJj2yRPw9z8atsi1R6nknZf16sRJiZmPZ1/4VqaaPkjlwhH0S7MEMPaidIFlGI6Ekgol2lG4b aGCcNQPz7AUVa6LdK2iitgz1GRJmyk54oUrnyo4qWFmyJgekP3NYEOkuv9aAHgPqE93OmEwOq xMJGwyPxfMy4DD2VqaSq8IYXOKF/E0qX9jX8SBB1qvR9LBT+78NMJecIn/IxJ2UNWwfv5ExrL HuckEVkw2YXdHXfzHho/tnDOUvNG3tezWmcOEQI1hGb/OxvuYeztP8CJqIsUSlTwDjlOiYYjm HA/4MwmCEZdgbt5ymEcsCZ1RZhd38c9f6D4KXWcQMkWoG5eLIsF74klfo+MJIJ2Wywx28Z6rz iDhDbDDjyhuZoYoVaZd3RicgdWcCO7F3MZ46hfsKn8ptN3/uDKT08sv+WPRskORI143xOHRa4 TLWgoZ2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Jun 2018 17:16:08 -0000 LS0tLS1CRUdJTiBQR1AgU0lHTkVEIE1FU1NBR0UtLS0tLQ0KSGFzaDogU0hBNTEyDQoNCkEgcmVj ZW50IHVwZGF0ZSBvZiBzb3VyY2VzIHJlZG5lcmVkIGJ1aWxkaW5nIHdvcmxkIGZhdWx0eToNCg0K Wy4uLl0NCg0KPT09PiBjZGRsL3Vzci5iaW4vY3RmY29udmVydCAob2JqLGFsbCxpbnN0YWxsKQ0K QnVpbGRpbmcgL3Vzci9vYmovdXNyL3NyYy9hbWQ2NC5hbWQ2NC90bXAvb2JqLXRvb2xzL2NkZGwv dXNyLmJpbi9jdGZjb252ZXJ0L2R3YXJmLm8NCi0gLS0tIGR3YXJmLm8gLS0tDQovdXNyL3NyYy9j ZGRsL2NvbnRyaWIvb3BlbnNvbGFyaXMvdG9vbHMvY3RmL2N2dC9kd2FyZi5jOjE5ODA6ODogZXJy b3I6IHVzZSBvZiB1bmRlY2xhcmVkDQppZGVudGlmaWVyICdEV19MQU5HX0MxMScgY2FzZSBEV19M QU5HX0MxMToNCiAgICAgICAgICAgICAgICAgICAgIF4NCi91c3Ivc3JjL2NkZGwvY29udHJpYi9v cGVuc29sYXJpcy90b29scy9jdGYvY3Z0L2R3YXJmLmM6MTk4Mjo4OiBlcnJvcjogdXNlIG9mIHVu ZGVjbGFyZWQNCmlkZW50aWZpZXIgJ0RXX0xBTkdfQ19wbHVzX3BsdXNfMDMnIGNhc2UgRFdfTEFO R19DX3BsdXNfcGx1c18wMzoNCiAgICAgICAgICAgICAgICAgICAgIF4NCi91c3Ivc3JjL2NkZGwv Y29udHJpYi9vcGVuc29sYXJpcy90b29scy9jdGYvY3Z0L2R3YXJmLmM6MTk4Mzo4OiBlcnJvcjog dXNlIG9mIHVuZGVjbGFyZWQNCmlkZW50aWZpZXIgJ0RXX0xBTkdfQ19wbHVzX3BsdXNfMTEnIGNh c2UgRFdfTEFOR19DX3BsdXNfcGx1c18xMToNCiAgICAgICAgICAgICAgICAgICAgIF4NCi91c3Iv c3JjL2NkZGwvY29udHJpYi9vcGVuc29sYXJpcy90b29scy9jdGYvY3Z0L2R3YXJmLmM6MTk4NDo4 OiBlcnJvcjogdXNlIG9mIHVuZGVjbGFyZWQNCmlkZW50aWZpZXIgJ0RXX0xBTkdfQ19wbHVzX3Bs dXNfMTQnIGNhc2UgRFdfTEFOR19DX3BsdXNfcGx1c18xNDoNCiAgICAgICAgICAgICAgICAgICAg IF4NCjQgZXJyb3JzIGdlbmVyYXRlZC4NCioqKiBbZHdhcmYub10gRXJyb3IgY29kZSAxDQoNCm1h a2VbM106IHN0b3BwZWQgaW4gL3Vzci9zcmMvY2RkbC91c3IuYmluL2N0ZmNvbnZlcnQNClsuLi5d DQoNCg0KDQpTaW5jZSBJIGRvIG5vdCBnZXQgYW55IGVtYWlsIGZyb20gZnJlZUJTRCdzIG1haWxp bmcgbGlzdCwgSSBjYW4gbm90IGV4YWN0bHkgdGVsbCB3aGF0DQpjb21taXQgY2F1c2VkIHRoZSBw cm9ibGVtLg0KDQpLaW5kIHJlZ2FyZHMsDQoNCm9oDQoNCg0KLSAtLSANCk8uIEhhcnRtYW5uDQoN CkljaCB3aWRlcnNwcmVjaGUgZGVyIE51dHp1bmcgb2RlciDDnGJlcm1pdHRsdW5nIG1laW5lciBE YXRlbiBmw7xyDQpXZXJiZXp3ZWNrZSBvZGVyIGbDvHIgZGllIE1hcmt0LSBvZGVyIE1laW51bmdz Zm9yc2NodW5nICjCpyAyOCBBYnMuIDQgQkRTRykuDQotLS0tLUJFR0lOIFBHUCBTSUdOQVRVUkUt LS0tLQ0KDQppTFVFQVJNS0FCMFdJUVFaVlpNekF0d0MyVC84NlRyUzUyOGZ5RmhZbEFVQ1d4djhU UUFLQ1JEUzUyOGZ5RmhZDQpsSkdCQWY5aE9PdVhwV1hjK1NUU284RDJXejRNM0EyWFgzR1U2Q0hH UC9RMXpEWEZSY3ZJRHZ0QWw0WjRKdTNUDQpsZ2p4TUpoQXhsYnhOTTRFeFMrRmhFSVBXOTR5QWZ3 Sm5raEx2SVo3OFJzYTROZ3FtWTdtYUNYMkJUWG1LR3BiDQpvQ1JURSsxTGRFVW1odUk4ZU12UW0y cFlYRnVsdE9hTitqU0o2eUcrSE52SzZYSWJEcDh3DQo9Vll1Yw0KLS0tLS1FTkQgUEdQIFNJR05B VFVSRS0tLS0tDQo= From owner-freebsd-current@freebsd.org Sat Jun 9 17:16:16 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 80B5E10118AC for ; Sat, 9 Jun 2018 17:16:16 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9CC8280FAD; Sat, 9 Jun 2018 12:36:57 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w59Catua019021; Sat, 9 Jun 2018 05:36:55 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w59CatKw019020; Sat, 9 Jun 2018 05:36:55 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201806091236.w59CatKw019020@pdx.rh.CN85.dnsmgr.net> Subject: Re: Is kern.sched.preempt_thresh=0 a sensible default? In-Reply-To: <20180608164033.5ff948f9@ernst.home> To: gljennjohn@gmail.com Date: Sat, 9 Jun 2018 05:36:55 -0700 (PDT) CC: Andriy Gapon , FreeBSD Current X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Jun 2018 17:16:16 -0000 > On Fri, 8 Jun 2018 17:18:43 +0300 > Andriy Gapon wrote: > > > On 08/06/2018 15:27, Gary Jennejohn wrote: > > > On Thu, 7 Jun 2018 20:14:10 +0300 > > > Andriy Gapon wrote: > > > > > >> On 03/05/2018 12:41, Andriy Gapon wrote: > > >>> I think that we need preemption policies that might not be expressible as one or > > >>> two numbers. A policy could be something like this: > > >>> - interrupt threads can preempt only threads from "lower" classes: real-time, > > >>> kernel, timeshare, idle; > > >>> - interrupt threads cannot preempt other interrupt threads > > >>> - real-time threads can preempt other real-time threads and threads from "lower" > > >>> classes: kernel, timeshare, idle > > >>> - kernel threads can preempt only threads from lower classes: timeshare, idle > > >>> - interactive timeshare threads can only preempt batch and idle threads > > >>> - batch threads can only preempt idle threads > > >> > > >> > > >> Here is a sketch of the idea: https://reviews.freebsd.org/D15693 > > >> > > > > > > What about SCHED_4BSD? Or is this just an example and you chose > > > SCHED_ULE for it? > > > > I haven't looked at SCHED_4BSD code at all. > > > > I hope you will eventually because that's what I use. I find its > scheduling of interactive processes much better than ULE. +1 Bruce Evans may have some info and/or changes here too. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Sat Jun 9 17:16:59 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9125E1011F80 for ; Sat, 9 Jun 2018 17:16:59 +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 08BE6756D7; Sat, 9 Jun 2018 15:43:17 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([78.55.173.237]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MHal6-1fQa0v0vk4-003OWh; Sat, 09 Jun 2018 17:38:13 +0200 Date: Sat, 9 Jun 2018 17:37:37 +0200 From: "O. Hartmann" To: Don Lewis Cc: "O. Hartmann" , FreeBSD CURRENT Subject: Re: rndc: connect failed: 127.0.0.1#953: permission denied Message-ID: <20180609173804.140e65aa@thor.intern.walstatt.dynvpn.de> In-Reply-To: References: <20180602091203.146839ea@thor.intern.walstatt.dynvpn.de> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 X-Provags-ID: V03:K1:skFpuLZpkulxsLvvNF2R0sQ2xyFz0WOttRJM6Wlk3n+/nTJMCPb e+OKXE9pdvAfqQKHlh5jYgG8W6oKweQPUXHyUo6grys2Cqnz7InZPO4H1WWqMz5kIqx9WZo ZgXpSmWLwW94t9IPHuXhffy/3tSHKkEJT/I6BOvyzrHjkBni+VFSC95eGgnxq7y2I1aH8MK 2PufLM8JCHiUXeMELHUug== X-UI-Out-Filterresults: notjunk:1;V01:K0:YT44TywZhhw=:GsFzrm7xVklfcGre9+vONg q5hyrTDrF6lz71uDYr+ixkLgymoKP0aPCHFJ3JrsOoYq81FUXjv+aequK/ym/aj0YBHQyrhYP h7T4muXRFyDIFTz77ENxzTmi8COfY4sbo4GoAdiUA176AQZVlQk+5i8VnHiLAWy5i56YEsNG9 +2/QQSRw+B8AjAdVjWmMWmycKzT68Gji+WfXdDtu5DGN1T50ROzvET0JYLJ4xXsCWmlBnoJc2 Wk2g3twmsiB0Z6IELGuW1sQveKjZl1ghsNrWzOKxG/9pHyVbCO1QpRPsE37rA3ZS7JxnqvCFY cFBgIJM1wkymS+QnTFw5zNpQTI24qa1iCM++br5kpOrYyM2Q0XqWWWP9xkuFGuotIkLYcT3tG aWHjGMZomBQgXvP/40yDDoJnoamw0CD9pcSsn4ugAI9wDzer/WK3tA66tqPpdtsf7RcvQlao3 Mce2/mKY1C5bxIDMxSXYrdseozhXbK00E5w0o49RlICMiZmdmd5TWRY5gx1Dq2iOriB0gf1Ad jhaYhlTBM9nnc/IKBrwG9I5zXS2EeBhHjBk392oYBCgyXHF4/Wz276sLzSVLEs7PMhjsYaga6 gjm+hyA/i/klH/NgtQlSaHA1DgRC1cxwUh3AP0dEc6ljfo7+l4DirjgB9BTEyJ2KThd4rL8li cokCIHHaVggFa47AfwzlSn+PGels3AjFPzwtgfvcJXRTnRsgXJwjjUrGNwmlGdRQlE7O5P9zw kz6vG4/OWPrCk5r3u5OVZo5LNTTl5TlYvFWh4vyHsCmQfUndSbpKatFbBBp2U4ZYhCxCx+wHT jKvrb3o X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Jun 2018 17:17:00 -0000 LS0tLS1CRUdJTiBQR1AgU0lHTkVEIE1FU1NBR0UtLS0tLQ0KSGFzaDogU0hBNTEyDQoNCkFtIFNh dCwgMiBKdW4gMjAxOCAxNjowNzo0OCAtMDcwMCAoUERUKQ0KRG9uIExld2lzIDx0cnVja21hbkBG cmVlQlNELm9yZz4gc2NocmllYjoNCg0KPiBPbiAgMiBKdW4sIE8uIEhhcnRtYW5uIHdyb3RlOg0K PiA+IC0tLS0tQkVHSU4gUEdQIFNJR05FRCBNRVNTQUdFLS0tLS0NCj4gPiBIYXNoOiBTSEE1MTIN Cj4gPiANCj4gPiBPbiBDVVJSRU5ULCBydW5uaW5nIG9uIGFuIEFQVSBhcyByb3V0ZXIvZmlyZXdh bGwgc2VydmljZSwgb3V0IG9mIHRoZSBibHVlIGFmdGVyIGFuDQo+ID4gdXBkYXRlIEkgcmVjZWl2 ZSB0aGlzIHdlaXJkIG1lc3NhZ2Ugd2hlbiB0cnlpbmcgdG8gcmVzdGFydCAibmFtZWQiIChCSU5E IDkuMTIsIGxhdGVzdA0KPiA+IGZyb20gdGhlIHBvcnRzKToNCj4gPiANCj4gPiBzZXJ2aWNlIG5h bWVkIHJlc3RhcnQNCj4gPiBybmRjOiBjb25uZWN0IGZhaWxlZDogMTI3LjAuMC4xIzk1MzoNCj4g PiBwZXJtaXNzaW9uIGRlbmllZCBybmRjIGZhaWxlZCwgdHJ5aW5nIGtpbGw6IFdhaXRpbmcgZm9y IFBJRFM6IDg3MS4NCj4gPiANCj4gPiBTZWFyY2hpbmcgdGhlIG5ldCByZXZlYWxzIHRoYXQgcG9z c2libGUgYWNjZXNzIHJpZ2h0cyBpc3N1ZXMgY291bGQgY2F1c2UgdGhpcyBwcm9ibGVtLA0KPiA+ IGJ1dCBJIGRvIG5vdCBzZWUgYW55LiBEb2VzIHNvbWVib2R5IHNlZSBzdWNoIHByb2JsZW1zLCB0 b28gYW5kIGRvZXMgaGF2ZSBhIHNvbHV0aW9uPyAgDQo+IA0KPiBEbyB5b3UgaGF2ZSBhIGZpcmV3 YWxsIHJ1bGUgdGhhdCBibG9ja3Mgc2VuZGluZyB0byBVRFAgcG9ydCA5NTMgb24NCj4gMTI3LjAu MC4xPw0KDQpIZWxsby4NCg0KU29ycnkgZm9yIHRoZSB2ZXJ5IGxhdGUgYW5zd2VyLg0KDQpZb3Vy IGhpbnQgd2FzIHJpZ2h0ISBJIGNoYW5nZWQgc29tZSBtaW5vciBjb25maXVyYXRpb24gcGFydHMg YW5kIGRpZG4ndCByZWFsaXNlIHRoYXQgSQ0KZHJvcHBlZCBhY2Nlc3MgZ3JhbnRlZCBmb3IgMTIu MC4wLjEgaW4gSVBGVy4NCg0KQWZ0ZXIgcmVpbnN0YWxsaW5nIGEgcHJvcHBlciBydWxlIGV2ZXJ5 dGhpbmcgd29ya2VkIGFzIGV4cGVjdGVkLg0KDQpUaGFua3MuDQoNCm9oDQoNCi0gLS0gDQpPLiBI YXJ0bWFubg0KDQpJY2ggd2lkZXJzcHJlY2hlIGRlciBOdXR6dW5nIG9kZXIgw5xiZXJtaXR0bHVu ZyBtZWluZXIgRGF0ZW4gZsO8cg0KV2VyYmV6d2Vja2Ugb2RlciBmw7xyIGRpZSBNYXJrdC0gb2Rl ciBNZWludW5nc2ZvcnNjaHVuZyAowqcgMjggQWJzLiA0IEJEU0cpLg0KLS0tLS1CRUdJTiBQR1Ag U0lHTkFUVVJFLS0tLS0NCg0KaUxVRUFSTUtBQjBXSVFRWlZaTXpBdHdDMlQvODZUclM1MjhmeUZo WWxBVUNXeHYwWEFBS0NSRFM1MjhmeUZoWQ0KbEFicEFnQ2d5ZkxxS3dBRXUwL01Tcm9SalFLYnhN NW91UzNkc2g1bjYzR3NxUEFFdmtOM0dSZWtNMzFjNkRVaA0KMVBVSXYxd05rZ3lLVENDNVMzNmhO QzA4S2tjOEFnQ0pzMDhEOW9ObUhTTDFEMnFPa25RYXVLWVFUcXhvTlFtMg0KSTluWHJ3WjgzZ0FZ c2dLdVMrYk5aUm91cG1CL2ZoUERJNUJHa3UrVEduRTJXNnJCNDdGaA0KPWxJU2UNCi0tLS0tRU5E IFBHUCBTSUdOQVRVUkUtLS0tLQ0K From owner-freebsd-current@freebsd.org Sat Jun 9 20:07:19 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6EE0E1014B78; Sat, 9 Jun 2018 20:07:19 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C575672D41; Sat, 9 Jun 2018 20:07:18 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w59K7PBs006088 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 9 Jun 2018 13:07:26 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w59K7PBE006087; Sat, 9 Jun 2018 13:07:25 -0700 (PDT) (envelope-from fbsd) Date: Sat, 9 Jun 2018 13:07:24 -0700 From: bob prohaska To: freebsd-arm@freebsd.org, freebsd-current@freebsd.org Cc: bob prohaska Subject: use of undeclared identifier 'DW_LANG_C11' Message-ID: <20180609200724.GA5728@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Jun 2018 20:07:19 -0000 I'm seeing persistent --- dwarf.o --- /usr/src/cddl/contrib/opensolaris/tools/ctf/cvt/dwarf.c:1980:8: error: use of undeclared identifier 'DW_LANG_C11' case DW_LANG_C11: ^ errors very early in buildworld attempts on 334890 I've tried "make clean" in /usr/src to no avail, is there something else to try, or should I just wait for a source update? Thanks for reading, bob prohaska From owner-freebsd-current@freebsd.org Sat Jun 9 20:13:14 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B466610161B4; Sat, 9 Jun 2018 20:13:14 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-it0-x22a.google.com (mail-it0-x22a.google.com [IPv6:2607:f8b0:4001:c0b::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4687C7349D; Sat, 9 Jun 2018 20:13:14 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-it0-x22a.google.com with SMTP id 188-v6so5565621ita.5; Sat, 09 Jun 2018 13:13:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=mJ606R5uACqUdT+gXv9itmjT+hG/pHdzjzCoBCXEQ2E=; b=aY2rOrEA5O98wdpdO/3p43DKUROfN1Zv1fD1UL9NywgmHT1H1fcyFm2AP15gz1AS/z BD2UJWwzzWTsFg9Hcgwem0fC4qNCeV7PfwNvKrqZTq3nmr0b4+azCPH63vWKQh5Ue5iN Ee5Ufk/UP30qDVbUYty7YWAoaDeklLm7R1c/UKszmeWAScs9EHN7W1ufJEqpFDzfxaZ4 qs5hK6rXsR7akjbgq6Xx0MnZVDwaNuzqKhocn/8TAR0HFb74RxmnM3K4FxLwCywriXxl eZuMOVMmhS6gesSJLvRWD73uZnwe5yB2tNR1N1jhCLsD1Ez3/RAB2kUjlretGYsK0yIc ApVg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=mJ606R5uACqUdT+gXv9itmjT+hG/pHdzjzCoBCXEQ2E=; b=Wbd6sIOKNtIvk3RclSkeCJnoagggoGwWL3OLLwTJbmFPrMtqt5EyD+u3wOs5pTvFB4 po2ewnGMfksXkTqH4c9xWLwhEdRhQzmguDRTDT8zObdzrn2jiJn68E+XpcTh7MC5Y0Ky GauSqZwcp8hkV4vBauC7NCGJNLCkUnqn6Qwuk6kGg1PhXhUHDfPYzDLDNzO8xMy2gonq NRBoy80jB8s5ITB7w2V+lII2nb6zFDnBdeaxS/GjzSQL0ZQ07nzK3sEwHAE1adnE/vLy 5Eqvl01mGaibnW3eATtlmQailQG8V9YDsqJ4LBcxO3iSr4R6dQtgOcY1DZoupG4QPdQ7 nAgA== X-Gm-Message-State: APt69E0hMEfJ6UnAFKJ3yTKug5iEXpAHY5fjZEVFrUtHhFU0BUuEm59z flUu3/tld4RcUc4q/DG5Spj+sVAi X-Google-Smtp-Source: ADUXVKIaSa3YXtuho+RNCJuUup8rNr6c9hy07AVWNoBt+Ab9M8ClDfsWYOUF6hBvELPQq/jx79K1Pg== X-Received: by 2002:a24:d80a:: with SMTP id b10-v6mr5892815itg.141.1528575193717; Sat, 09 Jun 2018 13:13:13 -0700 (PDT) Received: from pesky ([137.122.64.159]) by smtp.gmail.com with ESMTPSA id q203-v6sm2296526itb.32.2018.06.09.13.13.12 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 09 Jun 2018 13:13:12 -0700 (PDT) Sender: Mark Johnston Date: Sat, 9 Jun 2018 16:13:08 -0400 From: Mark Johnston To: bob prohaska Cc: freebsd-arm@freebsd.org, freebsd-current@freebsd.org Subject: Re: use of undeclared identifier 'DW_LANG_C11' Message-ID: <20180609201308.GA13305@pesky> References: <20180609200724.GA5728@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180609200724.GA5728@www.zefox.net> User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Jun 2018 20:13:14 -0000 On Sat, Jun 09, 2018 at 01:07:24PM -0700, bob prohaska wrote: > I'm seeing persistent > --- dwarf.o --- > /usr/src/cddl/contrib/opensolaris/tools/ctf/cvt/dwarf.c:1980:8: error: use of undeclared identifier 'DW_LANG_C11' > case DW_LANG_C11: > ^ > errors very early in buildworld attempts on 334890 > > I've tried "make clean" in /usr/src to no avail, is there something else > to try, or should I just wait for a source update? Please give r334892 a try. From owner-freebsd-current@freebsd.org Sat Jun 9 21:05:08 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C177B10004E5; Sat, 9 Jun 2018 21:05:08 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3A68975FE6; Sat, 9 Jun 2018 21:05:08 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w59L5LQm006245 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 9 Jun 2018 14:05:22 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w59L5L1n006244; Sat, 9 Jun 2018 14:05:21 -0700 (PDT) (envelope-from fbsd) Date: Sat, 9 Jun 2018 14:05:20 -0700 From: bob prohaska To: Mark Johnston Cc: freebsd-arm@freebsd.org, freebsd-current@freebsd.org Subject: Re: use of undeclared identifier 'DW_LANG_C11' Message-ID: <20180609210520.GB5728@www.zefox.net> References: <20180609200724.GA5728@www.zefox.net> <20180609201308.GA13305@pesky> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180609201308.GA13305@pesky> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Jun 2018 21:05:08 -0000 On Sat, Jun 09, 2018 at 04:13:08PM -0400, Mark Johnston wrote: > On Sat, Jun 09, 2018 at 01:07:24PM -0700, bob prohaska wrote: > > I'm seeing persistent > > --- dwarf.o --- > > /usr/src/cddl/contrib/opensolaris/tools/ctf/cvt/dwarf.c:1980:8: error: use of undeclared identifier 'DW_LANG_C11' > > case DW_LANG_C11: > > ^ > > errors very early in buildworld attempts on 334890 > > > > I've tried "make clean" in /usr/src to no avail, is there something else > > to try, or should I just wait for a source update? > > Please give r334892 a try. Thank you, bob prohaska From owner-freebsd-current@freebsd.org Sat Jun 9 21:49:37 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 069BD100A116 for ; Sat, 9 Jun 2018 21:49:37 +0000 (UTC) (envelope-from ler@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AE460790E7 for ; Sat, 9 Jun 2018 21:49:36 +0000 (UTC) (envelope-from ler@FreeBSD.org) Received: from ler-imac.local (unknown [IPv6:2600:1700:210:b18f:e948:4d52:fe47:94a5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: ler) by smtp.freebsd.org (Postfix) with ESMTPSA id 665492471F for ; Sat, 9 Jun 2018 21:49:36 +0000 (UTC) (envelope-from ler@FreeBSD.org) Date: Sat, 9 Jun 2018 16:49:35 -0500 From: Larry Rosenman To: freebsd-current@freebsd.org Subject: rack: m_copydata: negative offset panic Message-ID: <20180609214935.ksi5ekifgcbbjg7f@ler-imac.local> Mail-Followup-To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="o6iy5q26i4wicoe2" Content-Disposition: inline User-Agent: NeoMutt/20180512 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Jun 2018 21:49:37 -0000 --o6iy5q26i4wicoe2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Got the following panic. vmcore IS available: borg.lerctr.org dumped core - see /var/crash/vmcore.0 Sat Jun 9 16:46:17 CDT 2018 FreeBSD borg.lerctr.org 12.0-CURRENT FreeBSD 12.0-CURRENT #35 r334894: Sat = Jun 9 15:53:46 CDT 2018 root@borg.lerctr.org:/usr/obj/usr/src/amd64.am= d64/sys/VT-LER amd64 panic: m_copydata, negative off -1 GNU gdb (GDB) 8.1 [GDB v8.1 for FreeBSD] Copyright (C) 2018 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-portbld-freebsd12.0". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /boot/kernel/kernel...Reading symbols from /usr/lib/de= bug//boot/kernel/kernel.debug...done. done. Unread portion of the kernel message buffer: panic: m_copydata, negative off -1 cpuid =3D 20 time =3D 1528580395 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe344db49= 6d0 vpanic() at vpanic+0x1a3/frame 0xfffffe344db49730 doadump() at doadump/frame 0xfffffe344db497b0 m_copydata() at m_copydata+0x111/frame 0xfffffe344db497f0 rack_output() at rack_output+0x31fd/frame 0xfffffe344db49a60 tcp_hpts_thread() at tcp_hpts_thread+0x6ab/frame 0xfffffe344db49b20 intr_event_execute_handlers() at intr_event_execute_handlers+0x99/frame 0xf= ffffe344db49b60 ithread_loop() at ithread_loop+0xb7/frame 0xfffffe344db49bb0 fork_exit() at fork_exit+0x84/frame 0xfffffe344db49bf0 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe344db49bf0 --- trap 0, rip =3D 0, rsp =3D 0, rbp =3D 0 --- Uptime: 23m59s Dumping 6766 out of 130994 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%.= =2E91% __curthread () at ./machine/pcpu.h:231 231 __asm("movq %%gs:%1,%0" : "=3Dr" (td) (kgdb) #0 __curthread () at ./machine/pcpu.h:231 #1 doadump (textdump=3D1) at /usr/src/sys/kern/kern_shutdown.c:366 #2 0xffffffff80b844d2 in kern_reboot (howto=3D260) at /usr/src/sys/kern/kern_shutdown.c:446 #3 0xffffffff80b84ab3 in vpanic (fmt=3D, ap=3D0xfffffe344db= 49770) at /usr/src/sys/kern/kern_shutdown.c:863 #4 0xffffffff80b84820 in kassert_panic ( fmt=3D0xffffffff8125ae7e "m_copydata, negative off %d") at /usr/src/sys/kern/kern_shutdown.c:749 #5 0xffffffff80c107f1 in m_copydata (m=3D0xfffff801e3e5c400, off=3D-1, len= =3D15, cp=3D0xfffff801e3e686a4 "\336\300\255\336\336\300\255\336\336\300\255\3= 36\336\300\255\336\336\300\255\336\336\300\255\336\336\300\255\336\336\300\= 255\336\336\300\255\336\336\300\255\336\336\300\255\336\336\300\255\336\336= \300\255\336\336\300\255\336\336\300\255\336\336\300\255\336\336\300\255\33= 6\336\300\255\336\336\300\255\336\336\300\255\336\336\300\255\336\336\300\2= 55\336\336\300\255\336\336\300\255\336\336\300\255\336\336\300\255\336\336\= 300\255\336\336\300\255\336\336\300\255\336\336\300\255\336\336\300\255\336= \336\300\255\336\336\300\255\336\336\300\255\336\336\300\255\336\336\300\25= 5\336\336\300\255\336\336\300\255\336\336\300\255\336\336\300\255\336\336\3= 00\255\336\336\300\255\336\336\300\255\336\336\300\255\336\336\300\255\336\= 336\300\255\336\336\300\255\336\336\300\255\336\336\300\255\336\336\300\255= \336"...) at /usr/src/sys/kern/uipc_mbuf.c:582 #6 0xffffffff839a739d in rack_output (tp=3D) at /usr/src/sys/modules/tcp/rack/../../../netinet/tcp_stacks/rack.c:7922 #7 0xffffffff80da568b in tcp_hptsi (hpts=3D, ctick=3D0x59f) at /usr/src/sys/netinet/tcp_hpts.c:1615 #8 tcp_hpts_thread (ctx=3D) at /usr/src/sys/netinet/tcp_hpts.c:1808 #9 0xffffffff80b46369 in intr_event_execute_handlers (p=3D, ie=3D0xfffff80151f47d00) at /usr/src/sys/kern/kern_intr.c:1013 #10 0xffffffff80b46a57 in ithread_execute_handlers (ie=3D, p=3D) at /usr/src/sys/kern/kern_intr.c:1026 #11 ithread_loop (arg=3D0xfffff80151f47900) at /usr/src/sys/kern/kern_intr.c:1106 #12 0xffffffff80b43754 in fork_exit ( callout=3D0xffffffff80b469a0 , arg=3D0xfffff80151f47900, frame=3D0xfffffe344db49c00) at /usr/src/sys/kern/kern_fork.c:1039 #13 (kgdb) --=20 Larry Rosenman https://people.FreeBSD.org/~ler/ Phone: +1 214-642-9640 E-Mail: ler@FreeBSD.org US Mail: 5708 Sabbia Drive, Round Rock, TX 78665-2106 --o6iy5q26i4wicoe2 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQHBBAABCgCrFiEEHjgknedhWzvJgwVzaXyZsatIp30FAlscS28tFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3JnbGVyQEZyZWVCU0Qub3JnXxSAAAAAAC4AKGlz c3Vlci1mcHJAbm90YXRpb25zLm9wZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxRTM4 MjQ5REU3NjE1QjNCQzk4MzA1NzM2OTdDOTlCMUFCNDhBNzdEAAoJEGl8mbGrSKd9 4ssH/jjLwLwxwjlZegcXADRqmIUTtNFNbWySRVLAbjcXqfH4eMDjCFdL5vMyytnU S/UovawUNKdHLJl8mSrsgXMMlirIDJy1hGf2O4i8NjoT7N+OIYPJ6HbJ7QuvbCZn TYsTHg8gXkGylXsJ1jwcMLZKeJhfYXVyy5zF5ecMFi5FVB7b2yrDqUlJuJpQl0JQ fznGXejmi5GEkfFIDDFby2fvsL85wXL+yZwJS2EAX297pCsHZL6fjQEmTCrKh1ob Xfqx2stfhyIIcj50atN/NJZd8hnZ3QfhiQCdcipFBYiqkg+ho+SDti/yxaiAs+xc 4DYmsSgPAPIKmBWjpK0BO0y5HXQ= =yCjI -----END PGP SIGNATURE----- --o6iy5q26i4wicoe2--