panic message:

uvm_fault(...) -> 0xe
kernel: supervisor trap page fault, code=0
stopped in pid 6690.1 (ifconfig) at netbsd:sysctl_iflist+0x56 movl0 
(%ebx),%eax


tr output:

sysctl_iflist(...) at netbsd:sysctl_iflist+0x56
sysctl_rtable(...) at netbsd:sysctl_rtable,0x19d
sysctl_dispatch(...) at netbsd:sysctl_dispatch,0x76
sys___sysctl(...) at netbsd:sys_sysctl+0xad
syscall_plain() at netbsd:syscall_plain,0x17e

--- syscall (number 202) ---


cu
Uwe

On Mon, 20 Feb 2006, Manuel Bouyer wrote:

> Date: Mon, 20 Feb 2006 20:14:26 +0100
> From: Manuel Bouyer <bouyer@antioche.eu.org>
> To: 6bone@6bone.informatik.uni-leipzig.de
> Cc: tech-net@NetBSD.org
> Subject: Re: pim6sd bug?
> 
> On Mon, Feb 20, 2006 at 11:24:11AM +0100, 6bone@6bone.informatik.uni-leipzig.de wrote:
>> Hello,
>>
>> I am using pim6sd with multiple vlan interfaces. After starting pim6sd
>> some programms (e.g. ifconfig -a) crashs the netbsd kernel.
>>
>> kernel: netbsd-current
>> kernelconfig:
>>
>> options         MROUTING        # IP multicast routing
>> options         PIM             # Protocol Independent Multicast
>>
>>
>> Is this a kernel bug or a pim6sd problem?
>
> If the kenrel crash it's clearly a problem in the kernel.
>
> Can you report the panic message, and the stack trace ("tr" at the ddb
> prompt)
>
> BTW I run pim6sd in a NetBSD 3.0/Xen domain, no problems.
>
> -- 
> Manuel Bouyer <bouyer@antioche.eu.org>
>     NetBSD: 26 ans d'experience feront toujours la difference
> --
>