Date: Tue, 19 Apr 2005 10:46:50 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Robert Watson <rwatson@FreeBSD.org> Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: "panic: trap: fast data access mmu miss" in m_copym Message-ID: <20050419174650.GA55289@xor.obsecurity.org> In-Reply-To: <20050419083350.V31061@fledge.watson.org> References: <20050419032947.GA23047@xor.obsecurity.org> <20050419083350.V31061@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Tue, Apr 19, 2005 at 08:36:28AM +0100, Robert Watson wrote: > 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? I could, but I don't know how well this is likely to work. > Do you have the full trap message? The full trap message is as above. sparc64 doesn't seem to give very detailed trap information. > 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. I'll try to get the line number. Kris [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCZUQJWry0BWjoQKURAubJAKDtQMZvdC//MFqc4pXzg0McS4SvhwCdHO09 e9LIbbORoSBY34xtZImQ1jY= =h3DR -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050419174650.GA55289>