Re: (maybe) crash your VAX from userspace

I think the point was that he wanted confirmation on real hardware. He 
also already observed this in simh. :)

But I saw you also already found the problem and provided a fix. Nice 
work. I started looking a bit yesterday, suspecting what you found, but 
I didn't manage to spot it myself.

   Johnny

On 2024-03-23 06:26, matthew green wrote:
>> do you have a real metal VAX? Do you run NetBSD 10.0 RC6 on it? Are
>> you ok with (maybe) crashing it? Then you are the person I'm looking
>> for (maybe)!
> 
> don't need a real vax.  i booted my simh vax with "boot -c",
> "disable qt*" "quit", and then it attached a qe0, and then
> running the ifconfig mtu, i have this stack:
> 
> panic: SEGV in kernel mode: pc 0x802f50e0 addr 0
> Stack traceback :
> 0xa71fba84: vpanic+0x179(0x8035714b,0xa71fbb1c)
> 0xa71fbaa4: printf_nostamp+0x0(0x8035714b,0x802f50e0,0)
> 0xa71fbad0: trap+0x729(0xa71fbbdc)
> 0xa71fbbdc: trap type=0x4c code=0x0 pc=0x802f50e0 psl=0xd70008
> 0xa71fbba8: if_init+0x1a(0x9fed4828)
> 0xa71fbc30: ether_ioctl+0xa1(0x9fed4828,0x8090697f,0x9fe45e00)
> 0xa71fbc54: qeioctl+0x9e(0x9fed4828,0x8090697f,0x9fe45e00)
> 0xa71fbc88: if_ioctl+0x24(0x9fed4828,0x8090697f,0x9fe45e00)
> 0xa71fbcc0: doifioctl+0xa7c(0x9e22316c,0x8090697f,0x9fe45e00,0x9fbc00c0)
> 0xa71fbddc: soo_ioctl+0x5f(0x9fde0dac,0x8090697f,0x9fe45e00)
> 0xa71fbe44: sys_ioctl+0x1ad(0x9fbc00c0,0xa71fbf54,0xa71fbf4c)
> 0xa71fbf08: syscall+0x126(0xa71fbfb4)
> db>
> 

-- 
Johnny Billquist                  || "I'm on a bus
                                   ||  on a psychedelic trip
email: [email protected]             ||  Reading murder books
pdp is alive!                     ||  tryin' to stay hip" - B. Idol