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.
