RE: Beaglebone Black -current error on partition resize

[<dhop%nwlink.com@localhost>]

A-ha, thanks Jared, I saw you had FDTized the Beagles but I assumed NetBSD-9
== -current still.  My bad. That said, on this image I'm getting an
undefined instruction and a reset loop:

U-Boot SPL 2018.11 (Nov 26 2019 - 15:10:39 -0800)
Trying to boot from MMC1
Loading Environment from FAT... *** Warning - bad CRC, using default
environment
Loading Environment from MMC... *** Warning - bad CRC, using default
environment

U-Boot 2018.11nb4 (Nov 26 2019 - 15:10:39 -0800)

CPU  : AM335X-GP rev 2.1
I2C:   ready
DRAM:  512 MiB
No match for driver 'omap_hsmmc'
No match for driver 'omap_hsmmc'
Some drivers were not found
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Loading Environment from FAT... *** Warning - bad CRC, using default
environment
Loading Environment from MMC... *** Warning - bad CRC, using default
environment

<ethaddr> not set. Validating first E-fuse MAC
Net:   Updated phy address for CPSW#0, old: 0, new: 2
cpsw, usb_ether
Press SPACE to abort autoboot in 2 seconds
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
201 bytes read in 3 ms (65.4 KiB/s)
Running bootscript from mmc0 ...
## Executing script at 82000000
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
86636 bytes read in 9 ms (9.2 MiB/s)
Found EFI removable media binary efi/boot/bootarm.efi
Scanning disks on usb...
Disk usb0 not ready
Disk usb1 not ready
Disk usb2 not ready
Disk usb3 not ready
Scanning disks on mmc...
MMC Device 2 not found
MMC Device 3 not found
Found 5 disks
181376 bytes read in 18 ms (9.6 MiB/s)
## Starting EFI application at 82000000 ...
[...linefeeds...]

undefined instruction
pc : [<9cf02100>]          lr : [<9cf01800>]
reloc pc : [<7d7ab100>]    lr : [<7d7aa800>]
sp : 9df35bd8  ip : 00007ee6     fp : 00000003
r10: 9df44940  r9 : 9df36eb8     r8 : 00000000
r7 : 9cf29ce8  r6 : 9df47028     r5 : 9cf29e40  r4 : 00000000
r3 : 9ff849f9  r2 : 00000000     r1 : 00000000  r0 : 00000001
Flags: nZCv  IRQs off  FIQs on  Mode SVC_32
Code: 00023818 00027ee0 000237d0 000237e0 (f2c00010) 
UEFI image [0x9cf01000:0x9cf2b07f] pc=0x1100 '/\efi\boot\bootarm.efi'
Resetting CPU ...

resetting ...

U-Boot SPL 2018.11 (Nov 26 2019 - 15:10:39 -0800)
Trying to boot from MMC1
[...]

The U-Boot I'm using was built on 9.0_BETA (Oct. 28) using pkgsrc-current.
I *think* what I'll need to do is rebuild the U-Boot on a -current
environment, is that right?

If not I'll mess around with images from -HEAD now that I'm schooled on
where they are.

Thanks,
David

-----Original Message-----
From: Jared McNeill <jmcneill%invisible.ca@localhost> 
Sent: Wednesday, November 27, 2019 2:18 AM
To: dhop%nwlink.com@localhost
Cc: port-arm%netbsd.org@localhost
Subject: Re: Beaglebone Black -current error on partition resize

The images on my site are from the netbsd-9 branch. I suspect -current 
will work a lot better on BeagleBone Black as I've cleaned up most of the 
code for that SOC in the meantime. Can you try this image instead?

http://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/latest/evbarm-earmv7hf/binary/
gzimg/armv7.img.gz


On Wed, 27 Nov 2019, dhop%nwlink.com@localhost wrote:

