From owner-freebsd-arm@freebsd.org Thu Nov 22 19:23:03 2018 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 9ED1A1104AE1 for ; Thu, 22 Nov 2018 19:23:03 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it1-x12a.google.com (mail-it1-x12a.google.com [IPv6:2607:f8b0:4864:20::12a]) (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 39E63829E6 for ; Thu, 22 Nov 2018 19:23:02 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it1-x12a.google.com with SMTP id c9so15175126itj.1 for ; Thu, 22 Nov 2018 11:23:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=p2nCoYvwsxxN2znSaPzrY3MyaMmadbslH6dJpE45r5o=; b=dv+WICIivqSrAAkxbgdNFUrpewFzORpgRuEzcYIPQ/xVjk2vrsZIEmwUIBLU9FgEl3 BjhSIMD6jnO6yFxN1aLXoXjOPrn5iCOMuZlMw75lqVJbnMKQl0FH8VjZb0x1uMCxucwi HHhR6DX3zEgE24KJAv4h8jE4JcSownm3sDdLlju5NQ/RW3DtleA/26VHX6BaSRe8jiCm RcQraHMaO8gnynVqTv2NTGcytz+caas9LXqF2RPA1ZcJVqv3wWd1RjIL9v2aFTr/IIRa aUUE6+TbrH1Q8A1JU40dnrRy4PQs83qR6SJrRAiNmVQekQCnimWv2BlGJ6OhdjqOdyjj DJBA== 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=p2nCoYvwsxxN2znSaPzrY3MyaMmadbslH6dJpE45r5o=; b=i6EWrSG5StwHjtOGuFO549zw52K6NySR/QwPp6XD62eh5tNNvV6qAOK2e5kJSd9/tH oQYIJPZd6UdAVbzcHUiCBYjWXK9XASJ55h32EwwuuqJiyHuQeEUbFeYfRq/JvfquLNy5 uvdPOviXPWil2Vi+i60h/7rceyl9n+phjpjcYDubY4O2KJIUC7aPqjMQLJiyheLV61fp hAwqB56vvfdq2CXWuYONnncK6XY7ZX7J8pxMtukSpmD56Tqwac0+Tu+qX4K438G+MFMk kPLuJRidjzKAx+jYgveo42TXJza42wgCC3YokziJn8iR/6hY1kEBmjWsOGxGwZxg7dgv Bh0w== X-Gm-Message-State: AA+aEWaB4NcI3h9Yt64t1/2vFs9FgBXmY+ayagvTqWHRY/2s1p6fJAE9 SWARJMzjfMD196gfkXNSMslvhgBKmdTWZbZ3HwMNDg== X-Google-Smtp-Source: AFSGD/U1SC83z7AR99ekKBQ5rYHszMmY4scBjpsr70tT+jzuYxIp+4F/Dlqt0ehlTFhtbAUH8Z5jUQQAO/gSn7iY2sc= X-Received: by 2002:a02:3da:: with SMTP id e87mr9690949jae.78.1542914581259; Thu, 22 Nov 2018 11:23:01 -0800 (PST) MIME-Version: 1.0 References: <201811212303.wALN3Vv9074328@pdx.rh.CN85.dnsmgr.net> <820fac5d-dc79-64ca-33ac-7604157db423@denninger.net> <7FF4BE2B-DD9C-47AE-9775-7CBFE9813C6F@yahoo.com> <1A96848B-1B6B-4F06-9377-C702DDE4A403@yahoo.com> <818D581C-D2AE-4CC9-B71F-A426B8D5D003@yahoo.com> In-Reply-To: <818D581C-D2AE-4CC9-B71F-A426B8D5D003@yahoo.com> From: Warner Losh Date: Thu, 22 Nov 2018 12:22:49 -0700 Message-ID: Subject: Re: Lost my serial console! :-) To: Mark Millard Cc: Karl Denninger , FreeBSD Release Engineering Team , "freebsd-arm@freebsd.org" , "Rodney W. Grimes" X-Rspamd-Queue-Id: 39E63829E6 X-Spamd-Result: default: False [-3.61 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; TO_DN_SOME(0.00)[]; URI_COUNT_ODD(1.00)[13]; RCPT_COUNT_FIVE(0.00)[5]; SUBJECT_HAS_EXCLAIM(0.00)[]; MX_GOOD(-0.01)[cached: ALT1.aspmx.l.google.com]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; FREEMAIL_TO(0.00)[yahoo.com]; RCVD_TLS_LAST(0.00)[]; IP_SCORE(-1.63)[ip: (-4.45), ipnet: 2607:f8b0::/32(-2.09), asn: 15169(-1.51), country: US(-0.09)]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_SHORT(-0.98)[-0.981,0]; NEURAL_HAM_LONG(-1.00)[-0.997,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[a.2.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Server: mx1.freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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: Thu, 22 Nov 2018 19:23:03 -0000 On Thu, Nov 22, 2018, 12:01 PM Mark Millard On 2018-Nov-22, at 09:45, Warner Losh wrote: > > > > >> On Thu, Nov 22, 2018 at 9:32 AM Mark Millard via freebsd-arm < > freebsd-arm@freebsd.org> wrote: > >> On 2018-Nov-22, at 08:14, Mark Millard wrote: > >> > >> > On 2018-Nov-22, at 03:27, Karl Denninger > wrote: > >> > > >> >> On 11/21/2018 17:03, Rodney W. Grimes wrote: > >> >>>> On 11/20/2018 09:57, Rodney W. Grimes wrote: > >> >>>> ..... > >> >>>>>> Lots.? I have several 3Bs, one 3B+ (since that's the current > model), and > >> >>>>>> a passel of 2s. :-)? The 2s are fine but I'm building 11.STABLE > for > >> >>>>>> those.? Can't for the 3s, as the code to run those isn't in 11. > >> >>>>> Ok which of PI3B or PI3B+ or is it both that you are having > >> >>>>> serial console issues on? > >> >>>>> > >> >>>>> Also can you try: > >> >>>>> > http://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/12.0/FreeBSD-12.0-RC1-arm64-aarch64-RPI3.img.xz > >> >>>>> on both boards and report success/failure/problems? > >> >>>>> > >> >>>>> Thanks, > >> >>>> RC1 boots on both and I have a serial console on both.? > >> >>> Thank you for the testing, I am ccing this reply to RE@ so they > >> >>> know we have at least 1 data point that says we can boot our > >> >>> release canadate image on both a RPI3B and RPI3B+, > >> >>> that is valuable data. > >> >> One note -- there is a complaint about umodem.ko missing dependencies > >> >> right at the top of the kernel messages on boot and indeed it does > not > >> >> load out of the loader.conf entry -- but if I load it by hand once > the > >> >> system is up (or out of /etc/rc.local, etc) it works. So while it > does > >> >> indeed boot I wouldn't call it completely "working" (at least not if > you > >> >> need the umodem kernel module!) > >> >> > >> >> This happens to impact me on these devices (I have a USB device that > >> >> "appears" as a serial modem).... it's been broken for a while on > >> >> -CURRENT, but I don't know exactly *when* it broke. On the Pi2 under > >> >> 11-Stable it hasn't been a problem. > >> > > >> > Looking on the web I see an example from -r335317 : > >> > > >> > FreeBSD 12.0-CURRENT #0 r335317: Mon Jun 18 17:37:04 UTC 2018 > >> > root@releng3.nyi.freebsd.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC > arm64 > >> > FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) (based on > LLVM 6.0.0) > >> > WARNING: WITNESS option enabled, expect reduced performance. > >> > VT: init without driver. > >> > KLD file umodem.ko is missing dependencies > >> > KLD file if_run.ko is missing dependencies > >> > > >> > But if I remove umodem.ko being the specific > >> > example there is more --and some notes that > >> > might provide a workaround . . . > >> > > >> > There are examples around of folks getting the type of message for > >> > zfs.ko , where the solution was to force /boot/kernel/opensolaris.ko > >> > to load ahead of time instead of depending on it automatically > >> > happening. -r317181 was an example, quoting: > >> > > >> > QUOTE > >> > With a slimmed down kernel config, I can load zfs.ko and boot the > kernel > >> > BUT opensolaris is not loaded and I get at kernel boot: > >> > > >> > OK load zfs > >> > /boot/kernel/zfs.ko text=0x9d980 text=0xe0480 data=0x214c8+0x9eb78 > >> > syms=[0x8+0x1d6a0+0x8+0x187bd] > >> > OK boot > >> > Booting... > >> > KDB: debugger backends: ddb > >> > KDB: current backend: ddb > >> > Copyright (c) 1992-2017 The FreeBSD Project. > >> > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, > 1994 > >> > The Regents of the University of California. All rights > reserved. > >> > FreeBSD is a registered trademark of The FreeBSD Foundation. > >> > FreeBSD 12.0-CURRENT #0 r317181M: Sun May 14 14:01:52 CEST 2017 > >> > [hidden email]:/usr/obj/usr/src/sys/NORQUAY arm64 > >> > FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on > >> > LLVM 4.0.0) > >> > VT: init without driver. > >> > KLD file zfs.ko is missing dependencies > >> > END QUOTE > >> > > >> > and: > >> > > >> > QUOTE > >> > If I load opensolaris manually, I can mount My root filesystem from > zfs > >> > > >> > OK load opensolaris > >> > /boot/kernel/opensolaris.ko text=0x19d8 text=0xda0 > data=0x10178+0x125b8 > >> > syms=[0x8+0x1020+0x8+0x8ca] > >> > OK boot -s > >> > Booting... > >> > . . . > >> > END QUOTE > >> > > >> > That does suggest that there may be a workaround of explicitly > >> > loading the modules that umodem.ko requires instead of depending > >> > on implicit loading. This is true even if the person needed to > >> > do a kldxref and at the time it might have worked after that. > >> > > >> > (In the current context having an up to date linker.hints file > >> > is known to be insufficient. Back then I'm unsure of the > >> > status. But the procedure may either anyway.) > >> > > >> > The quotes are from: > >> > > >> > > http://freebsd.1045724.x6.nabble.com/Re-DTB-provided-by-loader-efi-from-head-r317181-on-pine64-smashed-by-zfs-ko-td6185085.html > >> > > >> > All the examples I'm referring to are arm64 in 2017 or later. > >> > Over such a range I've not run into a non-arm64 example. > >> > > >> > (I Did find old FreeBSD 9 missing-dependencies reports and > >> > powerpc reports from years before that range. I ignored these.) > >> > >> > >> I just tested and: > >> > >> hw.usb.template=3 > >> # ucom is not automatically being loaded when umodem is loaded at boot. > >> ucom_load="YES" > >> umodem_load="YES" > >> > >> in /boot/loader.conf worked: no more message about umodem.ko > >> missing dependencies. > >> > >> It looks like 12.x should have a note about amd64 requiring > >> such completeness in what is listed in /boot/loader.conf > >> or what is types at the loader prompts. (Presuming that this > >> is not fixed before 12.0-RELEASE .) > > > > Better to add the proper module dependency rather than this half A***ED > workaround, don't you think? > > Did I do something to justify that public disrepect > in the tone of your reply? > > I'll note that after booting, without preloading > ucom.ko at all, "kldload umodem" works fine and > implicitly loads ucom.ko just fine. So some form > of module dependency would seem to already be > in place. (This has been noted in past reports > on the lists.) > > The indirection-problem is only at boot time via using > /boot/loader.conf --not later. > Ah. We should try to fix that bug then. I've been distracted or I'd have jumped on this sooner. Warner > Warner > >> I greatly doubt that the issue is specific to umodem.ko and > >> what it requires to also be loaded. (Note the if_run.ko > >> example that was in materials that I quoted and the > >> zfs.ko example that suggested the workaround.) > >> > > > > > > > === > Mark Millard > marklmi at yahoo.com > ( dsl-only.net went > away in early 2018-Mar) > >