From owner-freebsd-arm@freebsd.org Mon Dec 18 18:02:18 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 61BDEEA050E for ; Mon, 18 Dec 2017 18:02:18 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 44B4C67940 for ; Mon, 18 Dec 2017 18:02:17 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 90a30d4c-e41d-11e7-8486-0934409070aa X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.ore.mailhop.org (Halon) with ESMTPSA id 90a30d4c-e41d-11e7-8486-0934409070aa; Mon, 18 Dec 2017 18:02:09 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id vBII2FFv001684; Mon, 18 Dec 2017 11:02:15 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1513620135.95072.70.camel@freebsd.org> Subject: Re: RPI2 boot failure with recent changes to u-boot From: Ian Lepore To: Karl Denninger , freebsd-arm@freebsd.org Date: Mon, 18 Dec 2017 11:02:15 -0700 In-Reply-To: <4a2c96e1-b1bd-376f-34f5-e1f0163be2ba@denninger.net> References: <20ad35ef-2166-c429-fad6-21fedef1ff0e@denninger.net> <1513614709.95072.48.camel@freebsd.org> <401bad68-a6f4-ff9f-49e5-431c9441dde7@denninger.net> <4a2c96e1-b1bd-376f-34f5-e1f0163be2ba@denninger.net> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Dec 2017 18:02:18 -0000 On Mon, 2017-12-18 at 11:52 -0600, Karl Denninger wrote: > On 12/18/2017 11:25, Karl Denninger wrote: > > > > On 12/18/2017 10:31, Ian Lepore wrote: > > > > > > On Mon, 2017-12-18 at 10:24 -0600, Karl Denninger wrote: > > > > > > > > [...] > > > Back and forth with Ian a bit, added the dtb file declaration to > config.txt in the dos partition (and it's load address) and now the > kernel comes up but the disk device is missing, and thus the mount > fails..... > > Hit [Enter] to boot immediately, or any other key for command prompt. > Booting [/boot/kernel/kernel]... > Using DTB provided by U-Boot at address 0x100. > Kernel entry at 0x1200180... > Kernel args: (null) > Copyright (c) 1992-2017 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 >         The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 11.1-STABLE #0 r326933M: Mon Dec 18 11:14:31 CST 2017 >     > freebsd@NewFS.denninger.net:/pics/Crochet-work/obj/arm.armv6/pics/CrossBuild/src/sys/RPI2 > arm > FreeBSD clang version 5.0.0 (tags/RELEASE_500/final 312559) (based on > LLVM 5.0.0svn) > VT: init without driver. > CPU: ARM Cortex-A7 r0p5 (ECO: 0x00000000) > CPU Features: >   Multiprocessing, Thumb2, Security, Virtualization, Generic Timer, VMSAv7, >   PXN, LPAE, Coherent Walk > Optional instructions: >   SDIV/UDIV, UMULL, SMULL, SIMD(ext) > LoUU:2 LoC:3 LoUIS:2 > Cache level 1: >  32KB/64B 4-way data cache WB Read-Alloc Write-Alloc >  32KB/32B 2-way instruction cache Read-Alloc > Cache level 2: >  512KB/64B 8-way unified cache WB Read-Alloc Write-Alloc > real memory  = 994045952 (947 MB) > avail memory = 961916928 (917 MB) > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > random: entropy device external interface > kbd0 at kbdmux0 > ofwbus0: > simplebus0: mem 0x3f000000-0x3fffffff > on ofwbus0 > local_intc0: mem 0x40000000-0x400000ff on > simplebus0 > intc0: mem 0xb200-0xb3ff irq 4 on simplebus0 > generic_timer0: irq 0,1,2,3 on ofwbus0 > Timecounter "ARM MPCore Timecounter" frequency 19200000 Hz quality 1000 > Event timer "ARM MPCore Eventtimer" frequency 19200000 Hz quality 1000 > bcmwd0: mem 0x10001c-0x100027 on simplebus0 > gpio0: mem 0x200000-0x2000af irq 5,6,7,8 > on simplebus0 > gpio0: read-only pins: 46,48-53. > gpio0: reserved pins: 48-53. > gpiobus0: on gpio0 > gpioc0: on gpio0 > iichb0: mem 0x205000-0x20501f irq 9 on > simplebus0 > iichb1: mem 0x804000-0x80401f irq 10 on > simplebus0 > spi0: mem 0x204000-0x20401f irq 11 on > simplebus0 > spibus0: on spi0 > bcm_dma0: mem 0x7000-0x7fff,0xe05000-0xe05fff > irq 12,13,14,15,16,17,18,19,20,21,22,23,24 on simplebus0 > mbox0: mem 0xb880-0xb8bf irq 25 on simplebus0 > sdhci_bcm0: mem 0x300000-0x3000ff irq > 26 on simplebus0 Right here is where it turns strange, because the next line after sdhci_bcm0: should be this one: mmc0: on sdhci_bcm0 The only thing I can think of that would cause it to be missing is if "device mmc" is missing from the kernel config.  It's also available as a module, so you could try interrupting ubldr to get the prompt and do "load mmc". If that's not the problem, maybe the output from "boot -v" will have more clues. -- Ian > uart0: mem 0x201000-0x201fff irq 27 on simplebus0 > uart0: console (115200,n,8,1) > vchiq0: mem 0xb800-0xb84f irq 28 on simplebus0 > vchiq: local ver 8 (min 3), remote ver 8. > pcm0: on vchiq0 > bcm283x_dwcotg0: mem > 0x980000-0x99ffff irq 29 on simplebus0 > usbus0 on bcm283x_dwcotg0 > cpulist0: on ofwbus0 > cpu0: on cpulist0 > bcm2835_cpufreq0: on cpu0 > cpu1: on cpulist0 > cpu2: on cpulist0 > cpu3: on cpulist0 > fb0: on ofwbus0 > fbd0 on fb0 > VT: initialize with new VT driver "fb". > fb0: 656x416(656x416@0,0) 24bpp > fb0: fbswap: 1, pitch 1968, base 0x3eb33000, screen_size 818688 > gpioled0: on ofwbus0 > cryptosoft0: > Timecounters tick every 1.000 msec > iicbus0: on iichb0 > iic0: on iicbus0 > iicbus1: on iichb1 > iic1: on iicbus1 > usbus0: 480Mbps High Speed USB v2.0 > bcm2835_cpufreq0: ARM 600MHz, Core 250MHz, SDRAM 400MHz, Turbo OFF > ugen0.1: at usbus0 > uhub0: on usbus0 > Release APs > Trying to mount root from ufs:/dev/mmcsd0s2a [ro]... > Root mount waiting for: usbus0 > uhub0: 1 port with 1 removable, self powered > Root mount waiting for: usbus0 > ugen0.2: at usbus0 > uhub1 on uhub0 > uhub1: > on usbus0 > uhub1: MTT enabled > uhub1: 5 ports with 4 removable, self powered > Root mount waiting for: usbus0 > ugen0.3: at usbus0 > smsc0 on uhub1 > smsc0: on usbus0 > mountroot: waiting for device /dev/mmcsd0s2a... > smsc0: chip 0xec00, rev. 0002 > miibus0: on smsc0 > ukphy0: PHY 1 on miibus0 > ukphy0:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > ue0: on smsc0 > ue0: Ethernet address: b8:27:eb:be:e6:f8 > Mounting from ufs:/dev/mmcsd0s2a failed with error 19. > Trying to mount root from ufs:mmcsd0s2 []... > mountroot: waiting for device mmcsd0s2... > Mounting from ufs:mmcsd0s2 failed with error 19. > > Loader variables: >   vfs.root.mountfrom=ufs:/dev/mmcsd0s2a >   vfs.root.mountfrom.options=ro > > Manual root filesystem specification: >   : [options] >       Mount using filesystem >       and with the specified (optional) option list. > >     eg. ufs:/dev/da0s1a >         zfs:tank >         cd9660:/dev/cd0 ro >           (which is equivalent to: mount -t cd9660 -o ro /dev/cd0 /) > >   ?               List valid disk boot devices >   .               Yield 1 second (for background tasks) >       Abort manual input > > mountroot> ? > > List of GEOM managed disk devices: > > > mountroot> > >