From owner-freebsd-arm@freebsd.org Sun Sep 30 09:12:17 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 45D3810B97B4 for ; Sun, 30 Sep 2018 09:12:17 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id AC1D57AAB9 for ; Sun, 30 Sep 2018 09:12:16 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id 2258485b; Sun, 30 Sep 2018 11:12:09 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=zXdVBjwHogQ3cixsz+kcI0hO1F8=; b=E+HEPFynS1T4dkBtL0GRC+5++Ga7 Hr62p5Asw2Q1OiQhq+K4FSth8SX096mW1Y69Ln3bGXFWQRA0+S0juSDhj2gmxcZG w9/3WrJKSdopB+FXrNFHRHqyle1f5wBFECHdQlrs1aFnKgP0CzFW/uayory/24bF qyVcAoRnEfVFFJo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=N7jOQ3WorZ18x0BUsmcxTUKQZPFKP9ktV/L+nAsikLmHTlRy3nx7JTnI FOGA9myQ8r9HyJL09zA0Lvv9VTOrqb5U7uoL3m5CzNZ1b51HEVWmSOkzbHIp1vb/ NnTqEq2UosbcirqSMISjDDDySMxVJ9TPKB6IyWwKImM/L7hXH+s= Received: from knuckles.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 5463103a TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Sun, 30 Sep 2018 11:12:09 +0200 (CEST) Date: Sun, 30 Sep 2018 11:12:08 +0200 From: Emmanuel Vadot To: bob prohaska Cc: freebsd-arm@freebsd.org Subject: Re: Timeout poll on interrupt endpoint for RPI3 with keyboard and mouse Message-Id: <20180930111208.5df04f5b7fb336cdfcf2fd74@bidouilliste.com> In-Reply-To: <20180929185213.GA58381@www.zefox.net> References: <20180929185213.GA58381@www.zefox.net> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Sep 2018 09:12:17 -0000 Hi, On Sat, 29 Sep 2018 11:52:13 -0700 bob prohaska wrote: > For the first time in a few months I connected a monitor, Dell keyboard and > mouse to my Pi3, presently running > 12.0-ALPHA7 r338964 GENERIC arm64 > which have all worked well since I got the Pi3 around six months ago. > > With the peripherals connected, the serial console spews > Timeout poll on interrupt endpoint > and does not seem to accept normal inputs, so it isn't > possible to get into the debugger, boot an old kernel > or otherwise try to sort out what's going on. > > disconnecting the monitor had no effect. > Removing the keyboard/mouse restores normal behavior. > > Anybody got a hint what might be wrong? FWIW, this OS/kernel > pair were compiled and installed with neither mouse/keyboard > nor monitor connected. I wouldn't expect that to matter, but... > > Thanks for reading, > > bob prohaska Are you talking about U-Boot or kernel itself ? I don't remember if I tested keyboard in u-boot when I updated it to 2018.09 but it definitly works for me in FreeBSD. I'll try again ALPHA7 to be sure. -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Sun Sep 30 09:12:53 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 8F00210B98E8 for ; Sun, 30 Sep 2018 09:12:53 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 063707AB2D for ; Sun, 30 Sep 2018 09:12:52 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id 3e766b63; Sun, 30 Sep 2018 11:12:51 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=hNNU7t9Uv200ObC9jBIMb5KjM6I=; b=RCnUuAIVoiEKevsdLeyEjVhmDiTq ZOF/czRxieAE7e5Q0RoZeIhpBsNx32VMikGuwmF5Pvt++46O57w0tv4J7Knrh1EK vJLDiEQh8XAOUOmmgBK/FF1J/kSK3RnSB1Mm0qgFdITgxdoPr5Nm7D6egdcgPSAC fu0Uob7psI06Dxo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=O1X80QIVf7+7euXTLFQSwKvPHRp+gMYOHsRwn/On1HgS5gXkSr1ZKIbN URTd55bIIbltAnjiGIi0OP8s2DSugFR3T+NCbCWy9kW3Zm9/5kC5UKIH2saDqa0n y7zlvfUIuPZbc4NawQ/POw2BpIChQ5BiY2EVJ4BALh1p4tcEces= Received: from knuckles.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 8722ca46 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Sun, 30 Sep 2018 11:12:51 +0200 (CEST) Date: Sun, 30 Sep 2018 11:12:50 +0200 From: Emmanuel Vadot To: locke@airmail.cc Cc: freebsd-arm@freebsd.org Subject: Re: dwc ethernet Rock64 on 100mbit Message-Id: <20180930111250.4de8100a27ec0617983a601a@bidouilliste.com> In-Reply-To: References: X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Sep 2018 09:12:53 -0000 Hi, On Wed, 26 Sep 2018 11:54:08 +0000 locke@airmail.cc wrote: > When I use the ethernet adapter on the Rock64 I don't get any connection > when I connect it to some 100Base TX network. I see packages on the > ethernet interface but they never seem to make it on the wire. > Netbooting as well as ethernet works when the other end is also Gbit. > Can anyone confirm this issue? Yes it's known, we need proper clock support, andreast@ is currently working on this. -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Sun Sep 30 13:09:36 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 38EDA10BF39D for ; Sun, 30 Sep 2018 13:09:36 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8CB68820CC for ; Sun, 30 Sep 2018 13:09:35 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w8UD9VV8061650 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 30 Sep 2018 06:09:32 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w8UD9UnA061649; Sun, 30 Sep 2018 06:09:31 -0700 (PDT) (envelope-from fbsd) Date: Sun, 30 Sep 2018 06:09:30 -0700 From: bob prohaska To: Emmanuel Vadot Cc: freebsd-arm@freebsd.org, bob prohaska Subject: Re: Timeout poll on interrupt endpoint for RPI3 with keyboard and mouse Message-ID: <20180930130930.GB58381@www.zefox.net> References: <20180929185213.GA58381@www.zefox.net> <20180930111208.5df04f5b7fb336cdfcf2fd74@bidouilliste.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <20180930111208.5df04f5b7fb336cdfcf2fd74@bidouilliste.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Sep 2018 13:09:36 -0000 On Sun, Sep 30, 2018 at 11:12:08AM +0200, Emmanuel Vadot wrote: >=20 > Hi, >=20 > On Sat, 29 Sep 2018 11:52:13 -0700 > bob prohaska wrote: >=20 > > For the first time in a few months I connected a monitor, Dell keyboard= and > > mouse to my Pi3, presently running > > 12.0-ALPHA7 r338964 GENERIC arm64 > > which have all worked well since I got the Pi3 around six months ago. > >=20 > > With the peripherals connected, the serial console spews > > Timeout poll on interrupt endpoint > > and does not seem to accept normal inputs, so it isn't > > possible to get into the debugger, boot an old kernel > > or otherwise try to sort out what's going on. > >=20 > > disconnecting the monitor had no effect. > > Removing the keyboard/mouse restores normal behavior.=20 > >=20 > > Anybody got a hint what might be wrong? FWIW, this OS/kernel > > pair were compiled and installed with neither mouse/keyboard > > nor monitor connected. I wouldn't expect that to matter, but... > >=20 > > Thanks for reading, > >=20 > > bob prohaska >=20 > Are you talking about U-Boot or kernel itself ? > I don't remember if I tested keyboard in u-boot when I updated it to > 2018.09 but it definitly works for me in FreeBSD. I'll try again ALPHA7 > to be sure. >=20 The messages appeared in u-boot and continued into loader. The system has since been updated to=20 FreeBSD 12.0-ALPHA8 r339018 GENERIC=20 Here is a sample of console output with HDMI monitor, mouse and keyboard connected, starting from a power-off condition: Please press any key to reboot. MMC: mmc@7e300000: 1 Loading Environment from FAT... *** Warning - bad CRC, using default enviro= nment Failed (-5) In: serial Out: vidconsole Err: vidconsole Net: No ethernet found. starting USB... USB0: scanning bus 0 for devices... 9 USB Device(s) found scanning usb for storage devices... 2 Storage Device(s) found Hit any key to stop autoboot: 2 Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint 1 Timeout poll on interrupt endpoint 0=20 Timeout poll on interrupt endpoint MMC Device 0 not found no mmc device at slot 0 Timeout poll on interrupt endpoint switch to partitions #0, OK mmc1 is current device Timeout poll on interrupt endpoint Scanning mmc 1:1... Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Found EFI removable media binary efi/boot/bootaa64.efi libfdt fdt_check_header(): FDT_ERR_BADMAGIC Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Scanning disk mmc@7e300000.blk... Scanning disk usb_mass_storage.lun0... Scanning disk usb_mass_storage.lun0... Found 14 disks 473400 bytes read in 51 ms (8.9 MiB/s) libfdt fdt_check_header(): FDT_ERR_BADMAGIC ## Starting EFI application at 00080000 ... Consoles: EFI console =20 FreeBSD/arm64 EFI loader, Revision 1.1 (Thu Aug 2 21:57:02 UTC 2018 root@releng3.nyi.freebsd.org) Command line arguments: loader.efi EFI version: 2.70 EFI Firmware: Das U-Boot (rev 0.00) Console: efi (0) Load Path: /\efi\boot\bootaa64.efi Load Device: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(1)/SD(0)/HD= (1,0x01,0,0x81f,0x18fa8) Trying ESP: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(1)/SD(0)/HD(1,0= x01,0,0x81f,0x18fa8) Setting currdev to disk0p1: Trying: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(1)/SD(0)/HD(2,0x01,= 0,0x197c7,0x1d92839) Setting currdev to disk0p2: Loading /boot/defaults/loader.conf /boot/kernel/kernel text=3D0x8c5f73 data=3D0x178df8+0x83ddd4 syms=3D[0x8+0x= 122928+0x8+0x115b27] /boot/entropy size=3D0x1000 /boot/kernel/umodem.ko text=3D0x2160 text=3D0x13d0 data=3D0x102c8+0xfd48 sy= ms=3D[0x8+0xf18+0x8+0xb62] Hit [Enter] to boot immediately, or any other key for command prompt. Type '?' for a list of commands, 'help' for more detailed help. OK ;21;97t ;21;97t not found OK ~=02 Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint ~=02 not found OK Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint ~=02Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint [plug pulled] The unprintable characters are my attempts to use enter-tilda-control-b to start the debugger, which were seemingly ignored.=20 Not sure what to make of things like "warning, bad CRC". Far as I can remember, that's normal and harmless. I'm less sure about the "Failed, -5" message; I don't recall seeing that before, but neither did I look for it. Thanks for reading, please let me know if there's anything I can test. bob prohaska From owner-freebsd-arm@freebsd.org Sun Sep 30 13:29:33 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 C80BC10BFA93 for ; Sun, 30 Sep 2018 13:29:33 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C8807829C2 for ; Sun, 30 Sep 2018 13:29:32 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w8UDTTgN061703 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 30 Sep 2018 06:29:30 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w8UDTSMt061702; Sun, 30 Sep 2018 06:29:28 -0700 (PDT) (envelope-from fbsd) Date: Sun, 30 Sep 2018 06:29:28 -0700 From: bob prohaska To: Emmanuel Vadot Cc: freebsd-arm@freebsd.org, bob prohaska Subject: Re: Timeout poll on interrupt endpoint for RPI3 with keyboard and mouse Message-ID: <20180930132928.GC58381@www.zefox.net> References: <20180929185213.GA58381@www.zefox.net> <20180930111208.5df04f5b7fb336cdfcf2fd74@bidouilliste.com> <20180930130930.GB58381@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=unknown-8bit Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20180930130930.GB58381@www.zefox.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Sep 2018 13:29:34 -0000 I just tried rebooting with HDMI only connected, and that failed in a different way: �MMC: mmc@7e300000: 1 Loading Environment from FAT... *** Warning - bad CRC, using default environment Failed (-5) In: serial Out: vidconsole Err: vidconsole Net: No ethernet found. starting USB... USB0: scanning bus 0 for devices... 6 USB Device(s) found scanning usb for storage devices... 2 Storage Device(s) found Hit any key to stop autoboot: 0 MMC Device 0 not found no mmc device at slot 0 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found EFI removable media binary efi/boot/bootaa64.efi libfdt fdt_check_header(): FDT_ERR_BADMAGIC Scanning disk mmc@7e300000.blk... Scanning disk usb_mass_storage.lun0... Scanning disk usb_mass_storage.lun0... Found 14 disks 473400 bytes read in 50 ms (9 MiB/s) libfdt fdt_check_header(): FDT_ERR_BADMAGIC ## Starting EFI application at 00080000 ... Consoles: EFI console FreeBSD/arm64 EFI loader, Revision 1.1 (Thu Aug 2 21:57:02 UTC 2018 root@releng3.nyi.freebsd.org) Command line arguments: loader.efi EFI version: 2.70 EFI Firmware: Das U-Boot (rev 0.00) Console: efi (0) Load Path: /\efi\boot\bootaa64.efi Load Device: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(1)/SD(0)/HD(1,0x01,0,0x81f,0x18fa8) Trying ESP: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(1)/SD(0)/HD(1,0x01,0,0x81f,0x18fa8) Setting currdev to disk0p1: Trying: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(1)/SD(0)/HD(2,0x01,0,0x197c7,0x1d92839) Setting currdev to disk0p2: Loading /boot/defaults/loader.conf �/boot/kernel/kernel text=0x8c5f73 data=0x178df8+0x83ddd4 syms=[0x8+0x122928+0x8+0x115b27] /boot/entropy size=0x1000 /boot/kernel/umodem.ko text=0x2160 text=0x13d0 data=0x102c8+0xfd48 syms=[0x8+0xf18+0x8+0xb62] Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel]... Using DTB provided by EFI at 0x7ff8000. EFI framebuffer information: addr, size 0x3e330000, 0x8ca000 dimensions 1920 x 1200 stride 1920 masks 0x00ff0000, 0x0000ff00, 0x000000ff, 0xff000000 panic: Too many early devmap mappings 2 cpuid = 0 time = 1 KDB: stack backtrace: #0 0xffff0000003cc660 at ??+0 #1 0xffff000000387e98 at ??+0 #2 0xffff000000387c44 at ??+0 #3 0xffff0000006e4824 at ??+0 #4 0xffff000000250c38 at ??+0 #5 0xffff000000253168 at ??+0 #6 0xffff00000032b81c at ??+0 #7 0xffff0000006a60a0 at ??+0 Uptime: 1s [no response to debugger escape] The "found 14 disks" seems very wrong. There are 2 USB flash drives connected. Thanks for reading! bob prohaska From owner-freebsd-arm@freebsd.org Sun Sep 30 13:43:55 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 5645710C029A for ; Sun, 30 Sep 2018 13:43:55 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CE3C9833C5 for ; Sun, 30 Sep 2018 13:43:54 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id b4a15e70; Sun, 30 Sep 2018 15:43:53 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=bqTpb9LwinM4jNJ/BBZISTyK3l4=; b=b7t37KvA1oGHjHw0Bf4dvDz/t3PW agNo15zj//RaMb/K3x25sbFDYP+ZDxBaFutCV0XyW/l8Fprd/mVkeyCLnnKE547t k9QwJfTQaTkCxgQq9/d+J45sMfarjiYZkWy1bVKGrqKiiidfuSf1omEgkptGA6+A iAG2got/1S+/+2M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=HAin/kwSxwIKtNy6uFcjZkth4UQEcEM4vN2xY0wLZAVc2VcA0rDsiLYx kXIPJFcmsuJvyZyQdnLAgeoWdaIc532MCta847lC04zgdfQN/wZ8RwEJuh9J/s27 w26W91qHY+ZA0CEhSP3fB+i6I8AvfSWE9I5xUNHy7OW5E1cPI+8= Received: from knuckles.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 0725e62c TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Sun, 30 Sep 2018 15:43:52 +0200 (CEST) Date: Sun, 30 Sep 2018 15:43:49 +0200 From: Emmanuel Vadot To: bob prohaska Cc: freebsd-arm@freebsd.org Subject: Re: Timeout poll on interrupt endpoint for RPI3 with keyboard and mouse Message-Id: <20180930154349.1dfa4779060932ef8ebc3a00@bidouilliste.com> In-Reply-To: <20180930130930.GB58381@www.zefox.net> References: <20180929185213.GA58381@www.zefox.net> <20180930111208.5df04f5b7fb336cdfcf2fd74@bidouilliste.com> <20180930130930.GB58381@www.zefox.net> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Sep 2018 13:43:55 -0000 On Sun, 30 Sep 2018 06:09:30 -0700 bob prohaska wrote: > On Sun, Sep 30, 2018 at 11:12:08AM +0200, Emmanuel Vadot wrote: > >=20 > > Hi, > >=20 > > On Sat, 29 Sep 2018 11:52:13 -0700 > > bob prohaska wrote: > >=20 > > > For the first time in a few months I connected a monitor, Dell keyboa= rd and > > > mouse to my Pi3, presently running > > > 12.0-ALPHA7 r338964 GENERIC arm64 > > > which have all worked well since I got the Pi3 around six months ago. > > >=20 > > > With the peripherals connected, the serial console spews > > > Timeout poll on interrupt endpoint > > > and does not seem to accept normal inputs, so it isn't > > > possible to get into the debugger, boot an old kernel > > > or otherwise try to sort out what's going on. > > >=20 > > > disconnecting the monitor had no effect. > > > Removing the keyboard/mouse restores normal behavior.=20 > > >=20 > > > Anybody got a hint what might be wrong? FWIW, this OS/kernel > > > pair were compiled and installed with neither mouse/keyboard > > > nor monitor connected. I wouldn't expect that to matter, but... > > >=20 > > > Thanks for reading, > > >=20 > > > bob prohaska > >=20 > > Are you talking about U-Boot or kernel itself ? > > I don't remember if I tested keyboard in u-boot when I updated it to > > 2018.09 but it definitly works for me in FreeBSD. I'll try again ALPHA7 > > to be sure. > >=20 >=20 > The messages appeared in u-boot and continued into loader. >=20 > The system has since been updated to=20 > FreeBSD 12.0-ALPHA8 r339018 GENERIC=20 >=20 > Here is a sample of console output with HDMI monitor, mouse and keyboard > connected, starting from a power-off condition: >=20 > Please press any key to reboot. >=20 > MMC: mmc@7e300000: 1 > Loading Environment from FAT... *** Warning - bad CRC, using default envi= ronment >=20 > Failed (-5) > In: serial > Out: vidconsole > Err: vidconsole > Net: No ethernet found. > starting USB... > USB0: scanning bus 0 for devices... 9 USB Device(s) found > scanning usb for storage devices... 2 Storage Device(s) found > Hit any key to stop autoboot: 2 Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > 1 Timeout poll on interrupt endpoint > 0=20 > Timeout poll on interrupt endpoint > MMC Device 0 not found > no mmc device at slot 0 > Timeout poll on interrupt endpoint > switch to partitions #0, OK > mmc1 is current device > Timeout poll on interrupt endpoint > Scanning mmc 1:1... > Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > Found EFI removable media binary efi/boot/bootaa64.efi > libfdt fdt_check_header(): FDT_ERR_BADMAGIC > Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > Scanning disk mmc@7e300000.blk... > Scanning disk usb_mass_storage.lun0... > Scanning disk usb_mass_storage.lun0... > Found 14 disks > 473400 bytes read in 51 ms (8.9 MiB/s) > libfdt fdt_check_header(): FDT_ERR_BADMAGIC > ## Starting EFI application at 00080000 ... > Consoles: EFI console =20 > FreeBSD/arm64 EFI loader, Revision 1.1 > (Thu Aug 2 21:57:02 UTC 2018 root@releng3.nyi.freebsd.org) >=20 > Command line arguments: loader.efi > EFI version: 2.70 > EFI Firmware: Das U-Boot (rev 0.00) > Console: efi (0) > Load Path: /\efi\boot\bootaa64.efi > Load Device: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(1)/SD(0)/= HD(1,0x01,0,0x81f,0x18fa8) > Trying ESP: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(1)/SD(0)/HD(1= ,0x01,0,0x81f,0x18fa8) > Setting currdev to disk0p1: > Trying: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(1)/SD(0)/HD(2,0x0= 1,0,0x197c7,0x1d92839) > Setting currdev to disk0p2: > Loading /boot/defaults/loader.conf > /boot/kernel/kernel text=3D0x8c5f73 data=3D0x178df8+0x83ddd4 syms=3D[0x8+= 0x122928+0x8+0x115b27] > /boot/entropy size=3D0x1000 > /boot/kernel/umodem.ko text=3D0x2160 text=3D0x13d0 data=3D0x102c8+0xfd48 = syms=3D[0x8+0xf18+0x8+0xb62] >=20 > Hit [Enter] to boot immediately, or any other key for command prompt. >=20 >=20 > Type '?' for a list of commands, 'help' for more detailed help. > OK ;21;97t > ;21;97t not found > OK ~=02 Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint >=20 > ~=02 not found > OK Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > ~=02Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > [plug pulled] >=20 > The unprintable characters are my attempts to > use enter-tilda-control-b to start the debugger, > which were seemingly ignored.=20 That's because there is no debugger in the loader. > Not sure what to make of things like > "warning, bad CRC". Far as I can remember, that's normal and harmless. It is, it's because you don't have any u-boot env in the mmc. > I'm less sure about the "Failed, -5" message; I don't recall seeing > that before, but neither did I look for it. It think it's related to env too. > Thanks for reading, please let me know if there's anything I can test. >=20 > bob prohaska --=20 Emmanuel Vadot From owner-freebsd-arm@freebsd.org Sun Sep 30 13:50:58 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 40E5210C0457 for ; Sun, 30 Sep 2018 13:50:58 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B87ED8355F for ; Sun, 30 Sep 2018 13:50:57 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id b2af0520; Sun, 30 Sep 2018 15:50:56 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=P3L+gHHsMNBv0o9Q8pkgx+TwWKM=; b=oqwb5M2WR64fWRXY44p0V5yAvwXU biRuNIwjQA4TQ2CtIaFELPrfk0D68+Gn9lUk0HoO6/zEjDVYY++doqI2KumOr7z8 nGEpr4SAym1i5YqA93EmQszbB9EOotJZc2VRpsS1AK6xuF/a5dl7SCCvZr7QXXMM cQK3lVhxuePbBSA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=niMq+CoMvwKHul1DxZHPca6wdYDhwWlfSsFZl/CRTfeZT7S8A+mxnRgx 2dIhpe6+qexnyMR5GomnszV7NFPVKVpdYc3P24ObHZLnlFNbk49AOCeDQ06kJovu 4VZCcIPfWIWCa61ld0NTtmeBeteW2DZgpQGzPaaArlB0A6cmsNo= Received: from knuckles.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 0ea7e7f8 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Sun, 30 Sep 2018 15:50:56 +0200 (CEST) Date: Sun, 30 Sep 2018 15:50:55 +0200 From: Emmanuel Vadot To: bob prohaska Cc: freebsd-arm@freebsd.org Subject: Re: Timeout poll on interrupt endpoint for RPI3 with keyboard and mouse Message-Id: <20180930155055.2c35693431e8dfff4eb7d7bd@bidouilliste.com> In-Reply-To: <20180930132928.GC58381@www.zefox.net> References: <20180929185213.GA58381@www.zefox.net> <20180930111208.5df04f5b7fb336cdfcf2fd74@bidouilliste.com> <20180930130930.GB58381@www.zefox.net> <20180930132928.GC58381@www.zefox.net> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Sep 2018 13:50:58 -0000 On Sun, 30 Sep 2018 06:29:28 -0700 bob prohaska wrote: >=20 > I just tried rebooting with HDMI only connected, and that failed in a=20 > different way: >=20 > ?MMC: mmc@7e300000: 1 > Loading Environment from FAT... *** Warning - bad CRC, using default envi= ronment >=20 > Failed (-5) > In: serial > Out: vidconsole > Err: vidconsole > Net: No ethernet found. > starting USB... > USB0: scanning bus 0 for devices... 6 USB Device(s) found > scanning usb for storage devices... 2 Storage Device(s) found > Hit any key to stop autoboot: 0=20 > MMC Device 0 not found > no mmc device at slot 0 > switch to partitions #0, OK > mmc1 is current device > Scanning mmc 1:1... > Found EFI removable media binary efi/boot/bootaa64.efi > libfdt fdt_check_header(): FDT_ERR_BADMAGIC > Scanning disk mmc@7e300000.blk... > Scanning disk usb_mass_storage.lun0... > Scanning disk usb_mass_storage.lun0... > Found 14 disks > 473400 bytes read in 50 ms (9 MiB/s) > libfdt fdt_check_header(): FDT_ERR_BADMAGIC > ## Starting EFI application at 00080000 ... > Consoles: EFI console =20 > FreeBSD/arm64 EFI loader, Revision 1.1 > (Thu Aug 2 21:57:02 UTC 2018 root@releng3.nyi.freebsd.org) >=20 > Command line arguments: loader.efi > EFI version: 2.70 > EFI Firmware: Das U-Boot (rev 0.00) > Console: efi (0) > Load Path: /\efi\boot\bootaa64.efi > Load Device: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(1)/SD(0)/= HD(1,0x01,0,0x81f,0x18fa8) > Trying ESP: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(1)/SD(0)/HD(1= ,0x01,0,0x81f,0x18fa8) > Setting currdev to disk0p1: > Trying: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(1)/SD(0)/HD(2,0x0= 1,0,0x197c7,0x1d92839) > Setting currdev to disk0p2: > Loading /boot/defaults/loader.conf > ?/boot/kernel/kernel text=3D0x8c5f73 data=3D0x178df8+0x83ddd4 syms=3D[0x8= +0x122928+0x8+0x115b27] > /boot/entropy size=3D0x1000 > /boot/kernel/umodem.ko text=3D0x2160 text=3D0x13d0 data=3D0x102c8+0xfd48 = syms=3D[0x8+0xf18+0x8+0xb62] >=20 > Hit [Enter] to boot immediately, or any other key for command prompt. > Booting [/boot/kernel/kernel]... =20 > Using DTB provided by EFI at 0x7ff8000. > EFI framebuffer information: > addr, size 0x3e330000, 0x8ca000 > dimensions 1920 x 1200 > stride 1920 > masks 0x00ff0000, 0x0000ff00, 0x000000ff, 0xff000000 > panic: Too many early devmap mappings 2 > cpuid =3D 0 > time =3D 1 > KDB: stack backtrace: > #0 0xffff0000003cc660 at ??+0 > #1 0xffff000000387e98 at ??+0 > #2 0xffff000000387c44 at ??+0 > #3 0xffff0000006e4824 at ??+0 > #4 0xffff000000250c38 at ??+0 > #5 0xffff000000253168 at ??+0 > #6 0xffff00000032b81c at ??+0 > #7 0xffff0000006a60a0 at ??+0 > Uptime: 1s Looks like the framebuffer size is too big, could you try with this : diff --git a/sys/arm64/include/pte.h b/sys/arm64/include/pte.h index acd3f81ab41c..7aa216e92b43 100644 --- a/sys/arm64/include/pte.h +++ b/sys/arm64/include/pte.h @@ -109,7 +109,7 @@ typedef uint64_t pt_entry_t; /* page table entry */ /* 0x2 also marks an invalid address */ #define L3_PAGE 0x3 =20 -#define PMAP_MAPDEV_EARLY_SIZE (L2_SIZE * 4) +#define PMAP_MAPDEV_EARLY_SIZE (L2_SIZE * 8) =20 #define L0_ENTRIES_SHIFT 9 #define L0_ENTRIES (1 << L0_ENTRIES_SHIFT) > [no response to debugger escape] This is too early for debugger. > The "found 14 disks" seems very wrong.=20 > There are 2 USB flash drives connected. >=20 > Thanks for reading! >=20 > bob prohaska --=20 Emmanuel Vadot From owner-freebsd-arm@freebsd.org Sun Sep 30 14:57:08 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 269F310C218F for ; Sun, 30 Sep 2018 14:57:08 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 77C9386408 for ; Sun, 30 Sep 2018 14:57:07 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w8UEv3ds061975 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 30 Sep 2018 07:57:04 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w8UEv3kh061974; Sun, 30 Sep 2018 07:57:03 -0700 (PDT) (envelope-from fbsd) Date: Sun, 30 Sep 2018 07:57:03 -0700 From: bob prohaska To: Emmanuel Vadot Cc: freebsd-arm@freebsd.org, bob prohaska Subject: Re: Timeout poll on interrupt endpoint for RPI3 with keyboard and mouse Message-ID: <20180930145702.GD58381@www.zefox.net> References: <20180929185213.GA58381@www.zefox.net> <20180930111208.5df04f5b7fb336cdfcf2fd74@bidouilliste.com> <20180930130930.GB58381@www.zefox.net> <20180930132928.GC58381@www.zefox.net> <20180930155055.2c35693431e8dfff4eb7d7bd@bidouilliste.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180930155055.2c35693431e8dfff4eb7d7bd@bidouilliste.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Sep 2018 14:57:08 -0000 On Sun, Sep 30, 2018 at 03:50:55PM +0200, Emmanuel Vadot wrote: > > Looks like the framebuffer size is too big, could you try with this : > diff --git a/sys/arm64/include/pte.h b/sys/arm64/include/pte.h > index acd3f81ab41c..7aa216e92b43 100644 > --- a/sys/arm64/include/pte.h > +++ b/sys/arm64/include/pte.h > @@ -109,7 +109,7 @@ typedef uint64_t > pt_entry_t; /* page table entry */ /* 0x2 also marks an > invalid address */ #define L3_PAGE 0x3 > > -#define PMAP_MAPDEV_EARLY_SIZE (L2_SIZE * 4) > +#define PMAP_MAPDEV_EARLY_SIZE (L2_SIZE * 8) > > #define L0_ENTRIES_SHIFT 9 > #define L0_ENTRIES (1 << L0_ENTRIES_SHIFT) > > Copy and paste from the email didn't work, probably it's a mail formatting issue. Here's what happened: root@www:/usr/src # patch < vadot.patch Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/sys/arm64/include/pte.h b/sys/arm64/include/pte.h |index acd3f81ab41c..7aa216e92b43 100644 |--- a/sys/arm64/include/pte.h |+++ b/sys/arm64/include/pte.h -------------------------- Patching file sys/arm64/include/pte.h using Plan A... patch: **** malformed patch at line 6: pt_entry_t; /* page table entry */ /* 0x2 also marks an where vadot.patch contains root@www:/usr/src # more vadot.patch diff --git a/sys/arm64/include/pte.h b/sys/arm64/include/pte.h index acd3f81ab41c..7aa216e92b43 100644 --- a/sys/arm64/include/pte.h +++ b/sys/arm64/include/pte.h @@ -109,7 +109,7 @@ typedef uint64_t pt_entry_t; /* page table entry */ /* 0x2 also marks an invalid address */ #define L3_PAGE 0x3 -#define PMAP_MAPDEV_EARLY_SIZE (L2_SIZE * 4) +#define PMAP_MAPDEV_EARLY_SIZE (L2_SIZE * 8) #define L0_ENTRIES_SHIFT 9 #define L0_ENTRIES (1 << L0_ENTRIES_SHIFT) I tried manually editing to put the comment on one line, didn't help. Can you put the patch someplace where I can download it? Thanks! bob prohaska From owner-freebsd-arm@freebsd.org Mon Oct 1 02:24:23 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 3E95E10AFB40 for ; Mon, 1 Oct 2018 02:24:23 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B05307CC84 for ; Mon, 1 Oct 2018 02:24:22 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w912OGKB063957 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 30 Sep 2018 19:24:17 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w912OGNB063956; Sun, 30 Sep 2018 19:24:16 -0700 (PDT) (envelope-from fbsd) Date: Sun, 30 Sep 2018 19:24:16 -0700 From: bob prohaska To: Trevor Roydhouse Cc: bob prohaska , freebsd-arm@freebsd.org Subject: Re: Timeout poll on interrupt endpoint for RPI3 with keyboard and mouse Message-ID: <20181001022415.GA63212@www.zefox.net> References: <20180929185213.GA58381@www.zefox.net> <20180930111208.5df04f5b7fb336cdfcf2fd74@bidouilliste.com> <20180930130930.GB58381@www.zefox.net> <20180930132928.GC58381@www.zefox.net> <20180930155055.2c35693431e8dfff4eb7d7bd@bidouilliste.com> <20180930145702.GD58381@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Oct 2018 02:24:23 -0000 On Mon, Oct 01, 2018 at 08:57:04AM +1000, Trevor Roydhouse wrote: > > You just need to change one character in the file > .../sys/arm64/include/pte.h - change the 4 to an 8 in this existing line: > > #define PMAP_MAPDEV_EARLY_SIZE (L2_SIZE * 4) > Ok, that wasn't hard 8-) The machine now boots with the monitor connected and continues to run correctly when keyboard and mouse are plugged in. With monitor, keyboard and mouse connected it still spits out a stream of Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint .... during the boot process. The spew seems continuous, but when I typed boot into the spew, it looks as if the kernel took over and the machine is now multi-user. Evidently it got stuck in loader, the boot command got it unstuck and after that all is normal. So, I guess the video issue was a distraction that's now fixed. The problem with USB mouse and keyboard remain unresolved but nonfatal. Thanks _very_ much for your help! bob prohaska From owner-freebsd-arm@freebsd.org Mon Oct 1 11:00:09 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 8316410B0FBC for ; Mon, 1 Oct 2018 11:00:09 +0000 (UTC) (envelope-from vdemart@gmail.com) Received: from smtpcmd04131.aruba.it (smtpcmd04131.aruba.it [62.149.158.131]) by mx1.freebsd.org (Postfix) with ESMTP id E51027168F for ; Mon, 1 Oct 2018 11:00:08 +0000 (UTC) (envelope-from vdemart@gmail.com) Received: from macbookvittorio.homenet.telecomitalia.it ([82.61.157.83]) by smtpcmd04.ad.aruba.it with bizsmtp id iAwy1y00l1oEWVe01AwzAG; Mon, 01 Oct 2018 12:56:59 +0200 From: Victor Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Booting the raspberry pi 2 from a usb hd Date: Mon, 1 Oct 2018 12:56:58 +0200 Message-Id: To: freebsd-arm@freebsd.org Mime-Version: 1.0 (Apple Message framework v1283) X-Mailer: Apple Mail (2.1283) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aruba.it; s=a1; t=1538391419; bh=Iwv6fY/0tTG14FYb5s/eF6mRMY3xT9hxt2A8LJXLpFg=; h=From:Content-Type:Subject:Date:To:Mime-Version; b=QJI956ANI1oNbVvGHMyOcWf/6ZDRp5fjDxxfSR/PhmUrK0jkoBHS1ZUPoK6DJOmuJ 7rwuzdD4OXqYaXc/T3CVMugXzxiL+yOqnz+eqoX55vqhhrh37j6otBZ+YPCgLg3ffD erJ9LoQtnkZXRA7LnBpm7TAu1QSiuWKd881aaPYnd7sj+0tUlzgx/n+huRNPWL2Tig w+4RPlcko0/xHfV70voAlybMmB5sgOTrLTbdCsx0NN5PywWm0/Xyto+r+QNj7i3ktQ jx7DGcnBlN5s/eeV1txZgMpR5kmKuEo7nMjHvF9iYz8MgRHRD59lnARzCp+qxHI05J FKrS+6PDs1cew== X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Oct 2018 11:00:09 -0000 I'm using a pi 2 card with FreeBSD 11.2-STABLE on the required sd card. = It works like a charm but using it as a postgresql server with many = write operation on it, to be on the safe side, I would like to move the = operating system to an external hard-disk or ssd.=20 I've been surfing the net to find if it is possible to boot my pi 2 from = an external hard-disk (or SSD) to no avail. Could you please give me some hint, directions on this subject? Ciao Vittorio= From owner-freebsd-arm@freebsd.org Mon Oct 1 14:59:40 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 94CDA10C00B3 for ; Mon, 1 Oct 2018 14:59:40 +0000 (UTC) (envelope-from simond@irrelevant.org) Received: from mail-qt1-x82a.google.com (mail-qt1-x82a.google.com [IPv6:2607:f8b0:4864:20::82a]) (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 36B847A61C for ; Mon, 1 Oct 2018 14:59:40 +0000 (UTC) (envelope-from simond@irrelevant.org) Received: by mail-qt1-x82a.google.com with SMTP id q41-v6so9473211qtq.10 for ; Mon, 01 Oct 2018 07:59:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=irrelevant.org; s=irrelevant; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Fl1vruD60MWLuvMwmAyfD3h1U4XN/egwwC1kVfZdDO4=; b=Fh1CBBYcmw6r7mHcZo/pKqG029qv6shp1w8DrMg0w5gK/nwESTTEsNdB0fEfoSKeK6 U8E8y0Tgy9w/HVJiEMrxZAUflo9xF/R/xmYHvQSM78CyN6w/rpr2+f+sHp7CuoIwEIyU +zc6ItFvyroWcIlM4r2On+KzWHhNbmPQuYET0= 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=Fl1vruD60MWLuvMwmAyfD3h1U4XN/egwwC1kVfZdDO4=; b=phOPBJ/6uZ2Xbg+wLZATNxvn09CUqPbfE7cPY9/Dhc3fojR2G/fj6h0wZ684uT0us1 emeIDJy+GMxffGJX7BoDt0VPPKZEI0wnNawE3t6DWegFgv00F4nGO5qXxTozHr6nkF6g TSbSiFrXSClbBq5/KBwnJaVMgq2Jenjnz+h5x1UUWqrmK6AAtwV4hqPoMckVlB1qZzgb FfnsF6SMsOjVHVH6WNQ/4XGt9JvjjBrWgV1e1bvIeDQdBe2FzZGojpcucg3Ktxw7IPUm AvoMsYgzQpdHFIbOXmM95cxfBORUEKKe5cThfHOFReQinlfmPumQGsc2qGqQeTs4SN9F wutA== X-Gm-Message-State: ABuFfoiS8VhLNuKJWeSxlwQTddslwL5MmJbjVUBlGULR6lqcB7HG+IIy UsivdfuTlfAQYD1EH6p7ChQTN48//eMvGkRFACF+0w== X-Google-Smtp-Source: ACcGV60Nvv9PyccVtGnng+6rMIeE7SV/bC5nI5NpPLxKj4asg3HBX4pfKnbeSpUuMeHnE06Jj0+iig7v+9IBmh+xaa8= X-Received: by 2002:ac8:435b:: with SMTP id a27-v6mr8581460qtn.295.1538405979658; Mon, 01 Oct 2018 07:59:39 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Simon Dick Date: Mon, 1 Oct 2018 15:59:28 +0100 Message-ID: Subject: Re: Booting the raspberry pi 2 from a usb hd To: vdemart@gmail.com Cc: freebsd-arm@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Oct 2018 14:59:41 -0000 On Mon, 1 Oct 2018 at 15:32, Victor wrote: > I'm using a pi 2 card with FreeBSD 11.2-STABLE on the required sd card. It > works like a charm but using it as a postgresql server with many write > operation on it, to be on the safe side, I would like to move the operating > system to an external hard-disk or ssd. > I've been surfing the net to find if it is possible to boot my pi 2 from > an external hard-disk (or SSD) to no avail. > Could you please give me some hint, directions on this subject? > >From memory the Pi 2 itself doesn't support booting from USB so your best bet would be to mount the external drive and then place your postgres data files on there. I believe the Pi 3 upwards can do USB booting, though I don't know how much support there is in FreeBSD for it yet as I've not had a reason to try. From owner-freebsd-arm@freebsd.org Mon Oct 1 16:36:27 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 2C973109E519 for ; Mon, 1 Oct 2018 16:36:27 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic310-22.consmr.mail.ne1.yahoo.com (sonic310-22.consmr.mail.ne1.yahoo.com [66.163.186.203]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B74DE80DD0 for ; Mon, 1 Oct 2018 16:36:26 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: IbbmJDEVM1kNCuDR477ddnjkC_iGU9e3_SbsQg_e3DI7lJR_YxB3pfUcugsZIP2 HRW.EKEeAMCuwxQP6D5Nw63K_4XCZzpejbCS7qnErErGLCQwC7_ayKOTul2EgSoY_8RTGxxjiKxc xfwexx7H23Q5E0hOFtRUNbRlAUomYw4BUBMHfAooteAJuQn.osY0j9CtfSnGs0O2YQYZZrO_lvbR rVxyYk51.a5BoX.2Ik2MI5UOy1Uql3y4dW5xP3WtWs5VB5Y3aqPbTfnaHxCi_DnTDYPp5m0WCo_d x.NbLsMTGwrJ2NJKZt.bhgz1BXv9mZ8pu_r60ICehFDmbKUCQ43ujZQ6gHkxpT_zskmDk8HH5CnY rNqqwlJP2Cb_hhzlhFhVnq8qkq_GWFnPshqoAlLEmEm6Ra._LkcbQr.NCmyzPaKSr4nA4FM1xTT0 yFR_rhAvZXHq0qMdi0LKZIt8CwuRTqe_8MN2fBrfn04IcKoORPGXLuOtMP4kxEiAhlK.cY9oLK6i 2ounB5Fc1AawgfM9PmHritq04WX13ixaAya6Z9T1kw_HS0F1p_mw5x5eegH7Fgb8sIa3V9zgjmtF 9.jqkh3E0WxeAyCDowWe4ro81ZT7f.E1pJLBzVQaTRdbh6sg31sSzarw_J__x8Y2uDXF6BGkEn1w BXBtHN31Gj8CVcrn4656ZUHc9qjb7sCPZgpJ49kmT0RmTGI274Uaj67O2pkK5Vg5l6mGDEwo51hc lB30UASEAov4YMFiSZcYpZbLd_8X5_y8KyEaAwZTcVLZomFDOYdddALat8JONJ8v8gFKwvG1Hdq1 zunN0O_q39ukNW4omt2HObg90bOvHyNTRLiFqIzZLwssABaFOdxZFLLxKvY0Hjrj5kQ8XyMgXKVJ T0AdTi53Pptwif1ZgaaqVtAuGdnx2Uaj.9CF.hXNS3c4hE_wnVE7S5SbuXbZ8ZolXpYai28uTuw3 9PYFkIdjcyDjPweysRd6.zNhQp4AG2p0QzHxGfMPtSVET4IGsGki7izX9h9lI3O6_yVF99SeaY6Z 3Rx1By.nAA06W_k4- Received: from sonic.gate.mail.ne1.yahoo.com by sonic310.consmr.mail.ne1.yahoo.com with HTTP; Mon, 1 Oct 2018 16:36:20 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.101]) ([76.115.7.162]) by smtp403.mail.ne1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 8ddafcbb719b3cf857a25f11e43408fb; Mon, 01 Oct 2018 16:36:19 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: Booting the raspberry pi 2 from a usb hd From: Mark Millard In-Reply-To: Date: Mon, 1 Oct 2018 09:36:17 -0700 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Victor X-Mailer: Apple Mail (2.3445.9.1) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Oct 2018 16:36:27 -0000 On 2018-Oct-1, at 3:56 AM, Victor wrote: > I'm using a pi 2 card with FreeBSD 11.2-STABLE on the required sd = card. It works like a charm but using it as a postgresql server with = many write operation on it, to be on the safe side, I would like to move = the operating system to an external hard-disk or ssd.=20 > I've been surfing the net to find if it is possible to boot my pi 2 = from an external hard-disk (or SSD) to no avail. > Could you please give me some hint, directions on this subject? The notes below are not rpi2 specific. I've done such on many systems, including an rpi2. One technique is that /etc/fstab on the microsd card media that has the kernel can redirect to another device for where to mount / . (I use one partition for all of world.) I also tend to have /boot/loader.conf copies that contain something like: kern.cam.boot_delay=3D10000 vfs.mountroot.timeout=3D10 to help make sure things are ready for the external storage device to be used. Additional notes: I tend to install a full world on the microsd card slot media with the kernel so that I can boot that if needed, absent the external drive. (This involves the boot prompting for where to boot from.) I tend to keep the extra world's configuration tracking nearly all of the external device's world configuration. That includes /boot/loader.conf . But my configurations are rather simple, with little changed from defaults. But this also means that I might not notice if more than the files /etc/fstab and /boot/loader.conf from the microsd card media are put to use. For /etc/fstab I tend to have comments that point to the microsd card media for quick editing for switching the world device: just switch which lines are commented vs. not. I also tend to install the kernel on the external media, even though it is not booted from. So I end up having 2 installs overall. I tend to use various forms of labels and paths that reference labels instead of directly using device names, path prefixes: /dev/ufs/ /dev/msdosfs/ /dev/gpt/ /dev/label/ =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-arm@freebsd.org Mon Oct 1 17:11:12 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 0561410A43D2 for ; Mon, 1 Oct 2018 17:11:12 +0000 (UTC) (envelope-from luca.cappelletti@gmail.com) Received: from mail-wr1-x42c.google.com (mail-wr1-x42c.google.com [IPv6:2a00:1450:4864:20::42c]) (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 7036382983 for ; Mon, 1 Oct 2018 17:11:11 +0000 (UTC) (envelope-from luca.cappelletti@gmail.com) Received: by mail-wr1-x42c.google.com with SMTP id w5-v6so5605101wrt.2 for ; Mon, 01 Oct 2018 10:11:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=+jD5Tb6gXQ9jXcylAOT6YlY2182/zPFxQYhZXRO3HcM=; b=BI9V6YCsOPqO/t45TjvmyrUo7tywr+hs4isvDRQdP1MDw/ghDumTf+iGqi52iSGFdc FM57ET3tUrd3BBqeSXgnIHYZngeLibzjiq8Q+jAzKFIMwOlwIc3pmjvOPiA/dNvh7iBq v3j6vxe5h1Ewh2WdRbs+AbBQ0KOLy+n3P7qNvtrKqy8b+/5xIYSC9f0X7J+Y28VRtp9+ IwxxnJiHprQm0l5IhT1a9hHueI/5IwNB6uf9tVx3YJjyO/5pYjBKYFqdsKKe8SEZxN30 y3pek2XHtd2PPcxpNE8QJBchgNbPbIcOYJMM+i8Vzk2tv7wGH51SPqBdhT+VJJrE4JMK cvdQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=+jD5Tb6gXQ9jXcylAOT6YlY2182/zPFxQYhZXRO3HcM=; b=oLBXjosyjU5+/yB817ot2DScrRI68iLSSW06gOmNi2BZjMbBv5jfqNXodwtfE79NRg Jsa09qhnyXLdk95ch3bmM4KD+i38NpzxuvYPcocUA/Q9z6nZp+DX8/OCZUaxBvALNyi7 NxnvOZv6UPTzQDc8TF9GzgI/KOZTOETv0kBN+dKXFUQQCfRSVUcnDoBmdlj6S8nWmBS9 +Nny28TMhS2HGZWgK39bE+H7t6Dzs8AzGYaDYY2WAcLIagiAG5oPtc4MJmzKQqR1FP7q cCeFPLyrFn+/kWzVanO6eY3146JbWbE/6zG0c9rf+YtJa5ELBBwT5dYpsgq6j65y254Y o9RQ== X-Gm-Message-State: ABuFfoj6fuCqheMxzKK1HZPi8RpxtxlI5QwvukMGU7seW9InWO1gQMQH ZHdBFfxAtnp7s/9qeKvY/XX8gP/w X-Google-Smtp-Source: ACcGV63kjAjHWibwzYOJZCfuZhqYhRbceLrohWStJ7gj7bUBmwaeT0DQAztp2dfYrLUopoWSAAD37g== X-Received: by 2002:a5d:540d:: with SMTP id g13-v6mr5267743wrv.4.1538413869971; Mon, 01 Oct 2018 10:11:09 -0700 (PDT) Received: from [192.168.1.64] (93-44-96-206.ip96.fastwebnet.it. [93.44.96.206]) by smtp.gmail.com with ESMTPSA id b2-v6sm5095431wru.51.2018.10.01.10.11.08 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 01 Oct 2018 10:11:08 -0700 (PDT) Subject: Re: Booting the raspberry pi 2 from a usb hd To: freebsd-arm@freebsd.org References: From: Luca Cappelletti Message-ID: <3d7bb861-3604-3b4f-a6df-a734532e6ca7@gmail.com> Date: Mon, 1 Oct 2018 19:11:08 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: it Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Oct 2018 17:11:12 -0000 Il 01/10/18 12:56, Victor ha scritto: > I'm using a pi 2 card with FreeBSD 11.2-STABLE on the required sd card. It works like a charm but using it as a postgresql server with many write operation on it, to be on the safe side, I would like to move the operating system to an external hard-disk or ssd. > I've been surfing the net to find if it is possible to boot my pi 2 from an external hard-disk (or SSD) to no avail. > Could you please give me some hint, directions on this subject? > Ciao > Vittorio try to mirror the SD in the USB, then edit fstab to reflect the change at boot of the root I've never tried it but following a basic logic I would start like this If you find a solid and working solution, please post it in this mailinglist that I would try for sure ciao Luca From owner-freebsd-arm@freebsd.org Mon Oct 1 17:44:02 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 3512110A5235 for ; Mon, 1 Oct 2018 17:44:02 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic301-32.consmr.mail.ne1.yahoo.com (sonic301-32.consmr.mail.ne1.yahoo.com [66.163.184.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C5E8883F40 for ; Mon, 1 Oct 2018 17:44:01 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: n9tscJEVM1k9kKe30jdNYVFlak9HHtqeOeYIVbXbgT7Bo73XPnI6tZdXJqqBBg. TNnZvPcdhBsXwWH0sRJOy3Vn0DjLkFGCsSmk9HzwPchrMMUc61.hrzwaw6bYWVpNBXisrr25kp90 xmn9ow7Benl1nWEucdEDRBuIW44FAvXqUjJRVmcocfrP6py4PldY7AAOCHeDslB2UjS20KN0v1jd aMc2u4kF45ckAKjqprxP7mU_FFowyq5xfpao.oFD6qHLfcQu1bFRamLoNLBnEFuWa32jZboTSeDG JpXeIFr3bMH3.LSo8ZzItEVuvNqmhlKtywIMK5vQsw9OTlVIgTM1GrFtpB8jpEPWijczxna1GIdw 3xMjHw3QjR.HSEKbaIE4mhGFAyUUBhWuz2lxrZhhcrewZm893AgdPrXb8.thb56OWR93El8JaQLv _Grf5.2AX_V56ZZgpuIuBKAQMw.XlfjKcjNMI1QJR2lDnjCEL36bspZwnsBEWs0YwrOoEGE4AW1n WTOAg.aMYoYeW5WzvPp53UywqCs6.HSaByKJ2aPn5oKhRbFiTr2SmYqx0ZH7V7pAd9WO71aNVuxn ZMsLQ9roPOM9YEnliG5K8_1wleIqRKcCreerJEeEMUmr8QgqN91FuXjviTV314ex6ihgPns_7IcJ SMvLBKxtD22dXTAAe3mZK91h668e1Cc5OeQ.XMswtVRuHDMaj1SG.M__rqnfzXGwwBsxodyub4hY Sbt_sdv4hPJ5uriTnHaSWdJl4eiQ8alvTNGjNVWkNHnUr.X5Ne1iechSiHQQCoB58MzaCOrrPfip WVNEh_J1Nh6crETpq0vZh7Osz2iL63aSpqABWUvvADWShD6rz9HB2vehkP.bHVwobkTA7bUMdgOi Roy4FUCpx5zTi7P8aPG4yHBRWqbY.Zqz1BZtYkrhF6nFAIJMe50zWVqFAEDrJGqL9rQL1VnnB18x A_Cst8tRq5Iyi7_PBrs4byDCLkhKu0bE0ed7V3cABd93C5R6kQW3xbAPdlbYJDYef.oktJxErMRk BggBDVszHYGua4Xg- Received: from sonic.gate.mail.ne1.yahoo.com by sonic301.consmr.mail.ne1.yahoo.com with HTTP; Mon, 1 Oct 2018 17:43:55 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.101]) ([76.115.7.162]) by smtp405.mail.ne1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 038155f39af66d64170e94dba2b85dfe; Mon, 01 Oct 2018 17:43:54 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: Booting the raspberry pi 2 from a usb hd From: Mark Millard In-Reply-To: <3d7bb861-3604-3b4f-a6df-a734532e6ca7@gmail.com> Date: Mon, 1 Oct 2018 10:43:53 -0700 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <9EB03ECE-5E5A-4DE3-9DAA-BFE1F64785B3@yahoo.com> References: <3d7bb861-3604-3b4f-a6df-a734532e6ca7@gmail.com> To: Luca Cappelletti X-Mailer: Apple Mail (2.3445.9.1) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Oct 2018 17:44:02 -0000 On 2018-Oct-1, at 10:11 AM, Luca Cappelletti wrote: > Il 01/10/18 12:56, Victor ha scritto: >> I'm using a pi 2 card with FreeBSD 11.2-STABLE on the required sd = card. It works like a charm but using it as a postgresql server with = many write operation on it, to be on the safe side, I would like to move = the operating system to an external hard-disk or ssd. >> I've been surfing the net to find if it is possible to boot my pi 2 = from an external hard-disk (or SSD) to no avail. >> Could you please give me some hint, directions on this subject? >> Ciao >> Vittorio >=20 > try to mirror the SD in the USB, then edit fstab to reflect the change = at boot of the root After the mirroring there are two /etc/fstab files, one in each place. The one on the microsd card media needs to be changed as it will be found and used to mount what it lists for / . After that the /etc/fstab on what is mounted on / will be used as I understand. (But I normally keep the two files tracking and so would not see the distinction.) > I've never tried it but following a basic logic I would start like = this > If you find a solid and working solution, please post it in this = mailinglist that I would try for sure =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-arm@freebsd.org Mon Oct 1 18:42:05 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 3C6F410A706D for ; Mon, 1 Oct 2018 18:42:05 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D30A686BC7 for ; Mon, 1 Oct 2018 18:42:04 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.110.112]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1g738l-00072w-Eq; Mon, 01 Oct 2018 20:41:55 +0200 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-arm@freebsd.org, Victor Subject: Re: Booting the raspberry pi 2 from a usb hd References: Date: Mon, 01 Oct 2018 20:41:55 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.4.0 X-Scan-Signature: 9090f8a1960d7f777b94d17b6f36e747 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Oct 2018 18:42:05 -0000 On Mon, 01 Oct 2018 12:56:58 +0200, Victor wrote: > I'm using a pi 2 card with FreeBSD 11.2-STABLE on the required sd card. > It works like a charm but using it as a postgresql server with many > write operation on it, to be on the safe side, I would like to move the > operating system to an external hard-disk or ssd. > I've been surfing the net to find if it is possible to boot my pi 2 from > an external hard-disk (or SSD) to no avail. > Could you please give me some hint, directions on this subject? > Ciao > Vittorio Booting a raspberry pi starts with u-boot. It is loaded from a msdos partition on the SD-card. U-boot loads the FreeBSD boot loader, which knows how to load the kernel. A modern u-boot can load the FreeBSD boot loader from USB. An alternative is to have the FreeBSD /boot dir on the SD and load all the rest from the SSD. This is the relevant part of my fstab: /dev/gpt/ssdrootfs / ufs rw,noatime 1 1 /dev/ufs/rootfs /bootdir ufs rw,noatime 1 1 /dev/msdosfs/MSDOSBOOT /boot/msdos msdosfs rw,noatime 0 0 And a symlink to keep it together: $ ls -l /boot lrwxr-xr-x 1 root wheel 12 Jul 15 17:38 /boot@ -> bootdir/boot A little bit more information: https://wiki.freebsd.org/FreeBSD/arm/Raspberry%20Pi https://wiki.freebsd.org/FreeBSD/arm/U-Boot-ports https://wiki.freebsd.org/RootOnZFS/UFSBoot Regards, Ronald. From owner-freebsd-arm@freebsd.org Mon Oct 1 23:11:12 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 91A3F10ACD68 for ; Mon, 1 Oct 2018 23:11:12 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic305-22.consmr.mail.ne1.yahoo.com (sonic305-22.consmr.mail.ne1.yahoo.com [66.163.185.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 27ED670A27 for ; Mon, 1 Oct 2018 23:11:11 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: Kav2PIUVM1lWENKjy03JaBr0e.qPveRq5s.TJ4jgniYDm_phletfD3QNyt0qrix rfxAaP2.3eqKKxOOHr2yy9jUUDKZqdZ81skf25px_cuIaB8vS4sluT8r9V8q.pDZkgdy3NFKnczC xCzl4rwVTj4BycKzo2EJvvejATMS7efeEzV.eKpsaie_4JUJOt13I79GbaKReF7tCi9MnwtFMxg1 XqdW0Ye_LlpN1XRGclo.a9EBv1NT_PwjtlZScKLbLacDAOit._WTHELj_AMByIJz1ERZ3d540HuB HVMTd6pbfmyhKNUop5woei8saKrUCXT7bzrTsOqNesiHxMx.4ypBz4a7FxMsH28LN_5ofkd3nrl_ pUV0eQkNbQ.TM1jd.xIBq4e8dQ3B8_USodpb5U_BIaD9yMRW2HLgJQa8_5TEwJztHsZ8G8bUzM3Q xnFQtt_zcEG6MozQjRrgADBFWtybbkOrJqVW6w3k6MxfSTRJg448S9pGfCBDXBA48hqv_FDEp7aw aLAU7tRalHjovi7mAvct8y8H7qHV4GLNK_Q4nTRgXs59IEW3P7.vivOiW879AMcYkhSTPa68FS.1 aWFZJ3JLqoVHJ2cSkrbJwgx4aBUPkiLJnhrfPSG82HM5ZPpiopPkLbHrt4xnTYOChKxps6qg5X6E VSz2Q5N34lbbnsh4tU1pJ9NZJSwy.hALev3sGqXsTG209U8J66JlVLvPSUIxwZ_8MfydEmA__FuB ZTRRANGugdTWpzPDxPE60a4jSOHM0SL7z7uXAk4e.AWQEfYh8MRp4h.0JysUIrgJSm_mBiWAK96r HP.hl_m_dWDcbTMlfRH6rakfO73ZFC_vhtHDATcjClZI9UL.MEvfFrPJ_pGEVqkFMqBtmD03ZPK. E85LGTR2LcTjR4ErLbWBQYilgGowl4DA7HTuiMWm.exl7NpVrZ6TknJYOjAVe8oaQ8dxgGfILq7t YLe_PNNWUsPPY2oLKWfgaTtuBTEyMV2ZCuMQm7VjW1.TksiGi87bQRZ4VIi6uTG9tNR3mGOnuS0_ O2pDvNrAcXnteCVB15WqJ1Z0- Received: from sonic.gate.mail.ne1.yahoo.com by sonic305.consmr.mail.ne1.yahoo.com with HTTP; Mon, 1 Oct 2018 23:11:04 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.101]) ([76.115.7.162]) by smtp416.mail.ne1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 23b502d3147d50ba2cc1e600d9d99c2b; Mon, 01 Oct 2018 23:00:56 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: Timeout poll on interrupt endpoint for RPI3 with keyboard and mouse From: Mark Millard In-Reply-To: <20181001022415.GA63212@www.zefox.net> Date: Mon, 1 Oct 2018 16:00:54 -0700 Cc: Trevor Roydhouse , freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <39B3886F-CFB2-4DFE-B7C5-517E4836774A@yahoo.com> References: <20180929185213.GA58381@www.zefox.net> <20180930111208.5df04f5b7fb336cdfcf2fd74@bidouilliste.com> <20180930130930.GB58381@www.zefox.net> <20180930132928.GC58381@www.zefox.net> <20180930155055.2c35693431e8dfff4eb7d7bd@bidouilliste.com> <20180930145702.GD58381@www.zefox.net> <20181001022415.GA63212@www.zefox.net> To: bob prohaska X-Mailer: Apple Mail (2.3445.9.1) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Oct 2018 23:11:12 -0000 On 2018-Sep-30, at 7:24 PM, bob prohaska wrote: > On Mon, Oct 01, 2018 at 08:57:04AM +1000, Trevor Roydhouse wrote: >>=20 >> You just need to change one character in the file=20 >> .../sys/arm64/include/pte.h - change the 4 to an 8 in this existing = line: >>=20 >> #define PMAP_MAPDEV_EARLY_SIZE (L2_SIZE * 4) >>=20 >=20 > Ok, that wasn't hard 8-) >=20 > The machine now boots with the monitor connected and continues to run=20= > correctly when keyboard and mouse are plugged in. >=20 > With monitor, keyboard and mouse connected it still spits out a stream = of > Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > .... > during the boot process. The spew seems continuous, but when I typed > boot > into the spew, it looks as if the kernel took over and the machine is > now multi-user.=20 >=20 > Evidently it got stuck in loader, the boot command got it unstuck and > after that all is normal. >=20 > So, I guess the video issue was a distraction that's now fixed. The=20 > problem with USB mouse and keyboard remain unresolved but nonfatal. =20= I've replicated the issue in my current environment in that any time both a keyboard and a mouse are attached during power-up I get the: "Timeout poll on interrupt endpoint" messages. (I've found some other behavior as well.) The same is true when both are plugged into a powered hub that is in turn plugged into the rpi3. But with just one of the two plugged in I do not get the messages, directly plugged in or via the powered hub. The monitor HDMI connector makes no difference for if it is plugged in or not. (Ethernet and the serial console were connected and active during the experiments.) It seems that multiple USB input devices are mishandled in very early time frames, lasting at least to during the kernel 10 sec count down for getting to the loader prompt. (10 sec is just the default.) Similarly, having, say, a keyboard and a reader (with a usd card in it) seems to cause 1 MB/s classification instead of 40 MB/s classification for the reader's lun's, possibly carry over from u-boot time frame activity. The keyboard worked. Without the keyboard it boots assigning 40 MB/s to the lun's. These experiments were done using the powered hub. When I instead tried just 2 such readers via the powered hub, instead the boot hung up for booting after shutdown -r now, showing: In: serial Out: vidconsole Err: vidconsole Net: No ethernet found. starting USB... USB0: scanning bus 0 for devices... Device NOT ready Request Sense returned 02 3A 00 Device NOT ready Request Sense returned 02 3A 00 Device NOT ready Request Sense returned 02 3A 00 Device NOT ready Request Sense returned 02 3A 00 Device NOT ready Request Sense returned 02 3A 00 Device NOT ready Request Sense returned 02 3A 00 Device NOT ready Request Sense returned 02 3A 00 7 USB Device(s) found scanning usb for storage devices... 8 Storage Device(s) found Hit any key to stop autoboot: 0=20 MMC Device 0 not found no mmc device at slot 0 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found EFI removable media binary efi/boot/bootaa64.efi libfdt fdt_check_header(): FDT_ERR_BADMAGIC Scanning disk mmc@7e300000.blk... Scanning disk usb_mass_storage.lun0... Disk usb_mass_storage.lun0 not ready Scanning disk usb_mass_storage.lun1... Disk usb_mass_storage.lun1 not ready Scanning disk usb_mass_storage.lun2... Disk usb_mass_storage.lun2 not ready Scanning disk usb_mass_storage.lun3... Scanning disk usb_mass_storage.lun0... Disk usb_mass_storage.lun0 not ready Scanning disk usb_mass_storage.lun1... Disk usb_mass_storage.lun1 not ready Scanning disk usb_mass_storage.lun2... Disk usb_mass_storage.lun2 not ready Scanning disk usb_mass_storage.lun3... Disk usb_mass_storage.lun3 not ready Found 6 disks FDT memrsv map 0: Failed to add to map 637000 bytes read in 59 ms (10.3 MiB/s) libfdt fdt_check_header(): FDT_ERR_BADMAGIC FDT memrsv map 0: Failed to add to map ## Starting EFI application at 00080000 ... Consoles: EFI console =20 efipart_readwrite: rw=3D1, blk=3D64 size=3D1 status=3D7 efipart_readwrite: rw=3D1, blk=3D1 size=3D1 status=3D7 After a minute(?) wait there was: efipart_readwrite: rw=3D1, blk=3D104383 size=3D8 status=3D7 And another wait: efipart_readwrite: rw=3D1, blk=3D2079 size=3D257 status=3D7 - (That "-" was in the serial console output.) Another wait, then: efipart_readwrite: rw=3D1, blk=3D64 size=3D1 status=3D7 EFI: Watchdog timeout resetting ... MMC: mmc@7e300000: 1 Loading Environment from FAT... *** Warning - bad CRC, using default = environment . . . It booted fine from there. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-arm@freebsd.org Tue Oct 2 01:10:26 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 D113A10AF9E3 for ; Tue, 2 Oct 2018 01:10:25 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic305-22.consmr.mail.ne1.yahoo.com (sonic305-22.consmr.mail.ne1.yahoo.com [66.163.185.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5FB577482F for ; Tue, 2 Oct 2018 01:10:25 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: EQHejeIVM1lVhXtwzv_KKxnBA55KcH8BOTh72W_OoSc5fBw6N8WKAumFnCiY4c3 j8ASlu015LLvGosDn_EYZ4kOVwWvbz9Q.3YNSRVeSWMgvWrffFrfPyAxtqlg_2BswQHaFQksoeSW wbF5KDps.BrE_aNFX4SQu1Xb1Pu6pW87TEigPThEjLdw19o71SyE5g9weF5jOvsidy3mvuzlO8jO 78bzVwDXySYk827DtJ7BPZpHBnQcGgmMBlSXygxNJHgFXZzxQBnG0WyBpF_l.MS0wKhPGXFkLZqg AkVFsSAPaqltIlhQbQZu4HIOv5EFz55CeUuBPonDQcGETdlc9QsnMLixAEUWLKopKWcb7cTleg5S nLT0I1DqC3B8dpC26rCcw71USGzG1QRgyeOmthTGrVXztFgHfVOsnit8yPnuyKViMxJsLJXFLWZw aLXmcvO6up0fV_Tw_kLiDhQJwBAECIV4dbRDGR0QySio8f6JG3464CUw6NuZ642BZ75sYNDTyloM jJPBBm8A4GDda1RuVF7zpKbmJXOpG2mD6X6TSkFVAfIQhe5SRM5NMsJrYcsMB8Q9FWMBQXdZiOD1 rrrYhd1BwvbF6ybYJWP2pHn2T3_.WKhkKGFh7MGiRe4Tkb_GGwVEoHi..8LuUyJ0WPJspX.X_Q3i ny2YyNJbswnHN9FSQ7nXQJ4VA55fWFOc0KnWDhN9tDRlnDEuJVYKGTgh4t5uurrdnagydDPE6fYD KTdoPqiP7S5mDz5plG52CtB6__ClwyTGDHfAbrzGc.FI6z0XAfuaGKlfqe7hX6_0UlnT8a_k1MH3 XW1_dn8y6Pcz.gSwXoLWa2Z__gVJjCGFaMS2dobyKxcy6vodWrceXoFdbdJA1kCctPJ1qKmrD_2g GeX5pCUZZeN1Z6G6XQ9CdiZ0Ji0bVbcqA5LrGI9mdiV7W0tqmvkrFML0kAmXI.XRMQjIrR4ZPvP0 I6z.RCTGWJA6TRqNAdbeycl9OLon2VLS6b2wFcQHwy_18i0t_aV9e7NqANCO9MwYM7fDr31VlMMa sorkQHcE7u9yB5R8Yyw-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic305.consmr.mail.ne1.yahoo.com with HTTP; Tue, 2 Oct 2018 01:10:23 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.101]) ([76.115.7.162]) by smtp405.mail.ne1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 29f6b4cc1a8b50f6fba573fcae5942ca; Tue, 02 Oct 2018 01:10:19 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: Timeout poll on interrupt endpoint for RPI3 with keyboard and mouse From: Mark Millard In-Reply-To: <39B3886F-CFB2-4DFE-B7C5-517E4836774A@yahoo.com> Date: Mon, 1 Oct 2018 18:10:17 -0700 Cc: Trevor Roydhouse , freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20180929185213.GA58381@www.zefox.net> <20180930111208.5df04f5b7fb336cdfcf2fd74@bidouilliste.com> <20180930130930.GB58381@www.zefox.net> <20180930132928.GC58381@www.zefox.net> <20180930155055.2c35693431e8dfff4eb7d7bd@bidouilliste.com> <20180930145702.GD58381@www.zefox.net> <20181001022415.GA63212@www.zefox.net> <39B3886F-CFB2-4DFE-B7C5-517E4836774A@yahoo.com> To: bob prohaska X-Mailer: Apple Mail (2.3445.9.1) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Oct 2018 01:10:26 -0000 On 2018-Oct-1, at 4:00 PM, Mark Millard wrote: > On 2018-Sep-30, at 7:24 PM, bob prohaska = wrote: >=20 >> On Mon, Oct 01, 2018 at 08:57:04AM +1000, Trevor Roydhouse wrote: >>>=20 >>> You just need to change one character in the file=20 >>> .../sys/arm64/include/pte.h - change the 4 to an 8 in this existing = line: >>>=20 >>> #define PMAP_MAPDEV_EARLY_SIZE (L2_SIZE * 4) >>>=20 >>=20 >> Ok, that wasn't hard 8-) >>=20 >> The machine now boots with the monitor connected and continues to run=20= >> correctly when keyboard and mouse are plugged in. >>=20 >> With monitor, keyboard and mouse connected it still spits out a = stream of >> Timeout poll on interrupt endpoint >> Timeout poll on interrupt endpoint >> .... >> during the boot process. The spew seems continuous, but when I typed >> boot >> into the spew, it looks as if the kernel took over and the machine is >> now multi-user.=20 >>=20 >> Evidently it got stuck in loader, the boot command got it unstuck and >> after that all is normal. >>=20 >> So, I guess the video issue was a distraction that's now fixed. The=20= >> problem with USB mouse and keyboard remain unresolved but nonfatal. =20= >=20 > I've replicated the issue in my current environment in that any > time both a keyboard and a mouse are attached during power-up I > get the: "Timeout poll on interrupt endpoint" messages. (I've > found some other behavior as well.) >=20 > The same is true when both are plugged into a powered hub > that is in turn plugged into the rpi3. >=20 > But with just one of the two plugged in I do not get the > messages, directly plugged in or via the powered hub. >=20 > The monitor HDMI connector makes no difference for if it is > plugged in or not. >=20 > (Ethernet and the serial console were connected and > active during the experiments.) >=20 > It seems that multiple USB input devices are mishandled in > very early time frames, lasting at least to during the kernel > 10 sec count down for getting to the loader prompt. (10 sec > is just the default.) >=20 > Similarly, having, say, a keyboard and a reader (with a usd card > in it) seems to cause 1 MB/s classification instead of 40 MB/s > classification for the reader's lun's, possibly carry over > from u-boot time frame activity. The keyboard worked. Without > the keyboard it boots assigning 40 MB/s to the lun's. These > experiments were done using the powered hub. >=20 > When I instead tried just 2 such readers via the powered hub, > instead the boot hung up for booting after shutdown -r now, > showing: >=20 > In: serial > Out: vidconsole > Err: vidconsole > Net: No ethernet found. > starting USB... > USB0: scanning bus 0 for devices... Device NOT ready > Request Sense returned 02 3A 00 > Device NOT ready > Request Sense returned 02 3A 00 > Device NOT ready > Request Sense returned 02 3A 00 > Device NOT ready > Request Sense returned 02 3A 00 > Device NOT ready > Request Sense returned 02 3A 00 > Device NOT ready > Request Sense returned 02 3A 00 > Device NOT ready > Request Sense returned 02 3A 00 > 7 USB Device(s) found > scanning usb for storage devices... 8 Storage Device(s) found > Hit any key to stop autoboot: 0=20 > MMC Device 0 not found > no mmc device at slot 0 > switch to partitions #0, OK > mmc1 is current device > Scanning mmc 1:1... > Found EFI removable media binary efi/boot/bootaa64.efi > libfdt fdt_check_header(): FDT_ERR_BADMAGIC > Scanning disk mmc@7e300000.blk... > Scanning disk usb_mass_storage.lun0... > Disk usb_mass_storage.lun0 not ready > Scanning disk usb_mass_storage.lun1... > Disk usb_mass_storage.lun1 not ready > Scanning disk usb_mass_storage.lun2... > Disk usb_mass_storage.lun2 not ready > Scanning disk usb_mass_storage.lun3... > Scanning disk usb_mass_storage.lun0... > Disk usb_mass_storage.lun0 not ready > Scanning disk usb_mass_storage.lun1... > Disk usb_mass_storage.lun1 not ready > Scanning disk usb_mass_storage.lun2... > Disk usb_mass_storage.lun2 not ready > Scanning disk usb_mass_storage.lun3... > Disk usb_mass_storage.lun3 not ready > Found 6 disks > FDT memrsv map 0: Failed to add to map > 637000 bytes read in 59 ms (10.3 MiB/s) > libfdt fdt_check_header(): FDT_ERR_BADMAGIC > FDT memrsv map 0: Failed to add to map > ## Starting EFI application at 00080000 ... > Consoles: EFI console =20 > efipart_readwrite: rw=3D1, blk=3D64 size=3D1 status=3D7 > efipart_readwrite: rw=3D1, blk=3D1 size=3D1 status=3D7 >=20 > After a minute(?) wait there was: >=20 > efipart_readwrite: rw=3D1, blk=3D104383 size=3D8 status=3D7 >=20 > And another wait: >=20 > efipart_readwrite: rw=3D1, blk=3D2079 size=3D257 status=3D7 > - >=20 > (That "-" was in the serial console output.) >=20 > Another wait, then: >=20 > efipart_readwrite: rw=3D1, blk=3D64 size=3D1 status=3D7 >=20 > EFI: Watchdog timeout > resetting ... > MMC: mmc@7e300000: 1 > Loading Environment from FAT... *** Warning - bad CRC, using default = environment > . . . >=20 > It booted fine from there. >=20 Repeated testing shows that "EFI: Watchdog timeout" normally leads to the problem repeating. I've only had the one boot. Also: Each "efipart_readwrite" message has a wait before it, not just the ones that I listed. I've not been able to repeat the problem on a Pine64+ 2GB. I do not have access to any other aarch64 FreeBSD contexts at this time. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-arm@freebsd.org Tue Oct 2 03:43:00 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 C5D4F10B3DE8 for ; Tue, 2 Oct 2018 03:43:00 +0000 (UTC) (envelope-from mw@semihalf.com) Received: from mail-io1-xd43.google.com (mail-io1-xd43.google.com [IPv6:2607:f8b0:4864:20::d43]) (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 61F6D79760 for ; Tue, 2 Oct 2018 03:43:00 +0000 (UTC) (envelope-from mw@semihalf.com) Received: by mail-io1-xd43.google.com with SMTP id e12-v6so784382iok.12 for ; Mon, 01 Oct 2018 20:43:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=semihalf-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=fi+T+Gd//N4I+ry/ViDIv6Kdw4fhIJ5PLOlfd1s0+rE=; b=cBF77R6Q+lpWDtF+iFb6ctpomePMoqdLavgLcGkZJ+lD7VrLWMOD3xM5GTis9QYhs+ AFKtaSRGVkiYVfQkBhSnZnkLmFd8MegQf5fo9zeGAjFPw9TAqAN/8rugkkcAz4ucCHRC sa4iQtlLbTaRtCiDIGg4K5Rkw5PeU9A/dkWpyXZkVd/GgEURSDi26HnkBJB7n4f8stE3 hGkePPUZRYplHyLpg58hiWXgtKpa8h0y8TF/l3n80h55Gvpj5wT0sJj5NPBvA3oRisye Pnv0t8WmjZW4xc6nPbvnQX4jCPw9gsXxUIySZ+jL6kwzC17QFPxY3B5104ojokFawXHu Qp1w== 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:content-transfer-encoding; bh=fi+T+Gd//N4I+ry/ViDIv6Kdw4fhIJ5PLOlfd1s0+rE=; b=IpB3MbVpwEMG6pdg3tMB+o3S9sQjPOcQZeXXZIwGOG5ptHBKyOJRcTN6/Lw3e4+2OJ 14bUfsdD5CnvoobgpakVDmlKU5pexid4mAhhKOoVLx16pwmfmvwtR7Pzi0iT21jdP4TQ hAyOPluGKP4iChQZym9qgE0I2BnOJ9AuECQZoY0Fe3xjT7NU67mPk8gExkxu1+WVqAfd A9b4kWEfb+El1PNf4GCJQVqOACeYyKwBntv2IG9UBDvqo+9eCHZGQweo1nPs+R1LF/fh Sd7JUBQ/nAUfFHUs92D4xwNmXveoz2vuvW7hUDrV5lYLHKQBXmP1VsjOdTUzwNyRWDf/ SB8Q== X-Gm-Message-State: ABuFfog8qqNwCOi9CfiZsFK1Bvhrw0kCjzzHzlk3Pz5RZn9OxzLMjOoM MQBJTYcEVhIxI05b+Qk8o6pCgTbsBe5xI4doPDyJczuCi3A= X-Google-Smtp-Source: ACcGV6378ogKIiZcGKc2zP204uM8QbVIooQ6DRhlTXHTjFoSdeGtGZFIROU46Aj60yKaTGt7HGUH9CyjyYWwpfoxSSE= X-Received: by 2002:a6b:7e0c:: with SMTP id i12-v6mr9638560iom.221.1538451779636; Mon, 01 Oct 2018 20:42:59 -0700 (PDT) MIME-Version: 1.0 References: <03261C47-F7E5-46D6-9A91-B8FFDD96FDE3@sonic.net> In-Reply-To: <03261C47-F7E5-46D6-9A91-B8FFDD96FDE3@sonic.net> From: Marcin Wojtas Date: Tue, 2 Oct 2018 05:42:48 +0200 Message-ID: Subject: Re: ClearFog Base -- "status: no carrier" for mvneta1 To: pygr@sonic.net Cc: freebsd-arm Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Oct 2018 03:43:01 -0000 Hi Glenn, I can see, that armada-388-clearfog-base.dts connects eth1 to a PHY via MDI= O. Unfortunately my Clearfog boards have the SFP cage connected only to the SGMII lanes only (no PHY). Can you please try to boot with armada-388-clearfog.dts, where the SFP cage is configured as the 'fixed-link' and let know? Best regards, Marcin pt., 28 wrz 2018 o 18:47 glenn napisa=C5=82(a): > > With a recent build from source (FreeBSD 12.0-ALPHA7 FreeBSD 12.0-ALPHA7= 7fe1a714461(master) ARMADA38X arm) the ethernet port on a ClearFog Base n= ear the USB sockets works well, but the port near the SFP cage doesn=E2=80= =99t. ifconfig shows "mvneta1: status: no carrier=E2=80=9D. > > Both ports are connected to a gigabit switch. The green link LED on the C= learFog Base for mvneta0 is on most of the time, but flickering; the green = link LED for mvneta1 is on without flickering. On the switch, the correspon= ding link LED for mvneta0 is on constantly, the LED for mvneta1 is off. > > I don=E2=80=99t believe it=E2=80=99s a hardware issue, because, if the pa= tch cables are swapped at the board, mvneta1 still shows no carrier and whi= ch LED on the switch is illuminated swaps. Also, without touching the cable= s or switch, Debian can be booted up using a different SD card, and both et= hernet ports are functional with no special action taken. > > The device tree file being used is compiled from armada-388-clearfog-base= .dts in the FreeBSD source, but edited to allow the serial console to work. > > What might it take to get that second ethernet port to work? A modificati= on of the device tree file? A modification of the mvneta or miibus driver? = A modification of u-boot? Or, perhaps, just a simple configuration step? > > Glenn > _______________________________________________ > 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 Tue Oct 2 14:57:45 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 661731098848 for ; Tue, 2 Oct 2018 14:57:45 +0000 (UTC) (envelope-from lists.br@gmail.com) Received: from mail-ed1-x531.google.com (mail-ed1-x531.google.com [IPv6:2a00:1450:4864:20::531]) (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 CF7E38F249 for ; Tue, 2 Oct 2018 14:57:44 +0000 (UTC) (envelope-from lists.br@gmail.com) Received: by mail-ed1-x531.google.com with SMTP id t11-v6so2328538edq.11 for ; Tue, 02 Oct 2018 07:57:44 -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=lHLo0NWVGO06h/uI3DuX4tOBSfu6py8FIoozw3P9qMA=; b=IlpYfAB4SNKQz1KewPzdVMgRAnQkm9dnduvYdDP6JZwvbP9bMjqhwjYq2i4+WkmhrX mdpKUECly8/y4NgqsCfEP+h6S5TqUVd5NJa+M6lB2HbvjSp2Aa5Kmjb41y64JkmNiNt/ cDq7pOtN9dHAYaliEIfLRT7doyzqafwjD8tgHfb+QE75bpsnBIamBHynu1lZfpqUIvYG x+WH/g2XztFO1d8e/nZNWFFP61VfPk7W+Ots/5/YpwYb/0JjKi68aUiobHIBn38mNXnM MdrTc1iEpaujCPZTKAtGOT1iE8xDEsHaB3mAnEXR08Wjak54RFHuMRZfscQJUF2BWb+S 598Q== 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=lHLo0NWVGO06h/uI3DuX4tOBSfu6py8FIoozw3P9qMA=; b=Yd45JqHUWsMAj/7KZO3MgySZfnn/+79ZcYEzFH7mVJo6HRbGD8BHaRFi2YtBQBNtU1 9FFWfRzTC/qF5uazAv9PzYUhVvyN5FhKoqX/zXdggmVZ8Vx7cBETCAEcKX7NFU1DJAHy XybK4N70mP6MJm4s7+b/Cb8scXnPgJdfH4g51XsA004r2Tkngd9InZJKvxtc2e7wVL9K orfWak0gN8/NxZ2k4yjGxpVBv10XYsJeqSRfcK3jEYBF1eIlyU4eXiG2Imo3bXrvIZu8 DM/DCjnUOV4yO/p40c85EB0aBPSNvsSaH8bPIgMlkqNRkRqucp7MhmRerDC2N+mxsD0Q 7l5w== X-Gm-Message-State: ABuFfohp0NS0Vhpcq87axMcfsNV0EJP5cxJ4rcMsRbkTPEQaNV7n8DE9 D2sQ8DBJkWZQmw6gu65udVgqytxkrhCT9BINEsM= X-Google-Smtp-Source: ACcGV60MVK6gSnXNys05gFXFAaJqxPIJpXxXPwttYR6BR2y3PRN5v9lz+Z6uV2d1RtfpeTrgoXRu9dzWf2o4R5XVyjY= X-Received: by 2002:a50:fa8b:: with SMTP id w11-v6mr23971108edr.59.1538492263691; Tue, 02 Oct 2018 07:57:43 -0700 (PDT) MIME-Version: 1.0 References: <03261C47-F7E5-46D6-9A91-B8FFDD96FDE3@sonic.net> In-Reply-To: From: Luiz Otavio O Souza Date: Tue, 2 Oct 2018 11:57:32 -0300 Message-ID: Subject: Re: ClearFog Base -- "status: no carrier" for mvneta1 To: Marcin Wojtas Cc: pygr@sonic.net, "freebsd-arm@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Oct 2018 14:57:45 -0000 On Tue, 2 Oct 2018 at 00:43, Marcin Wojtas wrote: > > Hi Glenn, > > I can see, that armada-388-clearfog-base.dts connects eth1 to a PHY via MDIO. > Unfortunately my Clearfog boards have the SFP cage connected only to > the SGMII lanes only (no PHY). > > Can you please try to boot with armada-388-clearfog.dts, where the SFP > cage is configured as the 'fixed-link' and let know? I don't have the Clearfog Base here, but this board has the PHY1 reset connected to GPIO pin 19, you probably want to check this too. Luiz From owner-freebsd-arm@freebsd.org Tue Oct 2 18:31:44 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 6B09710A7E1E for ; Tue, 2 Oct 2018 18:31:44 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E0F0B76AE7 for ; Tue, 2 Oct 2018 18:31:43 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id c61cc8c9; Tue, 2 Oct 2018 20:31:35 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=wCYRIsYQ+BIM4ZtZavsi9I+qMTM=; b=gEjn3ct12qEuUvn20pPFBAgynoqZ 2wZqk4c+nkQwWWQVf30ypuwouw7K99K+PkQUUqAYdAd4sCThkZirrOUMuy7+aNcJ 4LfRuTA0+ACMJajm0+NMXbbolk0mWRhjTQLM4NM+80L8DRFHSEdYhsSzJKYdUIy6 g96XMJIFiYQUU4E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=k8UJZYVuLohJ92XN08H5qbqEJi/YR97vx92kXXgdR8Py74woJ/a888QS BB7SV4goNOfQOFZtB2beeVirAJnneEz4ISOSpwToMWrOw0gLc4WIWQkjgzmd7uW8 B8nmpa+eI7a6QOKGtY7qwLqlYy8PJNAUXn+D8W76KdBMID++EV4= Received: from skull.home.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 0ee2caad TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Tue, 2 Oct 2018 20:31:35 +0200 (CEST) Date: Tue, 2 Oct 2018 20:31:35 +0200 From: Emmanuel Vadot To: bob prohaska Cc: Trevor Roydhouse , freebsd-arm@freebsd.org Subject: Re: Timeout poll on interrupt endpoint for RPI3 with keyboard and mouse Message-Id: <20181002203135.245edff2acfcbd8441d67cc3@bidouilliste.com> In-Reply-To: <20181001022415.GA63212@www.zefox.net> References: <20180929185213.GA58381@www.zefox.net> <20180930111208.5df04f5b7fb336cdfcf2fd74@bidouilliste.com> <20180930130930.GB58381@www.zefox.net> <20180930132928.GC58381@www.zefox.net> <20180930155055.2c35693431e8dfff4eb7d7bd@bidouilliste.com> <20180930145702.GD58381@www.zefox.net> <20181001022415.GA63212@www.zefox.net> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Oct 2018 18:31:44 -0000 On Sun, 30 Sep 2018 19:24:16 -0700 bob prohaska wrote: > On Mon, Oct 01, 2018 at 08:57:04AM +1000, Trevor Roydhouse wrote: > > > > You just need to change one character in the file > > .../sys/arm64/include/pte.h - change the 4 to an 8 in this existing line: > > > > #define PMAP_MAPDEV_EARLY_SIZE (L2_SIZE * 4) > > > > Ok, that wasn't hard 8-) > > The machine now boots with the monitor connected and continues to run > correctly when keyboard and mouse are plugged in. > > With monitor, keyboard and mouse connected it still spits out a stream of > Timeout poll on interrupt endpoint > Timeout poll on interrupt endpoint > .... > during the boot process. The spew seems continuous, but when I typed > boot > into the spew, it looks as if the kernel took over and the machine is > now multi-user. > > Evidently it got stuck in loader, the boot command got it unstuck and > after that all is normal. > > So, I guess the video issue was a distraction that's now fixed. The > problem with USB mouse and keyboard remain unresolved but nonfatal. So I've just tested ALPHA8 on my RPI3 and RPI3B+. With *just* keyboard and mouse plugged in I do not have any problem at all. If I plug a cheap usb stick, same, no problem. But if I plug my Corsair Voyager USB3, u-boot is really slow to probe usb devices. I didn't see the Timeout poll message but I didn't have serial connected (I think it doesn't matter since u-boot send all prints to every console). The RPI u-boot maintainer is aware that there is issue regarding USB on RPI3B+, now he's aware that there is some on RPI3. I see in your mail that you have some usb harddrive or usb stick plugged too, can you try without them ? Thanks, > Thanks _very_ much for your help! > > bob prohaska > > _______________________________________________ > 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" -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Tue Oct 2 18:52:09 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 0049910A85D4 for ; Tue, 2 Oct 2018 18:52:08 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic314-21.consmr.mail.ne1.yahoo.com (sonic314-21.consmr.mail.ne1.yahoo.com [66.163.189.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8F4CC77404 for ; Tue, 2 Oct 2018 18:52:08 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: hIBRrJkVM1k7vp5SjG7SkXl5O1KM2UWuiQbTj58Z0mIgtQxbqNWzjNFKf1b2AdD IbKcKtTTIQUMQi7vFTmuGAPRo4pXMbcs_lAbDZMH7LPl5gldLcfFQLbkABOTKWFnE17G_xYgsQ.3 zFk2Hqn4P.dhgngomJeujSoHN56ZqzkFl_TGh1rRYCPDx8.M.dbOlnvtiRNuGZbzEbXP3ObJiMfv N7qk26Be3rgu8jN9wRGKiG.IlkswaifxJ_Hr1YPI.BJz.HV7NiqgIEzC8r7V5lWTldFC90PiKrzb g_2NKOPAk0IFnpCEpWWOwEcwnZSihauWaL5jJTKt9APfY8bZPOKbuXgkGyEPEj2mIv5Hris5SLcN SjIO8hDs1b05ihlrQ8YFt7tM2_RxE.FkO9MNFaVtL95OwtCtpo0RS17P1VgzAfbm3H0vsSQWGBPG Bs4CK18WVtpPVjtUsaBljs6b9NTvawrfGa.k.hzp6XR6HnFvfIgVDtiPgzei5wv67QewY0myVuoe o8lKvsZZlBtq5d6bT3NO7IS70q3Ahicv9_tBPg0YCVy4DyycYFsK5IHlA21.ko1yIjNOEv0X1oik 0ZRxgxZ4U3Tbw6d1Zez3Zu5lzoGS5JKC5FoFhAPnxVFU18Yd7EgBSmyJ84aHlGKLL.jnOBJPqrUm psvYS.6lv9rXr8x_yo7i6Xg8kwote9.1Jh7.blW0q1Lq23QXIQh.yxnGoeF_AlqwZ3goFMi1mRJX uUP3NtsHhavjVDxh0ny7O.7tAd0MR0lssH6g1Ox.uTSBCH1J3MH.zlHtWzPu6e3dAj_YOivVGBzu smRuOg_BsGyD3bWKsS.ystRb00qkdD8OWLEzXn5M2vmEpcG_vXiOujMo_2FRQxNZwd3ozuWnsXxf U2Ar_RIj5gilXfV1uXA_hTdVTMvlqOEIl3K_Aq53F1cjxCCRlWbxlElCiShVzkoorluwmB.vdtE6 tucOsaL3Va3OBvuJ1Qv99d.XVWRxz.CpNtdItoWcMTdZ7vbU2x8H_21Gpq0eiKL2zKB0Ljl2f805 O.ThqnBx.WdEOOYKGUKx2IJg- Received: from sonic.gate.mail.ne1.yahoo.com by sonic314.consmr.mail.ne1.yahoo.com with HTTP; Tue, 2 Oct 2018 18:52:02 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.101]) ([76.115.7.162]) by smtp423.mail.ne1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID cdf23a586050e0a351dd32887e560bc7; Tue, 02 Oct 2018 18:52:00 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: Timeout poll on interrupt endpoint for RPI3 with keyboard and mouse From: Mark Millard In-Reply-To: <20181002203135.245edff2acfcbd8441d67cc3@bidouilliste.com> Date: Tue, 2 Oct 2018 11:51:58 -0700 Cc: bob prohaska , freebsd-arm@freebsd.org, Trevor Roydhouse Content-Transfer-Encoding: 7bit Message-Id: <296E5CCA-19D5-4C5C-A641-2E8899917556@yahoo.com> References: <20180929185213.GA58381@www.zefox.net> <20180930111208.5df04f5b7fb336cdfcf2fd74@bidouilliste.com> <20180930130930.GB58381@www.zefox.net> <20180930132928.GC58381@www.zefox.net> <20180930155055.2c35693431e8dfff4eb7d7bd@bidouilliste.com> <20180930145702.GD58381@www.zefox.net> <20181001022415.GA63212@www.zefox.net> <20181002203135.245edff2acfcbd8441d67cc3@bidouilliste.com> To: Emmanuel Vadot X-Mailer: Apple Mail (2.3445.9.1) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Oct 2018 18:52:09 -0000 On 2018-Oct-2, at 11:31 AM, Emmanuel Vadot wrote: > On Sun, 30 Sep 2018 19:24:16 -0700 > bob prohaska wrote: > >> On Mon, Oct 01, 2018 at 08:57:04AM +1000, Trevor Roydhouse wrote: >>> >>> You just need to change one character in the file >>> .../sys/arm64/include/pte.h - change the 4 to an 8 in this existing line: >>> >>> #define PMAP_MAPDEV_EARLY_SIZE (L2_SIZE * 4) >>> >> >> Ok, that wasn't hard 8-) >> >> The machine now boots with the monitor connected and continues to run >> correctly when keyboard and mouse are plugged in. >> >> With monitor, keyboard and mouse connected it still spits out a stream of >> Timeout poll on interrupt endpoint >> Timeout poll on interrupt endpoint >> .... >> during the boot process. The spew seems continuous, but when I typed >> boot >> into the spew, it looks as if the kernel took over and the machine is >> now multi-user. >> >> Evidently it got stuck in loader, the boot command got it unstuck and >> after that all is normal. >> >> So, I guess the video issue was a distraction that's now fixed. The >> problem with USB mouse and keyboard remain unresolved but nonfatal. > > So I've just tested ALPHA8 on my RPI3 and RPI3B+. > > With *just* keyboard and mouse plugged in I do not have any problem at > all. I could only have one plugged in without a problem, but it may depend on the specific devices. > If I plug a cheap usb stick, same, no problem. > But if I plug my Corsair Voyager USB3, u-boot is really slow to probe > usb devices. I didn't see the Timeout poll message but I didn't have > serial connected (I think it doesn't matter since u-boot send all > prints to every console). My separate report that listed various combinations was using a USB 3.0 capable powered hub when a hub was used and was using media readers/writers that are USB 3.0 capable (4 LUN's per reader/writer, 8 overall). I forgot to mention the USB-3.0-capable aspect at the time. It was so slow overall that it got: EFI: Watchdog timeout and only managed to boot a couple of times out of lots of tries. So I can confirm your observation is not limited to your context. > The RPI u-boot maintainer is aware that there is issue regarding USB > on RPI3B+, now he's aware that there is some on RPI3. > > I see in your mail that you have some usb harddrive or usb stick > plugged too, can you try without them ? I happen to have done such in my context already . . . One of my tests that got "Timeout poll on interrupt endpoint" messages had no USB devices plugged in other than the keyboard and mouse that I tried (not even the powered hub). It had the serial console and Ethernet plugged in but no HDMI. With just the USB 3.0 capable powered hub plugged in as far as USB goes, and the keyboard and mouse as the only devices on the hub, I still got the "Timeout poll on interrupt endpoint" messages. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-arm@freebsd.org Wed Oct 3 01:19:42 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 7503410B3683 for ; Wed, 3 Oct 2018 01:19:42 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E0F58848D9 for ; Wed, 3 Oct 2018 01:19:41 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w931JV5v085071 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 2 Oct 2018 18:19:32 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w931JUub085070; Tue, 2 Oct 2018 18:19:30 -0700 (PDT) (envelope-from fbsd) Date: Tue, 2 Oct 2018 18:19:30 -0700 From: bob prohaska To: Emmanuel Vadot Cc: Trevor Roydhouse , freebsd-arm@freebsd.org, Mark Millard , bob prohaska Subject: Re: Timeout poll on interrupt endpoint for RPI3 with keyboard and mouse Message-ID: <20181003011930.GA84788@www.zefox.net> References: <20180929185213.GA58381@www.zefox.net> <20180930111208.5df04f5b7fb336cdfcf2fd74@bidouilliste.com> <20180930130930.GB58381@www.zefox.net> <20180930132928.GC58381@www.zefox.net> <20180930155055.2c35693431e8dfff4eb7d7bd@bidouilliste.com> <20180930145702.GD58381@www.zefox.net> <20181001022415.GA63212@www.zefox.net> <20181002203135.245edff2acfcbd8441d67cc3@bidouilliste.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181002203135.245edff2acfcbd8441d67cc3@bidouilliste.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Oct 2018 01:19:42 -0000 On Tue, Oct 02, 2018 at 08:31:35PM +0200, Emmanuel Vadot wrote: > On Sun, 30 Sep 2018 19:24:16 -0700 > bob prohaska wrote: > > > On Mon, Oct 01, 2018 at 08:57:04AM +1000, Trevor Roydhouse wrote: > > > > > > You just need to change one character in the file > > > .../sys/arm64/include/pte.h - change the 4 to an 8 in this existing line: > > > > > > #define PMAP_MAPDEV_EARLY_SIZE (L2_SIZE * 4) > > > > > > > Ok, that wasn't hard 8-) > > > > The machine now boots with the monitor connected and continues to run > > correctly when keyboard and mouse are plugged in. > > > > With monitor, keyboard and mouse connected it still spits out a stream of > > Timeout poll on interrupt endpoint > > Timeout poll on interrupt endpoint > > .... > > during the boot process. The spew seems continuous, but when I typed > > boot > > into the spew, it looks as if the kernel took over and the machine is > > now multi-user. > > > > Evidently it got stuck in loader, the boot command got it unstuck and > > after that all is normal. > > > > So, I guess the video issue was a distraction that's now fixed. The > > problem with USB mouse and keyboard remain unresolved but nonfatal. > > So I've just tested ALPHA8 on my RPI3 and RPI3B+. > > With *just* keyboard and mouse plugged in I do not have any problem at > all. > If I plug a cheap usb stick, same, no problem. > But if I plug my Corsair Voyager USB3, u-boot is really slow to probe > usb devices. I didn't see the Timeout poll message but I didn't have > serial connected (I think it doesn't matter since u-boot send all > prints to every console). > The RPI u-boot maintainer is aware that there is issue regarding USB > on RPI3B+, now he's aware that there is some on RPI3. > > I see in your mail that you have some usb harddrive or usb stick > plugged too, can you try without them ? > There were two USB flash drives connected in my test, taking them out seems to have no effect on early boot behavior (up to the point the kernel starts). There is a streem of Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint and, without a manually-typed boot command the machine just sits, evidently in loader. In this setup, the Dell mouse was plugged into a USB port on the Dell keyboard, so apparently there's a hub inside the keyboard. When I unplugged the mouse from the keyboard and power cycled the Pi the Timeout poll.... messages were sparser but still present, and the kernel booted without manual intervention. Startup eventually failed because of the missing storage devices, which makes sense. It appears that in my case the keyboard alone is enough to make mischief. Next, an ALPHA8 image downloaded yesterday written to an identical microSD card (Sandisk Ultra Plus 16 GB) was tried, with monitor and keyboard only connected. Again, Timeout poll messages appeared, but it looks as if the machine again got stuck in loader. Typing boot seems to have started the kernel, but then it got stuck with Timeout poll on interrupt endpoint bootTimeout poll on interrupt endpoint Using DTB provided by EFI at 0x7ff7000. Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint EFI framebuffer information: addr, size 0x3e330000, 0x8ca000 dimensions 1920 x 1200 stride 1920 masks 0x00ff0000, 0x0000ff00, 0x000000ff, 0xff000000 panic: Too many early devmap mappings 2 cpuid = 0 time = 1 KDB: stack backtrace: #0 0xffff0000003cc644 at ??+0 #1 0xffff000000387e7c at ??+0 #2 0xffff000000387c28 at ??+0 #3 0xffff0000006e4884 at ??+0 #4 0xffff000000250c1c at ??+0 #5 0xffff00000025314c at ??+0 #6 0xffff00000032b800 at ??+0 #7 0xffff0000006a6108 at ??+0 Uptime: 1s In my case the keyboard seems to be the root of the trouble. It's a Dell model SK-8125, probably ten years old, bought from a University surplus store. As a final test, I unplugged the PL2303 USB-serial adapter which had been in place throughout (I'd forgotten about it). On reboot the video console emitted sporadic non-latin characters and didn't progress past loader, far as I can tell. Output on the Pi3's serial console turned to complete gobbldygook, mostly unprintable with a few latin characters sprinkled in. In complete confusion, I tried again with the ALPHA8 snapshot, same story. At wit's end, I again removed both USB flash drives, leaving only the keyboard connected: No mouse, no PL2303. Same story. Finally, I pulled the keyboard plug. Both microSD cards put on the video console Net: No Ethernet found Starting USB USB0: Scanning Bus 0......3 devices found Scanning for storage devices.....0 found Hit any key to stop autoboot: 0 U-boot> [unprintable] In the meantime a flood of non-ASCII characters came out of the serial console, interspersed with familiar text. That pulling the PL2303 made matters worse was a real shock. Putting it back repeated former behavior, stopping with panic: Too many early devmap mappings 2` so it's not a fluke. If there is something you'd like me to try please let me know. Thanks for reading, apologies for the convoluted story! bob prohaska From owner-freebsd-arm@freebsd.org Wed Oct 3 03:49:41 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 1368910B6AD5 for ; Wed, 3 Oct 2018 03:49:41 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic310-15.consmr.mail.bf2.yahoo.com (sonic310-15.consmr.mail.bf2.yahoo.com [74.6.135.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A07698A50E for ; Wed, 3 Oct 2018 03:49:40 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: fUO8xTMVM1mFyI6gifKASkOtVuSntNfi1o8phUPwqMNWE2N3SvjTo5p7VEsczLt U1vRlUvgDRrk3mWRQN7xh4e2nXWfy3nd2FT32mnnu_YXg_U0Wjoz.jVQTWBDGiZluBVBxjFdesB2 kdd8QkSufEjx7HjOKSfBti7i7Aq4TW1WoFpoe9IVfhFnw1KF70hy_diKf7Imdfget4Gr1Yc6vLpv kUwGeo0SUDLSbIO70eWDWtscc4AULNe1QzKGbRIZxfTBvf69hZ0bKVe_XmxroxJp58fTFsSdtJQi UPlF1Fhfk8U8EFZupZTALtcudb9Ce5qgl8a5W7SklCv_9JGAUY4.0eqqtLaK.9I59xZ6WxI21sYi O4i1V_LDl3RRFOBsOp5PmWIgPkRn7Ko9M0D0CHENWe2.X7r9uACeWLJWH4M_wp8G2FkKEMyQ21wE eHnE18TfwLLFT3c3ZlZYwKQ91yhGklKYcPhEwdZ3roacQ.5xznDz3P7ralk6MsH.B9JsNgt19eix fCDFJrjikx5OMb.89xcOP8lRYAmOpdMRZwmYznM2QKJ7NvuUcr_00vf4nFADDkQAJrDVjZh.44ui r9hOyzzMNUkk9YW9bN0eoqVUnG6xTA2h6XgCSmyMwJlZsguIktRlJyKQYTQTOv3NeqfeH.meF82E _pn9Ie7iXjPMl.z0QQyATBh24ETbRMuWnqITTikmdhDZR3zBsKLy5jgiBUhCsXicyBg.uc4K2EVv 6RarbCKej3PJSm1MzJhnrLoau52iytDvMXZt.K2pqZERcdnDY0Q14TyQAtABZCsT6TRieuITJ1BZ YJX2BOIKyoSZJe5fA4HdGSeP658l2LPUif0P9ZS68J1FJmHMZW5iOuSIzmeYiKj.P4pVfCQLYpbr VwT8_56HaaBnpL18uuuHL8NTt0FCMhfG3i02Y1CJQRnqYbfF.O1Anq7jYfGshv3NZUDMuHN5uk17 pr.pqohu.Swm688jRTA.9XbXTuc3CV7_hGWdWVCK2L6EsYx_Ns7gmE36xKRes9K5lHyv62pEKeIn Frq1._bTZ6F8z1TcW0T7m6wyy1UhMAdQR27urFVEJuGkmrR6RORB8nw-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic310.consmr.mail.bf2.yahoo.com with HTTP; Wed, 3 Oct 2018 03:49:33 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.101]) ([76.115.7.162]) by smtp410.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID edbff90acf7148a887ae370b214fffca; Wed, 03 Oct 2018 03:49:31 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: FYI: head -r338341 on Pine64+ 2GB early "KLD file umodem.ko is missing dependencies" but later manual kldload works From: Mark Millard In-Reply-To: <20180831175007.GU45503@funkthat.com> Date: Tue, 2 Oct 2018 20:49:28 -0700 Cc: Ian Lepore , freebsd-arm Content-Transfer-Encoding: quoted-printable Message-Id: <14A39642-0BF6-4005-A4E1-C95384EAD0AB@yahoo.com> References: <1535556653.33841.29.camel@freebsd.org> <20180831175007.GU45503@funkthat.com> To: John-Mark Gurney X-Mailer: Apple Mail (2.3445.9.1) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Oct 2018 03:49:41 -0000 On 2018-Aug-31, at 10:50 AM, John-Mark Gurney = wrote: Ian Lepore wrote this message on Wed, Aug 29, 2018 at 09:30 -0600: > On Tue, 2018-08-28 at 22:53 -0700, Mark Millard via freebsd-arm wrote: >> Loading kernel... >> /boot/kernel/kernel text=3D0x8d4607 data=3D0x176e78+0x79d254 >> syms=3D[0x8+0x11f670+0x8+0x112dd8] >> Loading configured modules... >> /boot/entropy size=3D0x1000 >> /boot/kernel/umodem.ko text=3D0x2168 text=3D0x1410 = data=3D0x102d0+0xfd40 >> syms=3D[0x8+0xf30+0x8+0xb73] >> Using DTB provided by EFI at 0x47ff9000. >> Loading DTB overlays: 'sun50i-a64-sid,sun50i-a64-ths,sun50i-a64- >> timer' >> /boot/dtb/overlays/sun50i-a64-sid.dtbo size=3D0x1fd >> /boot/dtb/overlays/sun50i-a64-ths.dtbo size=3D0x3e8 >> /boot/dtb/overlays/sun50i-a64-timer.dtbo size=3D0x175 >> applying DTB overlay '/boot/dtb/overlays/sun50i-a64-sid.dtbo' >> applying DTB overlay '/boot/dtb/overlays/sun50i-a64-ths.dtbo' >> applying DTB overlay '/boot/dtb/overlays/sun50i-a64-timer.dtbo' >> EHCI failed to shut down host controller. >> ---<>--- >> KDB: debugger backends: ddb >> KDB: current backend: ddb >> Copyright (c) 1992-2018 The FreeBSD Project. >> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, >> 1994 >> The Regents of the University of California. All rights >> reserved. >> FreeBSD is a registered trademark of The FreeBSD Foundation. >> FreeBSD 12.0-ALPHA3 r338341M arm64 >> FreeBSD clang version 6.0.1 (tags/RELEASE_601/final 335540) (based on >> LLVM 6.0.1) >> VT: init without driver. >> KLD file umodem.ko is missing dependencies >> . . . >>=20 . . . >> But after login: >>=20 >> # kldstat >> Id Refs Address Size Name >> 1 1 0xffff000000000000 141bba8 kernel >> # kldload umodem.ko >> # kldstat >> Id Refs Address Size Name >> 1 6 0xffff000000000000 141bba8 kernel >> 2 1 0xffff00005d000000 41000 umodem.ko >> 3 1 0xffff00005d041000 41000 ucom.ko I finally have access to the BPI-M3 (armv7/cortexA7) again and I updated it from something in the range -r333??? . The BPI-M3 did not have this problem: QUOTE Loading kernel... /boot/kernel/kernel text=3D0x889d68 data=3D0xad8e0+0x1f79a0 = syms=3D[0x4+0xa6630+0x4+0x108bbf] Loading configured modules... /boot/kernel/umodem.ko text=3D0x1550 text=3D0xf30 data=3D0x1080+0xf84 = syms=3D[0x4+0xe90+0x4+0xa7e] loading required module 'ucom' /boot/kernel/ucom.ko text=3D0x174c text=3D0x2a30 data=3D0x1080+0x17b8 = syms=3D[0x4+0x13e0+0x4+0xbac] /boot/entropy size=3D0x1000 Hit [Enter] to boot immediately, or any other key for command prompt. END QUOTE The problem with loading ucom as a required module while loading the kernel seems to be aarch64 specific in some way. The same range of text for the Pine64+ 2GB (aarch64/cortexA53) shows no reference to ucom.ko : QUOTE Loading kernel... /boot/kernel/kernel text=3D0x8d5063 data=3D0x1770f8+0x79d454 = syms=3D[0x8+0x11f790+0x8+0x112f2c] Loading configured modules... /boot/entropy size=3D0x1000 /boot/kernel/umodem.ko text=3D0x2168 text=3D0x1410 data=3D0x102d0+0xfd40 = syms=3D[0x8+0xf30+0x8+0xb73] Hit [Enter] to boot immediately, or any other key for command prompt. END QUOTE The builds for the above are both based on -r339076 (cross builds from the same amd64 host using the same /usr/src/ tree content as the host). =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-arm@freebsd.org Wed Oct 3 13:19:34 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 5ED5B10C2D70 for ; Wed, 3 Oct 2018 13:19:34 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it1-x12d.google.com (mail-it1-x12d.google.com [IPv6:2607:f8b0:4864:20::12d]) (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 EBD267A2E4 for ; Wed, 3 Oct 2018 13:19:33 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it1-x12d.google.com with SMTP id c23-v6so8216080itd.5 for ; Wed, 03 Oct 2018 06:19:33 -0700 (PDT) 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=QpfM/ciI2YaJB02hhgf8gsmRuWn3YvSm0YmMW5mgVvA=; b=fba2LH/J+EzQ+taJmkjqLHwKHELyGAZhBuCGMD90VGB/Qv8BHwDjK+rvGHWqthrKOg AfERjW/wUhdv7a2Abn5C/r3HEnOJhc/GrH91BogEocwWq378G98SZwfTkhiv0ADvr7m/ Kp1yYtOA3fNUJ2kZYHnXQQQv81poNwABB9ovovfZEvlipkPD233udGwh93wdoyLJbgxk KIXHTT3ZuF5tsHgbGHZWPd1JZWdgveMi7orPdJ5I8U+KWk7RiFvHWqHuxGHgB1q/tEsT Pi2HRj3AWRJZ4nMhKu5/ftz5ce5XEO/K1bnTRrl5CuouVJxAjRwlAEMnUjRrP2Wt04XZ 9MOg== 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=QpfM/ciI2YaJB02hhgf8gsmRuWn3YvSm0YmMW5mgVvA=; b=Xk72AchWHR//V7G2tS+xyAfMZK8boi/h8dZlC+0zgYJikTfDew7hUYGc2+VCB+xXt4 stKyO9riPKDON6jFVoPedudifd1yNBkgRKWSzoZGS2OvCWAbIjTRedHLnvGsHnWu0Kqp FzDr0onvIf7zEk2wNVTuch/z5JgykHx+cD/ROX3rHfXarOMnLut5qbMPGKzP/syxUvMJ xD6ym+RX3z3RJXJUvAzgkdLVwvqKKgBjfyda2HDlkKagDOPJc+ygd6WUbi2mcGezTMYQ yfF0YMMZx4JvtzfchcjhDGyQHfer2clbvSg/JzcHZXTuLUFAJNdLNORNetb/1hclybbt I+AA== X-Gm-Message-State: ABuFfogO4jEDkuT0IZu/XpyXe7z63UWCZ/0B8RwSMU/oeGz9YGHnTQTi iywOlA4FiTgQDbhH1cADHJnwO7c+W5HBPTfw9mo1ig== X-Google-Smtp-Source: ACcGV61KhnA9dhE2yGsYp7UrBCbEVHnPdTFfFCiqa/ohNdPehpL2UzBLPfSpUr/omtIyNV/IhJS7hhZltEJed/mKPPk= X-Received: by 2002:a24:ac5:: with SMTP id 188-v6mr1167058itw.39.1538572772954; Wed, 03 Oct 2018 06:19:32 -0700 (PDT) MIME-Version: 1.0 References: <1535556653.33841.29.camel@freebsd.org> <20180831175007.GU45503@funkthat.com> <14A39642-0BF6-4005-A4E1-C95384EAD0AB@yahoo.com> In-Reply-To: <14A39642-0BF6-4005-A4E1-C95384EAD0AB@yahoo.com> From: Warner Losh Date: Wed, 3 Oct 2018 07:19:21 -0600 Message-ID: Subject: Re: FYI: head -r338341 on Pine64+ 2GB early "KLD file umodem.ko is missing dependencies" but later manual kldload works To: Mark Millard Cc: John-Mark Gurney , freebsd-arm@freebsd.org, Ian Lepore Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Oct 2018 13:19:34 -0000 Is loader.hints built in between the two attempts? Warner On Tue, Oct 2, 2018, 9:50 PM Mark Millard via freebsd-arm < freebsd-arm@freebsd.org> wrote: > On 2018-Aug-31, at 10:50 AM, John-Mark Gurney wrote: > > Ian Lepore wrote this message on Wed, Aug 29, 2018 at 09:30 -0600: > > On Tue, 2018-08-28 at 22:53 -0700, Mark Millard via freebsd-arm wrote: > >> Loading kernel... > >> /boot/kernel/kernel text=0x8d4607 data=0x176e78+0x79d254 > >> syms=[0x8+0x11f670+0x8+0x112dd8] > >> Loading configured modules... > >> /boot/entropy size=0x1000 > >> /boot/kernel/umodem.ko text=0x2168 text=0x1410 data=0x102d0+0xfd40 > >> syms=[0x8+0xf30+0x8+0xb73] > >> Using DTB provided by EFI at 0x47ff9000. > >> Loading DTB overlays: 'sun50i-a64-sid,sun50i-a64-ths,sun50i-a64- > >> timer' > >> /boot/dtb/overlays/sun50i-a64-sid.dtbo size=0x1fd > >> /boot/dtb/overlays/sun50i-a64-ths.dtbo size=0x3e8 > >> /boot/dtb/overlays/sun50i-a64-timer.dtbo size=0x175 > >> applying DTB overlay '/boot/dtb/overlays/sun50i-a64-sid.dtbo' > >> applying DTB overlay '/boot/dtb/overlays/sun50i-a64-ths.dtbo' > >> applying DTB overlay '/boot/dtb/overlays/sun50i-a64-timer.dtbo' > >> EHCI failed to shut down host controller. > >> ---<>--- > >> KDB: debugger backends: ddb > >> KDB: current backend: ddb > >> Copyright (c) 1992-2018 The FreeBSD Project. > >> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, > >> 1994 > >> The Regents of the University of California. All rights > >> reserved. > >> FreeBSD is a registered trademark of The FreeBSD Foundation. > >> FreeBSD 12.0-ALPHA3 r338341M arm64 > >> FreeBSD clang version 6.0.1 (tags/RELEASE_601/final 335540) (based on > >> LLVM 6.0.1) > >> VT: init without driver. > >> KLD file umodem.ko is missing dependencies > >> . . . > >> > . . . > >> But after login: > >> > >> # kldstat > >> Id Refs Address Size Name > >> 1 1 0xffff000000000000 141bba8 kernel > >> # kldload umodem.ko > >> # kldstat > >> Id Refs Address Size Name > >> 1 6 0xffff000000000000 141bba8 kernel > >> 2 1 0xffff00005d000000 41000 umodem.ko > >> 3 1 0xffff00005d041000 41000 ucom.ko > > I finally have access to the BPI-M3 (armv7/cortexA7) again and > I updated it from something in the range -r333??? . The BPI-M3 > did not have this problem: > > QUOTE > Loading kernel... > /boot/kernel/kernel text=0x889d68 data=0xad8e0+0x1f79a0 > syms=[0x4+0xa6630+0x4+0x108bbf] > Loading configured modules... > /boot/kernel/umodem.ko text=0x1550 text=0xf30 data=0x1080+0xf84 > syms=[0x4+0xe90+0x4+0xa7e] > loading required module 'ucom' > /boot/kernel/ucom.ko text=0x174c text=0x2a30 data=0x1080+0x17b8 > syms=[0x4+0x13e0+0x4+0xbac] > /boot/entropy size=0x1000 > > Hit [Enter] to boot immediately, or any other key for command prompt. > END QUOTE > > The problem with loading ucom as a required module while loading > the kernel seems to be aarch64 specific in some way. The same > range of text for the Pine64+ 2GB (aarch64/cortexA53) shows no > reference to ucom.ko : > > QUOTE > Loading kernel... > /boot/kernel/kernel text=0x8d5063 data=0x1770f8+0x79d454 > syms=[0x8+0x11f790+0x8+0x112f2c] > Loading configured modules... > /boot/entropy size=0x1000 > /boot/kernel/umodem.ko text=0x2168 text=0x1410 data=0x102d0+0xfd40 > syms=[0x8+0xf30+0x8+0xb73] > > Hit [Enter] to boot immediately, or any other key for command prompt. > END QUOTE > > The builds for the above are both based on -r339076 (cross builds from > the same amd64 host using the same /usr/src/ tree content as the host). > > > === > Mark Millard > marklmi at yahoo.com > ( dsl-only.net went > away in early 2018-Mar) > > _______________________________________________ > 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 Oct 3 13:39:30 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 609D910C351F for ; Wed, 3 Oct 2018 13:39:30 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic304-22.consmr.mail.gq1.yahoo.com (sonic304-22.consmr.mail.gq1.yahoo.com [98.137.68.203]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D8B6E7ACFC for ; Wed, 3 Oct 2018 13:39:29 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: CqgC4mYVM1nFGiZJvgSXIR3qFjhf6mDByhGn0HccpjKbnjjQzdlcxKLzVjTcXA1 uz0obB9vqa0w7Madgqlv172IHUt.lsKwpyhk_gcuNsDUeRoPU7fTXAlo1jDRG_0gxMss_dBIfMAb TemAa_FupLKyph4VWDa9a5nwk5C_j9wHQflJ_aVsu39yzQKpyHVv5djpFpmeCcvnUTCM4DNgD5sS v7SQAuj4MUXQ8jdmZOenS.zItkc8jG85frsqjVU1czwMkbCaVPkWWGM8tMSWOZcVbLiJ3jZwa5dC NIydFLaTqp4ScjBOAtkIX40vwz9VL3kVLgX56Io_OtCRPGC1HV_Mfnr8MBgDotD3md..h7aKqvrz KkQmure4PY5SFu5cdoZZvGQ0jFvc7Vj.kOEw2AfmGNr1g1n0RRjgL6O.UE9fJNz5mElrqhFfQsd1 NF5R9PVewyLX2o6uOZ.09OqrslfTcrgEJGd0Zmwc1cGLalfiN_qk0C9fkrytubOwBnEo7BuNzYDh 2yQgYMGD1Ad40xkyNNBKWYkJa3uAcr_TBnfGIVACRWa1O0u2616aVape26iIs7FNd5RkAQZjtNkz EhCjEucl87dfElB.zzRWgKPzt7SFQUDQw8PRSGq_H0gvKDfHmLJGS1s0WYSje5pu36beKmCsZrai GgR5TvpM4OZjStztytWm159fEbWcyQnL1tp91wFmlatrm0cdVXANWHdFR4faS.iUF7ufYrFCXVnf rNWID4tPjBii2AVMP9j9rAau6wy_LAXqK7fAP7A3jnd.We5KfPA4ek1JXVJ4dXuyhkNkn9m88zwU LppcPBiYdO0u1TIDStRTgpVbG4I4.IfKA9ke5hnQVIfh3exaEKCgJXRox7uTBUG3etXbjQVLtQQi zkuEsdRj8MQTIxrshjTRr0YzGYsMqqNm2UPZfSVYFp48kRUHMTgm.1BH88cwAD7GWSFq1fZyRPpg f74u_yhyn8CPeldVBgqS6f7iqO1AHFyGfiTsJyhzymku9xfrIrI8UiVJgf1jF354unMWuDIO5iM5 eVrrOUkDpOW.F4umoa7RSdvwNTSgbqi6rs_eb65RQz1KsNEnydjYa Received: from sonic.gate.mail.ne1.yahoo.com by sonic304.consmr.mail.gq1.yahoo.com with HTTP; Wed, 3 Oct 2018 13:39:23 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.101]) ([76.115.7.162]) by smtp406.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 0c24ea9717da9723b69f727cea91e3bf; Wed, 03 Oct 2018 13:39:21 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: FYI: head -r338341 on Pine64+ 2GB early "KLD file umodem.ko is missing dependencies" but later manual kldload works From: Mark Millard In-Reply-To: Date: Wed, 3 Oct 2018 06:39:21 -0700 Cc: John-Mark Gurney , freebsd-arm@freebsd.org, Ian Lepore Content-Transfer-Encoding: quoted-printable Message-Id: <582715A9-01E1-4AA3-953E-3B3A7A8ED3C9@yahoo.com> References: <1535556653.33841.29.camel@freebsd.org> <20180831175007.GU45503@funkthat.com> <14A39642-0BF6-4005-A4E1-C95384EAD0AB@yahoo.com> To: Warner Losh X-Mailer: Apple Mail (2.3445.9.1) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Oct 2018 13:39:30 -0000 On 2018-Oct-3, at 6:19 AM, Warner Losh wrote: >=20 > Is loader.hints built in between the two attempts? linker.hints ? Both the BPI-M3 example and the Pine64+ 2GB example are with /boot/kernel/linker.hints already present before the boot used as the example for the specific board. BPI-M3 (which loads /boot/kernel/ucom.ko during load kernel): # ls -lTd /boot/kernel/linker.hints -rw-r--r-- 1 root wheel 216744 Oct 2 17:26:16 2018 = /boot/kernel/linker.hints Pine64+ 2GB (which does not): # ls -lTd /boot/kernel/linker.hints -rw-r--r-- 1 root wheel 245344 Oct 2 09:11:18 2018 = /boot/kernel/linker.hints The Pine64+ 2GB was updated to -r339076 before the BPI-M3 was. Note that after booting the Pine64+ 2GB: # kldload umodem.ko causes /boot/kernel/ucom.ko to load and the kldload completes successfully overall, as shown in the nested quoted material. > Warner >=20 > On Tue, Oct 2, 2018, 9:50 PM Mark Millard via freebsd-arm = wrote: > On 2018-Aug-31, at 10:50 AM, John-Mark Gurney = wrote: >=20 > Ian Lepore wrote this message on Wed, Aug 29, 2018 at 09:30 -0600: > > On Tue, 2018-08-28 at 22:53 -0700, Mark Millard via freebsd-arm = wrote: > >> Loading kernel... > >> /boot/kernel/kernel text=3D0x8d4607 data=3D0x176e78+0x79d254 > >> syms=3D[0x8+0x11f670+0x8+0x112dd8] > >> Loading configured modules... > >> /boot/entropy size=3D0x1000 > >> /boot/kernel/umodem.ko text=3D0x2168 text=3D0x1410 = data=3D0x102d0+0xfd40 > >> syms=3D[0x8+0xf30+0x8+0xb73] > >> Using DTB provided by EFI at 0x47ff9000. > >> Loading DTB overlays: 'sun50i-a64-sid,sun50i-a64-ths,sun50i-a64- > >> timer' > >> /boot/dtb/overlays/sun50i-a64-sid.dtbo size=3D0x1fd > >> /boot/dtb/overlays/sun50i-a64-ths.dtbo size=3D0x3e8 > >> /boot/dtb/overlays/sun50i-a64-timer.dtbo size=3D0x175 > >> applying DTB overlay '/boot/dtb/overlays/sun50i-a64-sid.dtbo' > >> applying DTB overlay '/boot/dtb/overlays/sun50i-a64-ths.dtbo' > >> applying DTB overlay '/boot/dtb/overlays/sun50i-a64-timer.dtbo' > >> EHCI failed to shut down host controller. > >> ---<>--- > >> KDB: debugger backends: ddb > >> KDB: current backend: ddb > >> Copyright (c) 1992-2018 The FreeBSD Project. > >> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, > >> 1994 > >> The Regents of the University of California. All rights > >> reserved. > >> FreeBSD is a registered trademark of The FreeBSD Foundation. > >> FreeBSD 12.0-ALPHA3 r338341M arm64 > >> FreeBSD clang version 6.0.1 (tags/RELEASE_601/final 335540) (based = on > >> LLVM 6.0.1) > >> VT: init without driver. > >> KLD file umodem.ko is missing dependencies > >> . . . > >>=20 > . . . > >> But after login: > >>=20 > >> # kldstat > >> Id Refs Address Size Name > >> 1 1 0xffff000000000000 141bba8 kernel > >> # kldload umodem.ko > >> # kldstat > >> Id Refs Address Size Name > >> 1 6 0xffff000000000000 141bba8 kernel > >> 2 1 0xffff00005d000000 41000 umodem.ko > >> 3 1 0xffff00005d041000 41000 ucom.ko >=20 > I finally have access to the BPI-M3 (armv7/cortexA7) again and > I updated it from something in the range -r333??? . The BPI-M3 > did not have this problem: >=20 > QUOTE > Loading kernel... > /boot/kernel/kernel text=3D0x889d68 data=3D0xad8e0+0x1f79a0 = syms=3D[0x4+0xa6630+0x4+0x108bbf] > Loading configured modules... > /boot/kernel/umodem.ko text=3D0x1550 text=3D0xf30 data=3D0x1080+0xf84 = syms=3D[0x4+0xe90+0x4+0xa7e] > loading required module 'ucom' > /boot/kernel/ucom.ko text=3D0x174c text=3D0x2a30 data=3D0x1080+0x17b8 = syms=3D[0x4+0x13e0+0x4+0xbac] > /boot/entropy size=3D0x1000 >=20 > Hit [Enter] to boot immediately, or any other key for command prompt. > END QUOTE >=20 > The problem with loading ucom as a required module while loading > the kernel seems to be aarch64 specific in some way. The same > range of text for the Pine64+ 2GB (aarch64/cortexA53) shows no > reference to ucom.ko : >=20 > QUOTE > Loading kernel... > /boot/kernel/kernel text=3D0x8d5063 data=3D0x1770f8+0x79d454 = syms=3D[0x8+0x11f790+0x8+0x112f2c] > Loading configured modules... > /boot/entropy size=3D0x1000 > /boot/kernel/umodem.ko text=3D0x2168 text=3D0x1410 data=3D0x102d0+0xfd40= syms=3D[0x8+0xf30+0x8+0xb73] >=20 > Hit [Enter] to boot immediately, or any other key for command prompt. > END QUOTE >=20 > The builds for the above are both based on -r339076 (cross builds from > the same amd64 host using the same /usr/src/ tree content as the = host). =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-arm@freebsd.org Wed Oct 3 17:36:28 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 F322510A8110 for ; Wed, 3 Oct 2018 17:36:27 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CF18287D5A for ; Wed, 3 Oct 2018 17:36:24 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w93HZkgG088196 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 3 Oct 2018 10:35:48 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w93HZdAV088195; Wed, 3 Oct 2018 10:35:39 -0700 (PDT) (envelope-from fbsd) Date: Wed, 3 Oct 2018 10:35:37 -0700 From: bob prohaska To: Emmanuel Vadot Cc: Trevor Roydhouse , freebsd-arm@freebsd.org, Mark Millard , bob prohaska Subject: Re: Timeout poll on interrupt endpoint for RPI3 with keyboard and mouse Message-ID: <20181003173537.GB84788@www.zefox.net> References: <20180929185213.GA58381@www.zefox.net> <20180930111208.5df04f5b7fb336cdfcf2fd74@bidouilliste.com> <20180930130930.GB58381@www.zefox.net> <20180930132928.GC58381@www.zefox.net> <20180930155055.2c35693431e8dfff4eb7d7bd@bidouilliste.com> <20180930145702.GD58381@www.zefox.net> <20181001022415.GA63212@www.zefox.net> <20181002203135.245edff2acfcbd8441d67cc3@bidouilliste.com> <20181003011930.GA84788@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181003011930.GA84788@www.zefox.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Oct 2018 17:36:28 -0000 On Tue, Oct 02, 2018 at 06:19:30PM -0700, bob prohaska wrote: > > As a final test, I unplugged the PL2303 USB-serial adapter which > had been in place throughout (I'd forgotten about it). On reboot > the video console emitted sporadic non-latin characters and > didn't progress past loader, far as I can tell. > > Output on the Pi3's serial console turned to complete gobbldygook, > mostly unprintable with a few latin characters sprinkled in. > I'd forgotten that the PL2303's connector shell provided local ground for the serial console signals. The intention was to eliminate ground loops in the chain of serial connections. Using the ground pin next to the Pi3's UART pins restored normal serial console operation. Repeating the boot test with _only_ Dell keyboard/hub and mouse (no other USB devices and no monitor) connected repeated the former problem with ALPHA8: Type '?' for a list of commands, 'help' for more detailed help. OK ;21;150tTimeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint It looks like the system got to the loader and is stuck there. If I type "boot" just right (quickly, and perhaps at the right time) on the serial console the machine comes up to multi-user. If I unplug the mouse from the keyboard's hub and power-cycle the pattern repeats as with the mouse connected. The caps lock light on the USB keyboard does not seem active, evidently the keyboard isn't recognized at this point. With the Dell keyboard/hub connected the machine hasn't (this morning) booted past the loader. That's different from last night, likely attributable to the lack of grounding on the serial console signals. With a laptop-sized Mac-compatible keyboard (no hub) the machine comes up multi-user without error messages, recognizing the keyboard with ukbd0 on uhub1 ukbd0: on usbus0 kbd1 at ukbd0 Using a full size genuine Apple Mac keyboard with internal hub the machine boots without issue, reporting ugen0.4: at usbus0 uhub2 on uhub1 uhub2: on usbus0 uhub2: 3 ports with 2 removable, bus powered ugen0.5: at usbus0 ukbd0 on uhub2 ukbd0: on usbus0 kbd1 at ukbd0 Connecting an Amazon Essentials USB3.0 powered hub and power cycling reported no errors. Connecting the laptop-sized Mac-compatible keyboard (which worked on its own) to the hub and power cycling caused the console to report ue0: on smsc0 ue0: Ethernet address: b8:27:eb:ba:68:d5 ugen0.4: at usbus0 uhub2 on uhub1 uhub2: on usbus0 uhub2: 4 ports with 4 removable, self powered usb_alloc_device: set address 5 failed (USB_ERR_IOERROR, ignored) usbd_setup_device_desc: getting device descriptor at addr 5 failed, USB_ERR_IOERROR usbd_req_re_enumerate: addr=5, set address failed! (USB_ERR_IOERROR, ignored) Release APs...done It looks like hubs mixed with keyboards sometimes spell trouble, sometimes not. Apologies for the length, thanks for reading. bob prohaska From owner-freebsd-arm@freebsd.org Wed Oct 3 18:42:18 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 6EBC110AA178 for ; Wed, 3 Oct 2018 18:42:18 +0000 (UTC) (envelope-from pygr@sonic.net) Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0A9D38AAF3 for ; Wed, 3 Oct 2018 18:42:17 +0000 (UTC) (envelope-from pygr@sonic.net) Received: from [10.137.113.129] (108-169-4-40.dynamic.dsl.sonic.net [108.169.4.40] (may be forged)) (authenticated bits=0) by c.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id w93Ig8Oi004820 (version=TLSv1.2 cipher=DHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for ; Wed, 3 Oct 2018 11:42:09 -0700 From: glenn Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: ClearFog Base -- "status: no carrier" for mvneta1 Date: Wed, 3 Oct 2018 11:42:08 -0700 References: To: freebsd-arm@freebsd.org In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.3445.9.1) X-Sonic-CAuth: UmFuZG9tSVY/HvnM3/1TlAAT/cbaZENej1gbI7n1bwJIIEzUXQHX/OITTOWt07HXBG+KXKPsjxqcY+vvDcoxuCKqNSIf5zXb X-Sonic-ID: C;QPtzCDzH6BGIyoLirVfHYg== M;iCW2CDzH6BGIyoLirVfHYg== X-Spam-Flag: No X-Sonic-Spam-Details: 0.0/5.0 by cerberusd Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Oct 2018 18:42:18 -0000 Hi Luiz and Marcin, Thank you for taking an interest in this. I have looked into the problem further (Google is your friend) and made = progress. After modification of the u-boot source before build, the = message =E2=80=9Cstatus: no carrier=E2=80=9D for the second ethernet = port no longer appears . The recipe is detailed in the last post in this = thread: = http://forum.solid-run.com/linux-kernel-and-bootloaders-f34/port-light-is-= always-on-does-not-work-t3074.html = .=20 It was a surprise to me that modifying u-boot code affected the = functioning of the ethernet after control was passed to the OS. = Apparently some functionality that is built into u-boot continues to be = used by the OS. In addition to the changes in u-boot mentioned above, the = armada-388-clearfog-base.dts was edited to allow the serial console to = function. The second line in serial@12000 { compatible =3D "marvell,armada-38x-uart=E2=80=9D; was changed to=20 compatible =3D "snps,dw-apb-uart=E2=80=9D;=20 I=E2=80=99m thinking the reason that that enabled the serial console is = that FreeBSD doesn=E2=80=99t have a driver that responds to = "marvell,armada-38x-uart=E2=80=9D but does have one that responds to = "snps,dw-apb-uart=E2=80=9D. Glenn > Date: Tue, 2 Oct 2018 11:57:32 -0300 > From: Luiz Otavio O Souza > To: Marcin Wojtas > Cc: pygr@sonic.net, "freebsd-arm@freebsd.org" > > Subject: Re: ClearFog Base -- "status: no carrier" for mvneta1 > Message-ID: > = > Content-Type: text/plain; charset=3D"UTF-8" >=20 > On Tue, 2 Oct 2018 at 00:43, Marcin Wojtas wrote: >>=20 >> Hi Glenn, >>=20 >> I can see, that armada-388-clearfog-base.dts connects eth1 to a PHY = via MDIO. >> Unfortunately my Clearfog boards have the SFP cage connected only to >> the SGMII lanes only (no PHY). >>=20 >> Can you please try to boot with armada-388-clearfog.dts, where the = SFP >> cage is configured as the 'fixed-link' and let know? >=20 > I don't have the Clearfog Base here, but this board has the PHY1 reset > connected to GPIO pin 19, you probably want to check this too. >=20 > Luiz >=20 From owner-freebsd-arm@freebsd.org Wed Oct 3 19:09:23 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 44CEA10AAAB9 for ; Wed, 3 Oct 2018 19:09:23 +0000 (UTC) (envelope-from mw@semihalf.com) Received: from mail-io1-xd2b.google.com (mail-io1-xd2b.google.com [IPv6:2607:f8b0:4864:20::d2b]) (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 D89AE8B6DE for ; Wed, 3 Oct 2018 19:09:22 +0000 (UTC) (envelope-from mw@semihalf.com) Received: by mail-io1-xd2b.google.com with SMTP id w16-v6so5940236iom.7 for ; Wed, 03 Oct 2018 12:09:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=semihalf-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=JX0bxDlTrSkgPdugWGkGEzNshlGKnv5P6fejC87X+e8=; b=GemXpjtA5Qo7wklg8F2xrClu9fIUI9Wo5t2N+irTXH6p06+RIB0ugG7aARDviz5/Q8 Bg0RbFv8N8S16z9Mcg1uBv3goMqAowZp/8w7oNvH0gb9bLHFmHDKMIiWCxhxb7sjR1y2 FT+b/jFQGWWei0szQGfkdn5mUJobSmlvheZ0nDrmueOLRwBj6zi5ccIELh6LrheZ71hd 4dhKMoyIRUvjqzKQu/mH5y02EnGsucXMvaVT/AC1OU+QCxu9VYftsWV9prc98kODmCxG 2SL0enFA+9u0XwGNNGiAZZhO0xdvXXIrBbVe5ig5SSp/PEQnq7JmfNSHklWyXts+b7mh Ltow== 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:content-transfer-encoding; bh=JX0bxDlTrSkgPdugWGkGEzNshlGKnv5P6fejC87X+e8=; b=VDD4eNDAkmxf324Nc7ECTl5Ca8/Py/9ftcOIFEyx7UWG4Y0CU9aCJgwDpew99Dx4+3 3tZzd2gC0viNRAGqBssbfLtHVNprZ6E1/OWx/WUPtQiNlwnAIt9vLE1ynyqjZSi3S7Vp cYXWVDz2Ch3nBGOO9pXsUxpeJI8ClX/Xz57qcZcqkiwr/HU+nt3uxeW/Rc8bivturHBq bsDdHJkgONTVD9t77jm0+uHKlxp0CRyIWjQBiBaWio9FfKMuZscrmlwHAXUVIBmVaiX0 CuJXq6VyI5u473J8+6jrU/iDUOWFFpPqEP8358Q28USSxYlICmoh/+0PmP5qOGe/qUt8 65/A== X-Gm-Message-State: ABuFfoi3gF27y3nq9hoVUrf1KAooDjmY4LY+Cirbb/+UQQPgc2p6uDHv 6jqnnTd0qCkMDheWbDiGcfq/IjPv2Aj0dq8qS+OXpg== X-Google-Smtp-Source: ACcGV60IwbMa+13aavUg7ivsWZN/WkIh6surtOdpHwdkYkgTrauDxcmBEC4ixJPMVmHPrkZjFmc9V/Ri93BoaEvwYF4= X-Received: by 2002:a5e:c643:: with SMTP id s3-v6mr2163912ioo.108.1538593761996; Wed, 03 Oct 2018 12:09:21 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Marcin Wojtas Date: Wed, 3 Oct 2018 21:09:12 +0200 Message-ID: Subject: Re: ClearFog Base -- "status: no carrier" for mvneta1 To: pygr@sonic.net Cc: freebsd-arm Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Oct 2018 19:09:23 -0000 Hi Glenn , =C5=9Br., 3 pa=C5=BA 2018 o 20:42 glenn napisa=C5=82(a): > > Hi Luiz and Marcin, > > Thank you for taking an interest in this. > > I have looked into the problem further (Google is your friend) and made p= rogress. After modification of the u-boot source before build, the message = =E2=80=9Cstatus: no carrier=E2=80=9D for the second ethernet port no longer= appears . The recipe is detailed in the last post in this thread: http://f= orum.solid-run.com/linux-kernel-and-bootloaders-f34/port-light-is-always-on= -does-not-work-t3074.html . > > It was a surprise to me that modifying u-boot code affected the functioni= ng of the ethernet after control was passed to the OS. Apparently some func= tionality that is built into u-boot continues to be used by the OS. > Good catch. Yes, PHY initialization is supposed to be done in the bootloader, later the generic ukphy is used for handling the media status/update (no dedicated driver). > In addition to the changes in u-boot mentioned above, the armada-388-clea= rfog-base.dts was edited to allow the serial console to function. The secon= d line in > > serial@12000 { > compatible =3D "marvell,armada-38x-uart=E2=80=9D; > > was changed to > > compatible =3D "snps,dw-apb-uart=E2=80=9D; > > I=E2=80=99m thinking the reason that that enabled the serial console is t= hat FreeBSD doesn=E2=80=99t have a driver that responds to "marvell,armada-= 38x-uart=E2=80=9D but does have one that responds to "snps,dw-apb-uart=E2= =80=9D. I see it's a fairly fresh change in the mainline Linux, I hope I will manage to squeeze it to 12. Thanks, Marcin > > Glenn > > > Date: Tue, 2 Oct 2018 11:57:32 -0300 > > From: Luiz Otavio O Souza > > To: Marcin Wojtas > > Cc: pygr@sonic.net, "freebsd-arm@freebsd.org" > > > > Subject: Re: ClearFog Base -- "status: no carrier" for mvneta1 > > Message-ID: > > > > Content-Type: text/plain; charset=3D"UTF-8" > > > > On Tue, 2 Oct 2018 at 00:43, Marcin Wojtas wrote: > >> > >> Hi Glenn, > >> > >> I can see, that armada-388-clearfog-base.dts connects eth1 to a PHY vi= a MDIO. > >> Unfortunately my Clearfog boards have the SFP cage connected only to > >> the SGMII lanes only (no PHY). > >> > >> Can you please try to boot with armada-388-clearfog.dts, where the SFP > >> cage is configured as the 'fixed-link' and let know? > > > > I don't have the Clearfog Base here, but this board has the PHY1 reset > > connected to GPIO pin 19, you probably want to check this too. > > > > Luiz > > > > _______________________________________________ > 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 Oct 3 19:59:19 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 CA25D10ABBAB for ; Wed, 3 Oct 2018 19:59:19 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic304-12.consmr.mail.bf2.yahoo.com (sonic304-12.consmr.mail.bf2.yahoo.com [74.6.128.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 596A78CF6B for ; Wed, 3 Oct 2018 19:59:19 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: Y4MyGl0VM1kQ_y7Yg1GdgL5dm1bPwYCHikvKRpdLBQZ_qSy7wddHw3GirRchc1L b_Rq_A.WVPSTtWyuuIgu.mUxbUwdjDvsOA7j9haKBHrUopZCsLZy.BFISZAEnEUbU4V5O_GvJNiO GS8bJySJrDDrXqMku4vdnrBfjsmm0XaR377YiMIzupIO5IwNanNBK8sRcT19_iSjzW7UmfeqUh9T 9NOVqIIBC36ziR.29uYbK2SWqA2ymLkM8xfOceVqMgpaedUPAEEwfXanPc.TGGEbnVZQ2DxjOXts lOIrAtzFeo2G0k45WkjJG51YUt2Fr1Y7y3xyZBsdcDHSPABCqw3WU55gzdnjuyxNRjhzqzz0ih2T Wtu2t4JI.coqSuBgs9fQbLoHs8Tr8v4ndX78xXQDAsGTEn8P2XuInJAHQuabvpwOmAcMMons5G4o ak8ORgvTiqxW.gXTccXcAUjkAKjt.aQ3RzGfsRvQzElvk9OtHyYL85D0TPL6IaaOdN08W90TM3f7 a8WGr_8vBhWE1WdC.RMFVYjw6hOwD42hbyfJ7DATx1Jh.Z2r1l7igmaFX_1a741im8YlEAZuCalD IHed1l.MpVRfcxmf3HS9evQflr29AFLgBGFdK94yEGS.CyRSib3IN1yUJ6w6xT1zN1irdGKke1tC 3nmH9cCsdegRs_HnemXo2lc7U3vgisW9O3MnA3NKCcz52KmPBJ.hedOUaS2yf.Y.4Camzs2byXTY .X5NFCQP4g0KHNAJr9k31tAbLx1YSyJvUQAH_EAdTScd5p7_BpNj7cqT38xi.PJukdnro3aIuTcH 7HQmQix3EICy8u3rELjodp8eUeis1yvqKIVeX2Ek3q8VJq2BR65frveHrpuN8VuBv8Tae3c4axGJ aIMLLaShD5oLQIe1Im9wIWkfQCZF8hkcAaClkfXsb_ENvoFBbGTEm7HZoo7WgEatOIHqaBxKf8Ob dtnChfnM08REEAi1hJCaj236JcM3s5B7Vgeq2Y0abri2HJc8jC5SNZDLSyWZ9RP1iqCvPTUCravY nI4X8HGyKH4IYuup.5G4rCS8TGYuyGlMnyFG.Cg-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic304.consmr.mail.bf2.yahoo.com with HTTP; Wed, 3 Oct 2018 19:59:18 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.101]) ([76.115.7.162]) by smtp427.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID e667ad6857431554f960311e67e00465 for ; Wed, 03 Oct 2018 19:59:16 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Banana Pi M3 (armv7/CortexA7) with head -339076 and u-boot 2018.09_3 from ports: what CPU clock speed is it using? More. . . Message-Id: <5B9D79C7-306E-45E0-9311-DDA0CC70C4A5@yahoo.com> Date: Wed, 3 Oct 2018 12:59:13 -0700 To: freebsd-arm X-Mailer: Apple Mail (2.3445.9.1) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Oct 2018 19:59:20 -0000 The following leaves me wondering if the switch to linux based .dts files and related changes have also invalidated some "Supported devices" table entries in https://wiki.freebsd.org/FreeBSD/arm/Allwinner . For example: cpufreq / DVFS and/or Thermal for some columns. With -r308125 the BPi-M3 would -j4 or -j5 buildworld buildkernel for the src.conf settings that I use in about 9.5 hours. (From my 2016-Nov-05 list E-mail.) [The BPi-M3 has heat sinks, a case, and a fan.] I've not done such builds in a long time and I've not recorded times when I have. But having updated to -r339076 based and the modern 2018.09 u-boot context has the BPi-M3 just finished building lib/clang/libclang/AST/ materials after about 19 hours. top indicates swap has 1740M Total and Free. (My top modifications indicate the Max Observed Active Mem as 922M so far.) There is a big difference in clang between the two and that contributes to taking more time. But, by contrast, the (aarch64 A64 based) Pine64+ 2GB -j4 buildworld buildkernel for -r338860 built completely in about 13.75 hours, although it had faster media in the microsd card slot (e.MMC on an adapter and used in DDR52 mode via experimental changes to allow e.MMC use). This leaves me wondering if the BPi-M3 clock rate(s) for the CPU and/or RAM are set avoiding the upper end of the range compared to -r308125's time frame. (This may well be reasonable currently.) Taking a guess at relevant figures from the modern BPi-M3 configuration via sysctl -a output: hw.clock.c1cpux.frequency: 1008000000 hw.clock.c0cpux.frequency: 1008000000 . . . hw.clock.pll_c1cpux.frequency: 1008000000 hw.clock.pll_c0cpux.frequency: 1008000000 (I've not figured out anything for DRAM: I ignored anything reported as 0 and bus-*.frequency figures.) If the current context is without throttling or some such, it may be that 1 GHz or so is used to just keep things in a safe range: I see no evidence of cpu or such temperatures in the sysctl -a output so a feedback loop controlling the frequency (and voltages) may not be an option currently for the BPi-M3. However, it is possible the frequency or other behavior is unexpected. I can not tell. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-arm@freebsd.org Thu Oct 4 11:04:19 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 B4A8810C8A92 for ; Thu, 4 Oct 2018 11:04:19 +0000 (UTC) (envelope-from vdemart@gmail.com) Received: from smtpcmd01217.aruba.it (smtpcmd01217.aruba.it [62.149.158.217]) by mx1.freebsd.org (Postfix) with ESMTP id E7A908FD99 for ; Thu, 4 Oct 2018 11:04:18 +0000 (UTC) (envelope-from vdemart@gmail.com) Received: from macbookvittorio.homenet.telecomitalia.it ([82.61.157.83]) by smtpcmd01.ad.aruba.it with bizsmtp id jP181y00h1oEWVe01P180n; Thu, 04 Oct 2018 13:01:08 +0200 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1283) Subject: Re: Booting the raspberry pi 2 from a usb hd (SOLVED) From: Victor In-Reply-To: Date: Thu, 4 Oct 2018 13:01:08 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: freebsd-arm@freebsd.org X-Mailer: Apple Mail (2.1283) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aruba.it; s=a1; t=1538650868; bh=tQ2nd4JJEO3zLK76sZ6C7y4nTsE5i5uT52WXnUBYIUM=; h=Content-Type:Mime-Version:Subject:From:Date:To; b=XmDNPvOBLYtMdVGupAN9ujMOM9Gjr2dA2knACmlZSV6hxQKWJqh6FPfXMCOZCbIXh 558asUzBlJV3s4B4ajdbLtcEAIzl//x+LSzi5OoZRmA0IwbXzHhGfDZV35VTA2/Q2K bRwj6E4zQhx3zT8ojLHp/phlsdcxBH98SNL+WoHiI3agpNAfPL88PTxByx6JK9N43t GfPb2ZNHUurRkqCj0e9EvFZkStI4T/W17rlvcZ26D5ThbuR7MbY5c3MzOCQnipgmA7 iyUiUeqdO+XwJsgTfK/7U4EnFN7CStlt6GuEKDVFVUFV1THkiDEwhClVXmdhSZDl6f I12g6SLZJMl4w== X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Oct 2018 11:04:19 -0000 Dear All, As I pointed out my problem is that I have a postgresql db on my pi2 = heavily operating in read/write mode and therefore I expect a quick = deterioration of the sd card. reading the very fragmented pieces of info on the problem and combining = them all in the end I found a solution for using a complete = FreeBSD-armv6-12.0-RPI2-310476 installation (I mean thee root = filesystem) on an external usb device connected to my raspberry pi 2. First of all I specify that the sd card MUST be in the raspberry for the = very first boot of FreeBSD because the dos programs involved read the = /etc/fstab and the various loader files from /dev/mmcsd0s2, that is on = the sd card itself.=20 This is the procedure to follow: 1) As usual copy the image of file into the sd card via dd which in my = Mac OS X is called /dev/disk1 sudo dd if =3D FreeBSD-armv6-12.0-RPI2-310476.img of=3D/dev/disk1 bs=3D1M = conv=3Dsync 2) Start the fresh installation of FreeBSD from the pi2 and verify what = the external drive is called. In my case /dev/da0. Therefore the root = filesystem will be in /dev/da0s2a. 3) Modify /etc/fstab in this way: #/etc/fstab # Custom /etc/fstab for FreeBSD embedded images #/dev/ufs/rootfs / ufs rw 1 1 /dev/da0s2a / ufs rw 1 1 /dev/msdosfs/MSDOSBOOT /boot/msdos msdosfs rw,noatime 0 0 tmpfs /tmp tmpfs rw,mode=3D1777,size=3D50m 0 0 4) Create - because in the stock image there is not such a file - a = loader.conf file under the /boot directory with the following content: #/boot/loader.conf #Allowance of some more time for the recognition of the usb devices kern.cam.boot_delay=3D10000=20 #Inform where the root filesystem is vfs.root.mountfrom=3D"ufs:/dev/da0s2a" 5) Halt FreeBSD remove the sd card and copy it onto the external usb = drive (/dev/disk2 on my Mac): =20 sudo dd if =3D /dev/disk1 of=3D/dev/disk2 bs=3D1M conv=3Dsync 6) Insert again the sd card and the usb drive in your pi2 and ....start Now you are using FreeBSD booted from the sd card but using the root = filesystem on your external drive for the heavy read/write work!=20 It works like a charm! Be careful. The external hard drive shouldn't be too demanding in terms = of electricity for the tiny raspberry. Do not use the "old" external = hard-disk but the new and more expensive ssd drives. Believe me, in = spite of the usb 2 the increase in speed is incredible. Ciao Vittorio =20 From owner-freebsd-arm@freebsd.org Thu Oct 4 13:26:28 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 4763D10AA784 for ; Thu, 4 Oct 2018 13:26:28 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BE12396981 for ; Thu, 4 Oct 2018 13:26:27 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id 4e7ad5d6; Thu, 4 Oct 2018 15:26:20 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=2T9uCdQeqtCNG+ua/PcSwPB1pko=; b=WCjIOR2Hy1dby6OE/ja8l+SIoeTn rjCeXDRvN9DACaqnMKM4M62icQjlJgxRCcHY1+ZJ5ydyxRSf8/FCP38isPL+b1Sy jopDB7FVJLCVKmxX9Ioi5jrzZwsMVnPoL9oUj7eUpeQUmzJLxM0Tddswcv28M4Mm ntJNX+hEOWr0hNo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=WaDOQMTPhkBiGeqfvfFvOR38nFkWFZo0HNNIxMXUwYdV8HuHb7SmNj7A Y26S6Gls+NDJ4+yO21VEcXDO05vFSaqV0hJUlxoMkZbUdHq8vtqAgs+c1OnGBUyl 87Pq7TGtmFPcPdQ830uo+qASj3cxqMqpwOj6a7BI6mnGRvJw5Hs= Received: from skull.home.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id ccaa803a TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Thu, 4 Oct 2018 15:26:20 +0200 (CEST) Date: Thu, 4 Oct 2018 15:26:19 +0200 From: Emmanuel Vadot To: Mark Millard Cc: Mark Millard via freebsd-arm Subject: Re: Banana Pi M3 (armv7/CortexA7) with head -339076 and u-boot 2018.09_3 from ports: what CPU clock speed is it using? More. . . Message-Id: <20181004152619.b9daf1e395f543aa1621acd9@bidouilliste.com> In-Reply-To: <5B9D79C7-306E-45E0-9311-DDA0CC70C4A5@yahoo.com> References: <5B9D79C7-306E-45E0-9311-DDA0CC70C4A5@yahoo.com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Oct 2018 13:26:28 -0000 Hi, On Wed, 3 Oct 2018 12:59:13 -0700 Mark Millard via freebsd-arm wrote: > The following leaves me wondering if the switch to linux > based .dts files and related changes have also invalidated > some "Supported devices" table entries in > https://wiki.freebsd.org/FreeBSD/arm/Allwinner . For > example: cpufreq / DVFS and/or Thermal for some columns. Not really, see below. > > With -r308125 the BPi-M3 would -j4 or -j5 buildworld buildkernel for the > src.conf settings that I use in about 9.5 hours. (From my 2016-Nov-05 > list E-mail.) > > [The BPi-M3 has heat sinks, a case, and a fan.] > > I've not done such builds in a long time and I've not recorded times > when I have. But having updated to -r339076 based and the modern > 2018.09 u-boot context has the BPi-M3 just finished building > lib/clang/libclang/AST/ materials after about 19 hours. top > indicates swap has 1740M Total and Free. (My top modifications > indicate the Max Observed Active Mem as 922M so far.) > > There is a big difference in clang between the two and that > contributes to taking more time. But, by contrast, the (aarch64 > A64 based) Pine64+ 2GB -j4 buildworld buildkernel for -r338860 > built completely in about 13.75 hours, although it had faster > media in the microsd card slot (e.MMC on an adapter and used > in DDR52 mode via experimental changes to allow e.MMC use). > > This leaves me wondering if the BPi-M3 clock rate(s) for the > CPU and/or RAM are set avoiding the upper end of the range > compared to -r308125's time frame. (This may well be reasonable > currently.) > > Taking a guess at relevant figures from the modern > BPi-M3 configuration via sysctl -a output: > > hw.clock.c1cpux.frequency: 1008000000 > hw.clock.c0cpux.frequency: 1008000000 > . . . > hw.clock.pll_c1cpux.frequency: 1008000000 > hw.clock.pll_c0cpux.frequency: 1008000000 > > (I've not figured out anything for DRAM: I ignored > anything reported as 0 and bus-*.frequency figures.) There must be something wrong with the DRAM clock since we switch to the new clock model, someone (tm) should fix this. > If the current context is without throttling or some > such, it may be that 1 GHz or so is used to just keep > things in a safe range: I see no evidence of cpu or such > temperatures in the sysctl -a output so a feedback loop > controlling the frequency (and voltages) may not be an > option currently for the BPi-M3. > > However, it is possible the frequency or other behavior > is unexpected. I can not tell. There is two problem for cpufreq on BanapiM3 1) The current DTS (from linux 4.18) doesn't have the regulator define for switching voltage, this is fixed in later version. 2) A83T is a multi cluster ARM cpu, and this cause problem when switching frequency, I don't know exactly what's happening but removing the other cluster from the dts and I don't have any problem switching frequency. set->dev okay cpu_get_pcpu thread_lock sched_prio sched_bind panic: acquiring blockable sleep lock with spinlock or critical section held (sleep mutex) pmap @ /usr/home/manu/Work/freebsd/freebsd.git/sys /arm/arm/pmap-v6.c:6496 cpuid = 0 time = 1538658865 KDB: stack backtrace: db_trace_self() at db_trace_self pc = 0xc05c8b38 lr = 0xc0075d14 (db_trace_self_wrapper+0x30) sp = 0xddbaa890 fp = 0xddbaa9a8 db_trace_self_wrapper() at db_trace_self_wrapper+0x30 pc = 0xc0075d14 lr = 0xc029d418 (vpanic+0x16c) sp = 0xddbaa9b0 fp = 0xddbaa9d0 r4 = 0x00000100 r5 = 0x00000001 r6 = 0xc06d9038 r7 = 0xc0a90fd8 vpanic() at vpanic+0x16c pc = 0xc029d418 lr = 0xc029d1f8 (doadump) sp = 0xddbaa9d8 fp = 0xddbaa9dc r4 = 0xc06b36e7 r5 = 0xc06d32a9 r6 = 0xc06c560d r7 = 0x00000000 r8 = 0x00001960 r9 = 0xc7086834 r10 = 0x00000000 doadump() at doadump pc = 0xc029d1f8 lr = 0xc0307c44 (witness_checkorder+0xcd0) sp = 0xddbaa9e4 fp = 0xddbaaa38 r4 = 0xc029d1f8 r5 = 0xddbaa9e4 witness_checkorder() at witness_checkorder+0xcd0 pc = 0xc0307c44 lr = 0xc02822d0 (__mtx_lock_flags+0xb4) sp = 0xddbaaa40 fp = 0xddbaaa68 r4 = 0x00000000 r5 = 0x00000000 r6 = 0xc7086844 r7 = 0x00000000 r8 = 0xc7086834 r9 = 0xc06c560d r10 = 0x00001960 __mtx_lock_flags() at __mtx_lock_flags+0xb4 pc = 0xc02822d0 lr = 0xc05e6148 (pmap_fault+0x74) sp = 0xddbaaa70 fp = 0xddbaaa90 r4 = 0x00000005 r5 = 0x00516564 r6 = 0x00000005 r7 = 0xc7086834 r8 = 0xc7086844 r9 = 0xc0b275e4 r10 = 0x00000000 pmap_fault() at pmap_fault+0x74 pc = 0xc05e6148 lr = 0xc05eaca8 (abort_handler+0x110) sp = 0xddbaaa98 fp = 0xddbaab28 r4 = 0x00000005 r5 = 0x00000000 r6 = 0x00000000 r7 = 0x00000005 r8 = 0x00000013 r9 = 0xddbaab30 r10 = 0x00516564 abort_handler() at abort_handler+0x110 pc = 0xc05eaca8 lr = 0xc05cb488 (exception_exit) sp = 0xddbaab30 fp = 0xddbaac00 r4 = 0x00516540 r5 = 0xc06ecb29 r6 = 0x0000007a r7 = 0x00000000 r8 = 0xdb200024 r9 = 0xdb200000 r10 = 0xdb44a000 exception_exit() at exception_exit pc = 0xc05cb488 lr = 0xc02449e4 (cf_set_method+0x5bc) sp = 0xddbaabc0 fp = 0xddbaac00 r0 = 0xdf0ae780 r1 = 0x00000001 r2 = 0xddbaaafc r3 = 0x00000000 r4 = 0x00516540 r5 = 0xc06ecb29 r6 = 0x0000007a r7 = 0x00000000 r8 = 0xdb200024 r9 = 0xdb200000 r10 = 0xdb44a000 r12 = 0x20000000 cf_set_method() at cf_set_method+0x5c0 pc = 0xc02449e8 lr = 0xc0245fa8 (cpufreq_curr_sysctl+0x21c) sp = 0xddbaac08 fp = 0xddbaac38 r4 = 0xc0891b64 r5 = 0x00000001 r6 = 0xdb200000 r7 = 0xc5362a80 r8 = 0x00002454 r9 = 0xdb200000 r10 = 0xc0891b7c cpufreq_curr_sysctl() at cpufreq_curr_sysctl+0x21c pc = 0xc0245fa8 lr = 0xc02ac594 (sysctl_root_handler_locked+0xd0) sp = 0xddbaac40 fp = 0xddbaac68 r4 = 0xc534f9c0 r5 = 0xc5345000 r6 = 0xddbaaccc r7 = 0xc0245d8c r8 = 0xddbaac7c r9 = 0x00000000 r10 = 0x00000000 sysctl_root_handler_locked() at sysctl_root_handler_locked+0xd0 pc = 0xc02ac594 lr = 0xc02abc64 (sysctl_root+0x21c) sp = 0xddbaac70 fp = 0xddbaacb8 r4 = 0x00000000 r5 = 0xc534f9c0 r6 = 0x00000000 r7 = 0xc5345000 r8 = 0xddbaac7c r9 = 0x00000000 r10 = 0xddbaaccc sysctl_root() at sysctl_root+0x21c pc = 0xc02abc64 lr = 0xc02ac260 (userland_sysctl+0x15c) sp = 0xddbaacc0 fp = 0xddbaad18 r4 = 0x00000004 r5 = 0xddbaad40 r6 = 0x00000000 r7 = 0x00000000 r8 = 0xddbaaccc r9 = 0xdf0ae780 r10 = 0x00000000 userland_sysctl() at userland_sysctl+0x15c pc = 0xc02ac260 lr = 0xc02ac0c0 (sys___sysctl+0x7c) sp = 0xddbaad20 fp = 0xddbaadb0 r4 = 0xdf0aea20 r5 = 0xdf0ae780 r6 = 0xddbaad3c r7 = 0x00000000 r8 = 0x00000000 r9 = 0xdf0ae780 r10 = 0xdf0aea18 sys___sysctl() at sys___sysctl+0x7c pc = 0xc02ac0c0 lr = 0xc05ea608 (swi_handler+0x294) sp = 0xddbaadb8 fp = 0xddbaae40 r4 = 0x20057008 r5 = 0xc08e9250 r6 = 0xde875390 r10 = 0xdf0aea18 swi_handler() at swi_handler+0x294 pc = 0xc05ea608 lr = 0xc05cb418 (swi_exit) sp = 0xddbaae48 fp = 0xbfbfd778 r4 = 0x20057008 r5 = 0x00000000 r6 = 0xbfbfe3a0 r7 = 0x000000ca r8 = 0x00000000 r9 = 0x00000000 r10 = 0x00000000 swi_exit() at swi_exit pc = 0xc05cb418 lr = 0xc05cb418 (swi_exit) sp = 0xddbaae48 fp = 0xbfbfd778 KDB: enter: panic [ thread pid 868 tid 100103 ] Stopped at kdb_enter+0x58: ldrb r15, [r15, r15, ror r15]! In the meantime you can use https://people.freebsd.org/~manu/sun8i-a83t-bananapi-m3.dtb This is the DTB from Linux 4.20 (or what 4.20 will be) with one of the cluster removed. Setting the freq with sysctl dev.cpu.0.freq=XXXX or using powerd works. Simply put it in the /dtb directory of the FAT partition. -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Thu Oct 4 16:47:37 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 604E010B2B83 for ; Thu, 4 Oct 2018 16:47:37 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic317-20.consmr.mail.gq1.yahoo.com (sonic317-20.consmr.mail.gq1.yahoo.com [98.137.66.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3EAC8794A0 for ; Thu, 4 Oct 2018 16:47:35 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: Q2r_ArYVM1m0ElaYmFHCwUFBPuG5d1m4wbktHaUrjtUIa.W9LHJmjYvYyqc8_e8 k30a0KLcvrRyD1tXT1L1jm41tGIUU46GwyCThn1VJnQdc8y3volmXWW0hP3cnYuJ7LI4NO9OhwQ6 zkeAZ10IERP1nUOi9ueeXnm6NnJ3CLmMJ0qRhp3R099ItvOfDT.Vl4xDrDuoTLw0shgME9ej79cV aqJRQ9wQh3eRlsouQWHo115u19hEgcgRQw16nbSUaCx0E1k4vu2hsL1JyGkm95TjrBxZZWP8qsdE 48OL8yeUyXLRMo.x0I3rdej9Xm8sDxGomBc8puB_KuT5NOxe72P.01BSUOgB7hCmsT8CSZ_2pfPg MM027wgUB3zme_8J67RXcm01Nc.N9rnWP49tY3_2EMTRJy2r.Hnry5DXSvgxTte3RIhtuyktrGfq d8wqeG1PUpDODA9Io2FI8gUrUzjJHY_rWqAw6iw87oKx49HryZUO.Upy.lpZZvU1cb2yR3XRCDgY y0k.4MTPK4ZnCe10ijxYfz694hpLfX4xni8j8thT0aahRzIxMvxC571WvZ3HtvPCJZM0aV3Sq64O z0OAOPcZCHmbNDVAABGRlLykFHGRC5F3FiUM3LPQUjxOs.9SROlqdxZoehDAxxfkgZHT4kCSTpHU 1Xbi8J6d7Zo4NUtbAGn8HA.knDb8HGjC2jijnjPKHWJ_hcHqGKGarj2ZmMKz66b4dAU6udxFcZAo .hDzFWJvXHUwA5JGVLjJdQRETtwUP_r_GsALlWOC6NremuMsTW0rPaiVZoJC.jFBMqh9o4EM3O6j 9tH1WhTvMm1kqy0Xp6cYwEeRGWIoaJbC1BV8hPlY0ez.L4RyafF48TBIglisCRbp4pXiJl25fG_t 9fgQZeM8AUtoWazS7dzFMJylskUWn84BjPmWqwctv_jRrgg4IxTzK_Pn3gVBPJR4nqPaaYaDl2eJ mmKws53cUDf4cYnr98OvVZY3ZatbLqcPbXM8VYXBWSBNwLPmi8gRtj0N76fgP8dHBGthoI9GRUfM erstrNMJeZwU0wsjSN8UzVWrny5uTUkuTzKW2ecYEdoF_5JOSAAJc8PHm_mxGk7.g Received: from sonic.gate.mail.ne1.yahoo.com by sonic317.consmr.mail.gq1.yahoo.com with HTTP; Thu, 4 Oct 2018 16:47:28 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.101]) ([76.115.7.162]) by smtp402.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID a7050f3e572fc241b8eee30157bb6ea2; Thu, 04 Oct 2018 16:47:25 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: Banana Pi M3 (armv7/CortexA7) with head -339076 and u-boot 2018.09_3 from ports: what CPU clock speed is it using? More. . . From: Mark Millard In-Reply-To: <20181004152619.b9daf1e395f543aa1621acd9@bidouilliste.com> Date: Thu, 4 Oct 2018 09:47:24 -0700 Cc: Mark Millard via freebsd-arm Content-Transfer-Encoding: quoted-printable Message-Id: References: <5B9D79C7-306E-45E0-9311-DDA0CC70C4A5@yahoo.com> <20181004152619.b9daf1e395f543aa1621acd9@bidouilliste.com> To: Emmanuel Vadot X-Mailer: Apple Mail (2.3445.9.1) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Oct 2018 16:47:37 -0000 On 2018-Oct-4, at 6:26 AM, Emmanuel Vadot = wrote: > Hi, >=20 > On Wed, 3 Oct 2018 12:59:13 -0700 > Mark Millard via freebsd-arm wrote: >=20 >> . . . >=20 >>=20 >> With -r308125 the BPi-M3 would -j4 or -j5 buildworld buildkernel for = the >> src.conf settings that I use in about 9.5 hours. (=46rom my = 2016-Nov-05 >> list E-mail.) >>=20 >> [The BPi-M3 has heat sinks, a case, and a fan.] >>=20 >> I've not done such builds in a long time and I've not recorded times >> when I have. But having updated to -r339076 based and the modern >> 2018.09 u-boot context has the BPi-M3 just finished building >> lib/clang/libclang/AST/ materials after about 19 hours. top >> indicates swap has 1740M Total and Free. (My top modifications >> indicate the Max Observed Active Mem as 922M so far.) FYI on how long it took and what was built: It took around 36 hours to complete the buildworld buildkernel --and that was for: make[1]: "/usr/src/Makefile.inc1" line 341: SYSTEM_COMPILER: Determined = that CC=3Dcc matches the source tree. Not bootstrapping a = cross-compiler. make[1]: "/usr/src/Makefile.inc1" line 346: SYSTEM_LINKER: Determined = that LD=3Dld matches the source tree. Not bootstrapping a cross-linker. but I currently build for cortexA53 based on WITH_CLANG_FULL=3D WITH_CLANG_EXTRAS=3D but WITHOUT_LLDB=3D WITHOUT_BINUTILS_BOOTSTRAP=3D WITHOUT_BINUTILS=3D and no GCC/GNUCXX. I'm implicitly using WITH_LLVM_TARGET_ALL=3D so far. >> . . . >=20 > There is two problem for cpufreq on BanapiM3 >=20 > 1) The current DTS (from linux 4.18) doesn't have the regulator define > for switching voltage, this is fixed in later version. > 2) A83T is a multi cluster ARM cpu, and this cause problem when > switching frequency, I don't know exactly what's happening but = removing > the other cluster from the dts and I don't have any problem switching > frequency. >=20 > . . . > In the meantime you can use > https://people.freebsd.org/~manu/sun8i-a83t-bananapi-m3.dtb >=20 > This is the DTB from Linux 4.20 (or what 4.20 will be) with one of the > cluster removed. Setting the freq with sysctl dev.cpu.0.freq=3DXXXX or > using powerd works. Simply put it in the /dtb directory of the FAT > partition. That file seems to have helped when put in the ufs /boot/dtb/ directory. When /etc/rc.conf sets powerd_enable=3D"YES" the boot then cleanly reports: Starting powerd. Thanks. FYI: I had not looked at it at the time but prior to this change it was reporting the following. It still is reporting this after the change. gpio1: mem 0x1f02c00-0x1f02fff irq 33 = on simplebus0 gpiobus1: on gpio1 axp8xx_pmu0: at addr 0x746 irq = 35 on iicbus0 axp8xx_pmu0: regulator_parse_ofw_stdparam: Missing regulator name axp8xx_pmu0: cannot attach regulator dldo2 axp8xx_pmu0: regulator_parse_ofw_stdparam: Missing regulator name axp8xx_pmu0: cannot attach regulator dldo4 axp8xx_pmu0: regulator_parse_ofw_stdparam: Missing regulator name axp8xx_pmu0: cannot attach regulator eldo1 axp8xx_pmu0: regulator_parse_ofw_stdparam: Missing regulator name axp8xx_pmu0: cannot attach regulator eldo2 axp8xx_pmu0: regulator_parse_ofw_stdparam: Missing regulator name axp8xx_pmu0: cannot attach regulator eldo3 Putting your sun8i-a83t-bananapi-m3.dtb on just the msdosfs parition in a dtb directory and rebooting did not change the behavior. For example there was no: dev.cpu.0.freq_levels: 1200/-1 1128/-1 1008/-1 912/-1 864/-1 720/-1 = 600/-1 480/-1 But instead replacing the file in the ufs /boot/dtb/ did create such on the next boot. That is consistent with the what the boot text reports for where it gets the file: Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel]... =20 /boot/dtb/sun8i-a83t-bananapi-m3.dtb size=3D0x702a Loaded DTB from file 'sun8i-a83t-bananapi-m3.dtb'. (Not /boot/msdos/dtb/ .) If some stage before the kernel needs that .dtb I still may not have copies in all the correct places or other such issues. I still do not find thermal/temperature material in the sysctl -a output. (I'd guess that this is expected.) Whatever the details, the BPi-M3 is operational and I no longer have my old hacks involved (that were from the transition period). It is nice to get rid of them. Thanks again for the improvements. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-arm@freebsd.org Fri Oct 5 18:30:50 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 C94BE10B3643 for ; Fri, 5 Oct 2018 18:30:50 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic315-8.consmr.mail.gq1.yahoo.com (sonic315-8.consmr.mail.gq1.yahoo.com [98.137.65.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 35A9E8C03B for ; Fri, 5 Oct 2018 18:30:50 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: FR5fcJsVM1lrJvko490WLemMvA0.bmKYC5HRXizVtGkQKa53KR0CnrSgjlKZKvE smXl4NjUK6hpRsoRUEfuTFZxz1keUvt1xzTxyBj1LDfyU4U2IOzEAeq.rHuL1jTfx8NR5MAvuVPV eCuijYAuqclxGzbVvvj3KLVabjPgMVWRRM2vTNq3eHqDg6GNoFPZQdf7LR_q0EuDxegyAYV1rrK3 nIYzsYEDjmofF1h_01._sunMih0dUFiPOCUKR.DqeCBRd.7o3lVlsaZ6EYQeDaHjFEriFhZZ8uou gv7wAu1abVOyR_O8bk0RSqWayIg76dYTCcqZ.HBdGXEycJND0ybgywJyNzXarw9mwo3ks1zhfPY5 ZtmV15JTx_GlwFSEnU.cyrbcUEUJ4PsiY2I6_mfh6tSmrGOtqPiM90oNv1YMDwkaELO4aid2tAq2 uCOzaHdhDUZUorus3Fmx6W9sviRfFV3w_WEDvGq28GdDnFXPGzBOqsiJU21JcwjRBhjdORK3xb2f 5GFVolMPCERH36jgLXoaI6y_b6dxH0TdEhNmR3jai2t2zfZjr.CRGjkrLOvd89aw_66FJkFVAq1T 19VJHMg61psM3lZNjLaTez0s.YS9ZqKHGm2NJGS25rrbIZZPajYbedd6Gu0tOxmO4LJk1jXsj3SA FwE9jrIUJTs5voi5k06lfdZpCLzsj5Fn1PGsOIYJcrRwK1uU2SmUfVhhPiAHwKSg8dWrXiJ8uzaJ IAzrxNJAUAGd9ojVinMDTH0MpZhC_Zl5YkVhb7sdzUdPtLCcLgSsDhMKsVwfnofX.tMlZtLG3Oih T6DTLxMTn6jWt8786ZtDo8sFJF5AJWgaUXUEoYJKSvb0mVSnJnhMivGTl_r.oG_rxrN1d4CpLgLR lI39StGhNxfGsOdWP5kR7xVdJCGHbzKSvbmTAPSFafjdxaWRKLwm4ISIpmvhU_ncj.vfgumzQKrl AsA5aDOaQjtRMg.lpqWXe4z94w55oY_97JeYyLYyVwm0KxH80OxCF5G7scvWsno1alywUsHO5ME3 ooE2WyrSpvGmJ2yDbUr3Z5DRZ9Hj4jM.wuZsgMu4dCMY- Received: from sonic.gate.mail.ne1.yahoo.com by sonic315.consmr.mail.gq1.yahoo.com with HTTP; Fri, 5 Oct 2018 18:30:42 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.101]) ([76.115.7.162]) by smtp425.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID e393a882530828c8540234f2d1a23a05 for ; Fri, 05 Oct 2018 18:30:39 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: FYI: SoftIron Overdrive 1000 vs. Pine64+ 2GB buildworld buildkernel time examples (fairly modern head versions) Message-Id: <37BC2D1A-594A-425F-B4EB-1B1118B4B5B2@yahoo.com> Date: Fri, 5 Oct 2018 11:30:38 -0700 To: freebsd-arm X-Mailer: Apple Mail (2.3445.9.1) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Oct 2018 18:30:51 -0000 Self hosted (re-)build from scratch (empty build tree at start): SoftIron Overdrive 1000: a little under 3 hrs and 20 min Pine64+ 2GB: a little under 13 hrs and 45 min So somewhat more than a 10 hour difference and a factor of somewhat over 4 for total time. (I was testing the Overdrive and was curious. The Overdrive 1000 seems to be working fine.) Supporting context details (including the unusual storage) if you care . . . Both had: make[1]: "/usr/src/Makefile.inc1" line 341: SYSTEM_COMPILER: Determined = that CC=3Dcc matches the source tree. Not bootstrapping a = cross-compiler. make[1]: "/usr/src/Makefile.inc1" line 346: SYSTEM_LINKER: Determined = that LD=3Dld matches the source tree. Not bootstrapping a cross-linker. and: #WITH_CROSS_COMPILER=3D WITH_SYSTEM_COMPILER=3D WITH_SYSTEM_LINKER=3D # #CPUTYPE=3Dsoft WITH_LIBCPLUSPLUS=3D #WITH_LLD_BOOTSTRAP=3D WITHOUT_BINUTILS_BOOTSTRAP=3D WITH_ELFTOOLCHAIN_BOOTSTRAP=3D WITH_LLVM_TARGET_ALL=3D #WITH_CLANG_BOOTSTRAP=3D WITH_CLANG=3D WITH_CLANG_IS_CC=3D WITH_CLANG_FULL=3D WITH_CLANG_EXTRAS=3D WITH_LLD=3D WITH_LLD_IS_LD=3D WITHOUT_BINUTILS=3D WITH_LLDB=3D # WITH_BOOT=3D WITHOUT_LIB32=3D # WITHOUT_GCC_BOOTSTRAP=3D WITHOUT_GCC=3D WITHOUT_GCC_IS_CC=3D WITHOUT_GNUCXX=3D # NO_WERROR=3D #WERROR=3D MALLOC_PRODUCTION=3D Both were using: LDFLAGS.lld+=3D -Wl,--no-threads (via make.conf). Both were running non-debug builds (with symbols), including for the kernel. Both were building non-debug builds (with symbols). The file system is UFS with soft updates (no journaling) in both cases. File systems each is one partition. Trim enabled, vfs.ffs.dotrimcons=3D1 . fsck_ffs -E had been used in a prior boot in both cases. vm.pageout_oom_seq=3D120 was in use for both. (The default of 12 is not sufficient for the Pine64+ 2GB to complete buildworld buildkernel.) The Overdrive context was based on: CFLAGS.clang+=3D -mcpu=3Dcortex-a57 CXXFLAGS.clang+=3D -mcpu=3Dcortex-a57 CPPFLAGS.clang+=3D -mcpu=3Dcortex-a57 ACFLAGS.arm64cpuid.S+=3D -mcpu=3Dcortex-a57+crypto ACFLAGS.aesv8-armx.S+=3D -mcpu=3Dcortex-a57+crypto ACFLAGS.ghashv8-armx.S+=3D -mcpu=3Dcortex-a57+crypto and was a -r339076 context building itself. The Pine64+ 2GB context was based on: CFLAGS.clang+=3D -mcpu=3Dcortex-a53 CXXFLAGS.clang+=3D -mcpu=3Dcortex-a53 CPPFLAGS.clang+=3D -mcpu=3Dcortex-a53 ACFLAGS.arm64cpuid.S+=3D -mcpu=3Dcortex-a53+crypto ACFLAGS.aesv8-armx.S+=3D -mcpu=3Dcortex-a53+crypto ACFLAGS.ghashv8-armx.S+=3D -mcpu=3Dcortex-a53+crypto and was a -r338860 context building itself. (Some notes are from memory for this older build.) The Overdrive had the hard disk replaced by a SanDisk 860 Pro SSD (1TB). Around 95% of the space being free. It still had the original 8 GiByte RAM. 28 GiByte swap space on the same media. My modified version of top reported for the Overdrive: no observed use of swap. My modified version of top reported: Maximum Observed Active Mem 1627M. No observed use of Swap. The Pine64+ 2GB had a 128 GB e.MMC on a microsd adapter (used in DDR52 mode via local changes). Around 50% of the space being free. 3584M swap space on the same media. My modified version of top reported: Maximum Observed Active Mem 1501M. Maximum Observed Used Swap 198M. The Pine64+ 2GB does have a case, heat sinks, and a fan, but by no means equivalent to the Overdrive configuration. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-arm@freebsd.org Fri Oct 5 18:39:31 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 0CEE110B398A for ; Fri, 5 Oct 2018 18:39:31 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic315-13.consmr.mail.bf2.yahoo.com (sonic315-13.consmr.mail.bf2.yahoo.com [74.6.134.123]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9216F8C3DB for ; Fri, 5 Oct 2018 18:39:30 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: dcM.SFYVM1nGFy86yPomX.v0_7gW1XvCwnxZQ2X36.3814LXBzyWJVeHpKdzPwT 0u_DCLLx7UQNutzNnN6UaOHeJAtdO.JHnR81iHDqprpWIae30yIvJ08MpnB_OIfAACgIK_p.Dlom okEf4Yvds0bNHB5rc7j8Jtpj4q23hJgbPvFxiiTf16co9XJgio7KTi8ZRYnJvEjzWDBCOmfU2F_k .0bVG2j.lBot3IbNeZd0mxVLVsaPIXCgdmAcy1K5g75NXTZg3fI_kDQwTNvpjptopErPTqFxQErR pNPD_3b0XIasl0A6HSkcCjCRN2FNI.hqEkVDH_vlsDWSpKAyp7ZgrMACTchHiRZPKOTeKJRvb.AQ 66MTNaEKoF.2dyixbQ7coSYzgt5y6lHIO6x0MNr_0qKZE_J4RgFzoOv5muAIGuu2WJa6OiOOVK7S 1Yvhq1g2mktQOVYwlyWnt.Jfk38brxUUg5WlA4Wwccf8tvNVXdVoXNxAy4IXQJ8Adb0J9nIIDQzm VFtYmu.46kPudRRVklPoJxn.WyuRZSC0p_KnahaYTHL.GF7P1Y5YnrxMoT5O1_CR3fMxYh4zFjw. soalIFIw.D7qCasLodgTsMdneXZyqxYG4xy8hgnB7ssu1cN14aHSp3VI46XpKvHa21dcv1ZPRG5a oC3paEDK2HoK1jJYt0U8AQojXRew2j59ROWibIZ_ehcEmkQOXBcwC7FjYioHh07O2.lod2Zgvoav Zt6wtq0BKwi9q3SMjJSJKxO_8FcoJIL510jozT8JWywsQ97CrWo6TkiOkuyx7IrwvVXVVfBoAzrV y.JkwuoL_UslRL4olDaK5RiklWw2EQKSnqKNy8royOva5SpQVZLlV.vg4S4vPtGtd_aYxjT1zMh7 jCEB7RNiZzPa0N3X9_n_lZWmyivEVVqwJmJ8nYyzZRkq8FuZgQK1QveMKCWZG7KPEWOphXHJOu1z S1VDshOShztb.T1lxRkmCdBzDZjxVRKgZc0js4N8ZZWvYK5_7aXfQ5HjADTLpku150sZeFWCEEq_ WZZcB1U3dFMiLTYtSS6icWBTIo7_eA.vek.2UWJBtNpVg Received: from sonic.gate.mail.ne1.yahoo.com by sonic315.consmr.mail.bf2.yahoo.com with HTTP; Fri, 5 Oct 2018 18:39:24 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.101]) ([76.115.7.162]) by smtp430.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 45d2c9961ae194540de70a9ab553fbda for ; Fri, 05 Oct 2018 18:39:20 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: FYI: SoftIron Overdrive 1000 vs. Pine64+ 2GB buildworld buildkernel time examples (fairly modern head versions) Date: Fri, 5 Oct 2018 11:39:18 -0700 References: <37BC2D1A-594A-425F-B4EB-1B1118B4B5B2@yahoo.com> To: freebsd-arm In-Reply-To: <37BC2D1A-594A-425F-B4EB-1B1118B4B5B2@yahoo.com> Message-Id: <1E217216-4B31-4E52-9859-121A9E48D685@yahoo.com> X-Mailer: Apple Mail (2.3445.9.1) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Oct 2018 18:39:31 -0000 [I forgot to list the builds as -j4 builds in both examples.] On 2018-Oct-5, at 11:30 AM, Mark Millard wrote: > Self hosted (re-)build from scratch (empty build tree at start): >=20 > SoftIron Overdrive 1000: a little under 3 hrs and 20 min > Pine64+ 2GB: a little under 13 hrs and 45 min >=20 > So somewhat more than a 10 hour difference and a factor of > somewhat over 4 for total time. (I was testing the Overdrive > and was curious. The Overdrive 1000 seems to be working fine.) >=20 >=20 > Supporting context details (including the unusual storage) if > you care . . . >=20 > Both had: -j4 used to do the build. > make[1]: "/usr/src/Makefile.inc1" line 341: SYSTEM_COMPILER: = Determined that CC=3Dcc matches the source tree. Not bootstrapping a = cross-compiler. > make[1]: "/usr/src/Makefile.inc1" line 346: SYSTEM_LINKER: Determined = that LD=3Dld matches the source tree. Not bootstrapping a cross-linker. >=20 > and: >=20 > #WITH_CROSS_COMPILER=3D > WITH_SYSTEM_COMPILER=3D > WITH_SYSTEM_LINKER=3D > # > #CPUTYPE=3Dsoft > WITH_LIBCPLUSPLUS=3D > #WITH_LLD_BOOTSTRAP=3D > WITHOUT_BINUTILS_BOOTSTRAP=3D > WITH_ELFTOOLCHAIN_BOOTSTRAP=3D > WITH_LLVM_TARGET_ALL=3D > #WITH_CLANG_BOOTSTRAP=3D > WITH_CLANG=3D > WITH_CLANG_IS_CC=3D > WITH_CLANG_FULL=3D > WITH_CLANG_EXTRAS=3D > WITH_LLD=3D > WITH_LLD_IS_LD=3D > WITHOUT_BINUTILS=3D > WITH_LLDB=3D > # > WITH_BOOT=3D > WITHOUT_LIB32=3D > # > WITHOUT_GCC_BOOTSTRAP=3D > WITHOUT_GCC=3D > WITHOUT_GCC_IS_CC=3D > WITHOUT_GNUCXX=3D > # > NO_WERROR=3D > #WERROR=3D > MALLOC_PRODUCTION=3D >=20 > Both were using: LDFLAGS.lld+=3D -Wl,--no-threads > (via make.conf). >=20 > Both were running non-debug builds (with symbols), including > for the kernel. Both were building non-debug builds (with > symbols). >=20 > The file system is UFS with soft updates (no journaling) > in both cases. File systems each is one partition. Trim > enabled, vfs.ffs.dotrimcons=3D1 . fsck_ffs -E had been used > in a prior boot in both cases. >=20 > vm.pageout_oom_seq=3D120 was in use for both. (The default of > 12 is not sufficient for the Pine64+ 2GB to complete > buildworld buildkernel.) >=20 >=20 > The Overdrive context was based on: >=20 > CFLAGS.clang+=3D -mcpu=3Dcortex-a57 > CXXFLAGS.clang+=3D -mcpu=3Dcortex-a57 > CPPFLAGS.clang+=3D -mcpu=3Dcortex-a57 > ACFLAGS.arm64cpuid.S+=3D -mcpu=3Dcortex-a57+crypto > ACFLAGS.aesv8-armx.S+=3D -mcpu=3Dcortex-a57+crypto > ACFLAGS.ghashv8-armx.S+=3D -mcpu=3Dcortex-a57+crypto >=20 > and was a -r339076 context building itself. >=20 >=20 > The Pine64+ 2GB context was based on: >=20 > CFLAGS.clang+=3D -mcpu=3Dcortex-a53 > CXXFLAGS.clang+=3D -mcpu=3Dcortex-a53 > CPPFLAGS.clang+=3D -mcpu=3Dcortex-a53 > ACFLAGS.arm64cpuid.S+=3D -mcpu=3Dcortex-a53+crypto > ACFLAGS.aesv8-armx.S+=3D -mcpu=3Dcortex-a53+crypto > ACFLAGS.ghashv8-armx.S+=3D -mcpu=3Dcortex-a53+crypto >=20 > and was a -r338860 context building itself. (Some > notes are from memory for this older build.) >=20 >=20 > The Overdrive had the hard disk replaced by a SanDisk > 860 Pro SSD (1TB). Around 95% of the space being free. > It still had the original 8 GiByte RAM. 28 GiByte swap > space on the same media. >=20 > My modified version of top reported for the Overdrive: > no observed use of swap. >=20 > My modified version of top reported: > Maximum Observed Active Mem 1627M. > No observed use of Swap. >=20 >=20 > The Pine64+ 2GB had a 128 GB e.MMC on a microsd adapter > (used in DDR52 mode via local changes). Around 50% of > the space being free. 3584M swap space on the same media. >=20 > My modified version of top reported: > Maximum Observed Active Mem 1501M. > Maximum Observed Used Swap 198M. >=20 > The Pine64+ 2GB does have a case, heat sinks, and a fan, > but by no means equivalent to the Overdrive configuration. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)