From owner-freebsd-arm@freebsd.org Tue Feb 5 23:43:26 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5BCF314D47D6 for ; Tue, 5 Feb 2019 23:43:26 +0000 (UTC) (envelope-from c.jayachandran@gmail.com) Received: from mail-it1-f194.google.com (mail-it1-f194.google.com [209.85.166.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 771C86FFBC; Tue, 5 Feb 2019 23:43:25 +0000 (UTC) (envelope-from c.jayachandran@gmail.com) Received: by mail-it1-f194.google.com with SMTP id w18so2081274ite.1; Tue, 05 Feb 2019 15:43:25 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=M09eF0bGB/VOpSwqlF3JxTbJmTPsKsM5gFLl/MkBSqk=; b=T4UjpBcbQHGHmKoS6umey1Xtt9RS40DujRzfsOOm5fSCiYujRuLlFTo0yMeWfcYVz7 sWXlvqrM8PYA1IURgKr3QI3UPKtXm7n2qVoulKoqec96Sq2Far+xJXr0IwB4qdXgr/h3 YWQihnLcfFZB6ki+I+AA8NvNnspeZaVaVblwcgZGd6M1czCehGEDKx3sGim8S9BCyxag s7/2sSv2HUD4XH25KRiucb31PiWrm1XstTK/Maz54Yh6Rqr8J2daue0L7vmppV/rZTmp cMErFLF4tDJTy3r07QOsuTu9b+xuRs1CL06cAbNvUFwpllsPk/Oar826CIeKjgw0q2zm Puvg== X-Gm-Message-State: AHQUAuYnTj+CZ0WULNbcaRPVMa8Pa5tv1/DiFP5dNMNH5quP37zmbxS3 PoK9blyr8QIekRTGXTwC3ShQ8OgEJTA7Om9BG4yr3A== X-Google-Smtp-Source: AHgI3Iab+QBM/8ELxGPqyiW08J0r/4orOxqKDL9noKci148KiKspk+7BVisjU0Hu5HEDO4mzmMJY4+L3qtELmN1u1eI= X-Received: by 2002:a5e:d808:: with SMTP id l8mr3968593iok.299.1549410199130; Tue, 05 Feb 2019 15:43:19 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: "Jayachandran C." Date: Tue, 5 Feb 2019 15:42:52 -0800 Message-ID: Subject: Re: ThunderX2 support in FreeBSD/arm64 To: Ed Maste Cc: "freebsd-arm@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 771C86FFBC X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of cjayachandran@gmail.com designates 209.85.166.194 as permitted sender) smtp.mailfrom=cjayachandran@gmail.com X-Spamd-Result: default: False [-4.13 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_TLS_LAST(0.00)[]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[194.166.85.209.list.dnswl.org : 127.0.5.0]; NEURAL_HAM_SHORT(-0.96)[-0.963,0]; IP_SCORE(-1.16)[ipnet: 209.85.128.0/17(-3.76), asn: 15169(-1.95), country: US(-0.07)]; FORGED_SENDER(0.30)[jchandra@freebsd.org,cjayachandran@gmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[194.166.85.209.rep.mailspike.net : 127.0.0.17]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; TAGGED_FROM(0.00)[]; FROM_NEQ_ENVFROM(0.00)[jchandra@freebsd.org,cjayachandran@gmail.com]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2019 23:43:26 -0000 Hi Ed, On Mon, Feb 4, 2019 at 12:23 PM Ed Maste wrote: > > On Thu, 3 Jan 2019 at 15:52, Jayachandran C. wrote: > > > > There seems to be 2 issues here - both of them happen when the AMI > > firmware is used. > > The first issue is that the efi framebuffer does not work, and I am > > not able to select the serial console with AMI firmware. The second > > issue is that the on-chip SATA controller is not setup correctly by > > the AMI firmware and can cause a 'NBU BAR error' failure. > > > > I have uploaded a test firmware and instructions to > > https://people.freebsd.org/~jchandra/testfw/ which should boot FreeBSD > > fine. This is an internal build which does not have both the problems > > above. Let me know if this works, and I will try to push the fixes to > > AMI. > > Thanks, with the test firmware I'm able to make progress and the > kernel boots fine. It's now hanging while trying to mount root over > NFS; final console output is: > > Trying to mount root from nfs:10.0.0.1:/tank/export-root/arm64/ [rw]... > taskqgroup_attach_cpu_deferred: setaffinity failed: 3 I have not tried this configuration (rootfs over NFS) yet, will give it a try soon. Also please note that the default qlogic NIC on Sabre may not work with FreeBSD. I had setup the FreeBSD partition on my system by creating a freebsd disk image in kvm/qemu and then copying the image to a partition - this works well. JC.