Hi Ted, I've an update regarding this bug report:
[email protected] wrote: > > On Sun, Jan 2, 2011 at 8:18 AM, Florian Fuessl <[email protected]> wrote: > > > > [email protected] wrote: > >> > >> Synopsis: uvm_fault(0xd0a0ab60, 0x0, 0, 1) -> e > >> > >> State-Changed-From-To: open->closed > >> State-Changed-By: tedu > >> State-Changed-When: Sat Jan 1 23:37:35 MST 2011 > >> State-Changed-Why: > >> dupe > > > > sorry, used sendbug for each individual uvm_fault message. > > Duplicates could be closed of course... > > > > Do you have an idea what may cause these uvm_faults? > > No, but if it always happens after running ifconfig, it sounds like a > bug. Different traces just mean different ways of corrupting memory. since adding "inet6 alias [...]" on some interfaces and setting up some IPv6 services the OpenBSD router panics every few hours. Unfortunately I guess savecore does not work correctly: savecore: reboot after panic: pool_do_put: mcl2k: page header missing savecore: system went down at Thu Feb 3 18:18:11 2011 savecore: writing core to /var/crash/bsd.19.core more than 16 dma segs savecore: /dev/rsd0b: Input/output error savecore: WARNING: core may be incomplete The core file(s) only contain 532 byte. Is the content of these files useful for this bug report? How can I fix savecore to write the complete memory dump to the coredump file? Thanks for your feedback, -Florian
