Anybody else building #openbsd 7.9-stable base system for #octeon on your EdgeRouter 6P?

Kernel build was straight forward, but following release(8) for the base system yields a SIGILL in gnu/usr.bin/clang/include/llvm/AMDGPU

(Trying to setup, and ultimately share, errata patches for octeon)

Maybe I need an octeon chip with an AMDGPU to build it?! Anyone know what octeon machine the released kernel/binaries are built on?

Re-toots appreciated!

I won't say I love #OpenBSD , but when you have a package of a router with an #octeon processor (compatible with OpenBSD) that will arrive today, you know it's for good reasons :D
EdgeRouter 4 under OpenBSD with Failover WAN

Got myself a new untested octeon, and it mostly runs OpenBSD.  
Dmesg: https://dmesgd.nycbug.org/index.cgi?do=view&id=5933
#octeon
#OpenBSD
NYC*BUG dmesgd

New York City BSD User Group dmesgd

Now running 6.9-beta on the #octeon 

I'm excited to have the TCP ACK performance increase and the PF_LOCK change (good stuff for a router!)

Potentially unrelated to the above, but the reorder_kernel step also went from ~1.5 minutes to 30 seconds 

If anyone was curious:

Yes, OpenBSD does run well on the Edge Router 6p. Especially after upgrading the storage via the front USB port.

Neat little #octeon router with 5 ethernet ports plus 1 SFP (I think?). Should allow for all the network segmentation one should need at home.

I have to..."but can it run Slack?"
---
RT @marvellsemi
#NEWS: “Marvell Announces OCTEON TX2 Family of Multi-Core Infrastructure Processors.” 5th generation #OCTEON family supports 4 to 36 Arm v8 cores coupled with hardware accelerators for #Networking, #Security & #Wireless #Infrastructure @Arm Learn More: http://bit.ly/2I8zSiO
https://twitter.com/marvellsemi/status/1234472288470392833
Company - Newsroom - Marvell Announces OCTEON TX2 Family of Multi-Core Infrastructure Processors

First time building the system from source (-stable) on #octeon. Started the process on Friday afternoon, expecting it to take a while. Was not expecting the build to still be going 2 days later... 

I had a hunch that maybe this was a partition clash, and it seems my hunch was correct!

Solution: Recreate a new partition with a letter not already in use by the #ER6p (in my case 'f'). Flash drive mounted successfully after that!

So it seems that #octeon machines (or maybe just the ER6p) can only handle unique partition letters? (i.e. no simultaneous sd0a and sd1a)

#openbsd

#help

Am I a dummy for expecting a flash drive formatted (disklabel -E; newfs) on amd64 to be mount-able on an #octeon machine?

# mount -v /dev/sd1a /mnt/usb
mount_ffs: /dev/sd1a on /mnt/usb: Invalid argument

Does that mean the drive is trash, or should I simply try reformatting on the octeon box itself?