> Apologies if this is malformed, I've been away from the lists a spell and
> now trying different email clients to find one that behaves.
>
> I'm trying to boot -current using a generic 32-bit image from invisible.ca
> on a Beaglebone Black, and I'm getting a ton of errors after fs expansion.
> I suspect that the expansion is clobbering the FAT partition, because on
> reboot I get a ton of errors of the form:
> [...]
> /dev/rld0e: Cluster 20363 is marked free in FAT 0, but continues with
> cluster 19884 in FAT 1
> /dev/rld0e: Cluster 20364 is marked free in FAT 0, but continues with
> cluster 19885 in FAT 1
> /dev/rld0e: Cluster 20365 is marked free in FAT 0, but continues with
> cluster 19886 in FAT 1
> /dev/rld0e: Cluster 20366 is marked free in FAT 0, as EOF in FAT 1
> /dev/rld0e: Cluster 20403 is marked free in FAT 0, but continues with
> cluster 19924 in FAT 1
> /dev/rld0e: Cluster 20404 is marked free in FAT 0, but continues with
> cluster 19925 in FAT 1
> /dev/rld0e: Cluster 20405 is marked free in FAT 0, as EOF in FAT 1
> /dev/rld0e: Cluster 20412 is marked free in FAT 0, but continues with
> cluster 19933 in FAT 1
> /dev/rld0e: Cluster 20413 is marked free in FAT 0, but continues with
> cluster 19934 in FAT 1
> /dev/rld0e: Cluster 20414 is marked free in FAT 0, but continues with
> cluster 19935 in FAT 1
> [...]
>
> I'm using a Samsung EVO Plus 32-gig SD card.  The log looks like this:
> [   2.3838543] boot device: ld0
> [   2.3928375] root on ld0a dumps on ld0b
> [   2.3928375] mountroot: trying ffs...
> [   2.4036180] root file system type: ffs
> [   2.4126108] kern.module.path=/stand/evbarm/9.0/modules
> [   2.4126108] WARNING: no TOD clock present
> [   2.4126108] WARNING: using filesystem time
> [   2.4266791] WARNING: CHECK AND RESET THE DATE!
> [   2.4326108] init: copying out path `/sbin/init' 11
> Sun Nov 24 23:53:43 UTC 2019
> Starting root file system check:
> /dev/rld0a: file system is clean; not checking
> Growing ld0 MBR partition #1 (1065MB -> 30304MB)
> Growing ld0 disklabel (1289MB -> 30528MB)
> Resizing /
> reboot: rebooted by root
>
> [ 188.1726085] rebooting...
>
> [...]
> Starting root file system check:
> /dev/rld0a: file system is clean; not checking
> fdisk: Cannot determine the number of heads
> Not resizing /: already correct size
> swapctl: adding /dev/ld0b as swap device at priority 0
> Starting file system checks:
> [   7.7326103] sdhc0: cmd timeout error
> [   7.7573527] ld0e: error reading fsbn 1 of 1-80 (ld0 bn 32769; cn 16 tn
0
> sn 1), retrying
> [   8.4026094] sdhc0: timeout waiting for mask 0x3 value 0
(state=0x1f70a06)
> [   8.4026094] sdhc0: command or data phase inhibited
> [   8.4426097] sdhc0: cmd timeout error
> [   8.4539879] ld0e: error reading fsbn 81 of 81-160 (ld0 bn 32849; cn 16
tn
> 2 sn 17), retrying
> /dev/rld0e: FAT starts with odd byte sequence (00000000)
> FIXED
> /dev/rld0e: Cluster 256 in FAT 0 continues with out of range cluster
number
> 65520
> /dev/rld0e: FAT starts with odd byte sequence (00000000)
> FIXED
> [...]
>
> Then the cluster errors cascade ending with a panic.  I'm new to the BBB
so
> I bet I'm doing something wrong here, but I am using the current pkgsrc
> U-Boot:
>
> ----------
> U-Boot SPL 2018.11 (Nov 26 2019 - 15:10:39 -0800)
> Trying to boot from MMC1
> Loading Environment from FAT... *** Warning - bad CRC, using default
> environment
> Loading Environment from MMC... *** Warning - bad CRC, using default
> environment
>
> U-Boot 2018.11nb4 (Nov 26 2019 - 15:10:39 -0800)
>
> CPU  : AM335X-GP rev 2.1
> I2C:   ready
> DRAM:  512 MiB
> No match for driver 'omap_hsmmc'
> No match for driver 'omap_hsmmc'
> Some drivers were not found
> MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
> Loading Environment from FAT... *** Warning - bad CRC, using default
> environment
> Loading Environment from MMC... *** Warning - bad CRC, using default
> environment
>
> <ethaddr> not set. Validating first E-fuse MAC
> Net:   cpsw, usb_ether
> Press SPACE to abort autoboot in 2 seconds
> switch to partitions #0, OK
> mmc0 is current device
> SD/MMC found on device 0
> 480 bytes read in 5 ms (93.8 KiB/s)
> Running bootscript from mmc0 ...
> ## Executing script at 82000000
> 6490580 bytes read in 410 ms (15.1 MiB/s)
> ## Booting kernel from Legacy Image at 82000000 ...
>   Image Name:   NetBSD/beagle 9.0_BETA
>   Created:      2019-11-24  23:44:57 UTC
>   Image Type:   ARM NetBSD Kernel Image (uncompressed)
>   Data Size:    6490516 Bytes = 6.2 MiB
>   Load Address: 80300000
>   Entry Point:  80300000
>   Verifying Checksum ... OK
>   Loading Kernel Image ... OK
> ## Transferring control to NetBSD stage-2 loader (at address 80300000) ...
> [   1.0000000] uboot arg = 0x9df36f98, 0, 0x9ffa4003, 0x9df41168
> [...]
>
> --David
>
>
>
>