This report is totally useless without a dmesg.
We don't know which version,which arch, and a bunch of other
things that would be included in it.
On 2016-08-20, sven falempin <sven.falem...@gmail.com> wrote:
> Because it runs under qemu, filling a bug report is ...
> nevertheless i leave the trace info here, in case it is relevant,
> also does this mean i ran out of memmory ?>
>
> arp info overwritten for 10.14.0.1 by fe:e1:ba:d0:f8:62 on vether114
> arp info overwritten for REDACTED by 00:07:b4:00:01:02 on vio0
> arp info overwritten for REDACTED by 00:07:b4:00:01:01 on vio0
> arp: attempt to overwrite entry for 10.36.0.1 on vether136 by
> fe:e1:ba:db:c5:e9
> on trunk136
> arp info overwritten for 10.36.0.1 by fe:e1:ba:db:c5:e9 on vether136
> uvm_fault(0xffffff021680ee00, 0x11, 0, 1) -> e
> kernel: page fault trap, code=0
> Stopped at uvm_pmr_addr_RB_REMOVE+0x94: cmpq 0x10(%rax),%rbx
> ddb{0}> trace
> uvm_pmr_addr_RB_REMOVE() at uvm_pmr_addr_RB_REMOVE+0x94
> uvm_pmr_remove_addr() at uvm_pmr_remove_addr+0x11
> uvm_pmr_get1page() at uvm_pmr_get1page+0x1ae
> uvm_pmr_getpages() at uvm_pmr_getpages+0x514
> uvm_pagealloc() at uvm_pagealloc+0x128
> uvm_fault() at uvm_fault+0xaee
> trap() at trap+0x5f0
> --- trap (number 6) ---
> end of kernel
> end trace frame: 0x1482aa29b820, count: -7
> 0x148244132eb7:
>
> Those arp info overwritten are normal ?
