Re: Kernel Panic on 6.2 amd64 when run0 RT3070 based device is attached during boot

2018-01-28 Thread Denis
Hello Martin, Please let me know if need more information about machine and test conditions. $cat /etc/hostname.run0 dhcp lladdr xa:xb:xc:xx:xy:xz bssid ya:yb:yc:yx:yy:yz nwid wpa wpakey wpaprotos wpa2 I've copied the explanation from my previous post. "From time to time I receive Kernel Pan

Re: sparc64 ldom: interrupt_vector: spurious vector 40 at pil 15

2018-01-28 Thread Mark Kettenis
> From: Jeremie Courreges-Anglas > Date: Sun, 28 Jan 2018 21:41:06 +0100 > > Just spotted this, the ldom is currently unresponsive and nothing more > appeared on the serial output. fwiw this was spotted after rebooting > the domain 50+ times since yesterday. Have seen that before. Never got a

sparc64 ldom: interrupt_vector: spurious vector 40 at pil 15

2018-01-28 Thread Jeremie Courreges-Anglas
Just spotted this, the ldom is currently unresponsive and nothing more appeared on the serial output. fwiw this was spotted after rebooting the domain 50+ times since yesterday. ..>> OpenBSD BOOT 1.9 ERROR: /iscsi-hba: No iscsi-network-bootpath property Trying bsd... Booting /virtual-devices@10

Re: Kernel Panic on 6.2 amd64 when run0 RT3070 based device is attached during boot

2018-01-28 Thread Martin Pieuchot
On 28/01/18(Sun) 19:38, Denis wrote: > Catch the second one kernel panic. > > The output is the same, but on another kernel. Hope this helps. Sadly it doesn't. It only creates frustration from both sides. Please see https://www.openbsd.org/report.html .

Re: Kernel Panic on 6.2 amd64 when run0 RT3070 based device is attached during boot

2018-01-28 Thread Martin Pieuchot
Hello Denis, On 27/01/18(Sat) 12:38, Denis wrote: > Hello Martin, > > Thank you for your attention to the problem with run driver. > > Here is DDB output. Sorry but can you give more context? How does this happen, why do you need to do? What is the output of 'ps', what is your dmesg? What is

Re: Kernel Panic on 6.2 amd64 when run0 RT3070 based device is attached during boot

2018-01-28 Thread Denis
Catch the second one kernel panic. The output is the same, but on another kernel. Hope this helps. ... dmesg starting network panic: attempt to execute user address 0x0 in supervisor mode Stopped at db_enter+0x5popq%rbp TIDPIDUIDPRFLAGSPFLAGSCPUCOMMAND *123456

Re: random userland segfaults/abort with latest arm64 snapshot

2018-01-28 Thread Sebastien Marie
On Sun, Jan 28, 2018 at 12:59:39PM +0100, Mark Kettenis wrote: > > Date: Sun, 28 Jan 2018 07:27:49 +0100 > > From: Sebastien Marie > > > Did OpenBSD/arm64 ever run properly in qemu? I certainly never tried > it. Things are fairly stable on real hardware, but on the overdrive > 3000 we see rando

Re: random userland segfaults/abort with latest arm64 snapshot

2018-01-28 Thread Mark Kettenis
> Date: Sun, 28 Jan 2018 07:27:49 +0100 > From: Sebastien Marie > > Hi, > > I recently installed latest -current snapshot of arm64 using > qemu-system-aarch64 -M virt. > > $ doas what /bsd > /bsd > OpenBSD 6.2-current (GENERIC) #160: Wed Jan 24 18:26:59 MST 2018 > > But the system is r

Re: random userland segfaults/abort with latest arm64 snapshot

2018-01-28 Thread Otto Moerbeek
On Sun, Jan 28, 2018 at 07:27:49AM +0100, Sebastien Marie wrote: > Hi, > > I recently installed latest -current snapshot of arm64 using > qemu-system-aarch64 -M virt. > > $ doas what /bsd > /bsd > OpenBSD 6.2-current (GENERIC) #160: Wed Jan 24 18:26:59 MST 2018 > > But the system is rel