This is the same backtrace I got when I tried it too... The system would
get all the way through booting, then fam (I'm assuming) sent something to
rpcbind, which then caused this panic.
Ken
On Mon, 14 Jan 2002, Michael McGoldrick wrote:
> The trace was short, so I wrote the whole thing down.
>
I can second this. I have seen the same panic, but was too lazy to hand
copy it.
Ken
On Mon, 14 Jan 2002, Michael McGoldrick wrote:
> Kernel and world built with sources cvsupped as of Mon Jan 14 18:44:04 GMT from
> cvsup.freebsd.org.
> The panic message is hand copied. Please send me a mail if
On 14-Jan-02 Michael McGoldrick wrote:
> The trace was short, so I wrote the whole thing down.
That one is fixed already, re-cvsup. Also, you should probably be running with
INVARIANTS turned on in -current as that would give more useful error messages.
> _mtx_unlock_sleep(c232c834,0,0,0) at _
The trace was short, so I wrote the whole thing down.
_mtx_unlock_sleep(c232c834,0,0,0) at _mtx_unlock_sleep+0x9f
unp_externalize(c0b6ab00,c0b6ac00,cb5d3ccc,cb5d3c8c,cb5d3ccc) at unp_externalize
+0x38e
soreceive(ca29d420,cb5d3c18,cb5d3c44,0,cb5d3c1c) at soreceive+0x376
recvit(ca284304,b,cb5d3ccc,
On 14-Jan-02 Michael McGoldrick wrote:
> Kernel and world built with sources cvsupped as of Mon Jan 14 18:44:04 GMT
> from
> cvsup.freebsd.org.
> The panic message is hand copied. Please send me a mail if other details (eg
> dme
> sg) are required.
A traceback would be most useful. Type 't' in
Kernel and world built with sources cvsupped as of Mon Jan 14 18:44:04 GMT from
cvsup.freebsd.org.
The panic message is hand copied. Please send me a mail if other details (eg dme
sg) are required.
Kernel trap 12 with interrupts disabled
Fatal trap 12: page fault while in kernel mode
fault virtua