On Sun, Jan 22, 2006 at 02:12:05PM -0500, Kris Kennaway wrote: > 12-processor e4500 running 7.0: > > panic: trap: data access error > > db> wh > Tracing pid 57006 tid 100210 td 0xfffff80256141110 > panic() at panic+0x164 > trap() at trap+0x418 > -- data access error %o7=0xc0305490 -- > tsb_tte_lookup() at tsb_tte_lookup+0xd0 > pmap_copy() at pmap_copy+0xe0 > vm_map_copy_entry() at vm_map_copy_entry+0x12c > vmspace_fork() at vmspace_fork+0x2f4 > vm_forkproc() at vm_forkproc+0xe4 > fork1() at fork1+0xe14 > fork() at fork+0x10 > syscall() at syscall+0x2dc > -- syscall (2, FreeBSD ELF64, fork) %o7=0x1101a0 -- > userland() at 0x40649088 > user trace: trap %o7=0x1101a0 > pc 0x40649088, sp 0x7fdffffd701 > pc 0x106890, sp 0x7fdffffd7c1 > pc 0x1072b0, sp 0x7fdffffd981 > pc 0x10a498, sp 0x7fdffffda71 > pc 0x10be24, sp 0x7fdffffdc21 > pc 0x1065e8, sp 0x7fdffffdce1 I think this was another symptom of the e4500 hardware monitor detecting a failed CPU and taking it offline, and FreeBSD panicking because it's totally oblivious to that. Kris
Attachment:
pgpdlHofTK82Z.pgp
Description: PGP signature