Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 21 Jul 2019 12:31:32 -0600
From:      Ian Lepore <ian@freebsd.org>
To:        John-Mark Gurney <jmg@funkthat.com>, arm@FreeBSD.org
Subject:   Re: 13-CURRENT snapshot 20190718 r350103 doesn't boot on BeagleBone White
Message-ID:  <415c9b4760029235cd62bf95a35a736f7566cb9d.camel@freebsd.org>
In-Reply-To: <20190721180510.GQ2342@funkthat.com>
References:  <20190721180510.GQ2342@funkthat.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 2019-07-21 at 11:05 -0700, John-Mark Gurney wrote:
> The microSD card that I was using on my BeagleBone white got
> corrupted,
> so I decided to update to the latest version.  The latest snapshot
> fails
> to boot.  It loads the kernel, but then when starting the kernel, it
> hangs, and eventually it will reset.
> 
> The latest 12 snapshot boots fine: BEAGLEBONE-20190718-r350087.
> 
> Any ideas?  I tried all three available 13 snaps, and they all behave
> the same.
> 

This happened with the latest DTS import (which was months ago).  A
couple people have speculated that we just need a trivial do-nothing
driver for the new ti,sysc device, but when I tried that a couple
months ago it didn't work, so instead I just reverted sys/dts to the
old source and got on with what I needed to do.

This is just the latest in a years-long string of breakages because the
linux TI folks just never stop tinkering with their device-tree source.
I'm sure they're doing it because it gets them some benefits, but for
us the changes add no value and have a high maintenance cost.  A hang
before the copyright banner appears is especially painful to debug
(doubly so because there's no existing EARLY_PRINTF support in the ti
code).

- Ian

> The following is an example of the reset loop:
> Kernel entry at 0x84000180...
> Kernel args: (null)
> /
> U-Boot SPL 2019.04 (Jul 18 2019 - 04:19:33 +0000)
> Trying to boot from MMC1
> Loading Environment from FAT... *** Warning - bad CRC, using default
> environment
> 
> 
> 
> U-Boot 2019.04 (Jul 18 2019 - 04:19:33 +0000)
>   I just tried the trivial sysc driver again, it definitely hangs the
> same as not having the driver.
> CPU  : AM335X-GP rev 1.0
> Model: TI AM335x BeagleBone
> DRAM:  256 MiB
> NAND:  0 MiB
> MMC:   OMAP SD/MMC: 0
> Loading Environment from FAT... *** Warning - bad CRC, using default
> environment
> 
> <ethaddr> not set. Validating first E-fuse MAC
> Net:   eth0: ethernet@4a100000
> Warning: usb_ether MAC addresses don't match:
> Address in ROM is          de:ad:be:ef:00:01
> Address in environment is  d4:94:a1:85:ce:72
> , eth1: usb_ether
> Hit any key to stop autoboot:  0 
> switch to partitions #0, OK
> mmc0 is current device
> Scanning mmc 0:1...
> 80492 bytes read in 8 ms (9.6 MiB/s)
> Found EFI removable media binary efi/boot/bootarm.efi
> Scanning disk mmc@48060000.blk...
> Found 3 disks
> BootOrder not defined
> 616000 bytes read in 54 ms (10.9 MiB/s)
> ## Starting EFI application at 82000000 ...
> Consoles: EFI console  
>     Reading loader env vars from /efi/freebsd/loader.env
> Setting currdev to disk0p1:
> FreeBSD/arm EFI loader, Revision 1.1
> 
>    Command line arguments: l
>    EFI version: 2.70
>    EFI Firmware: Das U-Boot (rev 8217.1024)
>    Console: efi (0)
>    Load Path: /VenHw(e61d73b9-a384-4acc-aeab-
> 82e828f3628b)/SD(0)/SD(0)/HD(1,0x01,0,0x42f,0x18fa8)/efi\boot\bootarm
> .efi
>    Load Device: /VenHw(e61d73b9-a384-4acc-aeab-
> 82e828f3628b)/SD(0)/SD(0)/HD(1,0x01,0,0x42f,0x18fa8)
> Trying ESP: /VenHw(e61d73b9-a384-4acc-aeab-
> 82e828f3628b)/SD(0)/SD(0)/HD(1,0x01,0,0x42f,0x18fa8)
> Setting currdev to disk0p1:
> Trying: /VenHw(e61d73b9-a384-4acc-aeab-
> 82e828f3628b)/SD(0)/SD(0)/HD(2,0x01,0,0x193d7,0x5e6c11)
> Setting currdev to disk0p2:
> Loading /boot/defaults/loader.conf
> Loading /boot/device.hints
> Loading /boot/loader.conf
> Loading /boot/loader.conf.local
> Loading kernel...
> /boot/kernel/kernel text=0x85a6c4 data=0xb41e0+0x258720
> syms=[0x4+0xa8d50+0x4+0x10c071]
> Loading configured modules...
> can't find '/boot/entropy'
> /boot/kernel/umodem.ko text=0x1be0 text=0x1310 data=0x1088+0xf80
> syms=[0x4+0x1070+0x4+0xbcd]
> loading required module 'ucom'
> /boot/kernel/ucom.ko text=0x1f74 text=0x2e40 data=0x1088+0x17b4
> syms=[0x4+0x14f0+0x4+0xc5d]
> 
> Hit [Enter] to boot immediately, or any other key for command prompt.
> Booting [/boot/kernel/kernel]...               
> Using DTB provided by EFI at 0x87ee9000.
> Kernel entry at 0x84000180...
> Kernel args: (null)
> /
> U-Boot SPL 2019.04 (Jul 18 2019 - 04:19:33 +0000)
> Trying to boot from MMC1
> Loading Environment from FAT... *** Warning - bad CRC, using default
> environment
> 
> 




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?415c9b4760029235cd62bf95a35a736f7566cb9d.camel>