From owner-freebsd-arm@freebsd.org Sun Apr 16 00:37:51 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BD176D2A640 for ; Sun, 16 Apr 2017 00:37:51 +0000 (UTC) (envelope-from otacilio.neto@bsd.com.br) Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d: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 8241A1F11 for ; Sun, 16 Apr 2017 00:37:51 +0000 (UTC) (envelope-from otacilio.neto@bsd.com.br) Received: by mail-qk0-x233.google.com with SMTP id d131so86558101qkc.3 for ; Sat, 15 Apr 2017 17:37:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsd.com.br; s=capeta; h=to:from:subject:message-id:date:user-agent:mime-version; bh=XBZ+yRxkmNs8eVniX0kB0fL0Lwq4rF+3d+n63VOC30M=; b=aeFwyw9jSmYahLI/YsSdI52H/Qptb7q4KEwiEcfowkSYA3PeYSLCuwgFyjP0TPkedJ zKUjm4TlsN2CH8rq1CW9LsZPJxyOk+2eRAhaUCTz1Q3bJPQgRvuHvDcTgcomYb93B2+Q vYz6hg78+jM4uu85nlskyRA0lRn3Lk8gRQgvM= 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:message-id:date:user-agent :mime-version; bh=XBZ+yRxkmNs8eVniX0kB0fL0Lwq4rF+3d+n63VOC30M=; b=Vvr4qlR/jTPZMVxq39RWBetYhigbqtj6DBKR4DQihZYiJmB08zS2+hIcDvrieMuirN gGw2w9x3P/XxX+iPzmre2WfW0JGmy3HJ+o5LSW+9OM+GwHZ1y1ydLiV34Bbent8dXgEP sf560Gt2rkFMhkqwyz5M6dTSTUryZzynCLEQTNgOqstyA/ybkN4PHnnTjNuirHIxTEoC DRV2fpeB5yDBJ4ZV9dxGkZCS+not8IoJAStWqBWCUNtbvXBhwAVheJ/kkC9DapmCt7Hm XyJBdInIjfAH3uqprhv8+hQ/qgFmgP1zomRa9aBnJDxYrQayD+y6NIkwRAvemrm93Cwf j+8g== X-Gm-Message-State: AN3rC/712lwTxQoPoL607BPPLozMqvBbpAJ18Xv4EAhmiFvllLgIs3pK RA0pwDK8D2iUy2vF X-Received: by 10.55.72.17 with SMTP id v17mr3927676qka.208.1492303070195; Sat, 15 Apr 2017 17:37:50 -0700 (PDT) Received: from [192.168.0.11] ([177.89.67.185]) by smtp.googlemail.com with ESMTPSA id i19sm4142237qte.31.2017.04.15.17.37.48 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 15 Apr 2017 17:37:49 -0700 (PDT) To: "freebsd-arm@freebsd.org" From: =?UTF-8?B?T3RhY8OtbGlv?= Subject: What image is available for raspberry pi 3? Message-ID: Date: Sat, 15 Apr 2017 21:37:03 -0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Apr 2017 00:37:51 -0000 Hi The image FreeBSD-12.0-CURRENT-arm-armv6-RPI-B-20170413-r316750 is for that model of raspberry PI? 2 or 3? []'s -Otacilio From owner-freebsd-arm@freebsd.org Sun Apr 16 01:11:33 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3C4E6D3549E for ; Sun, 16 Apr 2017 01:11:33 +0000 (UTC) (envelope-from otacilio.neto@bsd.com.br) Received: from mail-qk0-x22b.google.com (mail-qk0-x22b.google.com [IPv6:2607:f8b0:400d:c09::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 F2D0017B2 for ; Sun, 16 Apr 2017 01:11:32 +0000 (UTC) (envelope-from otacilio.neto@bsd.com.br) Received: by mail-qk0-x22b.google.com with SMTP id h67so86914975qke.0 for ; Sat, 15 Apr 2017 18:11:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsd.com.br; s=capeta; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding; bh=oTm3Wg/WCn0oaVXXzDEoVxqVgBYCuE1k5SyN/InyhmA=; b=MhrzsamcEpcDRBNXnkcCqVrH5kevqBzqUDWlrb/R4GdzOBxRtAJeWBuojvKqJWbljC k1/3n0SgjeO4HwimzeuwbJSS2BkygjRVHGD5hXoaw2CaSo+kDWL77tIvE3ILOwG5ymc2 XZwb6i5Ni9uocWZLcqMwEOk3uaha9uOsvYp7g= 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:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=oTm3Wg/WCn0oaVXXzDEoVxqVgBYCuE1k5SyN/InyhmA=; b=T+73wIsZ69UUYcKbEy6SHuq43J+Oi5O1F9bXp7GvrBs5QnIrwr5oOE6W985QzhfS11 RVg85Ttof1uUTXqfFkjcWxTnwm8ojKlKmRttgzUqdzVN9+X5DVLAzO3fEKG4xZNFHRJm cqzUPgSH5DToXNk5+kM+d9K1H/S551cBE58cfcXnFW+gn8o9v+JirhS2Uh06WbzqPYrT g5nU1H0JJZGGgBHKp4kBuMh/IhvZU/sOrpktmu2Gmcgug0+6/ytaxywYJuE2mm/rYmnm gA6IvHyFs9iG3/NhI3gNhRyYA0fOma1+2qr2XfdIIrDWlXjcR79thP7B0xMaBrslAIXo t2yg== X-Gm-Message-State: AN3rC/59Q8E8oLkBVaaL7/Zj/SGDkhC5VxCD1lky1nuiHqdf9c7TW832 Y/2AJ/Jo4OsHR6Bh X-Received: by 10.55.76.12 with SMTP id z12mr3953391qka.205.1492305091950; Sat, 15 Apr 2017 18:11:31 -0700 (PDT) Received: from ?IPv6:2804:54:19ef:cc00:98a:7792:dddd:b13d? ([2804:54:19ef:cc00:98a:7792:dddd:b13d]) by smtp.googlemail.com with ESMTPSA id z29sm4168421qtz.67.2017.04.15.18.11.30 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 15 Apr 2017 18:11:31 -0700 (PDT) To: "freebsd-arm@freebsd.org" From: =?UTF-8?B?T3RhY8OtbGlv?= Subject: RPI3 and BBB broken Message-ID: Date: Sat, 15 Apr 2017 22:11:06 -0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Apr 2017 01:11:33 -0000 The images from HEAD r316755 for RPI3 and r316750 for beaglebone black are not working. The image for beaglebone downloaded from ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/arm/armv6/ISO-IMAGES/12.0/ is stucked during boot with this message: Found U-Boot device: disk Probing all disk devices... Checking unit=0 slice= partition=...disk0: write attempt, operation not supported! Checking unit=1 slice= partition=...disk1: write attempt, operation not supported! Checking unit=2 slice= partition=... Checking unit=3 slice= partition=... Checking unit=4 slice= partition=... Checking unit=5 slice= partition=... Found U-Boot device: net Booting from net0: cpsw Waiting for PHY auto negotiation to complete......... TIMEOUT ! And the image for RPI3 (316755 compiled locally) is stucked on boot with this message: vm_fault: pager read error, pid 1 (init) From owner-freebsd-arm@freebsd.org Sun Apr 16 01:50:32 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9D422D35265 for ; Sun, 16 Apr 2017 01:50:32 +0000 (UTC) (envelope-from jungleboogie0@gmail.com) Received: from mail-pf0-x22f.google.com (mail-pf0-x22f.google.com [IPv6:2607:f8b0:400e:c00::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6ED561A64 for ; Sun, 16 Apr 2017 01:50:32 +0000 (UTC) (envelope-from jungleboogie0@gmail.com) Received: by mail-pf0-x22f.google.com with SMTP id 194so14112089pfv.3 for ; Sat, 15 Apr 2017 18:50:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding; bh=YivXyz3is50XfaCCDv2Uj+X41R6N8c24FM5E/5oxTjQ=; b=qZ2ty5JqTaIRTJ7rCdeA4l1MeS0PTMHg61cuRsCNrO7/oAoXSseDLdKDeIRnHvSVct sa+C5+VmRWHA12d/Imf8byAuavgpykThy3DMFYb7FcYHYnao18ASoy2cfotsCZjv+be8 svKj5bYyEn+Wy2cx/MD8WIkkselDvPTHo/yKaUbCZjSJN+jHRIO9zzDOzwUyBdSLkLh2 jsVob0vCGQ9rrAqPB62jNmvHQZIveNH/q7aisuhpRsOfm+J0O3Q/D7nvvxw029tMvmeS gD+zvtKaTU4dr+368+tJe/C0QFevd6gUvL7WXdYlJsjUJZEukpg8Vza0PRSqdNAlsKlI BLyw== 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:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=YivXyz3is50XfaCCDv2Uj+X41R6N8c24FM5E/5oxTjQ=; b=N80qF6kZlK2gNY1cQYrs3tfLQkhX/tVbcdt7+bAGKzBUrp6aUFcJPvJ/OZ2AFE/5Nq 4GwbcBKddK+iAtOzGq1Hc/VTGMgXdKAo/OVMO/xCN8NF6Kzw1qq9TAUTXDVfphwtmcKj FBV0yzKpG/8zA4bcus8sPQANu8eqaYjhUwAEPY1lru4UKORf86N3hcR7GvmLqFt7L6+W XuGFZDdZRA0GSBkPJXgHFKaf4F/+li9VPQ8PQWYfIf3Bi9cP9RwQdxxxkBwQ4iHZwvUE 8IGrgnF69r+rRZZxCFOhdE9iloWf2iH/eYKdZUBRC1HHjZ3bknlZ9+MLuOINJ3wnrOVi FaPw== X-Gm-Message-State: AN3rC/47+jhaZwXclJLbBCJY+TNhh+4Lt9q9+FZbeTrkHK0R0iRiXDBA /T4iUV6dus9qYPjJQHI= X-Received: by 10.99.55.75 with SMTP id g11mr5080927pgn.224.1492307431815; Sat, 15 Apr 2017 18:50:31 -0700 (PDT) Received: from [192.168.88.254] (ip70-173-249-54.lv.lv.cox.net. [70.173.249.54]) by smtp.gmail.com with ESMTPSA id a77sm10407864pfj.1.2017.04.15.18.50.30 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 15 Apr 2017 18:50:31 -0700 (PDT) To: freebsd-arm@freebsd.org From: jungle boogie Subject: beaglebone black: MMC partition switch failed Message-ID: <5bac0dbc-6d2b-c757-0cd3-babbd048cfd2@gmail.com> Date: Sat, 15 Apr 2017 18:50:29 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Apr 2017 01:50:32 -0000 Hi All, It's been awhile since I've been able to run FreeBSD on my BBB. It was failing somewhere, but I didn't have good serial cable to see what was happening. Using the latest freebsd head image: FreeBSD-12.0-CURRENT-arm-armv6-BEAGLEBONE-20170413-r316750.img I'm writing it to my microSD card: sudo dd if=FreeBSD-12.0-CURRENT-arm-armv6-BEAGLEBONE-20170413-r316750.img of=/dev/sdf bs=8M 128+0 records in 128+0 records out 1073741824 bytes (1.1 GB, 1.0 GiB) copied, 1.01005 s, 1.1 GB/s Putting it in the BB and holding s2 for three seconds as mentioned in the FBSD Journal article[0]. Upon doing so, I see this: U-Boot SPL 2017.01-rc3 (Apr 13 2017 - 12:30:59) Trying to boot from MMC1** First descriptor is NOT a primary desc on 0:1 ** MMC partition switch failed *** Warning - MMC partition switch failed, using default environment ** Partition 1 not valid on device 0 ** spl_register_fat_device: fat register err - -1 spl_load_image_fat: error reading image u-boot.img, err - -1 MMC partition switch failed *** Warning - MMC partition switch failed, using default environment spl: no partition table found SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ### I can boot u-boot and see the version: U-Boot# version U-Boot 2013.04-dirty (Jul 10 2013 - 14:02:53) arm-angstrom-linux-gnueabi-gcc (Linaro GCC 4.7-2013.02-01) 4.7.3 20130205 (prerelease) GNU ld (GNU Binutils) 2.22 I can boot without an SD card and see armstrong. I just can't boot from the SD card. Do I need to upgrade/downgrade u-boot to fix this? ANY help will be appreciated! I want FreeBSD running again on my BBB. Thanks, JB [0] https://www.freebsdfoundation.org/wp-content/uploads/2015/12/vol1_no1_beaglebone_dkr.pdf From owner-freebsd-arm@freebsd.org Sun Apr 16 02:04:26 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 157DAD35BD4 for ; Sun, 16 Apr 2017 02:04:26 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: from mail-qt0-x22e.google.com (mail-qt0-x22e.google.com [IPv6:2607:f8b0:400d:c0d::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 BDDB7620 for ; Sun, 16 Apr 2017 02:04:25 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: by mail-qt0-x22e.google.com with SMTP id y33so484789qta.2 for ; Sat, 15 Apr 2017 19:04:25 -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:references:mime-version :content-disposition:in-reply-to:user-agent; bh=0b68YlxV8HB2z4Xbg8S7KeUNMlTRtImO8TKxQiFJ0m4=; b=cWSJE6DVry/4IeVSdDWMCXkhut4Y4FSqkWCGXOSJShzjKihyeP6I7AznFByTQViHgk 0JxGDNbYgo3nci+JxnGL1nIXZf6Ph71FzBY08T+qSr8MzdU3ObrOPmbY0txk3TTGgbRm 6LWgxfPkQLPm3+667wbUn3AgHUorL0RC1KZm1SFsLr+QIpprZfQ1e8GdE9x103AUIW/f F4gFgYT3J0xP/Q1n+WAnRqMFprCcFXtTrVfoklXkveDGe5DuoXhs9vnDtwUUXBrwGy7m eYtKi0uEfm3/N3WQf8O11LtHa2r3W5Pcvw7yp6LYwC0lHmqNr9jqmstIRd15CRov5AlD J6Dw== 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:references :mime-version:content-disposition:in-reply-to:user-agent; bh=0b68YlxV8HB2z4Xbg8S7KeUNMlTRtImO8TKxQiFJ0m4=; b=PQ3t2HjWCB98iymebHE9r5ZJ8xhS4wi4tXHYeU0tAvwL70iHjvE9+rSHbVNjGiX9uz OEbGAgQB/9CmwHR/Akn0eABR4vo8iuaft9HCP0ylyM84M8WJf5sceUE7qVi0ONzJOK8e xPNGyCf+1Sl9vuUOxk9+zErh1EjSNMOwZD4sTuMhGZQqq87MZGG2gEmDcSK+AOibVDDw YRlWGDlxWM27U7E/yYhB8ZFIZ/i6DWoAuYKYLv+2RsBUh9GA4YUCcnTA4XRAQY+qBAkX hFEmoY3OJIrYP44OZ9YyYSIR1I3Bm+sjTIwkSe/gpjH0LTviSyqb9ykM2NSBkgAvDnif kfmA== X-Gm-Message-State: AN3rC/7AEytrB/AYaIWMUozyZ3TOQMrM/cxdxDff0/kSu50xyfHva59u EdsBXkLTjmxQjtVu+4yFkw== X-Received: by 10.237.57.71 with SMTP id l65mr3657005qte.101.1492308264784; Sat, 15 Apr 2017 19:04:24 -0700 (PDT) Received: from mutt-hbsd (pool-100-16-218-40.bltmmd.fios.verizon.net. [100.16.218.40]) by smtp.gmail.com with ESMTPSA id f30sm4273232qte.11.2017.04.15.19.04.23 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sat, 15 Apr 2017 19:04:24 -0700 (PDT) Date: Sat, 15 Apr 2017 22:04:22 -0400 From: Shawn Webb To: Otac??lio Cc: "freebsd-arm@freebsd.org" Subject: Re: RPI3 and BBB broken Message-ID: <20170416020422.otw3g4rkpsb7cvom@mutt-hbsd> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="bfci2mwq57m5mlgv" Content-Disposition: inline In-Reply-To: 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/20170206 (1.7.2) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Apr 2017 02:04:26 -0000 --bfci2mwq57m5mlgv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Apr 15, 2017 at 10:11:06PM -0300, Otac??lio wrote: > The images from HEAD r316755 for RPI3 and r316750 for beaglebone black = are > not working. The image for beaglebone downloaded from > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/arm/armv6/ISO-IMAGES/12.0/ is > stucked during boot with this message: >=20 > Found U-Boot device: disk > Probing all disk devices... > Checking unit=3D0 slice=3D partition=3D...disk0: write atte= mpt, > operation not supported! >=20 > Checking unit=3D1 slice=3D partition=3D...disk1: write atte= mpt, > operation not supported! >=20 > Checking unit=3D2 slice=3D partition=3D... > Checking unit=3D3 slice=3D partition=3D... > Checking unit=3D4 slice=3D partition=3D... > Checking unit=3D5 slice=3D partition=3D... > Found U-Boot device: net > Booting from net0: > cpsw Waiting for PHY auto negotiation to complete......... TIMEOUT ! >=20 >=20 > And the image for RPI3 (316755 compiled locally) is stucked on boot with > this message: >=20 > vm_fault: pager read error, pid 1 (init) Hey Otacilio, The image of HardenedBSD I built earlier today works great on the RPI3: https://hardenedbsd.org/~shawn/rpi3/2017-04-15/HardenedBSD-RaspberryPi3-aar= ch64-12.0-HARDENEDBSD-8c2cfb341370.img.xz Thanks, --=20 Shawn Webb Cofounder and Security Engineer HardenedBSD GPG Key ID: 0x6A84658F52456EEE GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE --bfci2mwq57m5mlgv Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEKrq2ve9q9Ia+iT2eaoRlj1JFbu4FAljy0SQACgkQaoRlj1JF bu6dWg//boDhRyZISm6QjtMcy7tRNB+KGOBehEFGcKiq5KxyaQJmKE8OyvwjycYh xGt6QELqdEt4TywY8kLfRYEErokDmPkimPB9y2EnhtlHgQT9M3cSv858H/FgokAg xDr9Gyv0TIHPH3hYrVNiFHJBW7TE6om3E+SqFXyhsxv04PegbDUhOX8k1rTs0HcL Fr/3eOIUFqKrYhSUW6ggCszyEI63wtuPSceCOmsfYM0+rSjEp+OAj3R5R6LEwg7g hXlpQAblMfSk82iOdKibMWs3tLHyCdeB3soDhowdqua5Che50Bw88xHkq9k4C4Ko OrmtV03e9bz89casxJW4xEX2VLh/wNT5A7np5SycmJzQjFi1R/81ko877wRB1P6g 869YNukjDR3hKCyK+f7At888jaBBHQTAbr9hu4106Lm0N63wK0fgRsPPVEpA+Rf7 FCXF0GJCup7vplB6H75W5ypHn5OJmgrrjvBrJW1d7AGC+ZTYVKNo61O9Kozp4peI l+JrUM9SfBFIDdDLT3BV1E0LFsJiAPlT2SK5AlqleumlRjn4xKlE8CDVfNIIJFfJ n51nqoZuvjpG4EhirBNE8L5XGt0AeGq5zlDZrhqnBvOavjYIcwNHkD+/TdyZfNTA QyTk4HxNnWAFJRJABECS53khdANNvbt+u22U6G1Fy6F6y6b30dI= =hmSh -----END PGP SIGNATURE----- --bfci2mwq57m5mlgv-- From owner-freebsd-arm@freebsd.org Sun Apr 16 02:09:41 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 30D2DD35E1C for ; Sun, 16 Apr 2017 02:09:41 +0000 (UTC) (envelope-from jungleboogie0@gmail.com) Received: from mail-yb0-x229.google.com (mail-yb0-x229.google.com [IPv6:2607:f8b0:4002:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E37B4811 for ; Sun, 16 Apr 2017 02:09:40 +0000 (UTC) (envelope-from jungleboogie0@gmail.com) Received: by mail-yb0-x229.google.com with SMTP id m133so24751820ybb.1 for ; Sat, 15 Apr 2017 19:09:40 -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=8FOfyMy8jtSjcjMkzm+7NxanwyHAjYX50GP1gjTmTcQ=; b=qQbvnFECHjpb4tfHChb1X7OKpaNBi2lpivphwCoVE953J1T0ZO0P4N09J9L3wIaI3f hnGMtFbxPIgZZoyZ8sPXh/jnyjQTg5xeWIkJxmxBQS1zLmPwCGU9VfyRBDg29BP0v3Cq ZYu+nISGAzNjamVqWwAMArEiYizlAxy6+7VxA8L0g6A0RZ0bQbPoCt4aNKt3Kq9W+8Tt X0E6EAApyyxYrDsPPLTO2kJEFBngHyddAnjrn14gy6cE3W15lJ8EH8VrkUQqw/WsdZQf O8QOqLKZwEbI6k6nq1z19n1LTNVUiPWtv8h3JjQMkaO7mdbpyD/BiG62zDu9bRfslIMq alDQ== 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=8FOfyMy8jtSjcjMkzm+7NxanwyHAjYX50GP1gjTmTcQ=; b=atwIHbMWX+FVO+ng6Mrwx3aMTgKwoVwaG+LUiJ0LY2OsdfBhyhqPJPNAk3Jw9Zv2Jr qob9ma6o1MV0eOe9rVPqq2ddoSnu9COfJoSKuVTgL53PHnRPeCXfl+9yk2xBFczzZQ5D WIG1l1ldoq3A54DjMPHwyAvjT/lcY8++4sEfE579jeIVMH8gOpjqmHEvmx8Sl3igj7sa B0OsMwh5CTFnBjJbXGYDnGhEECZk0sChv21hI2tBTJBA/5Zh4nFsq9fhwnK3n9v9BK4+ TG/g6tfjaUgXJIAJrc0MIg1zSkydfJpU71rr39uba7xn1qaAQReR5uwL2a8PvDE8905P O7WQ== X-Gm-Message-State: AN3rC/7orIYwiEja1kLAGyJHQ3B2FL2japSXxceEnqbNPahZAjrPU+sJ n+3uKIVezF/DhomKVO5urZlgf3ODzA== X-Received: by 10.37.161.38 with SMTP id z35mr11327893ybh.134.1492308580134; Sat, 15 Apr 2017 19:09:40 -0700 (PDT) MIME-Version: 1.0 Received: by 10.37.193.70 with HTTP; Sat, 15 Apr 2017 19:09:39 -0700 (PDT) Received: by 10.37.193.70 with HTTP; Sat, 15 Apr 2017 19:09:39 -0700 (PDT) In-Reply-To: References: From: jungle Boogie Date: Sat, 15 Apr 2017 19:09:39 -0700 Message-ID: Subject: Re: RPI3 and BBB broken To: =?UTF-8?B?T3RhY8OtbGlv?= Cc: freebsd-arm@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Apr 2017 02:09:41 -0000 On 15 Apr 2017 18:12, "Otac=C3=ADlio" wrote: > > The images from HEAD r316755 for RPI3 and r316750 for beaglebone black are not working. The image for beaglebone downloaded from ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/arm/armv6/ISO-IMAGES/12.0/ is stucked during boot with this message: Just curious, what's your uboot version on the BBB? From owner-freebsd-arm@freebsd.org Sun Apr 16 03:17:56 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 61E6ED4006E for ; Sun, 16 Apr 2017 03:17:56 +0000 (UTC) (envelope-from otacilio.neto@bsd.com.br) Received: from mail-qt0-x231.google.com (mail-qt0-x231.google.com [IPv6:2607:f8b0:400d:c0d::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 214C2AAD for ; Sun, 16 Apr 2017 03:17:56 +0000 (UTC) (envelope-from otacilio.neto@bsd.com.br) Received: by mail-qt0-x231.google.com with SMTP id g60so17833267qtd.3 for ; Sat, 15 Apr 2017 20:17:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsd.com.br; s=capeta; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=rP7nnzYx05mOUTbumB9/vTGLErpBzrNIyKn3fzb+ZMg=; b=KsSL1yDp/X1vazfBSSTVWna0/W4vQujaONnU+QBs09iDzF0W0+PAozl+34T3icXwIq QhZ7/p7y97xhDIQlahBc83hHGii2qSJmsMsET8ua3ZBwkTmtzi8UFX0CuNKHpJfkIMiu TL6gDsj/J/kJ/0RG1pxh4JFHc90Hy2ys1Z1c0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=rP7nnzYx05mOUTbumB9/vTGLErpBzrNIyKn3fzb+ZMg=; b=kGyx+1yHJKlCcOnZS9WEKp1ShS+4qvsl4XPYXqCubmRtRUqfV0mMGfkHz+LRemkEjY M0H3AMY+QKfEGd6JZLbD6v6KQbDB/o8vVLjd8SZR3vmsRR/NlS0plu2JMryZKqZwk5Xu usnwVBNQq67XmeziZ65vGoSq6dkU4QB9NM5C33amfJIIRzKJ5O3L59GAZrZtKLtw009g /jGsGcF+l+kCWjy1E5nvZeegKM/kuKDWVoYRhJHUy6fMlK70pcShACvlJgLM5Mhs9htW Sg6eXJC1ie3UBE+bNNlpnCpCEV/A5I7kPsVm899CUGSnbNOQIQrqafhl4vyt0DNhEH3k OFYA== X-Gm-Message-State: AN3rC/7zQB5QwPx+Vs+sHxzjrTkV5jec8pK1VFDAJr3YSF4uug/BEn+/ ghaL16vCzrNgLg== X-Received: by 10.200.40.72 with SMTP id 8mr3851282qtr.204.1492312675211; Sat, 15 Apr 2017 20:17:55 -0700 (PDT) Received: from [192.168.0.11] ([177.89.67.185]) by smtp.googlemail.com with ESMTPSA id r30sm4331405qtc.66.2017.04.15.20.17.53 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 15 Apr 2017 20:17:54 -0700 (PDT) Subject: Re: RPI3 and BBB broken To: jungle Boogie References: Cc: freebsd-arm@freebsd.org From: =?UTF-8?B?T3RhY8OtbGlv?= Message-ID: Date: Sun, 16 Apr 2017 00:17:08 -0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Apr 2017 03:17:56 -0000 Em 15/04/2017 23:09, jungle Boogie escreveu: > > On 15 Apr 2017 18:12, "OtacĂ­lio" > wrote: > > > > The images from HEAD r316755 for RPI3 and r316750 for beaglebone > black are not working. The image for beaglebone downloaded from > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/arm/armv6/ISO-IMAGES/12.0/ > is stucked during boot with this message: > > Just curious, what's your uboot version on the BBB? > I have an image that I compiled in the beaglebone itself and *works fine*. This image uses this version: U-Boot 2017.01-rc3 (Mar 23 2017 - 22:35:37 +0000) arm-none-eabi-gcc (FreeBSD Ports Collection for armnoneeabi) 6.3.0 GNU ld (GNU Binutils) 2.28 And FreeBSD is: FreeBSD beaglebone 12.0-CURRENT FreeBSD 12.0-CURRENT #1 r316378M: Thu Apr 6 01:08:51 -03 2017 ota@beaglebone:/mnt/obj/mnt/src/sys/BEAGLEBONE arm ================================================================================ RPI3 locally compiled (using amd64) and that do *not work* is this (FreeBSD version HEAD r316755): U-Boot 2017.01 (Feb 04 2017 - 23:20:27 -0300) aarch64-none-elf-gcc (FreeBSD Ports Collection for aarch64noneelf) 6.3.0 GNU ld (GNU Binutils) 2.27 ================================================================================ The images that I have downloaded and *not work* (r316750) uses this versions (BBB): U-Boot 2017.01-rc3 (Apr 13 2017 - 12:30:59 +0000) arm-none-eabi-gcc (FreeBSD Ports Collection for armnoneeabi) 6.3.0 GNU ld (GNU Binutils) 2.28 The last version that I download and works for BBB was 316508. I have faced the problem of page fault a time ago, but I was think that this was related with a version mismatch on the build machine but now I did a rebuild on build machine also and the problem stay there. git pull says that I using the last version of crouchet also. []'s -Otacilio From owner-freebsd-arm@freebsd.org Sun Apr 16 06:30:14 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6F5BBD40A03 for ; Sun, 16 Apr 2017 06:30:14 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-41.reflexion.net [208.70.210.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 20C20B3C for ; Sun, 16 Apr 2017 06:30:12 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 26634 invoked from network); 16 Apr 2017 06:31:08 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 16 Apr 2017 06:31:08 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.40.0) with SMTP; Sun, 16 Apr 2017 02:30:06 -0400 (EDT) Received: (qmail 4606 invoked from network); 16 Apr 2017 06:30:05 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 16 Apr 2017 06:30:05 -0000 Received: from [192.168.1.106] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 30A94EC81B0; Sat, 15 Apr 2017 23:30:05 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: lang/gcc6-aux for head beyond __nonnull related issues: vm_ooffset_t and vm_pindex_t related changes (and more) From: Mark Millard In-Reply-To: <20170415093010.GA4104@lonesome.com> Date: Sat, 15 Apr 2017 23:30:04 -0700 Cc: "Ngie Cooper (yaneurabeya)" , Gerald Pfeifer , FreeBSD Ports , FreeBSD Current , FreeBSD Toolchain , freebsd-arm , Pedro Giffuni , ericturgeon.bsd@gmail.com Content-Transfer-Encoding: quoted-printable Message-Id: References: <9758023E-1526-41F9-9416-6AC8AD3201B5@dsl-only.net> <7606F976-20B7-4FB8-BE80-C27773F5529A@gmail.com> <20170415093010.GA4104@lonesome.com> To: Mark Linimon X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Apr 2017 06:30:14 -0000 On 2017-Apr-15, at 2:30 AM, Mark Linimon = wrote: > On Fri, Apr 14, 2017 at 08:27:29PM -0700, Mark Millard wrote: >> I've seen material quoted from a exp-run that reported >> that about 54(?) ports were then blocked by lang/gcc6-aux >> not building. >=20 > Although the first is an older run (the last complete run IIUC), there > were 50 and 51 respectively as of: >=20 > = http://thunderx1.nyi.freebsd.org/build.html?mastername=3D110arm64-default&= build=3D423029 > = http://beefy8.nyi.freebsd.org/build.html?mastername=3Dhead-armv6-default&b= uild=3Dp437390_s316341 >=20 > I think you're fairly deep into unexplored territory here. Looks like it. I tried an amd64 context (that was built using WITH_LLD_IS_LD=3D in case that matters) and ports-mgmt/synth's indirect build of lang/gcc6-aux quickly stopped for: configure:4439: = /usr/obj/portswork/usr/ports/lang/gcc6-aux/work/bootstrap/bin/gcc -O2 = -pipe -g -fstack-protector -fno-strict-aliasing -I/usr/local/include = -L/usr/local/lib -fstack-protector conftest.c >&5 /usr/bin/ld: error: unable to find library -lssp_nonshared /usr/bin/ld: error: unable to find library -lc collect2: error: ld returned 1 exit status configure:4443: $? =3D 1 configure:4480: result:=20 configure: failed program was: | /* confdefs.h */ | #define PACKAGE_NAME "" | #define PACKAGE_TARNAME "" | #define PACKAGE_VERSION "" | #define PACKAGE_STRING "" | #define PACKAGE_BUGREPORT "" | #define PACKAGE_URL "" | /* end confdefs.h. */ |=20 | int | main () | { |=20 | ; | return 0; | } configure:4486: error: in = `/usr/obj/portswork/usr/ports/lang/gcc6-aux/work/build': configure:4490: error: C compiler cannot create executables This happened even if I checked off in gcc6-aux's config to do a bootstrap. Even amd64 has build problems (at least for use of the modern/experimental ld). =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Sun Apr 16 08:36:12 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5A999D3E7BB for ; Sun, 16 Apr 2017 08:36:12 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-43.reflexion.net [208.70.210.43]) (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 0AEA11ED3 for ; Sun, 16 Apr 2017 08:36:11 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 9907 invoked from network); 16 Apr 2017 08:36:10 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 16 Apr 2017 08:36:10 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.40.0) with SMTP; Sun, 16 Apr 2017 04:36:10 -0400 (EDT) Received: (qmail 30400 invoked from network); 16 Apr 2017 08:36:10 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 16 Apr 2017 08:36:10 -0000 Received: from [192.168.1.106] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 6D394EC81B0; Sun, 16 Apr 2017 01:36:09 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: lang/gcc6-aux for head beyond __nonnull related issues: vm_ooffset_t and vm_pindex_t related changes (and more) [amd64 system ld being lld vs. binutils based] From: Mark Millard In-Reply-To: Date: Sun, 16 Apr 2017 01:36:08 -0700 Cc: Gerald Pfeifer , Pedro Giffuni , ericturgeon.bsd@gmail.com, FreeBSD Current , freebsd-arm , FreeBSD Toolchain , FreeBSD Ports , "Ngie Cooper (yaneurabeya)" Content-Transfer-Encoding: quoted-printable Message-Id: <79677236-E5F7-45D1-9C18-7FE7237384B8@dsl-only.net> References: <9758023E-1526-41F9-9416-6AC8AD3201B5@dsl-only.net> <7606F976-20B7-4FB8-BE80-C27773F5529A@gmail.com> <20170415093010.GA4104@lonesome.com> To: Mark Linimon X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Apr 2017 08:36:12 -0000 On 2017-Apr-15, at 11:30 PM, Mark Millard = wrote: > On 2017-Apr-15, at 2:30 AM, Mark Linimon = wrote: >=20 >> On Fri, Apr 14, 2017 at 08:27:29PM -0700, Mark Millard wrote: >>> I've seen material quoted from a exp-run that reported >>> that about 54(?) ports were then blocked by lang/gcc6-aux >>> not building. >>=20 >> Although the first is an older run (the last complete run IIUC), = there >> were 50 and 51 respectively as of: >>=20 >> = http://thunderx1.nyi.freebsd.org/build.html?mastername=3D110arm64-default&= build=3D423029 >> = http://beefy8.nyi.freebsd.org/build.html?mastername=3Dhead-armv6-default&b= uild=3Dp437390_s316341 >>=20 >> I think you're fairly deep into unexplored territory here. >=20 >=20 > Looks like it. I tried an amd64 context (that was built using > WITH_LLD_IS_LD=3D in case that matters) and ports-mgmt/synth's > indirect build of lang/gcc6-aux quickly stopped for: >=20 > configure:4439: = /usr/obj/portswork/usr/ports/lang/gcc6-aux/work/bootstrap/bin/gcc -O2 = -pipe -g -fstack-protector -fno-strict-aliasing -I/usr/local/include = -L/usr/local/lib -fstack-protector conftest.c >&5 > /usr/bin/ld: error: unable to find library -lssp_nonshared > /usr/bin/ld: error: unable to find library -lc > collect2: error: ld returned 1 exit status > configure:4443: $? =3D 1 > configure:4480: result:=20 > configure: failed program was: > | /* confdefs.h */ > | #define PACKAGE_NAME "" > | #define PACKAGE_TARNAME "" > | #define PACKAGE_VERSION "" > | #define PACKAGE_STRING "" > | #define PACKAGE_BUGREPORT "" > | #define PACKAGE_URL "" > | /* end confdefs.h. */ > |=20 > | int > | main () > | { > |=20 > | ; > | return 0; > | } > configure:4486: error: in = `/usr/obj/portswork/usr/ports/lang/gcc6-aux/work/build': > configure:4490: error: C compiler cannot create executables >=20 > This happened even if I checked off in gcc6-aux's config > to do a bootstrap. >=20 > Even amd64 has build problems (at least for use of the > modern/experimental ld). I reverted to an amd64 system based on WITHOUT_LLD_IS_LD=3D and that avoided this issue: at least the build has gotten farther and is still in progress. It looks like the lang/gcc6-aux bootstrap/bin/gcc for amd64 is using /usr/bin/ld in a way that is binutils specific at this point. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Mon Apr 17 10:39:49 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8E466D406E0; Mon, 17 Apr 2017 10:39:49 +0000 (UTC) (envelope-from tvijlbrief@gmail.com) Received: from mail-yw0-x232.google.com (mail-yw0-x232.google.com [IPv6:2607:f8b0:4002:c05::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 45A84D9; Mon, 17 Apr 2017 10:39:49 +0000 (UTC) (envelope-from tvijlbrief@gmail.com) Received: by mail-yw0-x232.google.com with SMTP id k13so54325534ywk.1; Mon, 17 Apr 2017 03:39:49 -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=y0w2IiJjsyVBQaiPzieLR+AS2mVZ/b2+WYCq1hItSjc=; b=FU+QXCSJfGvNbjETAwrg+MfmmhcCjlSr6ab4zbyzM+Ex+QNmvdmvEROZhroshsYNgZ jpSMgbaM4D7e+B8omxvfGy3yCjfGY5HdT4BUz2bchtjAUpn1Bt0Mgi/eYbp04lsd6Ng1 UoIeGueKmV0RaR0zRGA3agBuY9U2pGzRlD4WW5x0aEPgVtpXK6652cnD7leQM2fiUMjO 6+CkktWH/MhMKTofCO/TJKvoIHWJ0cAkUEOhicFTVtGotkTTEFD5MDx/mp7E8isNyDdw xaqqmb5cYLKwafb+ESIrbmhX+Np7X1p9DEILT1Nxcli6l+UdI4ATtiBEbGnefRJ7UULi K3ig== 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=y0w2IiJjsyVBQaiPzieLR+AS2mVZ/b2+WYCq1hItSjc=; b=POkJSmMh2EKILJ2J7fWBrxJU6zHDjsY8FMnWKjFHUporm9yaEqxhEix3dvvYWG+6bs O94CGpSBG14o2B6c0snf8t8UO7lCAENwsCSQ58wUbV8cKp+LI11FT/eLjAXUh9Wa27qO xxaSxZIQhQOuoq4Atd85Np8hY3WdYcl6aP96tL5zdIY0KyqPvIElB3wYX6+LDNLJNhys Fb4nXln6ag6eeRM8HSTEpCmKCFphHKziUhaxh0kB0SYxKf/t2zhRM/jPsx09uSKFIUgf modYcBRxRDlKGDR7Yu64+W2h0v84QJ1ZJFet2GXHl7ePZ30/rAYxJZs8lphSfgKX709d a4QQ== X-Gm-Message-State: AN3rC/6fv/G92/rmCeeqpQo3e1BVqeBzGvF++7gJp0dhEDNEymP6MlVy K37pMqL0MmMk/lsZj3nxe+qQn0sstdLS X-Received: by 10.129.78.6 with SMTP id c6mr14735931ywb.86.1492425588227; Mon, 17 Apr 2017 03:39:48 -0700 (PDT) MIME-Version: 1.0 From: Tom Vijlbrief Date: Mon, 17 Apr 2017 10:39:37 +0000 Message-ID: Subject: Sendmail eats CPU on r317039 To: "freebsd-current@freebsd.org" , freebsd-arm Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Apr 2017 10:39:49 -0000 On a recent kernel sendmail is constantly consuming CPU. truss -p PID shows: sendto(3,"<22>Apr 17 10:30:33 sendmail[362"...,163,0x0,NULL,0) ERR#55 'No buffer space available' nanosleep({ 0.000001000 }) = 0 (0x0) sendto(3,"<22>Apr 17 10:30:33 sendmail[362"...,163,0x0,NULL,0) ERR#55 'No buffer space available' nanosleep({ 0.000001000 }) ... This is on an arm64 system From owner-freebsd-arm@freebsd.org Mon Apr 17 12:28:30 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 84D00D413E4 for ; Mon, 17 Apr 2017 12:28:30 +0000 (UTC) (envelope-from mizhka@gmail.com) Received: from mail-ua0-x234.google.com (mail-ua0-x234.google.com [IPv6:2607:f8b0:400c:c08::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 320051257 for ; Mon, 17 Apr 2017 12:28:30 +0000 (UTC) (envelope-from mizhka@gmail.com) Received: by mail-ua0-x234.google.com with SMTP id f10so51400398uaa.2 for ; Mon, 17 Apr 2017 05:28: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=IiX0cKw2L2nfgcA+DJCbqkIS4KjTztw0sXQcPOuy08Y=; b=teJ4QOcDFk4dZ0r1o6A4CfdVcR8uo4veqSrmYVNELKx2gkC84l9wpOg3p8h6IySSCn 4VLI8Kxbuq/hr6RMwOeHMv+ZdbuKpWRp3HiU3GqoblPtaqdzDlhN4rafW+7VFHVkTqFU wmeOFnQ7N5ccgGVD72qhik3FkcMfPZQqDOAWKsK5VjYyMMT3w0wA6PYqS3gPUzToUAVa j2SuzrEGzggBIzfQyLZuGXOu7zu+rlyDi6bGwPx50TJTr7izpCPuoxzVANW9rQX/DijU LI/uQQYle9ad8TonwQcVczGOj3dPuk8qn2rx02rTzyw79oY2+Gl/KqRSj7gb6zdq7ZKC vDAA== 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=IiX0cKw2L2nfgcA+DJCbqkIS4KjTztw0sXQcPOuy08Y=; b=eHS4AIhvTQI+bPc+Dobth6nU6LFdbNTDe2yxk8XcWDh1apkTbhaw+Z13we35C6d8XW xVQ69vGoLGHCAoSiKNeCfzpdxCS/WCzfMBJSgJZoX0XnTIRDJaTmXgYNz3MLIzN11XVb PuQRISoz/Y8Eq4WJVYzoZ54Dc6ECBOc2uF587oXmYwQ7woSLWjWN9u5btv09FUE3ymmy VLb+kvo/xNTgDFs8EVK8D+yZaU+lWH+iB5wVvUrh63nZPd5xXuu9g2mO1d7hTgmr4aYU ZDTmMwsvAUt8VUZIx04/d1vr5qpFwCEp8hDuqF276tPsYmy+wcv3NiIGCrroZEYKnZld 1hMw== X-Gm-Message-State: AN3rC/65+gnmyIKBD6x+jJomk39OnjQiVpCRE+/sQei/pdz5SPXgGCZW +Tqc4iin5aiNqz4URi0a6cXJWnl7sQ== X-Received: by 10.176.80.148 with SMTP id c20mr10071833uaa.0.1492432109227; Mon, 17 Apr 2017 05:28:29 -0700 (PDT) MIME-Version: 1.0 Received: by 10.31.166.75 with HTTP; Mon, 17 Apr 2017 05:28:28 -0700 (PDT) In-Reply-To: References: <622336.93399.qm@web101714.mail.ssk.yahoo.co.jp> <107064.50750.qm@web101717.mail.ssk.yahoo.co.jp> From: Michael Zhilin Date: Mon, 17 Apr 2017 15:28:28 +0300 Message-ID: Subject: Re: Can't use mge on 88F5181 To: Adrian Chadd Cc: Mori Hiroki , "freebsd-arm@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Apr 2017 12:28:30 -0000 Hi Adrian, Hiroki, Did you manage this issue? Actually I see similar issue with BCM53115/53125 and bgmac/dwc. What I have: - Asus RT-N53 with working bgmac driver and with embedded switch (BCM5758) - Asus RT-N16 (dead) and Netgear WNR3500: same bgmac driver and external switch BCM53115 and CPU BCM4718 and default configuration (unmanaged mode, all in one VLAN, port based VLAN is on, 1Q VLAN is on). Laptop sends packets and according to switch's MIB switch forwards it to CPU port and according to gmac's MIB packets are received by gmac (roughly same size, wireshark shows 42 send bytes, MIB shows 44 received bytes), there is no errors in MIB (like corrupted packets), but there is no interrupts/DMA transactions as well. I don't know what is actual problem, but it seems that DMA of bgmac doesn't work. Same code works with embedded switch. If you have any idea, please Thanks! On Fri, Apr 14, 2017 at 12:00 AM, Adrian Chadd wrote: > hi, > > I'd have to go dig through the datasheets of everything to see what > the deal is. :( it could be ethernet switch side, it could be > interface config mismatch (MII, RMII, RGMII, SGMII, PSGMII, etc.); it > could be clock configuration (if it's MII, the clock is changed based > on 10/100; later interfaces run at a constant speed and just > bitstuff), etc, etc. > > Can you get per-switch-port counters on the switch? Is the CPU port on > the switch seeing traffic? > > > -adrian > > > On 12 April 2017 at 22:26, Mori Hiroki wrote: > > Hi. > > > > No arp and unicast packet receive mge checked by tcpdump command > > on this target. Also no pacet trans checked by tcpdump command on > > other machine. netstat -i have trans packet count without error. > > But no receive other machine. MIDO switch control is work fine. > > Giga switch physical port to physical port is receive and trans > > is fine. But cpu port nothing. > > > > My e6060sw.c code have dot1q support by VTU access code. e6000sw > > don't have it. I want add dot1q code to e6000sw too. But It is > > very hard no data sheet. > > > > I found ml topics is this type target at 2011. That subject is > > "Embedded switch instead of stadard PHY". I seem this is origin > > of etherswitch. > > > > Thanks > > > > Hiroki Mori > > > > > > ----- Original Message ----- > >> From: Adrian Chadd > >> To: Mori Hiroki > >> Cc: "freebsd-arm@freebsd.org" > >> Date: 2017/4/12, Wed 09:55 > >> Subject: Re: Can't use mge on 88F5181 > >> > >> hiya, > >> > >> did you figure it out? > >> > >> Is there something like CRC, etc packet errors or something on RX? > >> > >> > >> > >> -adrian > >> > >> > >> On 4 April 2017 at 04:42, Mori Hiroki wrote: > >>> Hi. > >>> > >>> I try to use Buffalo WZR-AMPG300NH. This module have 88F5181 and > 88E6131. > >>> I modify dev/mge and dev/etherswitch/e600sw/e6000sw.c. > >>> > >>> Network interface mge is detect but not work. Switch port is work by > >>> port vlan. But CPU connected port3 is nothing trans and receive > packet. > >>> > >>> I check marvell code but not fix this problem. > >>> > >>> If you have advice, please let me know. > >>> > >>> > >>> This is dmesg. > >>> > >>> https://gist.github.com/yamori813/ecd5df1b314053a73f310c1122775540 > >>> > >>> > >>> Thanks. > >>> > >>> Hiroki Mori > >>> _______________________________________________ > >>> freebsd-arm@freebsd.org mailing list > >>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm > >>> To unsubscribe, send any mail to > >> "freebsd-arm-unsubscribe@freebsd.org" > >> > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > From owner-freebsd-arm@freebsd.org Mon Apr 17 14:57:47 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DEF69D41492 for ; Mon, 17 Apr 2017 14:57:47 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-43.reflexion.net [208.70.210.43]) (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 6E3CAA62 for ; Mon, 17 Apr 2017 14:57:46 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 6135 invoked from network); 17 Apr 2017 14:58:43 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 17 Apr 2017 14:58:43 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.40.0) with SMTP; Mon, 17 Apr 2017 10:57:40 -0400 (EDT) Received: (qmail 21075 invoked from network); 17 Apr 2017 14:57:40 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 17 Apr 2017 14:57:40 -0000 Received: from [192.168.1.106] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id AB42AEC929D; Mon, 17 Apr 2017 07:57:39 -0700 (PDT) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Fwd: Sendmail eats CPU on r317039 [after -r316874 it may be -r316951 and -r316973 are not enough to fix everything] Date: Mon, 17 Apr 2017 07:57:39 -0700 References: Cc: Tom Vijlbrief , FreeBSD Current , freebsd-arm To: sobomax@FreeBSD.org, hrs@FreeBSD.org Message-Id: <91A4570B-69EE-4462-9C60-205C66267599@dsl-only.net> X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Apr 2017 14:57:48 -0000 Just an FYI of a more recent report of runaway sendmail on a more recent system version ( -r317039 ): Begin forwarded message: > From: Tom Vijlbrief > Subject: Sendmail eats CPU on r317039 > Date: April 17, 2017 at 3:39:37 AM PDT > To: "freebsd-current at freebsd.org" , = freebsd-arm >=20 > On a recent kernel sendmail is constantly consuming CPU. >=20 > truss -p PID >=20 > shows: >=20 > sendto(3,"<22>Apr 17 10:30:33 sendmail[362"...,163,0x0,NULL,0) ERR#55 = 'No > buffer space available' > nanosleep({ 0.000001000 }) =3D 0 (0x0) > sendto(3,"<22>Apr 17 10:30:33 sendmail[362"...,163,0x0,NULL,0) ERR#55 = 'No > buffer space available' > nanosleep({ 0.000001000 }) > ... >=20 > This is on an arm64 system Analysis of Tom V.'s context for this may be required. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Tue Apr 18 07:09:09 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ADE77D433BE for ; Tue, 18 Apr 2017 07:09:09 +0000 (UTC) (envelope-from jonc@chen.org.nz) 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 6EE40FA for ; Tue, 18 Apr 2017 07:09:09 +0000 (UTC) (envelope-from jonc@chen.org.nz) Received: by mail-qt0-x22d.google.com with SMTP id c45so117952135qtb.1 for ; Tue, 18 Apr 2017 00:09:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chen-org-nz.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=2a7mzCZFabP5p/PvGCA54rEMLZO4ZgqMs5jkitBCVLU=; b=15+Ydr3ofPPeA1AMu/hGHjoLApHJppgkEZRKhmUfDQz3AIc11yvaEHQf8uQ5e7m7Y7 0UTyDZbnClO/Yh++4U34mS1IL1n9x5lhdnd4X5lGyGVbDa1BguJLjiY47Efe7OU1HVCh yL1DlwyFKrCiJhiZ4ozp6amVQUk0tjD5/nBfK17wS9uF6HCyVl9cg4Cy+8dKgcwrHwPe xbqAvM2Y5HWo3ipVUYvKrJ+luIf/+bV8i771mrr92rINz++Impmdc+hmmHUhprxY8swJ 0iJTdGwdcZPUPkUeieJ17EdS6AqACfm1grW2I3iq2RvC/Eo8SFlJCElsBcnO4Ucf51HE o9ZA== 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=2a7mzCZFabP5p/PvGCA54rEMLZO4ZgqMs5jkitBCVLU=; b=QNLXZcKRikALFZuX3Pm6dpOZNSTYsRwEyeu9DN3rWpe9+es4s9+8gTtpwEDDU8In2K uP5KwKYqV++aTRg1XbFg9UEzndq2lVKBXhUSx9RXykUaU8yzKO1wXpuNQUigNM61x0or LjUtFqRk0pN3R6vjlgqFa66tqGrcdlxIJfAXEm2/x8MlZ8Aqo1+pmYfyqYUs/fAIY7lP oREP5AN2ZU1nN5P9joll9OY+pVh/L6oozJytYTXIQaKgN3Ab8J13EKxVMJXWFerQgl1F 2hQQ/50VhwTuLJuAnEIOwf1JsDjfvFJ87R5ECtc4B5KgjMxyubhpO3s+2xz3MNTvjn7x XESA== X-Gm-Message-State: AN3rC/6gseSQhA4NW0JkVQTsSqEM7nRmJMILS2QBp7l+CWpSV0nLV9WM SUovS2IPuBYHF0zi+USNCBejwoJ5mEiy X-Received: by 10.237.62.253 with SMTP id o58mr11870207qtf.152.1492499348565; Tue, 18 Apr 2017 00:09:08 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.108.102 with HTTP; Tue, 18 Apr 2017 00:09:08 -0700 (PDT) X-Originating-IP: [101.53.200.223] From: Jonathan Chen Date: Tue, 18 Apr 2017 19:09:08 +1200 Message-ID: Subject: Crossbuilding for armv6 To: freebsd-arm@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2017 07:09:09 -0000 Hi, I'm using https://wiki.freebsd.org/QemuUserModeHowTo to help me crossbuild some ports for my RPI2 on my amd64, with moderate success. I've managed to build the ports using pure-emulation, but attempts to use host cross-compilation to improve build times currently fail; partly because I believe the instructions are out of date. The instructions on "Cross Building Using the Host Cross Compiler (and other toolchain friends)" has a section on setting up the environment: # export CC=/usr/obj/usr/src/tmp/usr/bin/cc # export CPP=/usr/obj/usr/src/tmp/usr/bin/cpp # export CXX=/usr/obj/usr/src/tmp/usr/bin/c++ ... However, on STABLE-11/amd64, these binaries are not present. Does anyone here know what the correct entries should be? Cheers. -- Jonathan Chen From owner-freebsd-arm@freebsd.org Tue Apr 18 15:42:59 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EF37ED445DD for ; Tue, 18 Apr 2017 15:42:59 +0000 (UTC) (envelope-from jungleboogie0@gmail.com) Received: from mail-yw0-x234.google.com (mail-yw0-x234.google.com [IPv6:2607:f8b0:4002:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B4E38B84 for ; Tue, 18 Apr 2017 15:42:59 +0000 (UTC) (envelope-from jungleboogie0@gmail.com) Received: by mail-yw0-x234.google.com with SMTP id l189so71816999ywb.0 for ; Tue, 18 Apr 2017 08:42:59 -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=xlPgj+e49Zy5xIf4aKd8pTefniStXkpVwNVD1Rzp3XY=; b=W16K2GmeB9wd0naELKFMn2QXODu39dCwaTcP8H8VBnJciO7D9eVLdLx/14xFd7qlJz 1Eqq3RdR3O8lyQNvDNUabU0BNCGNZyunk0sXHYEf6G+17JnKjkX0k6jHbur3BS3L9MbN x6pZ0TMG/RGpAWprIqyYV1W6L4N7EaPx2V4D3tHwsmmlLZRfun+kboupvQu5SjXlZLQh aP4K5XBSsgeMmaNu9TZdweQM/ddu7TagQN7QBdTyCg2nv49+XHByeqlLxT3e5y4x/ok2 A8kgpkchSGyeNyFk9NQuwPKM3seUF2W/LPK4mQWX+51o1Rpexg+NYZhSTIKpfQRjDdF8 tuDA== 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=xlPgj+e49Zy5xIf4aKd8pTefniStXkpVwNVD1Rzp3XY=; b=mZPyTXNbbdfL3LCmrmVe5hpIOKwtBHevfzQypCVyeeDfBVKoPm+36f/5/XZ4hw9Q2k AeFGTJDlznjloFjUYAd4fBN90fjKeHvOCV5HdiM1M/9evEalcmplJJCQbmgG5l97DJMp z1/g7ofiPMXj6cS/h6ROvb80fGgyphaTfHsayvAEF4qgdL7AsjRN1ifCMFsDGN6xf7pq tvPocp75uXoZEBLcCZ2DElUcvhSPhd5sxyYa/K3BkF8tPA6zUO9u+BqK6q/c6iXAM+pX +WbkUXYczjGzKOmX1ggpNH57HF3ux1uqZkF+BFEqivFfMlDjO8HzgxJNxaz3oBVqF3lW iKzA== X-Gm-Message-State: AN3rC/6dOimt2ivnVIeeQ7f+xvcJpMy37o/DriF1ZI5+Z0xZzWC+YrV0 LWAdKUpC7C289ftNrPwd11JqtAqWxcz8 X-Received: by 10.129.181.19 with SMTP id t19mr19725302ywh.184.1492530178716; Tue, 18 Apr 2017 08:42:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.37.193.70 with HTTP; Tue, 18 Apr 2017 08:42:58 -0700 (PDT) In-Reply-To: <5bac0dbc-6d2b-c757-0cd3-babbd048cfd2@gmail.com> References: <5bac0dbc-6d2b-c757-0cd3-babbd048cfd2@gmail.com> From: jungle Boogie Date: Tue, 18 Apr 2017 08:42:58 -0700 Message-ID: Subject: Re: beaglebone black: MMC partition switch failed To: "freebsd-arm@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2017 15:43:00 -0000 On 15 April 2017 at 18:50, jungle boogie wrote: > Hi All, > > It's been awhile since I've been able to run FreeBSD on my BBB. It was > failing somewhere, but I didn't have good serial cable to see what was > happening. > > Using the latest freebsd head image: > FreeBSD-12.0-CURRENT-arm-armv6-BEAGLEBONE-20170413-r316750.img > > I'm writing it to my microSD card: > sudo dd if=FreeBSD-12.0-CURRENT-arm-armv6-BEAGLEBONE-20170413-r316750.img > of=/dev/sdf bs=8M > 128+0 records in > 128+0 records out > 1073741824 bytes (1.1 GB, 1.0 GiB) copied, 1.01005 s, 1.1 GB/s > > > Putting it in the BB and holding s2 for three seconds as mentioned in the > FBSD Journal article[0]. > > Upon doing so, I see this: > U-Boot SPL 2017.01-rc3 (Apr 13 2017 - 12:30:59) > Trying to boot from MMC1** First descriptor is NOT a primary desc on 0:1 ** > MMC partition switch failed > *** Warning - MMC partition switch failed, using default environment > > ** Partition 1 not valid on device 0 ** > spl_register_fat_device: fat register err - -1 > spl_load_image_fat: error reading image u-boot.img, err - -1 > MMC partition switch failed > *** Warning - MMC partition switch failed, using default environment > > spl: no partition table found > SPL: failed to boot from all boot devices > ### ERROR ### Please RESET the board ### > Anyone have recommendations on how to fix this? From owner-freebsd-arm@freebsd.org Tue Apr 18 15:51:09 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F0EE5D44929 for ; Tue, 18 Apr 2017 15:51:08 +0000 (UTC) (envelope-from gjb@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 ADB3DD6; Tue, 18 Apr 2017 15:51:08 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id 7BCEED13; Tue, 18 Apr 2017 15:51:06 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Tue, 18 Apr 2017 15:51:02 +0000 From: Glen Barber To: jungle Boogie Cc: "freebsd-arm@freebsd.org" Subject: Re: beaglebone black: MMC partition switch failed Message-ID: <20170418155102.GO2455@FreeBSD.org> References: <5bac0dbc-6d2b-c757-0cd3-babbd048cfd2@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="f0PSjARDFl/vfYT5" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.0-STABLE amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event X-PEKBAC-Definition: Problem Exists, Keyboard Between Admin/Computer X-Spidey-Sense: Uh oh, Peter logged in User-Agent: Mutt/1.7.1 (2016-10-04) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2017 15:51:09 -0000 --f0PSjARDFl/vfYT5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 18, 2017 at 08:42:58AM -0700, jungle Boogie wrote: > On 15 April 2017 at 18:50, jungle boogie wrote: > > Hi All, > > > > It's been awhile since I've been able to run FreeBSD on my BBB. It was > > failing somewhere, but I didn't have good serial cable to see what was > > happening. > > > > Using the latest freebsd head image: > > FreeBSD-12.0-CURRENT-arm-armv6-BEAGLEBONE-20170413-r316750.img > > > > I'm writing it to my microSD card: > > sudo dd if=3DFreeBSD-12.0-CURRENT-arm-armv6-BEAGLEBONE-20170413-r316750= =2Eimg > > of=3D/dev/sdf bs=3D8M > > 128+0 records in > > 128+0 records out > > 1073741824 bytes (1.1 GB, 1.0 GiB) copied, 1.01005 s, 1.1 GB/s > > > > > > Putting it in the BB and holding s2 for three seconds as mentioned in t= he > > FBSD Journal article[0]. > > > > Upon doing so, I see this: > > U-Boot SPL 2017.01-rc3 (Apr 13 2017 - 12:30:59) > > Trying to boot from MMC1** First descriptor is NOT a primary desc on 0:= 1 ** > > MMC partition switch failed > > *** Warning - MMC partition switch failed, using default environment > > > > ** Partition 1 not valid on device 0 ** > > spl_register_fat_device: fat register err - -1 > > spl_load_image_fat: error reading image u-boot.img, err - -1 > > MMC partition switch failed > > *** Warning - MMC partition switch failed, using default environment > > > > spl: no partition table found > > SPL: failed to boot from all boot devices > > ### ERROR ### Please RESET the board ### > > >=20 >=20 > Anyone have recommendations on how to fix this? There appears to be an issue with the 20170413 image. Please check if the FreeBSD-12.0-CURRENT-arm-armv6-BEAGLEBONE-20170405-r316508.img.xz image works. Glen --f0PSjARDFl/vfYT5 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCAAGBQJY9jXfAAoJEAMUWKVHj+KTWMQQAKTSTDPwC/KsxNn89cTpFrKF czIAfromERaWaL7YPAZK1RFTKDFr02d7a8ZhzbvfU8T3HygbIQkAonH/gvfZSRF2 bzG9bsFYxnoR7H9um0Y1j2LVb/iWTEcBwVt3Qar4XzMdh4W9WjJQnF4kZaGvIuxt /nS7Zj/zE5/umjDk6w+ZYUJbHOctFxC/xqnTVqCJBpovQgvj3bHTZJHcdsxYZi+W VeK0Ikf0k0OGT9ggFlffP9iJOXCiPKoQSCbuAzi0p1JtZhLWpAtf8Yvvpj3xaLps OZPe4kbWkIOWeMWyc2VykGzvp/7NXI9BeLGEWvunwQQ4RGt67UlzYTLrZctpn39/ mJ4+/dKpvRPYmEA00T0sjM9LCDAGStaC1bQbuRYr1wR44cydbVNdmmzRrEXVimQD ND/QoYQG4XDWT1UNL2uVa19kIUzbziEFGCxCobSbq/cdaj4G72DV1r8PpMmSJ4yb pnDavZszP4m2rBslkELq9kWj+k4qd6RpYoabU6BN56gvfQN/IcXiqAR52Hwaa1xk 8OsQnGet/RilMpfpztjkFUFUGCCYQ7unnvuMYGnM2izcQp0a34jg7VHHc5x69UVf nGEQuhxwdhz9F6JDVQmjqE9YvHNKimSJWXt/gTMswVuMrihMDW+2KZBvgNG8g/ER w7xDKDdNZQGgwsJruksq =9lRa -----END PGP SIGNATURE----- --f0PSjARDFl/vfYT5-- From owner-freebsd-arm@freebsd.org Tue Apr 18 16:55:16 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3CC5BD442D8 for ; Tue, 18 Apr 2017 16:55:16 +0000 (UTC) (envelope-from otacilio.neto@bsd.com.br) Received: from mail-qk0-x234.google.com (mail-qk0-x234.google.com [IPv6:2607:f8b0:400d:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ED810117D for ; Tue, 18 Apr 2017 16:55:15 +0000 (UTC) (envelope-from otacilio.neto@bsd.com.br) Received: by mail-qk0-x234.google.com with SMTP id f133so135620443qke.2 for ; Tue, 18 Apr 2017 09:55:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsd.com.br; s=capeta; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to; bh=AmW5Y/a3HxPkgA4RgQcQam+rcXd/qMcOn8GO17XfRSk=; b=UZwQJvhcqknmUIB37MHF0f3/nKpjiYL+vn45ISvKHkb13y3nSVB4WqqDyYwEXJBDMm yeQML73/nelU6ah+XkDHiXbYwZZtBaFMhiHi1FM0kBGuAMRoaHP3p5BNnmFolzOsHozC 995dXw4kSdEsP7uDanm5ZFO74tdcPVzyghczg= 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; bh=AmW5Y/a3HxPkgA4RgQcQam+rcXd/qMcOn8GO17XfRSk=; b=ewz+ZvRmRyQYtRnrprjlgLGJhh5hnAVqoZkRrvK5yEc6fSTdEmwqiOG/akgwhdoc02 jW8nro7xHuQvcrLLc1lFzfGUnwafCpxyEeE8//s0eCdUbLn4eE0zCjAKxEuhF0xOx3ui Z9NGynmVQUiyoX8qjgSga/Y2O5hZGxkPFJf1j4plUWSaVEI1ZpqOw/tKmCtmcsSnKLb3 T/CUn4N5ke1vEb1BOGsdW3RnyF68mgtdONflukLzqcjrNjvrVfSldVaYMOm8lgq3UVAH oDzT0cNfXjlwO2GYlv/jVbKkDXuTkXqnGdZl9f/JvwkT1Z00T/QQmYvcScGELXu4cLHh LFrQ== X-Gm-Message-State: AN3rC/4PE6ye4SOBn+yl5lVJvvbgvaEdlYBWx6tX1B1roMaquKxsCd3z FZMH0fW7BvQALV6s X-Received: by 10.55.217.71 with SMTP id u68mr13435627qki.272.1492534514518; Tue, 18 Apr 2017 09:55:14 -0700 (PDT) Received: from ?IPv6:2804:54:19ef:cc00:7c56:bc1b:d84d:7715? ([2804:54:19ef:cc00:7c56:bc1b:d84d:7715]) by smtp.googlemail.com with ESMTPSA id v11sm9946569qtg.33.2017.04.18.09.55.12 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 18 Apr 2017 09:55:13 -0700 (PDT) Subject: Re: beaglebone black: MMC partition switch failed To: freebsd-arm@freebsd.org References: <5bac0dbc-6d2b-c757-0cd3-babbd048cfd2@gmail.com> <20170418155102.GO2455@FreeBSD.org> From: =?UTF-8?B?T3RhY8OtbGlv?= Message-ID: Date: Tue, 18 Apr 2017 13:54:46 -0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <20170418155102.GO2455@FreeBSD.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2017 16:55:16 -0000 Em 18/04/2017 12:51, Glen Barber escreveu: > On Tue, Apr 18, 2017 at 08:42:58AM -0700, jungle Boogie wrote: >> On 15 April 2017 at 18:50, jungle boogie wrote: >>> Hi All, >>> >>> It's been awhile since I've been able to run FreeBSD on my BBB. It was >>> failing somewhere, but I didn't have good serial cable to see what was >>> happening. >>> >>> Using the latest freebsd head image: >>> FreeBSD-12.0-CURRENT-arm-armv6-BEAGLEBONE-20170413-r316750.img >>> >>> I'm writing it to my microSD card: >>> sudo dd if=FreeBSD-12.0-CURRENT-arm-armv6-BEAGLEBONE-20170413-r316750.img >>> of=/dev/sdf bs=8M >>> 128+0 records in >>> 128+0 records out >>> 1073741824 bytes (1.1 GB, 1.0 GiB) copied, 1.01005 s, 1.1 GB/s >>> >>> >>> Putting it in the BB and holding s2 for three seconds as mentioned in the >>> FBSD Journal article[0]. >>> >>> Upon doing so, I see this: >>> U-Boot SPL 2017.01-rc3 (Apr 13 2017 - 12:30:59) >>> Trying to boot from MMC1** First descriptor is NOT a primary desc on 0:1 ** >>> MMC partition switch failed >>> *** Warning - MMC partition switch failed, using default environment >>> >>> ** Partition 1 not valid on device 0 ** >>> spl_register_fat_device: fat register err - -1 >>> spl_load_image_fat: error reading image u-boot.img, err - -1 >>> MMC partition switch failed >>> *** Warning - MMC partition switch failed, using default environment >>> >>> spl: no partition table found >>> SPL: failed to boot from all boot devices >>> ### ERROR ### Please RESET the board ### >>> >> >> Anyone have recommendations on how to fix this? > There appears to be an issue with the 20170413 image. Please check if > the FreeBSD-12.0-CURRENT-arm-armv6-BEAGLEBONE-20170405-r316508.img.xz > image works. > > Glen > I tested them a few days ago and none of them worked. I also compiled locally and it does not work, even an image generated for the RPI3 prints the same error message. From owner-freebsd-arm@freebsd.org Tue Apr 18 16:57:46 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0DF0CD44391 for ; Tue, 18 Apr 2017 16:57:46 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [52.58.109.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A00E112D0 for ; Tue, 18 Apr 2017 16:57:45 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 1f346d29-2458-11e7-b96e-2378c10e3beb X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id 1f346d29-2458-11e7-b96e-2378c10e3beb; Tue, 18 Apr 2017 16:57:37 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id v3IGvWd5009088; Tue, 18 Apr 2017 10:57:32 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1492534652.96207.28.camel@freebsd.org> Subject: Re: beaglebone black: MMC partition switch failed From: Ian Lepore To: =?ISO-8859-1?Q?Otac=EDlio?= , freebsd-arm@freebsd.org Date: Tue, 18 Apr 2017 10:57:32 -0600 In-Reply-To: References: <5bac0dbc-6d2b-c757-0cd3-babbd048cfd2@gmail.com> <20170418155102.GO2455@FreeBSD.org> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2017 16:57:46 -0000 On Tue, 2017-04-18 at 13:54 -0300, Otacílio wrote: > Em 18/04/2017 12:51, Glen Barber escreveu: > > > > On Tue, Apr 18, 2017 at 08:42:58AM -0700, jungle Boogie wrote: > > > > > > On 15 April 2017 at 18:50, jungle boogie > > > wrote: > > > > > > > > Hi All, > > > > > > > > It's been awhile since I've been able to run FreeBSD on my BBB. > > > > It was > > > > failing somewhere, but I didn't have good serial cable to see > > > > what was > > > > happening. > > > > > > > > Using the latest freebsd head image: > > > > FreeBSD-12.0-CURRENT-arm-armv6-BEAGLEBONE-20170413-r316750.img > > > > > > > > I'm writing it to my microSD card: > > > > sudo dd if=FreeBSD-12.0-CURRENT-arm-armv6-BEAGLEBONE-20170413- > > > > r316750.img > > > > of=/dev/sdf bs=8M > > > > 128+0 records in > > > > 128+0 records out > > > > 1073741824 bytes (1.1 GB, 1.0 GiB) copied, 1.01005 s, 1.1 GB/s > > > > > > > > > > > > Putting it in the BB and holding s2 for three seconds as > > > > mentioned in the > > > > FBSD Journal article[0]. > > > > > > > > Upon doing so, I see this: > > > > U-Boot SPL 2017.01-rc3 (Apr 13 2017 - 12:30:59) > > > > Trying to boot from MMC1** First descriptor is NOT a primary > > > > desc on 0:1 ** > > > > MMC partition switch failed > > > > *** Warning - MMC partition switch failed, using default > > > > environment > > > > > > > > ** Partition 1 not valid on device 0 ** > > > > spl_register_fat_device: fat register err - -1 > > > > spl_load_image_fat: error reading image u-boot.img, err - -1 > > > > MMC partition switch failed > > > > *** Warning - MMC partition switch failed, using default > > > > environment > > > > > > > > spl: no partition table found > > > > SPL: failed to boot from all boot devices > > > > ### ERROR ### Please RESET the board ### > > > > > > > Anyone have recommendations on how to fix this? > > There appears to be an issue with the 20170413 image.  Please check > > if > > the FreeBSD-12.0-CURRENT-arm-armv6-BEAGLEBONE-20170405- > > r316508.img.xz > > image works. > > > > Glen > > > I tested them a few days ago and none of them worked. I also > compiled  > locally and it does not work, even an image generated for the RPI3  > prints the same error message. The 20170405 image Glen mentioned works fine, I just DLed and tested it. -- Ian From owner-freebsd-arm@freebsd.org Tue Apr 18 17:26:56 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9F609D4429B for ; Tue, 18 Apr 2017 17:26:56 +0000 (UTC) (envelope-from otacilio.neto@bsd.com.br) Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d: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 577D4E5D for ; Tue, 18 Apr 2017 17:26:56 +0000 (UTC) (envelope-from otacilio.neto@bsd.com.br) Received: by mail-qk0-x233.google.com with SMTP id p68so136384499qke.1 for ; Tue, 18 Apr 2017 10:26:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsd.com.br; s=capeta; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to; bh=XDfTSZjzBuydkvElkrBXQkgDEzNf2gGlNcnBiVXdMQQ=; b=QsWqTIYhdOvxIvpKtrE3GnzQlTWQuP8dkAaMUN/5QNZ3tyKa9jEcmvRAiugsQKG6If SHupRm82aU07sj1JfRFj38TscylWwB/N86ujATIgfrOHl4eEgirr0gVO3kn1z2fyrTd1 QEF55nU3ZqDUAqVCMN6Htu47lc9M4hqDoxZFk= 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; bh=XDfTSZjzBuydkvElkrBXQkgDEzNf2gGlNcnBiVXdMQQ=; b=j5AhI43RYrLSzYznMCmBLuCIZo3YYjgjedMgdsYuwN38pZuLdw/5YTQr1cc15sBn0Q DuJgN65ZsMqcXfxYmath/cRjKZj+J4Ee4DuVAf0MUx6Iz3N9VrBKBqBGacSYukOH+zyX trrIpVUTCsLVbfqUpomAGMLiR6caeBtmZC80t1C3zjGJ/zd+mjGL0A3ALXF0OdIqSGbi Zem8jZCkyPqeO0JkuJmnZ9e/d+dz3oL4LFJPZZK8ShMz+YT6cX1mPR0rEVGyJ3KDgpq+ hsGnHhQuETTOeFCBVE5CYny/KZjS60/0a06uZA6YKjaoO2fAhcp66yOzU6wF4cXwJTVt fMJA== X-Gm-Message-State: AN3rC/6VfwPhZf19JJlLDVmOVSGzVp1bhFphPSPofn/Z9TRg7l09Lm1o fKJFW4kv1H4Nhw== X-Received: by 10.55.112.6 with SMTP id l6mr13381536qkc.187.1492536415391; Tue, 18 Apr 2017 10:26:55 -0700 (PDT) Received: from [192.168.0.11] ([177.89.67.185]) by smtp.googlemail.com with ESMTPSA id d67sm10043010qkg.40.2017.04.18.10.26.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 18 Apr 2017 10:26:54 -0700 (PDT) Subject: Re: beaglebone black: MMC partition switch failed To: Ian Lepore , freebsd-arm@freebsd.org References: <5bac0dbc-6d2b-c757-0cd3-babbd048cfd2@gmail.com> <20170418155102.GO2455@FreeBSD.org> <1492534652.96207.28.camel@freebsd.org> From: =?UTF-8?B?T3RhY8OtbGlv?= Message-ID: <53fe500c-4aa3-c1a4-6a59-33e90aac5281@bsd.com.br> Date: Tue, 18 Apr 2017 14:26:04 -0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <1492534652.96207.28.camel@freebsd.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2017 17:26:56 -0000 Em 18/04/2017 13:57, Ian Lepore escreveu: > On Tue, 2017-04-18 at 13:54 -0300, Otacílio wrote: >> Em 18/04/2017 12:51, Glen Barber escreveu: >>> On Tue, Apr 18, 2017 at 08:42:58AM -0700, jungle Boogie wrote: >>>> On 15 April 2017 at 18:50, jungle boogie >>>> wrote: >>>>> >>>>> Hi All, >>>>> >>>>> It's been awhile since I've been able to run FreeBSD on my BBB. >>>>> It was >>>>> failing somewhere, but I didn't have good serial cable to see >>>>> what was >>>>> happening. >>>>> >>>>> Using the latest freebsd head image: >>>>> FreeBSD-12.0-CURRENT-arm-armv6-BEAGLEBONE-20170413-r316750.img >>>>> >>>>> I'm writing it to my microSD card: >>>>> sudo dd if=FreeBSD-12.0-CURRENT-arm-armv6-BEAGLEBONE-20170413- >>>>> r316750.img >>>>> of=/dev/sdf bs=8M >>>>> 128+0 records in >>>>> 128+0 records out >>>>> 1073741824 bytes (1.1 GB, 1.0 GiB) copied, 1.01005 s, 1.1 GB/s >>>>> >>>>> >>>>> Putting it in the BB and holding s2 for three seconds as >>>>> mentioned in the >>>>> FBSD Journal article[0]. >>>>> >>>>> Upon doing so, I see this: >>>>> U-Boot SPL 2017.01-rc3 (Apr 13 2017 - 12:30:59) >>>>> Trying to boot from MMC1** First descriptor is NOT a primary >>>>> desc on 0:1 ** >>>>> MMC partition switch failed >>>>> *** Warning - MMC partition switch failed, using default >>>>> environment >>>>> >>>>> ** Partition 1 not valid on device 0 ** >>>>> spl_register_fat_device: fat register err - -1 >>>>> spl_load_image_fat: error reading image u-boot.img, err - -1 >>>>> MMC partition switch failed >>>>> *** Warning - MMC partition switch failed, using default >>>>> environment >>>>> >>>>> spl: no partition table found >>>>> SPL: failed to boot from all boot devices >>>>> ### ERROR ### Please RESET the board ### >>>>> >>>> Anyone have recommendations on how to fix this? >>> There appears to be an issue with the 20170413 image. Please check >>> if >>> the FreeBSD-12.0-CURRENT-arm-armv6-BEAGLEBONE-20170405- >>> r316508.img.xz >>> image works. >>> >>> Glen >>> >> I tested them a few days ago and none of them worked. I also >> compiled >> locally and it does not work, even an image generated for the RPI3 >> prints the same error message. > The 20170405 image Glen mentioned works fine, I just DLed and tested > it. > > -- Ian You're right I downloaded it now, I recorded the SD and it worked. I did not understand what happened the other time. Maybe the problem was between the seat and the computer. Sorry for the noise From owner-freebsd-arm@freebsd.org Tue Apr 18 17:30:08 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6E4E2D4439E for ; Tue, 18 Apr 2017 17:30:08 +0000 (UTC) (envelope-from jungleboogie0@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 2CCA3F67; Tue, 18 Apr 2017 17:30:08 +0000 (UTC) (envelope-from jungleboogie0@gmail.com) Received: by mail-yw0-x22c.google.com with SMTP id l189so73300334ywb.0; Tue, 18 Apr 2017 10:30: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=PImhRU1WBGiRW0QRjGtqOKB4bkCOJbFQ22KN5wMd0TM=; b=R79MH3+q1OH462n9jRiUsPvaD4KiWdowgKeJ8sk/PmX74HUewYG85Z64XMxaUf/c98 KXSNaLTWXKtK13qpXa05TeDoWppHE0yTOrtxx8p3/yIqBIi5bQgIeaAVgWFRMXTdQpXP XW2/daIRQS9wfUZwAAy0enQtxhjpxega9hEHtLNFke18TMyCKYoFmT2JroHxwAR9Gm1Y L8QfovOLDjfrvplOwBUMvwT8AEF02ES/5xv1/ibLALw+qUOhe7l34x8h/FzDIn23Amxa F8MJUJU8U44mMGoTQNVQYvzjSq49mlB0gaHdWHqvvu6Q9gk/zzg9xm4Ay8ChlWCbkYI+ SBbQ== 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=PImhRU1WBGiRW0QRjGtqOKB4bkCOJbFQ22KN5wMd0TM=; b=MucbfviS9TT7cW5EXQnhIzqKFH2XBvPCMUtY5rO+FTfkFqXAZT2CLZiott/MIsOac0 1SYLyS5yct6Rb+aAibBXCY1GUxes5vlCFEooSQdnPSFLe/M+aALvxx8Hq8XSXFRrAvMP m8GJlENJ3ETCoF9PPinzkxlJH7Ow1s087sfiMKvZApGeSTGjrCvL+ZCgnvFyCRZpNR8v KCr9BXEe1Ws1tfpbvk3BkRVFIwjbJrm7CnJsoBRiTmEunFLMGk/8f2AFwqsQ/cHecFTv i4e1pJA61PM8SMScwCqzhqEIsu52kfETHtteaEM2i46sn04xSsAID09loRN/NOzuKaCT NLMw== X-Gm-Message-State: AN3rC/4zcNxrabUcToAFa/6APTXrMse4FTAiaStWEZJvNJMh/aGbHhgZ 6HIzVvXPF1xCSqrvHuonN8xA4Yd1gUPjc00= X-Received: by 10.129.4.134 with SMTP id 128mr22711738ywe.109.1492536607157; Tue, 18 Apr 2017 10:30:07 -0700 (PDT) MIME-Version: 1.0 Received: by 10.37.193.70 with HTTP; Tue, 18 Apr 2017 10:30:06 -0700 (PDT) In-Reply-To: <1492534652.96207.28.camel@freebsd.org> References: <5bac0dbc-6d2b-c757-0cd3-babbd048cfd2@gmail.com> <20170418155102.GO2455@FreeBSD.org> <1492534652.96207.28.camel@freebsd.org> From: jungle Boogie Date: Tue, 18 Apr 2017 10:30:06 -0700 Message-ID: Subject: Re: beaglebone black: MMC partition switch failed To: Ian Lepore Cc: =?UTF-8?B?T3RhY8OtbGlv?= , "freebsd-arm@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2017 17:30:08 -0000 On 18 April 2017 at 09:57, Ian Lepore wrote: > The 20170405 image Glen mentioned works fine, I just DLed and tested > it. Thanks for the confirmation, but that means something different is happening to my BBB. I wrote that build to my SD card, put it in the BBB, held down s2, powered it up: U-Boot SPL 2017.01-rc3 (Apr 05 2017 - 05:21:19) Trying to boot from MMC1** First descriptor is NOT a primary desc on 0:1 ** MMC partition switch failed *** Warning - MMC partition switch failed, using default environment ** Partition 1 not valid on device 0 ** spl_register_fat_device: fat register err - -1 spl_load_image_fat: error reading image u-boot.img, err - -1 MMC partition switch failed *** Warning - MMC partition switch failed, using default environment spl: no partition table found SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ### This says U-Boot 2017.01, is that the uboot version? If I boot the BBB up without a card and halt the boot process, I get a u-boot prompt. >From there, I can check the version: U-Boot 2013.04-dirty (Jul 10 2013 - 14:02:53) arm-angstrom-linux-gnueabi-gcc (Linaro GCC 4.7-2013.02-01) 4.7.3 20130205 (prerelease) GNU ld (GNU Binutils) 2.22 Does this version need to be more recent for it to read data from the SD card? Thanks! From owner-freebsd-arm@freebsd.org Tue Apr 18 18:16:35 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C33A5D4467C for ; Tue, 18 Apr 2017 18:16:35 +0000 (UTC) (envelope-from jiashiun@gmail.com) Received: from mail-qk0-x234.google.com (mail-qk0-x234.google.com [IPv6:2607:f8b0:400d:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7AFB0F38 for ; Tue, 18 Apr 2017 18:16:35 +0000 (UTC) (envelope-from jiashiun@gmail.com) Received: by mail-qk0-x234.google.com with SMTP id d131so852135qkc.3 for ; Tue, 18 Apr 2017 11:16:35 -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:cc; bh=Zv1gYKTynLBfrAd5e5LLTbHTUmeGWQ8BMgPZQFiuKQs=; b=QnixaanRSWAQuJOqc/LzbNkeU56dxNpLCKwe0I+wrjYXhZDD8IN4/nM+00ZkLhR1yx 7qjeGoGjw58z0y5bZ5rUMLNKwtFaxngNeT/1baOYhblrA/KVVCO1RAdkwSnBwwrC/S1S ElqtotoFScMhe0sjMPmxuFt262gH/kNkkGZeS3j3RyNvKe44Nb0iymrLyLDrJpSKmuX+ 8Cz8cqOYwWpPlwbKExgVswXF9U/9r3V4R6oOBv4JYK/CYozr7VBUKE8D5cZkLd1hQino Z2rFY5jt4QCkQScrblpF0O+K53sAKE4gLL0nua/AE6fOVT8to4h887wR51MIdK4hKwhH PuTw== 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:cc; bh=Zv1gYKTynLBfrAd5e5LLTbHTUmeGWQ8BMgPZQFiuKQs=; b=Tf3Fc8XmWT/c/3dfJrMNcezy8JYCmRyOePJNyKzkOOQoduSQfTmPmUoaHPbPcxIE7b r2F4tXkjHwn/pYkeg0LTfiJPBdGeJPt9UtFjBkekCLXo03Ke4WqvL9RM0t0v1Pu0cbWq knGnXcQLkvDTextKyZ/Ny6XtwO+yG1R681Z2KjtGEJIlG13FL0RR6W9Kv3C4jvwSy0zR FFR5PMzBAr5sLRTTJImTIKBS4jZ78gLTpaDUMDfqZ4yLU2lUqCrJBBxk8l+4ekWoaFbX cMxGrfv98D2FOkr9QMWoObpdxTb0CSBYHZm9ObAHVRK/oisCXeud4cLMglNyFehLsnM1 rAkQ== X-Gm-Message-State: AN3rC/6h2haRLomFvTCtqECR0UsBXgTN5/2JVVkG9g5j0OmYlu9bcuKv 7rKoBhjrV/zogq+3XscDlrrfP0jZhw== X-Received: by 10.55.109.199 with SMTP id i190mt16159341qkc.91.1492539393879; Tue, 18 Apr 2017 11:16:33 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.98.172 with HTTP; Tue, 18 Apr 2017 11:16:03 -0700 (PDT) In-Reply-To: <585B43F7-D4C8-431A-BFFE-68B48C3214AE@dsl-only.net> References: <4DEA2D76-9F27-426D-A8D2-F07B16575FB9@dsl-only.net> <163B37B0-55D6-498E-8F52-9A95C036CDFA@dsl-only.net> <08E7A5B0-8707-4479-9D7A-272C427FF643@dsl-only.net> <20170409122715.GF1788@kib.kiev.ua> <9D152170-5F19-47A2-A06A-66F83CA88A09@dsl-only.net> <9DCAF95B-39A5-4346-88FC-6AFDEE8CF9BB@dsl-only.net> <8FFE95AA-DB40-4D1E-A103-4BA9FCC6EDEE@dsl-only.net> <89D6D677-3BE2-45E2-A902-CC6A0305F3F9@dsl-only.net> <585B43F7-D4C8-431A-BFFE-68B48C3214AE@dsl-only.net> From: Jia-Shiun Li Date: Wed, 19 Apr 2017 02:16:03 +0800 Message-ID: Subject: Re: The arm64 fork-then-swap-out-then-swap-in failures: a program source for exploring them Cc: freebsd-hackers@freebsd.org, freebsd-arm Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2017 18:16:35 -0000 just noticed that rpi3 wiki page still has outdated issue info regarding this (the jemalloc error). Anyone to help update it? https://wiki.freebsd.org/arm64/rpi3 -Jia-Shiun On Mon, Apr 10, 2017 at 5:51 PM, Mark Millard wrote: > buildworld buildkernel completed non-stop for the first time > on a BPI-M3 board. > > Looks good for a check-in to svn to me (head and stable/11). > > This combined with 2017-Feb-15's -r313772's fix to the fork > trampline code's updating of sp_el0 makes arm64 far more stable > for my purposes. > > -r313772 was never MFC'd to stable/11. In my view it should be. > > From owner-freebsd-arm@freebsd.org Tue Apr 18 19:15:06 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2ED79D44F62 for ; Tue, 18 Apr 2017 19:15:06 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-93.reflexion.net [208.70.210.93]) (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 D655428 for ; Tue, 18 Apr 2017 19:15:05 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 18504 invoked from network); 18 Apr 2017 19:08:24 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 18 Apr 2017 19:08:24 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.40.0) with SMTP; Tue, 18 Apr 2017 15:08:24 -0400 (EDT) Received: (qmail 20130 invoked from network); 18 Apr 2017 19:08:24 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 18 Apr 2017 19:08:24 -0000 Received: from [192.168.1.106] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id ED3B3EC8AB1; Tue, 18 Apr 2017 12:08:23 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Sendmail eats CPU on r317039 [after -r316874 it may be -r316951 and -r316973 are not enough to fix everything] From: Mark Millard In-Reply-To: <91A4570B-69EE-4462-9C60-205C66267599@dsl-only.net> Date: Tue, 18 Apr 2017 12:08:23 -0700 Cc: sobomax@FreeBSD.org, hrs@FreeBSD.org, freebsd-arm , FreeBSD Current Content-Transfer-Encoding: quoted-printable Message-Id: <7AD329E1-2828-42EB-9A14-B44E357CC199@dsl-only.net> References: <91A4570B-69EE-4462-9C60-205C66267599@dsl-only.net> To: ronald-lists@klop.ws X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2017 19:15:06 -0000 Ronald Klop ronald-lists at klop.ws wrote on Tue Apr 18 09:59:50 UTC = 2017: > there is a thread ono this list about a problem in syslogd which made =20= > syslog-clients (like sendmail busy-looping on logging. > That might be related to this. (it is fixed in the source already, so =20= > upgrading again might help) > See the thread with subject like 'Re: r316958: booting a server takes = >10 =20 > minutes!' >=20 > Regards, >=20 > Ronald. Yes. But Tom V.'s report is for -r317039, which is after the reported fixes as far as I can tell. Something besides syslogd might also cause problems? In my nearly-default -r317015 ardm64 context [as a VirtualBox guest] I've not seen the problem, where I did before. (The only reason sendmail runs in my context is for the messages FreeBSD sends to it own local accounts. I do not otherwise use mail in this context.) Tom V.'s report vs. others finding lack of a problem suggests that the coverage of the fixes is incomplete somehow but useful. I happen to not be doing whatever causes the problem to appear. I've no clue what might be different or unusual in Tom V.'s context. There is also the possibility that Tom V.'s report is a fully = independent issue. But such does not seem all that likely on the initial = information. > On 2017-Apr-17, at 7:57 AM, Mark Millard = wrote: >=20 >> Just an FYI of a more recent report of runaway sendmail on a >> more recent system version ( -r317039 ): >>=20 >> Begin forwarded message: >>=20 >>> From: Tom Vijlbrief >>> Subject: Sendmail eats CPU on r317039 >>> Date: April 17, 2017 at 3:39:37 AM PDT >>> To: "freebsd-current at freebsd.org" , freebsd-arm >>>=20 >>> On a recent kernel sendmail is constantly consuming CPU. >>>=20 >>> truss -p PID >>>=20 >>> shows: >>>=20 >>> sendto(3,"<22>Apr 17 10:30:33 sendmail[362"...,163,0x0,NULL,0) = ERR#55 'No >>> buffer space available' >>> nanosleep({ 0.000001000 }) =3D 0 (0x0) >>> sendto(3,"<22>Apr 17 10:30:33 sendmail[362"...,163,0x0,NULL,0) = ERR#55 'No >>> buffer space available' >>> nanosleep({ 0.000001000 }) >>> ... >>>=20 >>> This is on an arm64 system >>=20 >> Analysis of Tom V.'s context for this may be required. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Wed Apr 19 03:11:01 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C6380D45BD9 for ; Wed, 19 Apr 2017 03:11:01 +0000 (UTC) (envelope-from otacilio.neto@bsd.com.br) Received: from mail-qt0-x230.google.com (mail-qt0-x230.google.com [IPv6:2607:f8b0:400d:c0d::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8C809EDD for ; Wed, 19 Apr 2017 03:11:00 +0000 (UTC) (envelope-from otacilio.neto@bsd.com.br) Received: by mail-qt0-x230.google.com with SMTP id y33so9543031qta.2 for ; Tue, 18 Apr 2017 20:11:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsd.com.br; s=capeta; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding; bh=1QSb+C//MRNET3p6ijUdtY0EyO2uddmVm6erb1Nq6M4=; b=c6GHE0kBArqk3DX1zgwjp76VYhCT3HZv8mg5A9bTzAeyhi0X6mos69RBpidNwkSnt5 0TBHyXIiB68GmIvZQaFcfl8nzRA8yfJKl434B7OROysN9MqldQmlbdfWxRps0Wdz2fD/ bht/rOGBJFEZlWYOm5a3vLS5KtTM0sbDk9CCI= 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:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=1QSb+C//MRNET3p6ijUdtY0EyO2uddmVm6erb1Nq6M4=; b=Z7QyIZ9oytHmnIpIlOpfjFysPh61tkt0hpmC6uA3AZF13QRUYyWAs5r+PQt/dPMFl2 NSUDYjckQXixE0T/520qbBSp6IRnWFRwj4twXGhvYAPESNjKGErUDbstpG7FcbbD3oou DHDRKbLzTVMAbvNDJwkwQpyYO6pjHRc5oRLy6sBizKBYYeLE1BmesuEyA7pHL3HWpl5U z3WDAN7V1HMCP+KRLGd7ukMfX4W7b+2Byt+493GhH4oSCh/Ahv1pFikz/8S9ZGXU6BWj Q4wdNxNdlz4s50bMDidzhyNZmHicZW/al7AwBGQrvDAzDrw4im0Y3NkCxcA7tFUtt73u x44Q== X-Gm-Message-State: AN3rC/5VSwVolk94tut6sauWa9fM6gqTSbwDG7YNk0WPUqX+l4SvZ82R Ewyh8wfni6LoNk4I X-Received: by 10.200.57.73 with SMTP id t9mr516407qtb.182.1492571459997; Tue, 18 Apr 2017 20:10:59 -0700 (PDT) Received: from ?IPv6:2804:54:19ef:cc00:ec2a:e594:b7c4:c7d3? ([2804:54:19ef:cc00:ec2a:e594:b7c4:c7d3]) by smtp.googlemail.com with ESMTPSA id l7sm952651qtf.24.2017.04.18.20.10.58 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 18 Apr 2017 20:10:59 -0700 (PDT) To: "freebsd-arm@freebsd.org" From: =?UTF-8?B?T3RhY8OtbGlv?= Subject: HEAD on RPI3 Message-ID: Date: Wed, 19 Apr 2017 00:10:52 -0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2017 03:11:01 -0000 Dears Someone that is using HEAD on a Raspberry PI3 can tell me the revision that is using? Thank you very much []'s -Otacilio From owner-freebsd-arm@freebsd.org Wed Apr 19 05:39:38 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CCC69D4540B for ; Wed, 19 Apr 2017 05:39:38 +0000 (UTC) (envelope-from b.16012508@edmmessage.com) Received: from mail28.wt1.edmmessage.com (mail28.wt1.edmmessage.com [101.78.203.28]) (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 F331C171B for ; Wed, 19 Apr 2017 05:39:37 +0000 (UTC) (envelope-from b.16012508@edmmessage.com) Received: from 101.78.203.28 (mail28.wt1.edmmessage.com [101.78.203.28]) by mail28.wt1.edmmessage.com (Postfix) with ESMTP id 4E033217C24 for ; Wed, 19 Apr 2017 13:39:36 +0800 (HKT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; t=1492580376; s=default; d=edmmessage.com; h=Date:From:Reply-To:To:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding; bh=bNiLTfOnaW/uDz+UjVRdx+aeKpHqoCU6pGp5687JBi0=; b=V9C+0d1p9wNn59/wbrEtSdS8cYmHSLzxYEuAPP1JIU4cAaUxq9g8x4i3bxHhX+W0 0HdZUIxgj+a6WU3JukJPXB8B5jDq3rafnp+sHGoOyyoypda2nG5vmXHOhavnP+7zmlm JK4lIp7cb4gXgR8ZRuiaBC9bYibeWYMw0ozh63DI= Date: Wed, 19 Apr 2017 13:39:36 +0800 (HKT) From: "jhie.powermax" Reply-To: "jhie.powermax" To: JHIE-07-YMLP Message-ID: <2121825720.6598968.1492580376318.JavaMail.tomcat@wt2> Subject: eBIR FORMS and 2017 Tax Updates - May 5 Errors-To: b.16012508@edmmessage.com X-Content-ID: nEd7sLMsTUlbvTZiji+C3Rp74StLtLMDcZAM17sTFQruDDlFOpcpETBcRS5SO+rC67hV7N25Yg+4App2OWCaYx0YL2pBNWdiI4cGq1ek3tQ866/fdikIBzzJ+TNbz7M0 Feedback-ID: 818157166346254:691887480124289:008494288642614:edmmessage.com MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2017 05:39:38 -0000 From owner-freebsd-arm@freebsd.org Wed Apr 19 07:11:23 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EE93DD44E72; Wed, 19 Apr 2017 07:11:23 +0000 (UTC) (envelope-from tvijlbrief@gmail.com) Received: from mail-yw0-x22d.google.com (mail-yw0-x22d.google.com [IPv6:2607:f8b0:4002:c05::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 A589C351; Wed, 19 Apr 2017 07:11:23 +0000 (UTC) (envelope-from tvijlbrief@gmail.com) Received: by mail-yw0-x22d.google.com with SMTP id k13so6670711ywk.1; Wed, 19 Apr 2017 00:11:23 -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=F7vU/zIPm/+iWyy7LV1oUJjzZ6ylvvnIIH0nuPXQy9A=; b=ADqkC2xkmRaN+/JOuGCH7NB7Op7ZktdWYHWtTb07VMbk3neU4ayybJ9v25FXwBzE90 aFoaE3PGGKTA2qZiHz7wyiHkLb0/CedWMlzyZInGKWM/McBv1li0J3WkpyCn9e6HF3xx +BHwMWZIIHb2/k5G685XzG/C5NcRkzlQE0z59JJN1WqQOA/xfNDJk71ObyGn771hATkz oup6+YSN/uUazfmzNFk5tNrRXxJMJNCm2wfLOwc1b5NNqt1n08V8JdvL1y50LzqXc3pZ cUx6736YIYFu73f+qmwloBifJholk9uzDZbQD6dpuz9EkrlX53Z6gpJR2KXO2x2wMlF8 4/8w== 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=F7vU/zIPm/+iWyy7LV1oUJjzZ6ylvvnIIH0nuPXQy9A=; b=mc5cmVMloWG9sBzUmp3YCruoaYUbe3VhCrQTvfKM2tU8fls7wSXfdxkTsw22gB+bma e73RIjHLp3jLCX+vQHqEZCUzt94KFc8CeyCKqPCj94YkwY7PPgKHU3I9u4KQ+h4c9DMj T9oyOM0y1TU/iNN3Bw4QDs6Fxf1yvTPv34mrxkqVP/4e8uCj5cH6P7anGvcMKhnDRvr5 RdsWTnM5jjJy5r84MvK4kzZGhmbPKYGwefVM7JtkCLWunxIxc0OyZpbotr2OLct6fKtO oMFft65Iz6v0+DW0b/AgncV90NNOY6IgB2soLG0AvhhNZQ8wlQ4sE9L6FlufBmS8e/RF wjAw== X-Gm-Message-State: AN3rC/4llB3CEnXvg24kQOZ9X4tF3R49ITHOejUwSZAM4OWP2m3GQY4d CsUEKbBRQUEPOdSd+VbZlqKWtJK1uUH6 X-Received: by 10.13.199.196 with SMTP id j187mr876819ywd.197.1492585882789; Wed, 19 Apr 2017 00:11:22 -0700 (PDT) MIME-Version: 1.0 References: <91A4570B-69EE-4462-9C60-205C66267599@dsl-only.net> <7AD329E1-2828-42EB-9A14-B44E357CC199@dsl-only.net> In-Reply-To: <7AD329E1-2828-42EB-9A14-B44E357CC199@dsl-only.net> From: Tom Vijlbrief Date: Wed, 19 Apr 2017 07:11:12 +0000 Message-ID: Subject: Re: Sendmail eats CPU on r317039 [after -r316874 it may be -r316951 and -r316973 are not enough to fix everything] To: Mark Millard , ronald-lists@klop.ws Cc: sobomax@freebsd.org, freebsd-arm , FreeBSD Current Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2017 07:11:24 -0000 I'm currently rebuilding world and kernel on a just completed SVN checkout. Note that the normal sendmail daemon which listens for incoming traffic does NOT loop. The sendmail instance which tries local delivery (echo Hi | mail root) or the msp_queue instance is looping. It might be an arm64 specific issue, but a few weeks ago this was not an issue. Op di 18 apr. 2017 om 21:15 schreef Mark Millard : > Ronald Klop ronald-lists at klop.ws wrote on Tue Apr 18 09:59:50 UTC 2017: > > > there is a thread ono this list about a problem in syslogd which made > > syslog-clients (like sendmail busy-looping on logging. > > That might be related to this. (it is fixed in the source already, so > > upgrading again might help) > > See the thread with subject like 'Re: r316958: booting a server takes >10 > > minutes!' > > > > Regards, > > > > Ronald. > > > Yes. But Tom V.'s report is for -r317039, which is after the reported > fixes as far as I can tell. Something besides syslogd might also cause > problems? > > In my nearly-default -r317015 ardm64 context [as a VirtualBox guest] > I've not seen the problem, where I did before. (The only reason sendmail > runs in my context is for the messages FreeBSD sends to it own local > accounts. I do not otherwise use mail in this context.) > > Tom V.'s report vs. others finding lack of a problem suggests that the > coverage of the fixes is incomplete somehow but useful. I happen to not > be doing whatever causes the problem to appear. I've no clue what might > be different or unusual in Tom V.'s context. > > There is also the possibility that Tom V.'s report is a fully independent > issue. But such does not seem all that likely on the initial information. > > > > On 2017-Apr-17, at 7:57 AM, Mark Millard wrote: > > > >> Just an FYI of a more recent report of runaway sendmail on a > >> more recent system version ( -r317039 ): > >> > >> Begin forwarded message: > >> > >>> From: Tom Vijlbrief > >>> Subject: Sendmail eats CPU on r317039 > >>> Date: April 17, 2017 at 3:39:37 AM PDT > >>> To: "freebsd-current at freebsd.org" , > freebsd-arm > >>> > >>> On a recent kernel sendmail is constantly consuming CPU. > >>> > >>> truss -p PID > >>> > >>> shows: > >>> > >>> sendto(3,"<22>Apr 17 10:30:33 sendmail[362"...,163,0x0,NULL,0) ERR#55 > 'No > >>> buffer space available' > >>> nanosleep({ 0.000001000 }) = 0 (0x0) > >>> sendto(3,"<22>Apr 17 10:30:33 sendmail[362"...,163,0x0,NULL,0) ERR#55 > 'No > >>> buffer space available' > >>> nanosleep({ 0.000001000 }) > >>> ... > >>> > >>> This is on an arm64 system > >> > >> Analysis of Tom V.'s context for this may be required. > > === > Mark Millard > markmi at dsl-only.net > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > From owner-freebsd-arm@freebsd.org Wed Apr 19 10:52:02 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AC9FBD44220 for ; Wed, 19 Apr 2017 10:52:02 +0000 (UTC) (envelope-from b.16012507@edmmessage.com) Received: from mail28.wt1.edmmessage.com (mail28.wt1.edmmessage.com [101.78.203.28]) (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 D63171702 for ; Wed, 19 Apr 2017 10:52:01 +0000 (UTC) (envelope-from b.16012507@edmmessage.com) Received: from 101.78.203.28 (mail28.wt1.edmmessage.com [101.78.203.28]) by mail28.wt1.edmmessage.com (Postfix) with ESMTP id 30873205396 for ; Wed, 19 Apr 2017 18:52:00 +0800 (HKT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; t=1492599120; s=default; d=edmmessage.com; h=Date:From:Reply-To:To:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding; bh=SYPBQW11VpDzeOeV2T9BjCYMfvQvrqPMffOIL+R2/3E=; b=TSgqc4ujxAISjjmkRJHnTnx5HrdXD+HnL7l2pmy04jFesVeV6W2sWaviMAbcf/KU dyR4Z+2/soX9ilpnS/SAbNz/bQoDaZQ1dz28tn3BZi6/OprOTxMqNz8Z78mYOqtndXV mur669D7Ccf1ImysnaDO67wGKDseIENZtKMDnxnw= Date: Wed, 19 Apr 2017 18:52:00 +0800 (HKT) From: "jhie.powermax" Reply-To: "jhie.powermax" To: JHIE-07-YMLP Message-ID: <518474622.6736402.1492599120198.JavaMail.tomcat@wt2> Subject: LAST CALL: Maximizing Productivity in Warehouse Management - May 4 Errors-To: b.16012507@edmmessage.com X-Content-ID: b9oJqFZalmIvJu28ix9Ap2yzl+X0ALNqcZAM17sTFQruDDlFOpcpETBcRS5SO+rC67hV7N25Yg+4App2OWCaYx0YL2pBNWdiI4cGq1ek3tQ866/fdikIBzzJ+TNbz7M0 Feedback-ID: 818157166346254:940156826202516:008494288642614:edmmessage.com MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2017 10:52:02 -0000 From owner-freebsd-arm@freebsd.org Wed Apr 19 12:22:57 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2D9BCD45D4A for ; Wed, 19 Apr 2017 12:22:57 +0000 (UTC) (envelope-from andrew@fubar.geek.nz) Received: from fry.fubar.geek.nz (fry.fubar.geek.nz [139.59.165.16]) by mx1.freebsd.org (Postfix) with ESMTP id 00A511984 for ; Wed, 19 Apr 2017 12:22:56 +0000 (UTC) (envelope-from andrew@fubar.geek.nz) Received: from [10.0.0.68] (host81-149-102-120.in-addr.btopenworld.com [81.149.102.120]) by fry.fubar.geek.nz (Postfix) with ESMTPSA id CEF804E737 for ; Wed, 19 Apr 2017 10:20:45 +0000 (UTC) From: Andrew Turner Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: HEADSUP: Removal of the ARMADAXP kernel config Message-Id: <97B5F7E6-698A-47EC-84C2-AB825F65FB8B@fubar.geek.nz> Date: Wed, 19 Apr 2017 11:20:41 +0100 To: freebsd-arm@freebsd.org X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2017 12:22:57 -0000 One month ago I proposed to make INTRNG a requirement on armv6 with a = list of kernel configurations that failed to build when this is the = case. Since then most of these configurations have either been fixed, or = have a fix in review, however there is one configuration left, ARMADAXP. As nobody has written patches, or even commented they will be working on = them I have to assume this code is unmaintained and holding back the = rest of FreeBSD/armv6. As such I will be removing the kernel config next = week to make way for enabling INTRNG by default on armv6.=20 If someone makes a serious proposal that they are willing to port this = to INTRNG I will hold off, however I would expect to see some progress = on this soon as to not hold back further cleanups in the code. Andrew= From owner-freebsd-arm@freebsd.org Wed Apr 19 12:33:51 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F1EBBD44513; Wed, 19 Apr 2017 12:33:51 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5571B36C; Wed, 19 Apr 2017 12:33:50 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from freyja.zeit4.iv.bundesimmobilien.de ([87.138.105.249]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0Lp3x6-1cMFKK1evk-00eqXR; Wed, 19 Apr 2017 14:33:48 +0200 Date: Wed, 19 Apr 2017 14:33:42 +0200 From: "O. Hartmann" To: freebsd-ports , freebsd-arm@freebsd.org Subject: poudriere: crossbuilding for arm64 fails: pkg-static: No package files have been found Message-ID: <20170419143342.17c190b9@freyja.zeit4.iv.bundesimmobilien.de> Organization: Walstatt X-Mailer: Claws Mail 3.15.0 (GTK+ 2.24.31; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:VFH3RXpUjXD0e/+ZzO8dEtrHESVlUqIut27c43rq4o63hHFAAsM ry1jc516eiZGXBHlRJhbSp+fg469DaPHtZwQ23NnsP/ClXhpAFY0vBhEwQ3+fsgcYukxlI9 i4tYzSebGeaScEJQk4iNNxCFfEgalhMGBkKcSFm0DZwI7cqezW9U1BTbX2f56oFRqud3M+b l9ncuQfuc48C6KeyfjHHg== X-UI-Out-Filterresults: notjunk:1;V01:K0:hieRvkK6Zk0=:ajh/BZUqFKaezMs0uQILFy FZRVeCJnXKAERc2VRVaxQ1oKTlLZn1hQtIIHAKsxLYbPMbKYh5hZuNdTExzHzJsFErHuQqd/g Q7guUg3vNbyf5hSYI30rfQnmug70zCy6ORso/k1jIZ6haO8eO8ZO6+KU4fr/rmERQGWc36xv1 JGdxVqnvprwCmIWgmT1uB00Pv81r6bxC4MUbyyZ9qXyQDjNcY0urN76vjCFHv0gM2rxUk0j/l 39x1GmuffO2rVUCSS4wPXO2MaDsEAdiA3k4PaJWHvWQZRujAgwcsA+rEZjXNKlRnaBZvqSFdC FRGqpKfpbMxwTooo2qZDBic5W2JrLn9boZoyiifYHxoqErmO8PAhU1d/2bf7BjqzVn+nVzC03 Ld62ysqbmfq+ir/PSQhO3bNoeUDhI8SCVk261+Cm8SmXYcDtrG2dS6853Mi7LGm7V2t+PKLz7 A1d3degoku+zamDQIHpDhczhxY/KBXxWLDQ5fcipfsPI4AhQ/Pi1DKHIdn29OHLtaQEJipGsK b2UMr09ssH+O4+jblCOqAYHRKMzblKSJp9WWZYkaPkHS9SxxolFxNrZvJfKkok+lDYO3m8D0E fJyu7DOnDj3L0bxWamQ+bfoA9SxIw1k2STaamo29cHGY8h8NsvpZpz3BwtWIZNH5vfzATFGRM Uty30CIVqmdsjMGqXzpWZxkzaOglztZZ8d10Ql/fRhHLMrtBTrgmIwTSLiP8jnbGh3zWPF/kq 9X8L/mX6hbJ3NrUQ6kdQtgDsaxPdvA4V8c+wd4xnqWve4CCkxYPbqdKglkaYzGHPRelTRqO6S loJugFQ X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2017 12:33:52 -0000 Trying to build a repository via poudriere fails on recent 12-CURRENT (FreeBSD 12.0-CURRENT #2 r317090: Tue Apr 18 15:32:23 CEST 2017 amd64) initially with failing to build ports-mgmt/pkg. poudriere's log reports: [...] configure: error: in `/wrkdirs/usr/ports/ports-mgmt/pkg/work/pkg-1.10.1': configure: error: C compiler cannot create executables Well, I'm running "home brewn jail" which means that I successfully cross compiled the 12-CURRENT sources as "TARGET=arm64" and having the obj tree resulting from this build installed as jail. While installing the jail, I also included the knob "-x" to "poudriere jail -c -a arm64.aarch64". The port emulators/qemu-user-static is installed and the kernel module is loaded successfully. Ports tree and /usr/src are up to date as of today, additinally, I rebuilt the qemu emulator and reloaded the kernel module to ensure nothing goes wrong there. When starting the poudriere build, QEMU reports no issues, but after starting to build ports-mgmt/pkg, I receive the error shown above. By the way, CROSS_BINUTILS_PREFIX is not set anywhere in poudriere's config files, nor do I set this variable in the environment as I think this is set via the .mk scripts according to settings of "TARGET=" for ARM/ARM64 cross compiling. So, what is going wrong here? Does anyone have an idea? Thanks in advance, Oliver p.s. Please CC me! From owner-freebsd-arm@freebsd.org Wed Apr 19 19:15:40 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 25315D4642B for ; Wed, 19 Apr 2017 19:15:40 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-185.reflexion.net [208.70.211.185]) (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 C9C631447 for ; Wed, 19 Apr 2017 19:15:39 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 5640 invoked from network); 19 Apr 2017 17:28:58 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 19 Apr 2017 17:28:58 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.40.0) with SMTP; Wed, 19 Apr 2017 13:28:58 -0400 (EDT) Received: (qmail 21793 invoked from network); 19 Apr 2017 17:28:58 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 19 Apr 2017 17:28:58 -0000 Received: from [192.168.1.106] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 65AAEEC7901; Wed, 19 Apr 2017 10:28:57 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: The arm64 fork-then-swap-out-then-swap-in failures: a program source for exploring them From: Mark Millard In-Reply-To: Date: Wed, 19 Apr 2017 10:28:56 -0700 Cc: freebsd-hackers@freebsd.org, freebsd-arm Content-Transfer-Encoding: 7bit Message-Id: <7D72C3EF-8F77-4701-93C9-1488072215FC@dsl-only.net> References: <4DEA2D76-9F27-426D-A8D2-F07B16575FB9@dsl-only.net> <163B37B0-55D6-498E-8F52-9A95C036CDFA@dsl-only.net> <08E7A5B0-8707-4479-9D7A-272C427FF643@dsl-only.net> <20170409122715.GF1788@kib.kiev.ua> <9D152170-5F19-47A2-A06A-66F83CA88A09@dsl-only.net> <9DCAF95B-39A5-4346-88FC-6AFDEE8CF9BB@dsl-only.net> <8FFE95AA-DB40-4D1E-A103-4BA9FCC6EDEE@dsl-only.net> <89D6D677-3BE2-45E2-A902-CC6A0305F3F9@dsl-only.net> <585B43F7-D4C8-431A-BFFE-68B48C3214AE@dsl-only.net> To: Jia-Shiun Li X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2017 19:15:40 -0000 On 2017-Apr-18, at 11:16 AM, Jia-Shiun Li wrote: > just noticed that rpi3 wiki page still has outdated issue info regarding > this (the jemalloc error). Anyone to help update it? > > https://wiki.freebsd.org/arm64/rpi3 stable/11 is still in process for the fork handling fixes. One of the 2 fixes to fork behavior has just been MFC'd: -r313772 from head is now -r317147 in stable/11 . So interrupts will no longer trash the sp_el0 register. There is still -r316679 from head to go so that Copy-On-Write would work for fork. (The defect may be more general than just being for fork.) > -Jia-Shiun > > On Mon, Apr 10, 2017 at 5:51 PM, Mark Millard wrote: > >> buildworld buildkernel completed non-stop for the first time >> on a BPI-M3 board. >> >> Looks good for a check-in to svn to me (head and stable/11). >> >> This combined with 2017-Feb-15's -r313772's fix to the fork >> trampline code's updating of sp_el0 makes arm64 far more stable >> for my purposes. >> >> -r313772 was never MFC'd to stable/11. In my view it should be. === Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Thu Apr 20 00:09:37 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B5967D46F51 for ; Thu, 20 Apr 2017 00:09:37 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-187.reflexion.net [208.70.211.187]) (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 6B9E5808 for ; Thu, 20 Apr 2017 00:09:37 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 28097 invoked from network); 20 Apr 2017 00:12:40 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 20 Apr 2017 00:12:40 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.40.0) with SMTP; Wed, 19 Apr 2017 20:09:35 -0400 (EDT) Received: (qmail 28230 invoked from network); 20 Apr 2017 00:09:35 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 20 Apr 2017 00:09:35 -0000 Received: from [192.168.1.106] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id CCB1DEC805D; Wed, 19 Apr 2017 17:09:34 -0700 (PDT) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: FYI on aarch64: building and installing devel/aarch64-gcc fails with "Unable to access file" for 6 files Message-Id: <921E1189-B07D-4BFA-873B-9C2DF195D771@dsl-only.net> Date: Wed, 19 Apr 2017 17:09:34 -0700 To: FreeBSD Toolchain , freebsd-arm X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2017 00:09:37 -0000 The attempt to build & install devel/aarch64-gcc on a aarch64 = environment gets (I use WRKDIRPREFIX=3D/usr/obj/portswork ): =3D=3D=3D> Installing for aarch64-gcc-6.3.0 =3D=3D=3D> Checking if aarch64-gcc already installed =3D=3D=3D> Registering installation for aarch64-gcc-6.3.0 as automatic pkg-static: Unable to access file = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/bin/aa= rch64-unknown-freebsd12.0-gcov:No such file or directory pkg-static: Unable to access file = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/bin/aa= rch64-unknown-freebsd12.0-gcov-tool:No such file or directory pkg-static: Unable to access file = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/man/ma= n1/aarch64-unknown-freebsd12.0-cpp.1.gz:No such file or directory pkg-static: Unable to access file = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/man/ma= n1/aarch64-unknown-freebsd12.0-g++.1.gz:No such file or directory pkg-static: Unable to access file = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/man/ma= n1/aarch64-unknown-freebsd12.0-gcc.1.gz:No such file or directory pkg-static: Unable to access file = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/man/ma= n1/aarch64-unknown-freebsd12.0-gcov.1.gz:No such file or directory *** Error code 74 Stop. make: stopped in /usr/ports/devel/aarch64-gcc =3D=3D=3D>>> Installation of aarch64-gcc-6.3.0 (devel/aarch64-gcc) = failed A hack before doing a portmaster -CDK lang/aarch64-gcc to continue the build/install is to execute the script shown below (I use WRKDIRPREFIX=3D/usr/obj/portswork ): # more ~/aarch64-gcc_fixup.sh=20 #!/bin/sh cp -ax = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/.build/gcc/gcov = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/bin/aa= rch64-unknown-freebsd12.0-gcov cp -ax = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/.build/gcc/gcov-tool = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/bin/aa= rch64-unknown-freebsd12.0-gcov-tool gzip -c = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/gcc-*/gcc/doc/cpp.1 = > = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/man/ma= n1/aarch64-unknown-freebsd12.0-cpp.1.gz gzip -c = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/.build/gcc/doc/g++.1 = > = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/man/ma= n1/aarch64-unknown-freebsd12.0-g++.1.gz gzip -c = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/.build/gcc/doc/gcc.1 = > = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/man/ma= n1/aarch64-unknown-freebsd12.0-gcc.1.gz gzip -c = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/gcc-*/gcc/doc/gcov.1 = > = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/man/ma= n1/aarch64-unknown-freebsd12.0-gcov.1.gz That puts in place the files that are not where they are expected. Of course this sort of hack-then-continue would not fit well with poudriere use or analogous build techniques. The same sort of thing happens for lang/powerpc64 on a powerpc64 environment. As I remember. . . The same sort of thing happens for lang/amd64 on a amd64 environment. So I have ~/powerpc64-gcc_fixup.sh and ~/amd64-gcc_fixup.sh as well. I get to these ???-gcc's by trying to install a self-hosted lang/???-xtoolchain-gcc in each case. Such allows for experimenting with self-hosted gcc based system builds that are libc++ based (instead of using gcc 4.2.1). =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Thu Apr 20 01:30:00 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E03A8D46B06; Thu, 20 Apr 2017 01:30:00 +0000 (UTC) (envelope-from jbeich@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 C158417ED; Thu, 20 Apr 2017 01:30:00 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1354) id DC5EF14DD; Thu, 20 Apr 2017 01:29:59 +0000 (UTC) From: Jan Beich To: "O. Hartmann" Cc: freebsd-ports , freebsd-arm@freebsd.org Subject: Re: poudriere: crossbuilding for arm64 fails: pkg-static: No package files have been found References: <20170419143342.17c190b9@freyja.zeit4.iv.bundesimmobilien.de> Date: Thu, 20 Apr 2017 03:29:56 +0200 In-Reply-To: <20170419143342.17c190b9@freyja.zeit4.iv.bundesimmobilien.de> (O. Hartmann's message of "Wed, 19 Apr 2017 14:33:42 +0200") Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2017 01:30:01 -0000 "O. Hartmann" writes: > Trying to build a repository via poudriere fails on recent 12-CURRENT (FreeBSD > 12.0-CURRENT #2 r317090: Tue Apr 18 15:32:23 CEST 2017 amd64) initially with > failing to build ports-mgmt/pkg. > > poudriere's log reports: > > [...] > configure: error: in `/wrkdirs/usr/ports/ports-mgmt/pkg/work/pkg-1.10.1': > configure: error: C compiler cannot create executables Probably https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217189 From owner-freebsd-arm@freebsd.org Thu Apr 20 01:33:25 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D1C98D46135 for ; Thu, 20 Apr 2017 01:33:25 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-189.reflexion.net [208.70.211.189]) (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 81F571D15 for ; Thu, 20 Apr 2017 01:33:25 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 16123 invoked from network); 20 Apr 2017 01:26:44 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 20 Apr 2017 01:26:44 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.40.0) with SMTP; Wed, 19 Apr 2017 21:26:44 -0400 (EDT) Received: (qmail 23924 invoked from network); 20 Apr 2017 01:26:44 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 20 Apr 2017 01:26:44 -0000 Received: from [192.168.1.106] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id BFFAEEC8663; Wed, 19 Apr 2017 18:26:43 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: HEAD on RPI3 From: Mark Millard In-Reply-To: Date: Wed, 19 Apr 2017 18:26:43 -0700 Cc: "freebsd-arm@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: <244BD33F-67B0-4C47-84E4-FD4B485689D1@dsl-only.net> References: To: =?utf-8?B?T3RhY8OtbGlv?= X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2017 01:33:25 -0000 On 2017-Apr-18, at 8:10 PM, Otac=C3=ADlio = wrote: > Dears >=20 > Someone that is using HEAD on a Raspberry PI3 can tell me the revision = that is using? >=20 > Thank you very much >=20 > []'s >=20 > -Otacilio Starting with the sysutils/u-boot-rpi3 installed: # ls -l /boot/efi total 7540 drwxr-xr-x 1 root wheel 4096 Mar 18 05:26 EFI -rwxr-xr-x 1 root wheel 1494 Mar 18 05:26 LICENCE.broadcom -rwxr-xr-x 1 root wheel 123 Mar 18 05:26 README -rwxr-xr-x 1 root wheel 6144 Mar 18 05:26 armstub8.bin -rwxr-xr-x 1 root wheel 17480 Mar 18 05:26 bcm2710-rpi-3-b.dtb -rwxr-xr-x 1 root wheel 17932 Mar 18 05:26 bootcode.bin -rwxr-xr-x 1 root wheel 137 Mar 18 05:26 config.txt -rwxr-xr-x 1 root wheel 6482 Mar 18 05:26 fixup.dat -rwxr-xr-x 1 root wheel 2504 Mar 18 05:26 fixup_cd.dat -rwxr-xr-x 1 root wheel 9716 Mar 18 05:26 fixup_x.dat drwxr-xr-x 1 root wheel 4096 Mar 18 05:26 overlays -rwxr-xr-x 1 root wheel 2747896 Mar 18 05:26 start.elf -rwxr-xr-x 1 root wheel 618296 Mar 18 05:26 start_cd.elf -rwxr-xr-x 1 root wheel 3879416 Mar 18 05:26 start_x.elf -rwxr-xr-x 1 root wheel 9 Mar 18 05:26 startup.nsh -rwxr-xr-x 1 root wheel 369456 Mar 18 05:26 u-boot.bin # ls -l /boot/efi/overlays/ total 8 -rwxr-xr-x 1 root wheel 1053 Mar 18 05:26 mmc.dtbo -rwxr-xr-x 1 root wheel 818 Mar 18 05:26 pi3-disable-bt.dtbo So this is from before the sysutils/u-boot-rpi3 -r436197 (2017-Mar-29) that was for: Do not overwrite WRKSRC when USE_GITHUB=3Dnodefault. but is from -r433351 instead (2017-Feb-5 check-in). To update I generally buildworld and buildkernel from source and install them, not doing anything with sysutils/u-boot-rpi3 unless something significant seems to have come along for u-boot. I just updated from head -r314687 to -r317015 : # uname -paKU FreeBSD rpi3 12.0-CURRENT FreeBSD 12.0-CURRENT r317015M arm64 aarch64 = 1200028 1200028 =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Thu Apr 20 07:13:06 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D78B9D47AA2 for ; Thu, 20 Apr 2017 07:13:06 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-187.reflexion.net [208.70.211.187]) (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 87459CBF for ; Thu, 20 Apr 2017 07:13:05 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 27095 invoked from network); 20 Apr 2017 07:13:04 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 20 Apr 2017 07:13:04 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.40.0) with SMTP; Thu, 20 Apr 2017 03:13:04 -0400 (EDT) Received: (qmail 6175 invoked from network); 20 Apr 2017 07:13:04 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 20 Apr 2017 07:13:04 -0000 Received: from [192.168.1.106] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 89504EC805D; Thu, 20 Apr 2017 00:13:03 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: The arm64 fork-then-swap-out-then-swap-in failures: a program source for exploring them From: Mark Millard In-Reply-To: <7D72C3EF-8F77-4701-93C9-1488072215FC@dsl-only.net> Date: Thu, 20 Apr 2017 00:13:03 -0700 Cc: freebsd-hackers@freebsd.org, freebsd-arm Content-Transfer-Encoding: quoted-printable Message-Id: <89EA7C2B-0AE8-4E99-A1A6-4BDE9CD4D343@dsl-only.net> References: <4DEA2D76-9F27-426D-A8D2-F07B16575FB9@dsl-only.net> <163B37B0-55D6-498E-8F52-9A95C036CDFA@dsl-only.net> <08E7A5B0-8707-4479-9D7A-272C427FF643@dsl-only.net> <20170409122715.GF1788@kib.kiev.ua> <9D152170-5F19-47A2-A06A-66F83CA88A09@dsl-only.net> <9DCAF95B-39A5-4346-88FC-6AFDEE8CF9BB@dsl-only.net> <8FFE95AA-DB40-4D1E-A103-4BA9FCC6EDEE@dsl-only.net> <89D6D677-3BE2-45E2-A902-CC6A0305F3F9@dsl-only.net> <585B43F7-D4C8-431A-BFFE-68B48C3214AE@dsl-only.net> <7D72C3EF-8F77-4701-93C9-1488072215FC@dsl-only.net> To: Jia-Shiun Li X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2017 07:13:06 -0000 On 2017-Apr-19, at 10:28 AM, Mark Millard wrote: > On 2017-Apr-18, at 11:16 AM, Jia-Shiun Li wrote: >=20 >> just noticed that rpi3 wiki page still has outdated issue info = regarding >> this (the jemalloc error). Anyone to help update it? >>=20 >> https://wiki.freebsd.org/arm64/rpi3 >=20 > stable/11 is still in process for the fork handling fixes. >=20 > One of the 2 fixes to fork behavior has just been MFC'd: > -r313772 from head is now -r317147 in stable/11 . So > interrupts will no longer trash the sp_el0 register. >=20 > There is still -r316679 from head to go so that > Copy-On-Write would work for fork. (The defect > may be more general than just being for fork.) >=20 >> -Jia-Shiun >>=20 >> On Mon, Apr 10, 2017 at 5:51 PM, Mark Millard = wrote: >>=20 >>> buildworld buildkernel completed non-stop for the first time >>> on a BPI-M3 board. >>>=20 >>> Looks good for a check-in to svn to me (head and stable/11). >>>=20 >>> This combined with 2017-Feb-15's -r313772's fix to the fork >>> trampline code's updating of sp_el0 makes arm64 far more stable >>> for my purposes. >>>=20 >>> -r313772 was never MFC'd to stable/11. In my view it should be. Another head-vintage-specific rpi3 note on: https://wiki.freebsd.org/arm64/rpi3 is where it says: If you want to build your own ports or packages, you'll need to install = the aarch64-binutils package and link /usr/bin/ld to = /usr/local/bin/aarch64-freebsd-ld:=20 # pkg install aarch64-binutils # ln /usr/local/bin/aarch64-freebsd-ld /usr/bin/ld But using WITH_LLD_IS_LD=3D for an aarch64 buildworld now provides an aarch64 system ld that works for many things. This is now the default for aarch64. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Thu Apr 20 09:31:52 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 93A24D47A09; Thu, 20 Apr 2017 09:31:52 +0000 (UTC) (envelope-from tvijlbrief@gmail.com) Received: from mail-yw0-x232.google.com (mail-yw0-x232.google.com [IPv6:2607:f8b0:4002:c05::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 4F9D773; Thu, 20 Apr 2017 09:31:52 +0000 (UTC) (envelope-from tvijlbrief@gmail.com) Received: by mail-yw0-x232.google.com with SMTP id u70so35947254ywe.2; Thu, 20 Apr 2017 02:31: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=ZnevUaJhp8o+62+JbDvqcEAzUqPJMpxIZKO2zCCXoLY=; b=jLkzL0Yi+mubmGgdD2rrZt3aaaGl8f9i7tyDtiuu2WxJRuZs5vG9hkc93senxFb1f/ roCkoRwI5nUgyn1DpFAvRzDld07TXDME2n/u+muDVemaom4UbIofuPi1Ellt4qoP0+/P UdJ/qAFwGEiARIjLGrRFI/a5qULC+Y717D139bSz7glcyIdT6dwFmYnk6Ih7Zsh/TXv6 cAFbCUqnw60YwbFW/9+PTsOpjga/HEtelKiAtvQogGVWzAMI9QyHRv/j811Fz8OcebzY MF2vfEHgqhK+6YJAipLj5nm1fa4gMsuFj2ZVewZk5F5iOsgWFbmlEsaxTW/ELz5ki8YY DtuA== 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=ZnevUaJhp8o+62+JbDvqcEAzUqPJMpxIZKO2zCCXoLY=; b=AuwbttPqHsDAORNogVk8Ivfl0dJ69630UykdHnZSTy3qdFElPsoP+ELKguaq0CNgGO HCMAZcGSgUcxYMEH9pdU94Q3pOloL9YyWpj7R8adoyKaQR70BjkYgrefBILhJUL1l/nt ZUCdDRlqaqGmV+LmDgzDb4lBwmvzGJ40B1ZBFx81IagCXLoGwaHcb/FSBIYdxpdUjydq tPg5rqXaZApk5b4p878hQJ+CGsTvv8btGpIp+twXDSS4MXg0F1haAInwtABJS4i2BZ9Z lTv4fO8nTafGvLmMoSk+mQrivDUKfrjKLZCDFht3x0kaJKEtsET6NNrCHpi40j/ehYRn hbuA== X-Gm-Message-State: AN3rC/4XnQla0TzHsBeXP2BHap7k5nCbopdoVtAA3xY/5XYf50G0SsOS ylj3P/rcWzs19ZnXjpNzrZCbSV9fd0Hk X-Received: by 10.13.249.130 with SMTP id j124mr5707553ywf.198.1492680711379; Thu, 20 Apr 2017 02:31:51 -0700 (PDT) MIME-Version: 1.0 References: <91A4570B-69EE-4462-9C60-205C66267599@dsl-only.net> <7AD329E1-2828-42EB-9A14-B44E357CC199@dsl-only.net> In-Reply-To: From: Tom Vijlbrief Date: Thu, 20 Apr 2017 09:31:40 +0000 Message-ID: Subject: Re: Sendmail eats CPU on r317039 [after -r316874 it may be -r316951 and -r316973 are not enough to fix everything] To: Mark Millard , ronald-lists@klop.ws Cc: FreeBSD Current , freebsd-arm , sobomax@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2017 09:31:52 -0000 Op wo 19 apr. 2017 09:11 schreef Tom Vijlbrief : > I'm currently rebuilding world and kernel on a just completed SVN checkout. > > Note that the normal sendmail daemon which listens for incoming traffic > does NOT loop. > > The sendmail instance which tries local delivery (echo Hi | mail root) or > the msp_queue instance is looping. > > It might be an arm64 specific issue, but a few weeks ago this was not an > issue. > I just completed a full rebuild on the Pine64 and I cannot reproduce the problem, so there is probably no issue anymore... (Except the spurious interrupts issue) > Op di 18 apr. 2017 om 21:15 schreef Mark Millard : > >> Ronald Klop ronald-lists at klop.ws wrote on Tue Apr 18 09:59:50 UTC >> 2017: >> >> > there is a thread ono this list about a problem in syslogd which made >> > syslog-clients (like sendmail busy-looping on logging. >> > That might be related to this. (it is fixed in the source already, so >> > upgrading again might help) >> > See the thread with subject like 'Re: r316958: booting a server takes >> >10 >> > minutes!' >> > >> > Regards, >> > >> > Ronald. >> >> >> Yes. But Tom V.'s report is for -r317039, which is after the reported >> fixes as far as I can tell. Something besides syslogd might also cause >> problems? >> >> In my nearly-default -r317015 ardm64 context [as a VirtualBox guest] >> I've not seen the problem, where I did before. (The only reason sendmail >> runs in my context is for the messages FreeBSD sends to it own local >> accounts. I do not otherwise use mail in this context.) >> >> Tom V.'s report vs. others finding lack of a problem suggests that the >> coverage of the fixes is incomplete somehow but useful. I happen to not >> be doing whatever causes the problem to appear. I've no clue what might >> be different or unusual in Tom V.'s context. >> >> There is also the possibility that Tom V.'s report is a fully independent >> issue. But such does not seem all that likely on the initial information. >> >> >> > On 2017-Apr-17, at 7:57 AM, Mark Millard >> wrote: >> > >> >> Just an FYI of a more recent report of runaway sendmail on a >> >> more recent system version ( -r317039 ): >> >> >> >> Begin forwarded message: >> >> >> >>> From: Tom Vijlbrief >> >>> Subject: Sendmail eats CPU on r317039 >> >>> Date: April 17, 2017 at 3:39:37 AM PDT >> >>> To: "freebsd-current at freebsd.org" , >> freebsd-arm >> >>> >> >>> On a recent kernel sendmail is constantly consuming CPU. >> >>> >> >>> truss -p PID >> >>> >> >>> shows: >> >>> >> >>> sendto(3,"<22>Apr 17 10:30:33 sendmail[362"...,163,0x0,NULL,0) ERR#55 >> 'No >> >>> buffer space available' >> >>> nanosleep({ 0.000001000 }) = 0 (0x0) >> >>> sendto(3,"<22>Apr 17 10:30:33 sendmail[362"...,163,0x0,NULL,0) ERR#55 >> 'No >> >>> buffer space available' >> >>> nanosleep({ 0.000001000 }) >> >>> ... >> >>> >> >>> This is on an arm64 system >> >> >> >> Analysis of Tom V.'s context for this may be required. >> >> === >> Mark Millard >> markmi at dsl-only.net >> >> _______________________________________________ >> freebsd-arm@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >> > From owner-freebsd-arm@freebsd.org Thu Apr 20 10:22:02 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7BB9FD48565 for ; Thu, 20 Apr 2017 10:22:02 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-186.reflexion.net [208.70.211.186]) (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 3CA08683 for ; Thu, 20 Apr 2017 10:22:01 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 23189 invoked from network); 20 Apr 2017 10:22:00 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 20 Apr 2017 10:22:00 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.40.0) with SMTP; Thu, 20 Apr 2017 06:22:00 -0400 (EDT) Received: (qmail 18250 invoked from network); 20 Apr 2017 10:22:00 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 20 Apr 2017 10:22:00 -0000 Received: from [192.168.1.106] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 6747AEC7901; Thu, 20 Apr 2017 03:21:59 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Sendmail eats CPU on r317039 [after -r316874 it may be -r316951 and -r316973 are not enough to fix everything] From: Mark Millard In-Reply-To: Date: Thu, 20 Apr 2017 03:13:04 -0700 Cc: ronald-lists@klop.ws, FreeBSD Current , freebsd-arm , sobomax@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <56DF611E-E797-4D48-ADA4-0CFED35F2B2E@dsl-only.net> References: <91A4570B-69EE-4462-9C60-205C66267599@dsl-only.net> <7AD329E1-2828-42EB-9A14-B44E357CC199@dsl-only.net> To: Tom Vijlbrief X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2017 10:22:02 -0000 On 2017-Apr-20, at 2:31 AM, Tom Vijlbrief = wrote: >> Op wo 19 apr. 2017 09:11 schreef Tom Vijlbrief : >> I'm currently rebuilding world and kernel on a just completed SVN = checkout. >>=20 >> Note that the normal sendmail daemon which listens for incoming = traffic does NOT loop. >>=20 >> The sendmail instance which tries local delivery (echo Hi | mail = root) or the msp_queue instance is looping. >>=20 >> It might be an arm64 specific issue, but a few weeks ago this was not = an issue. >>=20 > I just completed a full rebuild on the Pine64 and I cannot reproduce = the problem, so there is probably no issue anymore... >=20 > (Except the spurious interrupts issue) FYI: I've not seen a spurious interrupts notification on arm64/aarch64. I have seen such on cortex-a7 (the armv6/7 examples that I have access to are this: so just armv7). For cortex-a7 I build with the following local experiment for information gathering: # svnlite diff /usr/src/sys/arm/arm/gic.c Index: /usr/src/sys/arm/arm/gic.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- /usr/src/sys/arm/arm/gic.c (revision 317015) +++ /usr/src/sys/arm/arm/gic.c (working copy) @@ -672,9 +672,13 @@ =20 if (irq >=3D sc->nirqs) { #ifdef GIC_DEBUG_SPURIOUS +#define EXPECTED_SPURIOUS_IRQ 1023 + if (irq !=3D EXPECTED_SPURIOUS_IRQ) { device_printf(sc->gic_dev, - "Spurious interrupt detected: last irq: %d on = CPU%d\n", + "Spurious interrupt %d detected of %d: last irq: %d = on CPU%d\n", + irq, sc->nirqs, sc->last_irq[PCPU_GET(cpuid)], PCPU_GET(cpuid)); + } #endif return (FILTER_HANDLED); } @@ -720,6 +724,16 @@ if (irq < sc->nirqs) goto dispatch_irq; =20 + if (irq !=3D EXPECTED_SPURIOUS_IRQ) { +#undef EXPECTED_SPURIOUS_IRQ +#ifdef GIC_DEBUG_SPURIOUS + device_printf(sc->gic_dev, + "Spurious end interrupt %d detected of %d: last irq: = %d on CPU%d\n", + irq, sc->nirqs, + sc->last_irq[PCPU_GET(cpuid)], PCPU_GET(cpuid)); +#endif + } + return (FILTER_HANDLED); } It has never reported a non-1023 IRQ. Quoting arm_gic_architecture_specification.pdf (various places about the = 1023 IRQ figure): =E2=80=A2 A processor reads the GICC_IAR and obtains the = interrupt ID 1023, indicating a spurious interrupt. The processor can = return from its interrupt service routine without writing to its = GICC_EOIR. The spurious interrupt ID indicates that the original interrupt is no = longer pending, typically because another target processor is handling = it. and . . . =E2=80=A2 1023 This value is returned to a processor, in = response to an interrupt acknowledge, if there is no pending interrupt = with sufficient priority for it to be signaled to the processor. and . . . GICC_IAR read = GICC_CTLR.AckCtl Returned interrupt ID Highest priority pending interrupt^a is Group 0 Non-secure x = Interrupt ID 1023 No pending interrupts^a x x = Interrupt ID 1023 Interrupt signaling of the required interrupt group by CPU interface = disabled x x = Interrupt ID 1023 ^a. Of sufficient priority to be signaled to the processor if signaling = by the CPU interface is enabled. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Thu Apr 20 11:56:04 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F040DD479D4; Thu, 20 Apr 2017 11:56:04 +0000 (UTC) (envelope-from kabaev@gmail.com) Received: from mail-qt0-x242.google.com (mail-qt0-x242.google.com [IPv6:2607:f8b0:400d:c0d::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 A78CF1C33; Thu, 20 Apr 2017 11:56:04 +0000 (UTC) (envelope-from kabaev@gmail.com) Received: by mail-qt0-x242.google.com with SMTP id t52so7111476qtb.3; Thu, 20 Apr 2017 04:56:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version; bh=PPvmY3NFCvdPf6QSGFSabXtv/UTEIVdOcza5kgocD4g=; b=QfGIBopruyBexHoaP4dSe0druFOIBArwJ7vl9Bb+MYuL9rjSO1/VjCLyv0MTHu3DG5 rPCNhA46+AvgP0jS8Mh4HMMPXXHB0C5tlwMWy+nB+xeN/SzPcwnDDPAtsTGsfQd56NhU zh6evtteWEoO7BtcXVmImAhK8Wqs4XpzhBiG6+i5mNk2twu2NXifnReEoWhlWyAijijZ Jyjv9jGm2726m9oPWE7J27kbl+MK0nIAqkaQd8eL1arjqRdsUMyshKDQ5m758ZWJZCS0 f/lrxQoUcPR2ZkPcqU5cNHkD8U8O7bh5V1Opeg/+QvKE62YdRPIg0YQOV0mKWqhY/+QR uW9Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version; bh=PPvmY3NFCvdPf6QSGFSabXtv/UTEIVdOcza5kgocD4g=; b=R8TT3ARBulO1nYGghAkaon30Iz5ixWvGFRV5tejMOS5EGH/I8TfdWUEdUjGJzFCaFa FR00dxlOn595pa3wFXjw0ARqTNJurIIgv0u33qZi7eBVTqcXYHPSS8BdsrWyAXjH42I3 lEoQhMZEqJrcWNS7ZKSh/Pi3lFjOuPmbL5WHaK+YHcrNrhI8EgBiYe0VaLEuuAtBIxqK Ph6Qx7Gdu07Et8mVr/c404P2P0RT8VWbxbac0VaxOLQMrPOmadZWWHcBCb8QAftOvAsg lMqkNXI8T7tjVevOYZCkzA4KRRRp8nQpn374kT8CWrJHA4u/NEheHeLoa2zHY4VpK3de i4eQ== X-Gm-Message-State: AN3rC/7TmYAiF7Nqw1BKjTZU6V3dTAdtOyzo06I9PE+bwzpyrsacBH5Q +97LYa1HrBQrJvxBXBk= X-Received: by 10.237.41.199 with SMTP id o65mr8152686qtd.239.1492689363740; Thu, 20 Apr 2017 04:56:03 -0700 (PDT) Received: from kan ([2601:18f:802:4680:226:18ff:fe00:232e]) by smtp.gmail.com with ESMTPSA id l10sm205941qte.15.2017.04.20.04.56.01 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 20 Apr 2017 04:56:02 -0700 (PDT) Date: Thu, 20 Apr 2017 07:55:48 -0400 From: Alexander Kabaev To: Mark Millard Cc: FreeBSD Toolchain , freebsd-arm Subject: Re: FYI on aarch64: building and installing devel/aarch64-gcc fails with "Unable to access file" for 6 files Message-ID: <20170420075548.66f6bc4d@kan> In-Reply-To: <921E1189-B07D-4BFA-873B-9C2DF195D771@dsl-only.net> References: <921E1189-B07D-4BFA-873B-9C2DF195D771@dsl-only.net> X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.29; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/4fTKOAL_R9aJXg5g7Fir6_8"; protocol="application/pgp-signature" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2017 11:56:05 -0000 --Sig_/4fTKOAL_R9aJXg5g7Fir6_8 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable aarch64-gcc is not a full compiler, but one intended to be used as cross toolchain. Said that, when built on x86-64, it does have gcov and man pages, so this must be an artefact of your build environment or your aarch64 setup, as this never was tested when run natively nor was it meant to be - there is unfinished work in ports/base to create native toolchain. Please provide full log of your port build soemwhere, though I will not be able to look at it under weekend at the earliest. % pkg info -l aarch64-gcc-6.3.0 | grep gcov /usr/local/bin/aarch64-unknown-freebsd12.0-gcov /usr/local/bin/aarch64-unknown-freebsd12.0-gcov-tool /usr/local/lib/gcc/aarch64-unknown-freebsd12.0/6.3.0/plugin/include= /gcov-counter.def /usr/local/lib/gcc/aarch64-unknown-freebsd12.0/6.3.0/plugin/include= /gcov-io.h /usr/local/man/man1/aarch64-unknown-freebsd12.0-gcov.1.gz Thanks, On Wed, 19 Apr 2017 17:09:34 -0700 Mark Millard wrote: > The attempt to build & install devel/aarch64-gcc on a aarch64 > environment gets (I use WRKDIRPREFIX=3D/usr/obj/portswork ): >=20 > =3D=3D=3D> Installing for aarch64-gcc-6.3.0 > =3D=3D=3D> Checking if aarch64-gcc already installed > =3D=3D=3D> Registering installation for aarch64-gcc-6.3.0 as automatic = =20 > pkg-static: Unable to access > file /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/= bin/aarch64-unknown-freebsd12.0-gcov:No > such file or directory pkg-static: Unable to access > file /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/= bin/aarch64-unknown-freebsd12.0-gcov-tool:No > such file or directory pkg-static: Unable to access > file /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/= man/man1/aarch64-unknown-freebsd12.0-cpp.1.gz:No > such file or directory pkg-static: Unable to access > file /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/= man/man1/aarch64-unknown-freebsd12.0-g++.1.gz:No > such file or directory pkg-static: Unable to access > file /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/= man/man1/aarch64-unknown-freebsd12.0-gcc.1.gz:No > such file or directory pkg-static: Unable to access > file /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/= man/man1/aarch64-unknown-freebsd12.0-gcov.1.gz:No > such file or directory *** Error code 74 >=20 > Stop. > make: stopped in /usr/ports/devel/aarch64-gcc >=20 > =3D=3D=3D>>> Installation of aarch64-gcc-6.3.0 (devel/aarch64-gcc) failed= =20 >=20 >=20 > A hack before doing a portmaster -CDK lang/aarch64-gcc to continue > the build/install is to execute the script shown below (I use > WRKDIRPREFIX=3D/usr/obj/portswork ): >=20 > # more ~/aarch64-gcc_fixup.sh=20 > #!/bin/sh > cp > -ax /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/.build/gcc/gcov /= usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/bin/aarc= h64-unknown-freebsd12.0-gcov >=20 > cp > -ax /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/.build/gcc/gcov-t= ool /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/bin= /aarch64-unknown-freebsd12.0-gcov-tool >=20 > gzip > -c /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/gcc-*/gcc/doc/cpp.1 > > /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/man= /man1/aarch64-unknown-freebsd12.0-cpp.1.gz >=20 > gzip > -c /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/.build/gcc/doc/g++= .1 > > /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/man= /man1/aarch64-unknown-freebsd12.0-g++.1.gz >=20 > gzip > -c /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/.build/gcc/doc/gcc= .1 > > /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/man= /man1/aarch64-unknown-freebsd12.0-gcc.1.gz >=20 > gzip > -c /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/gcc-*/gcc/doc/gcov= .1 > > /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/man= /man1/aarch64-unknown-freebsd12.0-gcov.1.gz >=20 > That puts in place the files that are not where they are expected. >=20 > Of course this sort of hack-then-continue would not fit well > with poudriere use or analogous build techniques. >=20 >=20 > The same sort of thing happens for lang/powerpc64 on a powerpc64 > environment. >=20 > As I remember. . . > The same sort of thing happens for lang/amd64 on a amd64 > environment. >=20 > So I have ~/powerpc64-gcc_fixup.sh and ~/amd64-gcc_fixup.sh > as well. >=20 >=20 > I get to these ???-gcc's by trying to install a > self-hosted lang/???-xtoolchain-gcc in each case. > Such allows for experimenting with self-hosted gcc > based system builds that are libc++ based (instead > of using gcc 4.2.1). >=20 > =3D=3D=3D > Mark Millard > markmi at dsl-only.net >=20 > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" --=20 Alexander Kabaev --Sig_/4fTKOAL_R9aJXg5g7Fir6_8 Content-Type: application/pgp-signature Content-Description: Цифровая подпиŃŃŚ OpenPGP -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEExffZlZm2QeE8UVaRBxMimZJ5Ln4FAlj4ocRfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEM1 RjdEOTk1OTlCNjQxRTEzQzUxNTY5MTA3MTMyMjk5OTI3OTJFN0UACgkQBxMimZJ5 Ln4Z1hAAqSf4Yf+BJHYKnQA4ENAWGluNnCLSBJ5NhHf4pveCOChIw7QdJKuzwNWA jHPakWRMO8NVpWyV43zvVrFGcXIC4RWjlrCMjlAHhqOcZPcbTwsap7cnhfSWt+QO viJH/ZNoS/zjRIv7GaYC2mgYBnpBuvlhlfK2SRoXhId6ypxr61bBTELEidyxH1kB B3sT4W7JAtj9TlUF48tiNNDxbF8JzHPmEfRugGPtoKQZptcfN+ws5vTm26uJzII/ b720tOd6YeO+lcdX4LkmYtzd6cyFeyeubToc5TFFg0/Dp2FsBERmMSQkJEn7jrRv MmapHrHJa2EzDn1MzlCM6NIH2oyTg3lq8bGVT/fBDC6W5tYN59voAGX15j9OKfKV 5nWiW9HoAS5U334vD540wxXysYWbMdhCFlSQLlE9bcWfqVxYCn+XsiMeWqG+k6S4 ZnC+BNKTjqwcNAbUvXvBHJX5chSL+ikyZpMMpzTSYR4SIACNopYDQAC2pYg3Ikze DiLxz978Cr8KsvDr/BPMeVByUMJ+iBgHUtR+YA6OHZPA1n7O1fEnezG+7AC+1Yh2 FRNnb0L66MkP1IWfvakYyHx7CCPo99HSIQf7S18X2O4ICAAXsnVdgU4JJKRbL4SN gNkapRNFGI+qNSQCBhMcfJq5kQHsQ0ftZHxIvIVvjLhR4Dny/js= =J+po -----END PGP SIGNATURE----- --Sig_/4fTKOAL_R9aJXg5g7Fir6_8-- From owner-freebsd-arm@freebsd.org Thu Apr 20 14:15:43 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A233ED48F9B for ; Thu, 20 Apr 2017 14:15:43 +0000 (UTC) (envelope-from mathieudube1977@gmail.com) Received: from mail-wr0-x236.google.com (mail-wr0-x236.google.com [IPv6:2a00:1450:400c:c0c::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 3B5B0FD1 for ; Thu, 20 Apr 2017 14:15:43 +0000 (UTC) (envelope-from mathieudube1977@gmail.com) Received: by mail-wr0-x236.google.com with SMTP id o21so36597592wrb.2 for ; Thu, 20 Apr 2017 07:15:43 -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=Gz7aedzcUiBoW35g/4NkHLkkvr6JqV3mjVrq/+5ngrE=; b=c8iWFZNQ9WwaxQnqNifsf+AxYmm55qB+auy0rhF6il73ArlO1B+/aouUFkYi+HazND MuAj/RTFZf0hV1Mi919V7Xjmh9v6ssDcxMKb+74w1LMjKl7CAuMMC291CIEwVW3RE6bF ou8KlYY/T1mVDSx71PFyZR0v8HqPrbHZ8h7BEswbLb+IHtlmLlXrLEA0Xr6xrkQsrz7F JpIHZffn9OI2X3W+qnV1aWfQ7gJ8P4JWa36VGLZhUAAMcBXi+8QlDwWksRhW/y2s0jxC FMoVad0ryBHkCpc4VzHEoqqc1ABRQXPwDlPV+Yk7Mipuroo95zfTiT6XZOJKwi4v28ps x7hA== 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=Gz7aedzcUiBoW35g/4NkHLkkvr6JqV3mjVrq/+5ngrE=; b=Jnf7/tJaSGLIKvBG34Wo6kPwQCPqXjo7zxWO6IATrnNOtU4/TNtTwXChPvaGDZZeQa X2AHaeIWSaycjP1K+D+6T74vFKdfRr5cU8Mr/9L/Vm8jqoRRvsDELaO0Q7BsR5NT2T74 nuaZqfToCHaQKDFMHUFtjO0FlRp+6rJPoLRvaoO3CbIXjL9CLRdaoVewKZuitZk4YKP+ ThdxQCM6TneMC8ndvkdF9aU6a1U2YwdmUaB63Rd8SDm/+R5em/Vo+YXqATzM8XGwqBso qJ/9Y6TmwaRFU+0iixaP51VcscgvI2pGMJP6GTXj5M8Ozz/XmrRb7UN0zQGa/AJBaTBG E6jA== X-Gm-Message-State: AN3rC/4dxuJujz7z8n/7kwHNdY9VriEVfqS8o1rpBihZG5CgD2fNkdns xFhCBJzD2RH+92yj+e6nKXzLal5uk7gL X-Received: by 10.223.176.83 with SMTP id g19mr3476277wra.12.1492697741003; Thu, 20 Apr 2017 07:15:41 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.166.146 with HTTP; Thu, 20 Apr 2017 07:15:40 -0700 (PDT) From: Mathieu Dube Date: Thu, 20 Apr 2017 10:15:40 -0400 Message-ID: Subject: Trying to crosscompile from RaspPi 3 To: freebsd-arm@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2017 14:15:43 -0000 Hi, I'll preface this by saying I'm a newbie to this. I've cloned out HEAD and I'm using the following guide to attempt to compile for RaspPi 3 board: https://people.freebsd.org/~cognet/arm.html However, I can't find the correct board in /sys/arm/conf Please let me know what I'm missing. Thanks -Matt From owner-freebsd-arm@freebsd.org Thu Apr 20 14:30:30 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 12243D469A9 for ; Thu, 20 Apr 2017 14:30:30 +0000 (UTC) (envelope-from otacilio.neto@bsd.com.br) Received: from mail-qt0-x230.google.com (mail-qt0-x230.google.com [IPv6:2607:f8b0:400d:c0d::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C9250793 for ; Thu, 20 Apr 2017 14:30:29 +0000 (UTC) (envelope-from otacilio.neto@bsd.com.br) Received: by mail-qt0-x230.google.com with SMTP id g60so46499623qtd.3 for ; Thu, 20 Apr 2017 07:30:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsd.com.br; s=capeta; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to; bh=wP1ndSCzGUCkG0fukEmY3KxWDhmRCI9PA45ZJTklB8U=; b=PQ+oOjxo9kADEKAvKyg+ZNfRoiG6eAYxV/uiIB2pBrhR2uE5UPZlL8LiwUXWSA+usV Atp4T9VcsohxVjpwaqJOi0X9vlfPb52i9B+HbeDbfgovmyhvdO/zPY85yxtm7OHwtxYw wC932fpjgkh9MS4Y/J3ARbQnpyLp2B8ykQqVQ= 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; bh=wP1ndSCzGUCkG0fukEmY3KxWDhmRCI9PA45ZJTklB8U=; b=eO8nDvpjHhgvtGyF5za0ou5wegsfvm+WB+bPH+XPmahJ9L175LTv7bvJMQVOIvqc07 clsWBZjo/wSvBBRtTAPSTa1LFNZUo+7jFoD6WP345EAD9nGk2Gv+Ik56kpz+d3AttL/y VlXZXcv8mwy2q6+vabEDEj1OY1fF51jBe490XJQnM7jgKC9ge1GxXTVRUXE+QMKsrZqA GhiK2tK4i+VnRILNfo+Nc3mjFmma6hNAwY4hRFevnhJA23V+15KXEXr8/RS6bA5n8ZeG qfK/LYck8jOe6M1S+mB04nqtvpIdprXm0w8j/XvyruCGQ/4WuQ7quEwQH01mowfIPFNN D6EQ== X-Gm-Message-State: AN3rC/6sDZNhrtC7ttA1TLdoN1XveMQuSReUfFxAP5lBobJKNKzkIWS8 Lsjad5WTkD1s9H9R X-Received: by 10.200.41.35 with SMTP id y32mr8156202qty.37.1492698627485; Thu, 20 Apr 2017 07:30:27 -0700 (PDT) Received: from [192.168.43.219] (179-240-167-78.3g.claro.net.br. [179.240.167.78]) by smtp.googlemail.com with ESMTPSA id i19sm4255785qte.31.2017.04.20.07.30.25 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Apr 2017 07:30:26 -0700 (PDT) Subject: Re: Trying to crosscompile from RaspPi 3 To: freebsd-arm@freebsd.org References: From: =?UTF-8?B?T3RhY8OtbGlv?= Message-ID: Date: Thu, 20 Apr 2017 11:30:21 -0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2017 14:30:30 -0000 Em 20/04/2017 11:15, Mathieu Dube escreveu: > Hi, > > I'll preface this by saying I'm a newbie to this. > > I've cloned out HEAD and I'm using the following guide to attempt to > compile for RaspPi 3 board: > > https://people.freebsd.org/~cognet/arm.html > > However, I can't find the correct board in /sys/arm/conf > > Please let me know what I'm missing. > > Thanks > -Matt I think the best option is to use the crouchet to generate the images for the RPI3. You can find crouchet here: Https://github.com/freebsd/crochet Although the crouchet page does not mention, in the configuration file it is also possible to inform the card as being the RPI3. So far I know, I understand the kernel configuration files are in the folder /usr/src/sys/arm64. Unfortunately for some time now the images I have generated are not working on my RPI3, it is giving a panic kernel at boot time. []'s -Otacilio From owner-freebsd-arm@freebsd.org Thu Apr 20 17:16:58 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 40F04D48AC6 for ; Thu, 20 Apr 2017 17:16:58 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-20.reflexion.net [208.70.210.20]) (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 01EF0A9C for ; Thu, 20 Apr 2017 17:16:57 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 7175 invoked from network); 20 Apr 2017 17:10:16 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 20 Apr 2017 17:10:16 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.40.0) with SMTP; Thu, 20 Apr 2017 13:10:16 -0400 (EDT) Received: (qmail 20525 invoked from network); 20 Apr 2017 17:10:16 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 20 Apr 2017 17:10:16 -0000 Received: from [192.168.1.106] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 9BF9CEC9008; Thu, 20 Apr 2017 10:10:15 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: FYI on aarch64: building and installing devel/aarch64-gcc fails with "Unable to access file" for 6 files From: Mark Millard In-Reply-To: <20170420075548.66f6bc4d@kan> Date: Thu, 20 Apr 2017 10:10:15 -0700 Cc: FreeBSD Toolchain , freebsd-arm Content-Transfer-Encoding: quoted-printable Message-Id: References: <921E1189-B07D-4BFA-873B-9C2DF195D771@dsl-only.net> <20170420075548.66f6bc4d@kan> To: Alexander Kabaev X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2017 17:16:58 -0000 On 2017-Apr-20, at 4:55 AM, Alexander Kabaev = wrote: > aarch64-gcc is not a full compiler, but one intended to be used as > cross toolchain. I've used powerpc64-xtoolchain-gcc and its powerpc64-gcc to build modern, libc++ based powerpc64 builds for years, mostly self-hosted on powerpc64 hardware but also cross built from amd64. So I'm familiar with the ???-gcc's and their purpose. ???-gcc is also part of how I test if the code is compliant with both gcc and clang in a self hosted manor. I've reported various examples over the years of incompatibilities that had appeared. > Said that, when built on x86-64, it does have gcov > and man pages, so this must be an artefact of your build environment = or > your aarch64 setup, as this never was tested when run natively nor was > it meant to be - The problem for self hosted is the need to add the prefixes, such as, aarch64-unknown-freebsd12.0- to the names such as: gcov gcov-tool gcov.1.gz The logic for doing that is conditional on the cross-build status and the prefix is not added when it is a self-hosted-build (so it is not a cross build). But pkg-plist has no such conditional status (using gcov-tool as an example) : # grep -R gcov-tool /usr/ports/devel/aarch64-gcc/ /usr/ports/devel/aarch64-gcc/pkg-plist:bin/%%GCC_TARGET%%-gcov-tool (and for good reasons for pkg-plist). Continuing to use gcov-tool as an example. . . =46rom = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/gcc-6.3.0/gcc/Makefile= .in : GCC_INSTALL_NAME :=3D $(shell echo gcc|sed '$(program_transform_name)') GCC_TARGET_INSTALL_NAME :=3D $(target_noncanonical)-$(shell echo gcc|sed = '$(program_transform_name)') CPP_INSTALL_NAME :=3D $(shell echo cpp|sed '$(program_transform_name)') GCOV_INSTALL_NAME :=3D $(shell echo gcov|sed = '$(program_transform_name)') GCOV_TOOL_INSTALL_NAME :=3D $(shell echo gcov-tool|sed = '$(program_transform_name)') # grep -R GCOV_TOOL_INSTALL_NAME = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/ | more = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/gcc-6.3.0/gcc/Makefile= .in:GCOV_TOOL_INSTALL_NAME :=3D $(shell echo gcov-tool|sed = '$(program_transform_name)') = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/gcc-6.3.0/gcc/Makefile= .in: rm -f $(DESTDIR)$(bindir)/$(GCOV_TOOL_INSTALL_NAME)$(exeext); = \ = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/gcc-6.3.0/gcc/Makefile= .in: gcov-tool$(exeext) = $(DESTDIR)$(bindir)/$(GCOV_TOOL_INSTALL_NAME)$(exeext); \ = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/gcc-6.3.0/gcc/Makefile= .in:$(DESTDIR)$(man1dir)/$(GCOV_TOOL_INSTALL_NAME)$(man1ext): = doc/gcov-tool.1 installdirs = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/.build/gcc/Makefile:GC= OV_TOOL_INSTALL_NAME :=3D $(shell echo gcov-tool|sed = '$(program_transform_name)') /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/.build/gcc/Makefile: = rm -f $(DESTDIR)$(bindir)/$(GCOV_TOOL_INSTALL_NAME)$(exeext); = \ /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/.build/gcc/Makefile: = gcov-tool$(exeext) = $(DESTDIR)$(bindir)/$(GCOV_TOOL_INSTALL_NAME)$(exeext); \ = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/.build/gcc/Makefile:$(= DESTDIR)$(man1dir)/$(GCOV_TOOL_INSTALL_NAME)$(man1ext): doc/gcov-tool.1 = installdirs So when GCOV_TOOL_INSTALL_NAME omits the prefix for self-hosted the result is incorrect for the pkg-plist . > there is unfinished work in ports/base to create > native toolchain. I'm aware. I've submitted Bugzilla reports 21400 though 214405 against it from attempting to use it and work around some of its problems. > Please provide full log of your port build soemwhere, though I will = not > be able to look at it under weekend at the earliest. I'll deal with sending a compressed copy of my: ~/ports_typescripts/r438677_aarch_xtoolchain_gcc_try-00-typescript separately later --and off list. But I doubt it will be any more interesting/useful than the above and below extractions. > % pkg info -l aarch64-gcc-6.3.0 | grep gcov > /usr/local/bin/aarch64-unknown-freebsd12.0-gcov > /usr/local/bin/aarch64-unknown-freebsd12.0-gcov-tool > = /usr/local/lib/gcc/aarch64-unknown-freebsd12.0/6.3.0/plugin/include/gcov-c= ounter.def > = /usr/local/lib/gcc/aarch64-unknown-freebsd12.0/6.3.0/plugin/include/gcov-i= o.h > /usr/local/man/man1/aarch64-unknown-freebsd12.0-gcov.1.gz Using gcov-tool as an example again: As far as the log goes for mentions of gcov-tool. . . # grep gcov-tool = ~/ports_typescripts/r438677_aarch_xtoolchain_gcc_try-00-typescript | = more c++ -std=3Dgnu++98 -fno-PIE -c -fbracket-depth=3D512 -DIN_GCC = -fno-strict-aliasing -fno-exceptions -fno-rtti = -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings = -Wcast-qual -Wmissing-format-attribute -Woverloaded-virtual -pedantic = -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings = -DHAVE_CONFIG_H -I. -I. = -I/usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/gcc-6.3.0/gcc = -I/usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/gcc-6.3.0/gcc/. = -I/usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/gcc-6.3.0/gcc/../inc= lude = -I/usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/gcc-6.3.0/gcc/../lib= cpp/include -I/usr/local/include = -I/usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/gcc-6.3.0/gcc/../lib= decnumber = -I/usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/gcc-6.3.0/gcc/../lib= decnumber/dpd -I../libdecnumber = -I/usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/gcc-6.3.0/gcc/../lib= backtrace -B/usr/local/aarch64-freebsd/bin/ -mcpu=3Dcortex-a53 = -DLIBICONV_PLUG -o gcov-tool.o -MT gcov-tool.o -MMD -MP -MF = ./.deps/gcov-tool.TPo = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/gcc-6.3.0/gcc/gcov-too= l.c ESC[0mIn file included from = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/gcc-6.3.0/gcc/gcov-too= l.c:28: ESC[0mIn file included from = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/gcc-6.3.0/gcc/gcov-too= l.c:28: ESC[0mIn file included from = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/gcc-6.3.0/gcc/gcov-too= l.c:28: ESC[0mIn file included from = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/gcc-6.3.0/gcc/gcov-too= l.c:28: ESC[0mIn file included from = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/gcc-6.3.0/gcc/gcov-too= l.c:28: = ESC[1m/usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/gcc-6.3.0/gcc/gc= ov-tool.c:490:7: ESC[0mESC[0;1;35mwarning: ESC[0mESC[1mvariable 'ret' is = used uninitialized whenever 'if' condition is false = [-Wsometimes-uninitialized]ESC[0m = ESC[0mESC[1m/usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/gcc-6.3.0/= gcc/gcov-tool.c:495:10: ESC[0mESC[0;1;30mnote: ESC[0muninitialized use = occurs hereESC[0m = ESC[0mESC[1m/usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/gcc-6.3.0/= gcc/gcov-tool.c:490:3: ESC[0mESC[0;1;30mnote: ESC[0mremove the 'if' if = its condition is always trueESC[0m = ESC[0mESC[1m/usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/gcc-6.3.0/= gcc/gcov-tool.c:459:10: ESC[0mESC[0;1;30mnote: ESC[0minitialize the = variable 'ret' to silence this warningESC[0m ESC[0mc++ -std=3Dgnu++98 -fbracket-depth=3D512 -DIN_GCC = -fno-strict-aliasing -fno-exceptions -fno-rtti = -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings = -Wcast-qual -Wmissing-format-attribute -Woverloaded-virtual -pedantic = -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings = -DHAVE_CONFIG_H gcov-tool.o libgcov-util.o libgcov-driver-tool.o = libgcov-merge-tool.o libcommon.a ../libcpp/libcpp.a = ../libbacktrace/.libs/libbacktrace.a ../libiberty/libiberty.a = ../libdecnumber/libdecnumber.a -o gcov-tool if [ -f gcov-tool ]; \ rm -f = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/bin/gc= ov-tool; \ gcov-tool = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/bin/gc= ov-tool; \ pkg-static: Unable to access file = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/bin/aa= rch64-unknown-freebsd12.0-gcov-tool:No such file or directory Note the lack of aarch64-unknown-freebsd12.0- except in the pkg-static = message. > Thanks, >=20 > On Wed, 19 Apr 2017 17:09:34 -0700 > Mark Millard wrote: >=20 >> The attempt to build & install devel/aarch64-gcc on a aarch64 >> environment gets (I use WRKDIRPREFIX=3D/usr/obj/portswork ): >>=20 >> =3D=3D=3D> Installing for aarch64-gcc-6.3.0 >> =3D=3D=3D> Checking if aarch64-gcc already installed >> =3D=3D=3D> Registering installation for aarch64-gcc-6.3.0 as = automatic =20 >> pkg-static: Unable to access >> file = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/bin/aa= rch64-unknown-freebsd12.0-gcov:No >> such file or directory pkg-static: Unable to access >> file = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/bin/aa= rch64-unknown-freebsd12.0-gcov-tool:No >> such file or directory pkg-static: Unable to access >> file = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/man/ma= n1/aarch64-unknown-freebsd12.0-cpp.1.gz:No >> such file or directory pkg-static: Unable to access >> file = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/man/ma= n1/aarch64-unknown-freebsd12.0-g++.1.gz:No >> such file or directory pkg-static: Unable to access >> file = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/man/ma= n1/aarch64-unknown-freebsd12.0-gcc.1.gz:No >> such file or directory pkg-static: Unable to access >> file = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/man/ma= n1/aarch64-unknown-freebsd12.0-gcov.1.gz:No >> such file or directory *** Error code 74 >>=20 >> Stop. >> make: stopped in /usr/ports/devel/aarch64-gcc >>=20 >> =3D=3D=3D>>> Installation of aarch64-gcc-6.3.0 (devel/aarch64-gcc) = failed =20 >>=20 >>=20 >> A hack before doing a portmaster -CDK lang/aarch64-gcc to continue >> the build/install is to execute the script shown below (I use >> WRKDIRPREFIX=3D/usr/obj/portswork ): >>=20 >> # more ~/aarch64-gcc_fixup.sh=20 >> #!/bin/sh >> cp >> -ax = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/.build/gcc/gcov = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/bin/aa= rch64-unknown-freebsd12.0-gcov >>=20 >> cp >> -ax = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/.build/gcc/gcov-tool = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/bin/aa= rch64-unknown-freebsd12.0-gcov-tool >>=20 >> gzip >> -c = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/gcc-*/gcc/doc/cpp.1 >>> = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/man/ma= n1/aarch64-unknown-freebsd12.0-cpp.1.gz >>=20 >> gzip >> -c = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/.build/gcc/doc/g++.1 >>> = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/man/ma= n1/aarch64-unknown-freebsd12.0-g++.1.gz >>=20 >> gzip >> -c = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/.build/gcc/doc/gcc.1 >>> = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/man/ma= n1/aarch64-unknown-freebsd12.0-gcc.1.gz >>=20 >> gzip >> -c = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/gcc-*/gcc/doc/gcov.1 >>> = /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/man/ma= n1/aarch64-unknown-freebsd12.0-gcov.1.gz >>=20 >> That puts in place the files that are not where they are expected. >>=20 >> Of course this sort of hack-then-continue would not fit well >> with poudriere use or analogous build techniques. >>=20 >>=20 >> The same sort of thing happens for lang/powerpc64 on a powerpc64 >> environment. >>=20 >> As I remember. . . >> The same sort of thing happens for lang/amd64 on a amd64 >> environment. >>=20 >> So I have ~/powerpc64-gcc_fixup.sh and ~/amd64-gcc_fixup.sh >> as well. >>=20 >>=20 >> I get to these ???-gcc's by trying to install a >> self-hosted lang/???-xtoolchain-gcc in each case. >> Such allows for experimenting with self-hosted gcc >> based system builds that are libc++ based (instead >> of using gcc 4.2.1). From owner-freebsd-arm@freebsd.org Fri Apr 21 08:06:28 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 39194D49329 for ; Fri, 21 Apr 2017 08:06:28 +0000 (UTC) (envelope-from 3g735WCgKALIfgjWhdq-SWXyUzXWuwSWUTz0yzwSy1VySVUtwSuWYggYdW.Uge@unified-notifications.bounces.google.com) Received: from mail-oi0-x245.google.com (mail-oi0-x245.google.com [IPv6:2607:f8b0:4003:c06::245]) (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 004D51992 for ; Fri, 21 Apr 2017 08:06:27 +0000 (UTC) (envelope-from 3g735WCgKALIfgjWhdq-SWXyUzXWuwSWUTz0yzwSy1VySVUtwSuWYggYdW.Uge@unified-notifications.bounces.google.com) Received: by mail-oi0-x245.google.com with SMTP id m79so27633237oik.5 for ; Fri, 21 Apr 2017 01:06:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:date:list-unsubscribe:message-id:subject:from:to; bh=EKkPMDpUYCePLBY77iBAeyrH8TD9pStFv22o9aSMdzc=; b=iskDHr58gMAegMsTu/O8r4bgNaGK9q9+wnhVAWa91nEOjWxdxZfsv47Wqn3CF0IfZp QaAFM1cOdP+cydjAJV8FyrXmF1RiVgVsjpqFQZo48WcJS+eZ0E+9a3/ia/CmSYzwErLD BqhA6D/EzM1QmSW1aSlALRZYfi6oPsiqjrnHA67QiU3TdRk45AdTIADlfo+PzBEtd9nh wQGkTTVOz4XN3p1zwfLB9gr1XxVlcslS3MBrC/y1QfO638CmHf6Yn4VNdaAmuSTupQE6 VrZxLcwST9MrC+KJUQwN2dBne7kZxfnvxZDzD7zYEUd0qPSr9JKI514Rz3kQhfrVTnA5 JCbw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:date:list-unsubscribe:message-id :subject:from:to; bh=EKkPMDpUYCePLBY77iBAeyrH8TD9pStFv22o9aSMdzc=; b=sEG6BnrABJwdd9t1nk3q1eyUuTKtfWCKFpcgwEnwmLcpfkjeSl9ML2ySm+ZJZFAPnH PeNbc+SG4S5ltYPGWgRVSSFmukFUaFBI5tM2+WtBxJ0pvEqZ0cpzwZmuFzo4/Zk9hxPf e8MOu12ZgXLzO/DPxftz43KZ1zC6NGxrocy/wfmYzLwIxvLridMNj41sYfVrbooPXYbL DncdlCSY6t0yGE3B1YeBChr+jQ6Suz7G793ikeA/uP/w5YWw7gRqMRGfV/MqKrtdm1cw yBQBBCNVvOCKaRvFaoiS8QeHLkRSKOKM6Fi7ham4a7M353/i4JfgnxSXQgoTvnnhrCIU Ueaw== X-Gm-Message-State: AN3rC/5icHRuaEU35bF18evoZlQ2pVko9lRsSlbvlty2GyluNgPxnSXk c+UTyIH7GpdZxxPQkpNFBqpqZ3xPeQrfsEScfRqZ MIME-Version: 1.0 X-Received: by 10.157.48.135 with SMTP id s7mr5644167otc.52.1492761987164; Fri, 21 Apr 2017 01:06:27 -0700 (PDT) Date: Fri, 21 Apr 2017 01:06:26 -0700 (PDT) X-Notifications: XEAAAANLC1nPcTrUOCC2TW6wV-uA Message-ID: Subject: Castings casting&lost-wax casting for steel parts /bhgjn9 gbhgjn shared 1 photo with you From: "Castings casting&lost-wax casting for steel parts /bhgjn9 gbhgjn (via Google Photos)" To: freebsd-arm@freebsd.org Content-Type: text/plain; charset=UTF-8; format=flowed; delsp=yes X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Apr 2017 08:06:28 -0000 Google Photos Castings casting&lost-wax casting for steel parts /bhgjn9 gbhgjn: Dear Sir/Ms, Good day!|We mainly produce lost-wax casting for steel parts. We have own CNC machining shop. We |specialize in this field for several years, with good quality and pretty competitive |price. Just email us the drawing and detailed requirement, you will get a complete |quotation with technical analysis within 24 hours. Your prompt reply is highly | appreciated.Thanks and best regards,|China ||Yang Shengwu||Please do not reply directly, please copy the correct reply EMAIL | address:Castingscasting@outlook.com| View photos here: https://photos.google.com/share/AF1QipMPLOZvW3BHB5zsWKPtBf-BMI6_M0YssfWXBRqGrhwHqruvjYR9jGdxvoGVw2osEQ?key=TlNIOVFuV3ZYVUhXYTIzczgwQ2h3cnZtZXhMM0xB You received this mail because Castings casting&lost-wax casting for steel parts /bhgjn9 gbhgjn shared these photos with you. If you no longer wish to receive email notifications of shared photos, unsubscribe here: https://notifications.google.com/unsubscribe/AJ7SsMk20-UulrJmJ7jmSWGiKfu5nFTbqDhWbXzvISLc2YBo8RJK4LGD9z2NDFtmkzr8u8hJhBx1XeJNbvdtwFMuVwLpVEmEjXtI_80yVSWFedkbtTdIahinbg7YeDMMgJTYMorQ2GZSc4PNmkszBv8V9A7kdIGIug Get Google Photos (https://google.com/photos) Google Inc., 1600 Amphitheatre Pkwy, Mountain View, CA 94043 USA From owner-freebsd-arm@freebsd.org Fri Apr 21 08:07:31 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0EEF2D49399 for ; Fri, 21 Apr 2017 08:07:31 +0000 (UTC) (envelope-from tvijlbrief@gmail.com) Received: from mail-yw0-x229.google.com (mail-yw0-x229.google.com [IPv6:2607:f8b0:4002: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 DC5831A57 for ; Fri, 21 Apr 2017 08:07:30 +0000 (UTC) (envelope-from tvijlbrief@gmail.com) Received: by mail-yw0-x229.google.com with SMTP id 203so47138508ywe.0 for ; Fri, 21 Apr 2017 01:07:30 -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=yKPhBvd+pnxWTbqUA2y0R4updCU0imYwnYsx1LzaOlw=; b=nCkzaRaMSIRxlFyTztv++h2FbrFOUv1KZIL7A7NBfEpEhWMlj0LChf8KHs/n5Mdif8 oB3XE+ayZaQtpAe7+AtMnwmAOv7VVnNaaYMBvgPBhlsFkZZioNhtx3blAX1YSh5EKAcN GPGEDIRrx1mRusYUF5BlDti54eyWfJSx0GdHchA0Ryi1hnVu9hmXs/xex3GmK1GiZGSm dlqb4PjxejeuBjVw//6PeiMx0E+DoCFn07OCLTsP1rekWrm0uvnRZm9Ie/w6ocmwiSeh NMgteiPCVKZTJ6O/0glVVqcVXlCxCefQvAkhdm5DepgUtGQjpDOQhb7fLDjCiYujKMWQ sofw== 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=yKPhBvd+pnxWTbqUA2y0R4updCU0imYwnYsx1LzaOlw=; b=KVxFIqlMotuV4gzAC3DJjraAKDbP//9yVizg1CEDj7U5dM/w5HlLXyxkjii3On3HI4 HsEdrK7urekiiV6JDsFF2FUbprKT/obfXX/ww5t2fW2Kw9v4WmqY1rBeX2CQvrvEOYy2 jdFJCEqVOKGTZs07N6Yp0hAR7m4GiDHGmN6wXykGPiELVgCRYnhzD+kjP2o3ES9avHh7 sZd1MGssx+duyyGdNFinOdwzrMuwqe4yHBuVc8CiwXUDKqA8+NVRXkPc/z5vWONAKKXn qskHZjVHfVZh4VjqYwIg6UC0j9TgSJ9MYkRvsVZct9ZMbmF0ok/b1NVN+HvJ+745DXGG a2bA== X-Gm-Message-State: AN3rC/5vpGVQyULkuIDmtb1cg9XS3A6GzuYgoakvh0bbZ3Ue9ZtalSjK Vgmx8a7sb1Tl5i4cw/zIkTO4e7w7+672 X-Received: by 10.13.236.199 with SMTP id v190mr10058270ywe.65.1492762049805; Fri, 21 Apr 2017 01:07:29 -0700 (PDT) MIME-Version: 1.0 From: Tom Vijlbrief Date: Fri, 21 Apr 2017 08:07:19 +0000 Message-ID: Subject: Pine64 spurious interrupts To: freebsd-arm , Mark Millard Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Apr 2017 08:07:31 -0000 I have a lot of spurious interrupts on my Pine64. Even in idle single user mode: # pstree -+= 00001 root /sbin/init -- \-+= 01783 root -sh (sh) \-+= 01804 root pstree \--- 01805 root ps -axwwo user,pid,ppid,pgid,command # gic0: Spurious interrupt detected: last irq: 27 on CPU3 gic0: Spurious interrupt detected: last irq: 27 on CPU0 gic0: Spurious interrupt detected: last irq: 27 on CPU2 gic0: Spurious interrupt detected: last irq: 114 on CPU1 gic0: Spurious interrupt detected: last irq: 27 on CPU3 gic0: Spurious interrupt detected: last irq: 27 on CPU3 gic0: Spurious interrupt detected: last irq: 114 on CPU1 gic0: Spurious interrupt detected: last irq: 27 on CPU2 gic0: Spurious interrupt detected: last irq: 27 on CPU2 gic0: Spurious interrupt detected: last irq: 27 on CPU2 gic0: gic0: Spurious interrupt detected: last irq: 27 on CPU3 Spurious interrupt detected: last irq: 27 on CPU0 gic0: Spurious interrupt detected: last irq: 27 on CPU0 gic0: Spurious interrupt detected: last irq: 27 on CPU0 gic0: Spurious interrupt detected: last irq: 27 on CPU0 gic0: Spurious interrupt detected: last irq: 114 on CPU1 gic0: Spurious interrupt detected: last irq: 27 on CPU0 gic0: Spurious interrupt detected: last irq: 27 on CPU0 When building world (3 threads) the frequency is about a few each second, idle perhaps a few each hour. I have ethernet connected and a small USB hard disk with it's own power supply, which hosts /usr/{src,obj,ports}. In addition I noticed an ethernet lock up from time to time. Executing "dmesg" in a ssh session is often sufficient to trigger it. The weird thing is that after some boots (perhaps 1 out of 10) the spurious interrupts do not happen! I have not been able to detect a pattern here. Can others reproduce these findings? Thanks in advance for any hints. From owner-freebsd-arm@freebsd.org Fri Apr 21 08:57:57 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 13256D3B3DE for ; Fri, 21 Apr 2017 08:57:57 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-20.reflexion.net [208.70.210.20]) (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 CCE6C1D6A for ; Fri, 21 Apr 2017 08:57:56 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 8700 invoked from network); 21 Apr 2017 08:58:59 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 21 Apr 2017 08:58:59 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.40.0) with SMTP; Fri, 21 Apr 2017 04:57:54 -0400 (EDT) Received: (qmail 3421 invoked from network); 21 Apr 2017 08:57:54 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 21 Apr 2017 08:57:54 -0000 Received: from [192.168.1.106] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id CF605EC86E7; Fri, 21 Apr 2017 01:57:53 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Pine64 spurious interrupts From: Mark Millard In-Reply-To: Date: Fri, 21 Apr 2017 01:57:53 -0700 Cc: freebsd-arm Content-Transfer-Encoding: quoted-printable Message-Id: <28157698-A5E9-4194-9B5D-77D7B487ADFB@dsl-only.net> References: To: Tom Vijlbrief X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Apr 2017 08:57:57 -0000 [I had done the spurious-interrupt code change long enough ago that having not had any notices of non-1023 for the current irq that I'd forgotten which board I'd had the problem with. It was the Pine64+ 2GB. So correcting my earlier notes. . .] On 2017-Apr-21, at 1:07 AM, Tom Vijlbrief wrote: > I have a lot of spurious interrupts on my Pine64. I've seen this as well. I sent out notes on the lists back on 2016-Nov-07 and 2017-Jan-28/31. It is a Pine64+ 2GB. I later got access to a rpi3 as well but I run the same world and kernel build on it and so do not know if it would generate the messages. I'll have to try that at some point. I'd seen a couple of the notices on armv7 (a bpim3) before I'd made any changes to what I build. But very rare. (I'd swapped the status in my head when I wrote before.) > Even in idle single user mode: >=20 > # pstree > -+=3D 00001 root /sbin/init -- > \-+=3D 01783 root -sh (sh) > \-+=3D 01804 root pstree > \--- 01805 root ps -axwwo user,pid,ppid,pgid,command > #=20 >=20 > gic0: Spurious interrupt detected: last irq: 27 on CPU3 > gic0: Spurious interrupt detected: last irq: 27 on CPU0 > gic0: Spurious interrupt detected: last irq: 27 on CPU2 > gic0: Spurious interrupt detected: last irq: 114 on CPU1 > gic0: Spurious interrupt detected: last irq: 27 on CPU3 > gic0: Spurious interrupt detected: last irq: 27 on CPU3 > gic0: Spurious interrupt detected: last irq: 114 on CPU1 > gic0: Spurious interrupt detected: last irq: 27 on CPU2 > gic0: Spurious interrupt detected: last irq: 27 on CPU2 > gic0: Spurious interrupt detected: last irq: 27 on CPU2 > gic0: gic0: Spurious interrupt detected: last irq: 27 on CPU3 > Spurious interrupt detected: last irq: 27 on CPU0 > gic0: Spurious interrupt detected: last irq: 27 on CPU0 > gic0: Spurious interrupt detected: last irq: 27 on CPU0 > gic0: Spurious interrupt detected: last irq: 27 on CPU0 > gic0: Spurious interrupt detected: last irq: 114 on CPU1 > gic0: Spurious interrupt detected: last irq: 27 on CPU0 > gic0: Spurious interrupt detected: last irq: 27 on CPU0 >=20 > When building world (3 threads) the frequency is about a few each = second, idle perhaps a few each hour. I got thousands in sort order during buildworld buildkernel (-j4). Idle was normally rare for one to be generated but it did happen on occasion. If I re-enable the notices I should try -j3 vs. -j4 and see how much of a difference it makes. The 1023 IRQ can be delivered because another core has handled the original IRQ as I remember what I quoted in the prior message. So keeping all cores busy might generate more of these notices. > I have ethernet connected and a small USB hard disk with it's own = power supply, which hosts /usr/{src,obj,ports}. Similarly here (but an SSD on a powered hub), with the whole root file system on the SSD. Only booting through the kernel stage comes from /dev/mmcsd0 . > In addition I noticed an ethernet lock up from time to time. Executing = "dmesg" in a ssh session is often sufficient to trigger it. I used to get this but I've not seen it since the recent fixes to fork behavior. May be it would happen again if I re-enabled the gic0 messages for current irq 1023, another potential experiment. One of the fixes to fork was avoiding interrupts corrupting a special register. > The weird thing is that after some boots (perhaps 1 out of 10) the = spurious interrupts do not happen! I have not been able to detect a = pattern here. I also had occasions when it would not happen after booting, or at least for a significant time after booting, even if I did a buildworld buildkernel. I did have examples where it eventually started getting the messages again. > Can others reproduce these findings? I have in the past but I currently have things set up to generate messages only when the current irq is not 1023 --which generates no such messages to speak of. > Thanks in advance for any hints. I only got as far as learning that the current IRQ was (nearly?) always 1023. I really did not learn any more. (I went after investigating fork issues once I could use the console reasonably.) I've not figured out how to get any more useful information so far. But the code change that I sent should get rid of the notices. That in turn makes the console far more useful. Other than that it just masks the problem, whatever the problem is. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Fri Apr 21 09:21:34 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E0360D3BE4D for ; Fri, 21 Apr 2017 09:21:34 +0000 (UTC) (envelope-from tvijlbrief@gmail.com) Received: from mail-yw0-x236.google.com (mail-yw0-x236.google.com [IPv6:2607:f8b0:4002:c05::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 9F5FCCC6 for ; Fri, 21 Apr 2017 09:21:34 +0000 (UTC) (envelope-from tvijlbrief@gmail.com) Received: by mail-yw0-x236.google.com with SMTP id k11so4027770ywb.1 for ; Fri, 21 Apr 2017 02:21:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=u8FaWFDOoHxOlBJoLT2aCkIBlO3jCCZ2BvCVtZ05sgM=; b=oPMcbAvAkp4dLjhdPJ34CMgWnsXbuj9fy7ndYgD+kfCczGtJSy/nNbZgsHYZG1cIrT byMt4YP+VGRvjrBs75UWiWlQW6KyH2zCJNO1UZ9V/4ywCyqVRnz8tvrfO/yPqbnhSGwt FumIy/DHM4Jl6S7/g6O3Yj4qV/o90Vszfu64cSBJSshHUh8A6rXJDPSlChfcFITd1Dzt Nh4dFk4q7VYmVfj3E5pDp9vqx61zlN6izY2eGRjXXAk0xEaNMQRfOCIlY7KTwdv5lRw9 0LhLaTgiKDHrJWGVpEeMuqYsSpDe4/BaFMfdaLSiSW0aKrCEPX+hubFe/w+rxPduovjU 6rNg== 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=u8FaWFDOoHxOlBJoLT2aCkIBlO3jCCZ2BvCVtZ05sgM=; b=ujKdYxbUXhoAE9v/By4i21HMVr6A2NlpEpN9d2ZEtazW0STDX8lcOdx1jwZkTk0i03 e9saC0QR5fVj+QW4vPVDdBrYdECONIFbf3hBb2qq8BiGA7qHnpWXN8kEwJWMVsUnnu6b LPrlPfUMUA6TD6fg/PF1p44tFpk86lHBnX+lE6Pd0OqvdS1BOSO2/zuKhi46ImRZzWXx NEYlFHdLRY3Xr2R/Jyrb7bDm86FweZU5kRRcCNKP3XzM+1vzOQ054OyWIQwIxhaLfONH +xZmvLtO1XSqM8gjkL6hkZtu6OwevSi22jK475FJhHCzgONwqRW9v4ZcJPK/kClN4yb6 g92w== X-Gm-Message-State: AN3rC/4yfVWdQj+niP0241Avvox2E6W13O5CuyP21bI7tki+6SGVzJiV /nH/KZNg7bHvojlhDIrOMjmZ10WTv5fF X-Received: by 10.13.236.199 with SMTP id v190mr10239565ywe.65.1492766493744; Fri, 21 Apr 2017 02:21:33 -0700 (PDT) MIME-Version: 1.0 References: <28157698-A5E9-4194-9B5D-77D7B487ADFB@dsl-only.net> In-Reply-To: <28157698-A5E9-4194-9B5D-77D7B487ADFB@dsl-only.net> From: Tom Vijlbrief Date: Fri, 21 Apr 2017 09:21:23 +0000 Message-ID: Subject: Re: Pine64 spurious interrupts To: Mark Millard Cc: freebsd-arm Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Apr 2017 09:21:35 -0000 Hi Mark, Thanks for your feedback! On boot I often find a single spurious interrupt 92 generated on my 1GB Pine64+: root@pine64:~ # dmesg | grep pur gic0: Spurious interrupt detected: last irq: 92 on CPU0 I used to get a lot of 1023's but the current kernel gives me: ic0: Spurious interrupt detected: last irq: 92 on CPU0 root@pine64:~ # gic0: Spurious interrupt detected: last irq: 106 on CPU3 gic0: Spurious interrupt detected: last irq: 27 on CPU0 gic0: Spurious interrupt detected: last irq: 27 on CPU3 gic0: Spurious interrupt detected: last irq: 27 on CPU2 gic0: Spurious interrupt detected: last irq: 27 on CPU2 gic0: Spurious interrupt detected: last irq: 27 on CPU3 gic0: gic0: Spurious interrupt detected: last irq: 27 on CPU2 Spurious interrupt detected: last irq: 27 on CPU1 gic0: Spurious interrupt detected: last irq: 106 on CPU3 gic0: Spurious interrupt detected: last irq: 27 on CPU2 gic0: Spurious interrupt detected: last irq: 27 on CPU1 I want to upgrade my RPI first model (256Mb :-) which is my low power server to this Pine64 board, but this spurious interrupt issue holds me back. Op vr 21 apr. 2017 om 10:57 schreef Mark Millard : > [I had done the spurious-interrupt code change long enough ago > that having not had any notices of non-1023 for the current > irq that I'd forgotten which board I'd had the problem > with. It was the Pine64+ 2GB. So correcting my earlier > notes. . .] > > On 2017-Apr-21, at 1:07 AM, Tom Vijlbrief wrote: > > > I have a lot of spurious interrupts on my Pine64. > > I've seen this as well. I sent out notes on the > lists back on 2016-Nov-07 and 2017-Jan-28/31. It > is a Pine64+ 2GB. I later got access to a rpi3 > as well but I run the same world and kernel build > on it and so do not know if it would generate the > messages. I'll have to try that at some point. > > I'd seen a couple of the notices on armv7 (a bpim3) > before I'd made any changes to what I build. But > very rare. (I'd swapped the status in my head when > I wrote before.) > > > Even in idle single user mode: > > > > # pstree > > -+= 00001 root /sbin/init -- > > \-+= 01783 root -sh (sh) > > \-+= 01804 root pstree > > \--- 01805 root ps -axwwo user,pid,ppid,pgid,command > > # > > > > gic0: Spurious interrupt detected: last irq: 27 on CPU3 > > gic0: Spurious interrupt detected: last irq: 27 on CPU0 > > gic0: Spurious interrupt detected: last irq: 27 on CPU2 > > gic0: Spurious interrupt detected: last irq: 114 on CPU1 > > gic0: Spurious interrupt detected: last irq: 27 on CPU3 > > gic0: Spurious interrupt detected: last irq: 27 on CPU3 > > gic0: Spurious interrupt detected: last irq: 114 on CPU1 > > gic0: Spurious interrupt detected: last irq: 27 on CPU2 > > gic0: Spurious interrupt detected: last irq: 27 on CPU2 > > gic0: Spurious interrupt detected: last irq: 27 on CPU2 > > gic0: gic0: Spurious interrupt detected: last irq: 27 on CPU3 > > Spurious interrupt detected: last irq: 27 on CPU0 > > gic0: Spurious interrupt detected: last irq: 27 on CPU0 > > gic0: Spurious interrupt detected: last irq: 27 on CPU0 > > gic0: Spurious interrupt detected: last irq: 27 on CPU0 > > gic0: Spurious interrupt detected: last irq: 114 on CPU1 > > gic0: Spurious interrupt detected: last irq: 27 on CPU0 > > gic0: Spurious interrupt detected: last irq: 27 on CPU0 > > > > When building world (3 threads) the frequency is about a few each > second, idle perhaps a few each hour. > > I got thousands in sort order during buildworld buildkernel > (-j4). Idle was normally rare for one to be generated but > it did happen on occasion. > > If I re-enable the notices I should try -j3 vs. -j4 > and see how much of a difference it makes. > > The 1023 IRQ can be delivered because another core > has handled the original IRQ as I remember what I > quoted in the prior message. So keeping all cores > busy might generate more of these notices. > > > I have ethernet connected and a small USB hard disk with it's own power > supply, which hosts /usr/{src,obj,ports}. > > Similarly here (but an SSD on a powered hub), with the > whole root file system on the SSD. Only booting through > the kernel stage comes from /dev/mmcsd0 . > > > In addition I noticed an ethernet lock up from time to time. Executing > "dmesg" in a ssh session is often sufficient to trigger it. > > I used to get this but I've not seen it since the > recent fixes to fork behavior. May be it would happen > again if I re-enabled the gic0 messages for current > irq 1023, another potential experiment. > > One of the fixes to fork was avoiding interrupts > corrupting a special register. > > > The weird thing is that after some boots (perhaps 1 out of 10) the > spurious interrupts do not happen! I have not been able to detect a pattern > here. > > I also had occasions when it would not happen after booting, > or at least for a significant time after booting, even if > I did a buildworld buildkernel. I did have examples where > it eventually started getting the messages again. > > > Can others reproduce these findings? > > I have in the past but I currently have things set up > to generate messages only when the current irq is not > 1023 --which generates no such messages to speak of. > > > Thanks in advance for any hints. > > I only got as far as learning that the current IRQ > was (nearly?) always 1023. I really did not learn > any more. (I went after investigating fork issues > once I could use the console reasonably.) > > I've not figured out how to get any more useful > information so far. > > But the code change that I sent should get rid of the > notices. That in turn makes the console far more useful. > Other than that it just masks the problem, whatever the > problem is. > > === > Mark Millard > markmi at dsl-only.net > > > > From owner-freebsd-arm@freebsd.org Fri Apr 21 11:50:26 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C861CD49D75 for ; Fri, 21 Apr 2017 11:50:26 +0000 (UTC) (envelope-from jiashiun@gmail.com) Received: from mail-qt0-x235.google.com (mail-qt0-x235.google.com [IPv6:2607:f8b0:400d:c0d::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 8BC45DC for ; Fri, 21 Apr 2017 11:50:26 +0000 (UTC) (envelope-from jiashiun@gmail.com) Received: by mail-qt0-x235.google.com with SMTP id y33so67506414qta.2 for ; Fri, 21 Apr 2017 04:50:26 -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=yS3QiVApGLGdrrbbBzYYKzSSRFSlGZLRMNMfTno21g4=; b=IVfarFXxHke3gmH7z3GDHUbr/JhEPHtJbur7+WS34FuRwO/8gaVK+HT+Ihes7PLzk9 JmD1/yAr8ICKxR3VMxe3NI6WbFO9nzoapc2ldN00jQ8vpPzHonpGlTVdVMEav1Gsoqhk Aqi2brg4IhYyeeaFwETK+4IGRMjKlF6MiTSnJ5zy42R+7TVY4vjqkjjBXBPe9MaQ2yXT iR+iEzWe7Kmc3rFS3b2qHsOB9VXoYlpQ6SzFJlQGcLWTlaf67ZkVn7wBsLIaGQCubbak O6WSHGdsIvX36nS6moT9F4XotWfrvqzGjxvOI89QTR91CgKQMj+f2SiyiewZ2bxUl001 1acQ== 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=yS3QiVApGLGdrrbbBzYYKzSSRFSlGZLRMNMfTno21g4=; b=AptpX2zeQFf4gwcgXkECNSs6eO3OXRMqvXzBTNlGoX4R+smrWLx1+KguOJKJWrz9Kc 2Z14T86aUAdni2x6hxEaQBDw/CK4P3Q1a/uajOgZk3i2AyhnvaQi7I1xtGsejNnk9Wt4 EVKCkZfmychi8G+NyrvMHczPfoIIdHvQwtFiW6q5l2bN5JO/9qYkXzv2EGMJSvFL2xUY LbBxECjLyweDPzKblpnD2TvvWh7yAj70fTcBkYvaSlPm62gqK6jdLznr8x/BjhwGsWzQ rxbWorum1t/HrfkgcIjp/RnuzvSymdOgl0gv0rn5ip3Vaslb8Kyz6x8na683Gvx39iWf JTfA== X-Gm-Message-State: AN3rC/7ztB2wOKr/s3K5ZuQxnPtC0b6NVgtcUUDLgqKTT1F4TPondPhJ oeGEVdRxiUN6If83k3E6Iz9rd9LaMAxX X-Received: by 10.200.55.86 with SMTP id p22mr12140884qtb.167.1492775425057; Fri, 21 Apr 2017 04:50:25 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.100.143 with HTTP; Fri, 21 Apr 2017 04:49:54 -0700 (PDT) From: Jia-Shiun Li Date: Fri, 21 Apr 2017 19:49:54 +0800 Message-ID: Subject: aarch64 build on nfs often stops at objcopy To: "freebsd-arm@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Apr 2017 11:50:26 -0000 happens both on rpi3 native build and amd64 cross build, when MAKEOBJDIRPREFIX is set to nfs directory, it often stops at objcopy: failed to read section OTOH if set to output to local disks, then everything goes well. amd64 & armv6 are good on nfs. It happens to me since 1~2 weeks ago or so. native build on rpi3, r317096: --- clang-tblgen.debug --- objcopy --only-keep-debug clang-tblgen.full clang-tblgen.debug objcopy: failed to read section: *** [clang-tblgen.debug] Error code 1 make[3]: stopped in /personal/freebsd/testsource/usr.bin/clang/clang-tblgen 1 error make[3]: stopped in /personal/freebsd/testsource/usr.bin/clang/clang-tblgen *** [_bootstrap-tools-usr.bin/clang/clang-tblgen] Error code 2 make[2]: stopped in /personal/freebsd/testsource cross build from amd64, r317045: --- lldb.debug --- objcopy --only-keep-debug lldb.full lldb.debug ...... ...... objcopy: failed to read section: *** [lldb.debug] Error code 1 make[5]: stopped in /tmp/src/usr.bin/clang/lldb 1 error make[5]: stopped in /tmp/src/usr.bin/clang/lldb *** [all_subdir_usr.bin/clang/lldb] Error code 2 make[4]: stopped in /tmp/src/usr.bin/clang cross build, with aarch64-binutils-2.27_6,1: (time nice +20 env MAKEOBJDIRPREFIX=/mnt/external-binutils make -j12 KERNCONF=GENERIC-NODEBUG TARGET_ARCH=aarch64 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin buildworld buildkernel | tee build.ext-binutilslog) --- vers.c --- MAKE=make sh /tmp/src/sys/conf/newvers.sh GENERIC-NODEBUG --- vers.o --- cc -target aarch64-unknown-freebsd12.0 --sysroot=/mnt/external-binutils/arm64.aarch64/tmp/src/tmp -B/usr/local/aarch64-freebsd/bin -c -O -pipe -g -nostdinc -I. -I/tmp/src/sys -I/tmp/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -mgeneral-regs-only -ffixed-x18 -ffreestanding -fwrapv -fstack-protector -gdwarf-2 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual-Wundef -Wno-pointer-sign -D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -Wno-error-unused-function -Wno-error-pointer-sign -Wno-error-shift-negative-value -Wno-error-address-of-packed-member -std=iso9899:1999 -Werror vers.c ctfconvert -L VERSION -g vers.o --- kernel.full --- linking kernel.full ctfmerge -L VERSION -g -o kernel.full ... ERROR: ctfmerge: kernel.full: Can't open symbol table objcopy: failed to read section: *** [kernel.full] Error code 1 make[2]: stopped in /mnt/external-binutils/arm64.a arch64/tmp/src/sys/GENERIC-NODEBUG 1 error make[2]: stopped in /mnt/external-binutils/arm64.a arch64/tmp/src/sys/GENERIC-NODEBUG *** [buildkernel] Error code 2 make[1]: stopped in /tmp/src 1 error make[1]: stopped in /tmp/src 1 error*** [buildkernel] Error code 2 make: stopped in /tmp/src make: stopped in /tmp/src -Jia-Shiun From owner-freebsd-arm@freebsd.org Fri Apr 21 15:54:55 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 011FED494A8 for ; Fri, 21 Apr 2017 15:54:54 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-20.reflexion.net [208.70.210.20]) (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 B02A0803 for ; Fri, 21 Apr 2017 15:54:54 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 706 invoked from network); 21 Apr 2017 15:54:53 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 21 Apr 2017 15:54:53 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.40.0) with SMTP; Fri, 21 Apr 2017 11:54:53 -0400 (EDT) Received: (qmail 17990 invoked from network); 21 Apr 2017 15:54:52 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 21 Apr 2017 15:54:52 -0000 Received: from [192.168.1.106] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 44393EC8F25; Fri, 21 Apr 2017 08:54:52 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Pine64 spurious interrupts From: Mark Millard In-Reply-To: Date: Fri, 21 Apr 2017 08:54:51 -0700 Cc: freebsd-arm Content-Transfer-Encoding: quoted-printable Message-Id: References: <28157698-A5E9-4194-9B5D-77D7B487ADFB@dsl-only.net> To: Tom Vijlbrief X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Apr 2017 15:54:55 -0000 On 2017-Apr-21, at 2:21 AM, Tom Vijlbrief wrote: > Hi Mark, >=20 > Thanks for your feedback! >=20 > On boot I often find a single spurious interrupt 92 generated on my = 1GB Pine64+: >=20 > root@pine64:~ # dmesg | grep pur > gic0: Spurious interrupt detected: last irq: 92 on CPU0 >=20 > I used to get a lot of 1023's but the current kernel gives me: I'll note that the messages do not print the current IRQ value but just the prior/last one. (Possibly because 1023 was not useful once known.) It is the current IRQ number that seems to always be 1023 in my testing. > ic0: Spurious interrupt detected: last irq: 92 on CPU0 > root@pine64:~ # gic0: Spurious interrupt detected: last irq: 106 on = CPU3 > gic0: Spurious interrupt detected: last irq: 27 on CPU0 > gic0: Spurious interrupt detected: last irq: 27 on CPU3 > gic0: Spurious interrupt detected: last irq: 27 on CPU2 > gic0: Spurious interrupt detected: last irq: 27 on CPU2 > gic0: Spurious interrupt detected: last irq: 27 on CPU3 > gic0: gic0: Spurious interrupt detected: last irq: 27 on CPU2 > Spurious interrupt detected: last irq: 27 on CPU1 > gic0: Spurious interrupt detected: last irq: 106 on CPU3 > gic0: Spurious interrupt detected: last irq: 27 on CPU2 > gic0: Spurious interrupt detected: last irq: 27 on CPU1 >=20 > I want to upgrade my RPI first model (256Mb :-) which is my low power = server to this Pine64 board, > but this spurious interrupt issue holds me back. >=20 >=20 >=20 > Op vr 21 apr. 2017 om 10:57 schreef Mark Millard = : > [I had done the spurious-interrupt code change long enough ago > that having not had any notices of non-1023 for the current > irq that I'd forgotten which board I'd had the problem > with. It was the Pine64+ 2GB. So correcting my earlier > notes. . .] >=20 > On 2017-Apr-21, at 1:07 AM, Tom Vijlbrief = wrote: >=20 > > I have a lot of spurious interrupts on my Pine64. >=20 > I've seen this as well. I sent out notes on the > lists back on 2016-Nov-07 and 2017-Jan-28/31. It > is a Pine64+ 2GB. I later got access to a rpi3 > as well but I run the same world and kernel build > on it and so do not know if it would generate the > messages. I'll have to try that at some point. >=20 > I'd seen a couple of the notices on armv7 (a bpim3) > before I'd made any changes to what I build. But > very rare. (I'd swapped the status in my head when > I wrote before.) >=20 > > Even in idle single user mode: > > > > # pstree > > -+=3D 00001 root /sbin/init -- > > \-+=3D 01783 root -sh (sh) > > \-+=3D 01804 root pstree > > \--- 01805 root ps -axwwo user,pid,ppid,pgid,command > > # > > > > gic0: Spurious interrupt detected: last irq: 27 on CPU3 > > gic0: Spurious interrupt detected: last irq: 27 on CPU0 > > gic0: Spurious interrupt detected: last irq: 27 on CPU2 > > gic0: Spurious interrupt detected: last irq: 114 on CPU1 > > gic0: Spurious interrupt detected: last irq: 27 on CPU3 > > gic0: Spurious interrupt detected: last irq: 27 on CPU3 > > gic0: Spurious interrupt detected: last irq: 114 on CPU1 > > gic0: Spurious interrupt detected: last irq: 27 on CPU2 > > gic0: Spurious interrupt detected: last irq: 27 on CPU2 > > gic0: Spurious interrupt detected: last irq: 27 on CPU2 > > gic0: gic0: Spurious interrupt detected: last irq: 27 on CPU3 > > Spurious interrupt detected: last irq: 27 on CPU0 > > gic0: Spurious interrupt detected: last irq: 27 on CPU0 > > gic0: Spurious interrupt detected: last irq: 27 on CPU0 > > gic0: Spurious interrupt detected: last irq: 27 on CPU0 > > gic0: Spurious interrupt detected: last irq: 114 on CPU1 > > gic0: Spurious interrupt detected: last irq: 27 on CPU0 > > gic0: Spurious interrupt detected: last irq: 27 on CPU0 > > > > When building world (3 threads) the frequency is about a few each = second, idle perhaps a few each hour. >=20 > I got thousands in sort order during buildworld buildkernel > (-j4). Idle was normally rare for one to be generated but > it did happen on occasion. >=20 > If I re-enable the notices I should try -j3 vs. -j4 > and see how much of a difference it makes. >=20 > The 1023 IRQ can be delivered because another core > has handled the original IRQ as I remember what I > quoted in the prior message. So keeping all cores > busy might generate more of these notices. >=20 > > I have ethernet connected and a small USB hard disk with it's own = power supply, which hosts /usr/{src,obj,ports}. >=20 > Similarly here (but an SSD on a powered hub), with the > whole root file system on the SSD. Only booting through > the kernel stage comes from /dev/mmcsd0 . >=20 > > In addition I noticed an ethernet lock up from time to time. = Executing "dmesg" in a ssh session is often sufficient to trigger it. >=20 > I used to get this but I've not seen it since the > recent fixes to fork behavior. May be it would happen > again if I re-enabled the gic0 messages for current > irq 1023, another potential experiment. >=20 > One of the fixes to fork was avoiding interrupts > corrupting a special register. >=20 > > The weird thing is that after some boots (perhaps 1 out of 10) the = spurious interrupts do not happen! I have not been able to detect a = pattern here. >=20 > I also had occasions when it would not happen after booting, > or at least for a significant time after booting, even if > I did a buildworld buildkernel. I did have examples where > it eventually started getting the messages again. >=20 > > Can others reproduce these findings? >=20 > I have in the past but I currently have things set up > to generate messages only when the current irq is not > 1023 --which generates no such messages to speak of. >=20 > > Thanks in advance for any hints. >=20 > I only got as far as learning that the current IRQ > was (nearly?) always 1023. I really did not learn > any more. (I went after investigating fork issues > once I could use the console reasonably.) >=20 > I've not figured out how to get any more useful > information so far. >=20 > But the code change that I sent should get rid of the > notices. That in turn makes the console far more useful. > Other than that it just masks the problem, whatever the > problem is. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Sat Apr 22 02:22:48 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6067ED49749 for ; Sat, 22 Apr 2017 02:22:48 +0000 (UTC) (envelope-from jungleboogie0@gmail.com) Received: from mail-io0-x22f.google.com (mail-io0-x22f.google.com [IPv6:2607:f8b0:4001:c06::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 21C21FA; Sat, 22 Apr 2017 02:22:48 +0000 (UTC) (envelope-from jungleboogie0@gmail.com) Received: by mail-io0-x22f.google.com with SMTP id r16so132847820ioi.2; Fri, 21 Apr 2017 19:22:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=ENOcVDHjcEV0A989EK2hm+nQebBDMkejn//KzrTG/m0=; b=vEDFevFAC9EX2Wy/f3GPksw5yZTDqlto/aBF8RxgLbGYwKI0q7mS2bk+fpwwzYnPl+ sZxKNXWSSWEvCf75jCUx5asVjGgqAbD1mhTmjST4o+KJPYG9fem28OWt0x+uROqf3Gze osCLIv6JGbfAKcQF2GMSj/kRsYzKRIstbUDctyABNDY+3bY5sTccBzPcF97slyFqIRl4 2DS7jyW1gmPI2luNWCEx6ZozInVGsiMgrgs9LeUhafLNO928yTxw7VBNZ/lLgs2kLAXn CF7Zy2nkZLMtYFdIpPAhtLfxIU8vuctwaFrEHS4SerI2encp1hPfEv43r1j9O4c/5Nyg 6zXg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=ENOcVDHjcEV0A989EK2hm+nQebBDMkejn//KzrTG/m0=; b=XOTgMgr3rSCsIkGO5+8x0ohEcpCYrlkEwFbG/qDmJ3RpJQTv6FGA1wAfjmU+7o6+FJ CNUiFLbZN8fJFnFCrgkC/DvMOTtB1U+vRaHj+RBuRV8j6NPcIptqcLs5IZ8Xk5Cjc9OQ tu6HrFa2He3CZuPtkYFIXaVFVLkU3I8dsg110H1d2SyjCYV/Syd82GNSC2EQt0CfLqZx nogyi4OfQ0ph8dcDwTfMZNnw0D/nKJaMxvIsc6+9swoEhFAvWyo1plZzQxWW2nmc7qTK UiazclCmy2+7RMAeIqxteriTa+iQpTLPCUd1kESHHum/gyRzsTFG0CFSJQF3XKjGQmvw FuPw== X-Gm-Message-State: AN3rC/7DVXrhmOsHaWWK6hNSPg1RkGXFG1+X3JXsaRZRszeEQyORPSxr dMHuGrZ/xmKNGQ+45MI= X-Received: by 10.98.202.149 with SMTP id y21mr15167490pfk.225.1492827767245; Fri, 21 Apr 2017 19:22:47 -0700 (PDT) Received: from [192.168.88.254] (ip70-173-249-54.lv.lv.cox.net. [70.173.249.54]) by smtp.gmail.com with ESMTPSA id 12sm18184143pgb.35.2017.04.21.19.22.46 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 21 Apr 2017 19:22:46 -0700 (PDT) Subject: Re: beaglebone black: MMC partition switch failed To: Ian Lepore References: <5bac0dbc-6d2b-c757-0cd3-babbd048cfd2@gmail.com> <20170418155102.GO2455@FreeBSD.org> <1492534652.96207.28.camel@freebsd.org> Cc: =?UTF-8?B?T3RhY8OtbGlv?= , "freebsd-arm@freebsd.org" From: jungle boogie Message-ID: <108c5e4a-b93e-c8f7-5245-1edfb0831ad6@gmail.com> Date: Fri, 21 Apr 2017 19:22:45 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Apr 2017 02:22:48 -0000 On 04/18/2017 10:30 AM, jungle Boogie wrote: > On 18 April 2017 at 09:57, Ian Lepore wrote: >> The 20170405 image Glen mentioned works fine, I just DLed and tested >> it. > > > Thanks for the confirmation, but that means something different is > happening to my BBB. > > I wrote that build to my SD card, put it in the BBB, held down s2, > powered it up: > > U-Boot SPL 2017.01-rc3 (Apr 05 2017 - 05:21:19) > Trying to boot from MMC1** First descriptor is NOT a primary desc on 0:1 ** > MMC partition switch failed > *** Warning - MMC partition switch failed, using default environment > > ** Partition 1 not valid on device 0 ** > spl_register_fat_device: fat register err - -1 > spl_load_image_fat: error reading image u-boot.img, err - -1 > MMC partition switch failed > *** Warning - MMC partition switch failed, using default environment > > spl: no partition table found > SPL: failed to boot from all boot devices > ### ERROR ### Please RESET the board ### > > > Does this version need to be more recent for it to read data from the SD card? > So have I completely broken the BBB somehow? > Thanks! > From owner-freebsd-arm@freebsd.org Sat Apr 22 07:41:10 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0D90ED4A64A; Sat, 22 Apr 2017 07:41:10 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 63AFBCC; Sat, 22 Apr 2017 07:41:08 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([78.52.170.118]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MKpvc-1d1pfA15zk-0002gG; Sat, 22 Apr 2017 09:41:00 +0200 Date: Sat, 22 Apr 2017 09:40:49 +0200 From: "O. Hartmann" To: Jan Beich Cc: "O. Hartmann" , freebsd-ports , freebsd-arm@freebsd.org Subject: Re: poudriere: crossbuilding for arm64 fails: pkg-static: No package files have been found Message-ID: <20170422093814.3924e64d@thor.intern.walstatt.dynvpn.de> In-Reply-To: References: <20170419143342.17c190b9@freyja.zeit4.iv.bundesimmobilien.de> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/x0.amSuFZbVX8sSk+wQkPJ+"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:LbZtSfxLMdujZjwbYNEu1pOF/+sTviWYqujtyPgSRMRdAXVo/xS Xlse1m4bgomoAnlI6/YsMSRYAIBx9gb0b29hTV3kJ8zl5Hz69Yq7al9vAhNxsn+/kq5x1O1 Y4pnOhQECNZnqb9SOEnqny/1DLbjWGtk0F3w2ORHzuZF/wmsoDdgodtwQohP8DIyYp0I4TD ZafeNeU9x73JXVFTi0VIw== X-UI-Out-Filterresults: notjunk:1;V01:K0:KQgBWBXA49M=:qSZEem9qlmbICO3rhOCoLH 4ynzxtTWP/hveu7cuFFLzJy57ayN6KUC4QQWUZaGNZs/cEcAIgGWSKXDwuwpWDJmCwg2YquXH n0cr43W5cCl9qTMSEeNCcVKX/qQEIFGPO/FoLnvsH8M3jmIsv85Rd2ocF6wC+vQonRGHmocMH UpPoX6OcyTP8rZQeGK8GxtIGNrdiYY87lo2Qli+DY/nWUvlPbF/SjQjtWFTPIWIAZ0gieiH1c PZd/hC+MaQDOJtDWzJJi2iw3Jig2iQTunmUt9lajX+WFWEwEIAA27VA+6qcFQ31WsGQkFdmI5 OjFb6zi4a0vvnAvfvOE9jvAktV+rznumoigpOjV29vcRESa5k+CFmUIg62gU3sUXGLbFfycfa QKTdGkQj+Dikos44ZLU1TboWL99czo9YjnMnFa8YQB3IJ937kooZF1laaHbjmv92gxK21OoCT 7H1E/DQi8HdqB3FG53KTxC1N0csryCXXiFVQZIvgAlfWTYky0iEwdfhaTX2fPXEKAtwEu8uHE 5pAxVnw/Hvi1gA1xZZKWjhlq25FeYLIZIYTMbUN/vzJNFd0uj7NclnovSc3hvu5888W6RxPco dBozVShl7ciQVaIg1EwPcwpq8XbbkLdTLqPutExOeZWu16ipIsvk1SWCnIjsd9BeDLNv+Bh6b i2mr3gsh7wGB6Cxd1/37Rx0PZAcu3axxehEt62nGe5ms0vTnm/9Q6HHmkvs5L+TKaS2eMhJlW UhMNytb4cgBU8n3y+qARtrP+vU+t2oZ1CzNXZlhU2EXVndiaMj5SVdUxybU= X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Apr 2017 07:41:10 -0000 --Sig_/x0.amSuFZbVX8sSk+wQkPJ+ Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Thu, 20 Apr 2017 03:29:56 +0200 Jan Beich schrieb: > "O. Hartmann" writes: >=20 > > Trying to build a repository via poudriere fails on recent 12-CURRENT (= FreeBSD > > 12.0-CURRENT #2 r317090: Tue Apr 18 15:32:23 CEST 2017 amd64) initially= with > > failing to build ports-mgmt/pkg. > > > > poudriere's log reports: > > > > [...] > > configure: error: in `/wrkdirs/usr/ports/ports-mgmt/pkg/work/pkg-1.10.1= ': > > configure: error: C compiler cannot create executables =20 >=20 > Probably https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217189 Maybe, yes. It is a pity. When starting poudriere to build on 12-CURRENT/arm64, I see a long time not= hing before the error pops up. qemu_user_static is running on several instances on a 4-= core XEON E3-1245 V2 @ 3.40GHz and ~ 3 to 4 minutes, nothing obviously happens in con= trary to amd64's immediate response. The error pops up then very soon. --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/x0.amSuFZbVX8sSk+wQkPJ+ Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWPsJAQAKCRDS528fyFhY lFRNAf9rjXAi4Ju4D0l+mKbRV9ovrqA+HSaTy57ERoZXCnenCote/7FY3y3MPGHH c0kRMib2e3dOjFfnUwDJmYcRUylQAgCHt5xG1uGnEAFVLi5U/Z69w7yYfZOnURmH 1N6t7uiN8Jd8Nn10qu0v8nknD4HJzbpEpcXRXkySNupQ/P5rVAN2 =ybdH -----END PGP SIGNATURE----- --Sig_/x0.amSuFZbVX8sSk+wQkPJ+-- From owner-freebsd-arm@freebsd.org Sat Apr 22 23:04:18 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CCE58D4B1A1 for ; Sat, 22 Apr 2017 23:04:18 +0000 (UTC) (envelope-from brett@lariat.net) Received: from mail.lariat.net (mail.lariat.net [66.62.230.51]) by mx1.freebsd.org (Postfix) with ESMTP id 9AE6A1A3 for ; Sat, 22 Apr 2017 23:04:18 +0000 (UTC) (envelope-from brett@lariat.net) Received: from Toshi.lariat.net (IDENT:ppp1000.lariat.net@localhost [127.0.0.1]) by mail.lariat.net (8.9.3/8.9.3) with ESMTP id QAA09104 for ; Sat, 22 Apr 2017 16:36:58 -0600 (MDT) Message-Id: <201704222236.QAA09104@mail.lariat.net> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Sat, 22 Apr 2017 16:36:35 -0600 To: freebsd-arm@freebsd.org From: Brett Glass Subject: Building kernel and ports on i.MX6 platforms Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Apr 2017 23:04:18 -0000 Everyone: I am interested in using some tiny i.MX6 systems as Internet routers and firewalls. However, to do this, I need to compile my own patches into the mpd5 utility. I may also want to compile a slimmed-down kernel to save memory, as well as a special Netgraph node I've created. Unfortunately, the SD card images, as supplied, come with neither kernel sources nor the ports collection. What's more, there have been significant improvements to the ARM code since 11.0-RELEASE, and I may want to work with snapshots (which the freebsd-update utility won't update and which confuses the heck out of the bsdinstall utility; I haven't been able to use that utility to fetch the ports collection). What's the best way to build custom kernels and/or patched ports for this platform? Should I cross-compile or compile natively? If I do the latter, how best to bring in the ports collection and keep my kernel sources up to date on a system that's running a snapshot? --Brett Glass