From owner-freebsd-current Mon Jun 1 02:17:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA00952 for freebsd-current-outgoing; Mon, 1 Jun 1998 02:17:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA00920 for ; Mon, 1 Jun 1998 02:17:35 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id CAA09950; Mon, 1 Jun 1998 02:17:00 -0700 (PDT) Message-Id: <199806010917.CAA09950@implode.root.com> To: Bruce Evans cc: scrappy@hub.org, freebsd-current@FreeBSD.ORG Subject: Re: May29th kernel with May20th CAM drivers: panic? In-reply-to: Your message of "Mon, 01 Jun 1998 16:24:47 +1000." <199806010624.QAA13930@godzilla.zeta.org.au> From: David Greenman Reply-To: dg@root.com Date: Mon, 01 Jun 1998 02:16:59 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> It appears that the mbuf chain is getting corrupted somehow. The above >>trap info indicates that the m_data pointer is bogus, resulting in a panic >>when the system attempts to get the physical address from the page tables. >>I don't see anything obvious in the 'de' driver that could cause this, so >>I suspect the buffer corruption is external to the driver. > >I recently fixed one source of mbuf chain corruption: Do you plan to commit this before the end of the century? :-) -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message