Hi misc,

seem like I have type the wrong command by mistake using tab to complet the command. Don't know which command it was but I add a lot of output like this :

Faulted ikernel: double fault trap, code=0
  kernel: double fault trap, code=0
Faulted in DDB; continuing...
--db_more--kernel: type 269 trap, code=0
--db_more--kernel: type 269 trap, code=0
--db_more--kernel: type 269 trap, code=0
--db_more--kernel: type 269 trap, code=0
Faulted in DDB; continuing...
--db_more--kernel: type 269 trap, code=0
--db_more--kernel: type 269 trap, codekernel: type 269 trap, code=0
Faulted  kernel: type 269 trap, code=0
   kernel: double fault trap, code=0

I was working in minicom via serial and was not able to do ctrl z and also not able to ping the système so I rebooted it by cutting the power and now :

# ifconfig em2 192.168.23.1/24
# ifconfig em3 192.168.3.222/24
# pfctl -d
pf disabled
# route flush
kernel: kernel: kernel: kernel: kernel: kernel: privileged instruction fault tr
ap, code=0
panic: mtx_enter: locking against myself
panic: mtx_enter: locking against myself
panic: mtx_enter: locking against myself
panic: mtx_enter: locking against myself
panic: mtx_enter: lockin>> OpenBSD/amd64 BOOT 3.17
(bios sound that system as reboot)
boot> route flush
boot: illegal argument flush
boot> route
boot>

That a little scary. I was knowing it was possible to destroy a system with rm -rf but first time I see something like that. Anybody have a idea of what happen ? I can't scroll back enough to know which command was typed.

Here a little more output I found will scrolling :

Stopped at      0:uvm_fault(0xfffffe807b1b1cc8, 0x0, 0, 1) -> e
      kernel: page fault trap, code=0
--db_more--kernel: type 269 trap, code=0
Stopped at      0:uvm_fault(0xfffffe807b1b1cc8, 0x0, 0, 1) -> e
      kerkernel: type 269 trap, code=0
Stopped at      0:uvm_fault(0xfffffe807b1b1cc8, 0x0, 0, 1) -> e
      kernel: page fault trap, code=0
--db_morkernel: type 269 trap, code=0
Stopped at      0:uvm_fault(0xfffffe807b1b1cc8, 0x0, 0, 1) -> e
      kernel: page fault trap, code=0
--db_mkernel: type 269 trap, code=0
Stopped at      0:uvm_fault(0xfffffe807b1b1cc8, 0x0, 0, 1) -> e
      kernel: page fault trap, code=0
Stopped at      kernel: type 269 trap, code=0
Stopped at      0:uvm_fault(0xfffffe807b1b1cc8, 0x0, 0, 1) -> e
      kernel: page fault trap, code=0
Stopped at      kernel: type 269 trap, code=0
Stopped at      0:uvm_fault(0xfffffe807b1b1cc8, 0x0, 0, 1) -> e
      kernel: page fault trap, code=0
Stopped at      kernel: type 269 trap, code=0
Stopped at      0:uvm_fault(0xfffffe807b1b1cc8, 0x0, 0, 1) -> e
      kernel: page fault trap, code=0
Stopped at      kernel: type 269 trap, code=0
Stopped at      0:uvm_fault(0xfffffe807b1b1cc8, 0x0, 0, 1) -> e
      kernel: page fault trap, code=0
Stopped at      db_read_bytes+0x20:     movzbl  0(%rdi,%rcx,1),%eax

Thanks

Michel

Reply via email to