From owner-freebsd-arm@freebsd.org Mon Feb 4 20:23:41 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 63D2514B1116 for ; Mon, 4 Feb 2019 20:23:41 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-it1-f181.google.com (mail-it1-f181.google.com [209.85.166.181]) (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 7C27570C97; Mon, 4 Feb 2019 20:23:40 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-it1-f181.google.com with SMTP id c9so2993205itj.1; Mon, 04 Feb 2019 12:23:40 -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=94cv0GMqTSc0lPZ/50W6dS9UrZ5TQ1UDhSnnE46QnzA=; b=Dtu+vXjSwXcEPCV7mthbGxkg+0AiXVsx3IcWHG7vSBzE6PTjuLbHj6Inmbrjfpd0Tm 9FDhqNmeuTLZrXB4ASHAKyJbMDyiIi7TXSws/FXWXzXHoBQsmLvrqRfdazPhpzzurfaN 5gOINHjY1Fx+f0dkh1ZfZFGudflSa+YC3+TrSNzhv/dApT/bkWDfWFm5SpW05/t3C5GB KApL0rlTmLR67Gj6bE1G3/PLdsbvcELLuqzZ1JyxuEOkzOLEyXkFQIxTY9MUn3TFYgNV dbj72awpvbDSD6IInvfyEIavi4QlXNnALibelmZ3h/Uk+esA8jIoCgeTehld81ptcdir PP3A== X-Gm-Message-State: AHQUAuav0u2C0IABQqL4LmvYDElU4MFUsKoh48N4DRSu+LCWxxCmMTkl drlP+G6BT0umevIdMIJ8X4tph1C1xrZ36G/kPDDteVpP X-Google-Smtp-Source: AHgI3IaMjxQEG6KLDKI3S7m3hbp2WZBqGjOIGBmWsH729oFFLTOftSpRA1qk97xali2gMS+suuBb8pKJsVhAdxB20+E= X-Received: by 2002:a5d:878d:: with SMTP id f13mr755348ion.239.1549311813874; Mon, 04 Feb 2019 12:23:33 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Ed Maste Date: Mon, 4 Feb 2019 15:23:16 -0500 Message-ID: Subject: Re: ThunderX2 support in FreeBSD/arm64 To: "Jayachandran C." Cc: "freebsd-arm@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 7C27570C97 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of carpeddiem@gmail.com designates 209.85.166.181 as permitted sender) smtp.mailfrom=carpeddiem@gmail.com X-Spamd-Result: default: False [-6.07 / 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]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; IP_SCORE(-3.07)[ip: (-9.56), ipnet: 209.85.128.0/17(-3.76), asn: 15169(-1.94), country: US(-0.07)]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[181.166.85.209.list.dnswl.org : 127.0.5.0]; NEURAL_HAM_SHORT(-0.99)[-0.995,0]; FORGED_SENDER(0.30)[emaste@freebsd.org,carpeddiem@gmail.com]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[emaste@freebsd.org,carpeddiem@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: Mon, 04 Feb 2019 20:23:41 -0000 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