"panic: trap: fast data access mmu miss" in m_copym
Robert Watson
rwatson at FreeBSD.org
Tue Apr 19 00:35:18 PDT 2005
On Mon, 18 Apr 2005, Kris Kennaway wrote:
> This on an u10 running
>
> FreeBSD 5.3-STABLE (NETBOOT) #1: Sun Dec 12 18:38:35 JST 2004
>
> It may already be fixed, but since this is clearly a very infrequent
> problem (the other 7 machines with the same kernel have been running for
> months) it will be hard to tell empirically.
>
> Unfortunately I don't seem to have a kernel.debug for this machine.
Is it possible to build a kernel from around the right date and see how
closely things match? Do you have the full trap message? There was a
2005/01/12 change to tcp_output.c that corrected a possible crash, but I
don't have the details of the crash on-hand to know if it's the same one.
A lin number would be very helpful, even approximate, for the call to
m_copym() in tcp_output(), as well as the full fault message.
Robert N M Watson
>
> panic: trap: fast data access mmu miss
> cpuid = 0
> KDB: enter: panic
> [thread 100005]
> Stopped at kdb_enter+0x38: ta %xcc, 1
> db> wh
> panic() at panic+0x214
> trap() at trap+0x13c
> -- fast data access mmu miss tar=0 %o7=0xc02b2090 --
> m_copym() at m_copym+0x40
> tcp_output() at tcp_output+0xfa4
> tcp_input() at tcp_input+0x3680
> ip_input() at ip_input+0x150
> netisr_processqueue() at netisr_processqueue+0x7c
> swi_net() at swi_net+0x154
> ithread_loop() at ithread_loop+0x124
> fork_exit() at fork_exit+0x68
> fork_trampoline() at fork_trampoline+0x8
> db>
>
More information about the freebsd-sparc64
mailing list