Hi Ariane,
> Please supply a trace, dmesg and the output of ps (on ddb, type
> 'trace' for the trace, and 'ps' for the ps output.
>
> The uvm_fault is a null-pointer exception. We need the trace and ps to
> diagnose where the fault occured.
Below are the trace and the ps. I've typed them, because I couldn't copy
and paste them. How do I get a dmesg if I can't start the machine? Boot
from an installation CD?
ddb{0}> trace
fxp_load_ucode() at fxp_load_ucode+0x8a
fxp_init() at fxp_init+0x9b
fxp_ioctl() at fxp_ioctl+0xeb
in6_addmulti() at in6_addmulti+0x1ed
in6_joingroup() at in6_joingroup+0x4e
in6_update_ifa() at in6_update_ifa+0x5c1
in6_ifattach_linklocal() at in6_ifattach_linklocal+0x113
in6_ifattach() at in6_ifattach+0x104
in6_if_up() at in6_if_up+0x15
if_up() at if_up+0x78
ifioctl() at ifioctl+0xb98
sys_ioctl() at sys_ioctl+0x146
syscall() at syscall+0x248
--- syscall (number 54) ---
end trace frame: 0x0, count: -13
acpi_pdirpa+0x405402:
ddb{0}> ps
PID PPID PGRP UID S FLAGS WAIT COMMAND
*20399 7327 7327 0 7 0 dhclient
7327 1 7327 0 3 0x88 pause sh
14 0 0 0 3 0x100200 aiodoned aiodoned
13 0 0 0 3 0x100200 syncer update
12 0 0 0 3 0x100200 cleaner cleaner
11 0 0 0 3 0x100200 reaper reaper
10 0 0 0 3 0x100200 pgdaemon pagedaemon
9 0 0 0 3 0x100200 bored crypto
8 0 0 0 3 0x100200 pftm pfpurge
7 0 0 0 3 0x100200 usbtsk usbtask
6 0 0 0 3 0x100200 usbatsk usbatsk
5 0 0 0 3 0x100200 acpi0 acpi0
4 0 0 0 7 0x40100200 idle1
3 0 0 0 3 0x100200 bored syswq
2 0 0 0 3 0x40100200 idle0
1 0 1 0 3 0x80 wait init
0 -1 0 0 3 0x200 scheduler swapper
Kind regards,
Martijn Rijkeboer
