From owner-freebsd-net@FreeBSD.ORG  Tue Apr 19 07:35:18 2005
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 9563916A4CE; Tue, 19 Apr 2005 07:35:18 +0000 (GMT)
Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 475C843D53; Tue, 19 Apr 2005 07:35:18 +0000 (GMT)
	(envelope-from rwatson@FreeBSD.org)
Received: from fledge.watson.org (fledge.watson.org [204.156.12.50])
	by cyrus.watson.org (Postfix) with ESMTP id 49B8446B33;
	Tue, 19 Apr 2005 03:35:17 -0400 (EDT)
Date: Tue, 19 Apr 2005 08:36:28 +0100 (BST)
From: Robert Watson <rwatson@FreeBSD.org>
X-X-Sender: robert@fledge.watson.org
To: Kris Kennaway <kris@obsecurity.org>
In-Reply-To: <20050419032947.GA23047@xor.obsecurity.org>
Message-ID: <20050419083350.V31061@fledge.watson.org>
References: <20050419032947.GA23047@xor.obsecurity.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
cc: net@FreeBSD.org
cc: sparc64@FreeBSD.org
Subject: Re: "panic: trap: fast data access mmu miss" in m_copym
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Apr 2005 07:35:18 -0000

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>
>