Re: Kernel panic on earm

So here's the partial conclusion:

All toolchain/kernels I've built with OpenBSD 6.4 and clang 6.0 trigger this panic. This is on amd64 and arm64.

I built a Linux VM on my OpenBSD/amd64 box, and...

All toolchain/kernels I've built with Linux amd64 and gcc 6.3 do not trigger this panic.

This is on the same set of sources (shared via NFS), config files and mk.conf.

I've had issues building the toolchain on OpenBSD using gcc (either the built-in 4.2.1 or 4.9.4 from ports), so I can only guess that it's an OpenBSD rather than clang quirk.

I'll try to investigate some more at a later date.

Many thanks for the help and pointers which helped me work it out.

Michael

On Tue, 13 Nov 2018 at 09:04, Martin Husemann <martin%duskware.de@localhost> wrote:

On Sat, Nov 10, 2018 at 09:41:44AM +0000, Michael Blatt wrote:
> 1. Martin, can you manually confirm that this works on your Guruplug? I see
> that most automated tests have passed a few days ago, which implies it
> does. Seems there is no problem with the userland as that is identical to
> what I'm using, which brings us back to the kernel.

Yes, it works with a kernel from an hour or so ago:

# ifconfig -a
awge0: flags=0x8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ec_capabilities=1<VLAN_MTU>
ec_enabled=0
address: 02:0e:03:41:63:14
media: Ethernet autoselect (1000baseT full-duplex)
status: active
inet6 fe80::9a43:96ac:a66b:d416%awge0/64 flags 0x0 scopeid 0x1
inet6 2001:470:1f0b:e84:a982:4f01:4b81:7d8a/64 flags 0x0
inet 192.168.150.126/23 broadcast 192.168.151.255 flags 0x0
lo0: flags=0x8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33176
inet6 ::1/128 flags 0x20<NODAD>
inet6 fe80::1%lo0/64 flags 0x0 scopeid 0x2
inet 127.0.0.1/8 flags 0x0

> 2. Should I raise a PR for that - Nick, what info do you think I should
> include?

I guess something must be wrong with your kernel build, can you build a
netbsd.gdb and show the disassembly around the point where it crashes?

Martin