From owner-freebsd-scsi Sun May 31 22:38:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA04577 for freebsd-scsi-outgoing; Sun, 31 May 1998 22:38:06 -0700 (PDT) (envelope-from owner-freebsd-scsi@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 WAA04571; Sun, 31 May 1998 22:38:02 -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 WAA09607; Sun, 31 May 1998 22:37:33 -0700 (PDT) Message-Id: <199806010537.WAA09607@implode.root.com> To: The Hermit Hacker cc: freebsd-current@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: May29th kernel with May20th CAM drivers: panic? In-reply-to: Your message of "Sun, 31 May 1998 17:45:05 EDT." From: David Greenman Reply-To: dg@root.com Date: Sun, 31 May 1998 22:37:32 -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I'm not going to bother submitting a problem report on this, >mainly because I don't even have a core to analyze, but I figured I'd at >least put a 'head up' on this, in case this anything to someone... > > >Fatal trap 12: page fault while in kernel mode >fault virtual address = 0xefcb5b1c >fault code = supervisor read, page not present >instruction pointer = 0x8:0xf01a88ad >stack pointer = 0x10:0xf6951af4 >frame pointer = 0x10:0xf6951b28 >code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 >processor eflags = interrupt enabled, resume, IOPL = 0 >current process = 7011 (innfeed) >interrupt mask = net bio >kernel: type 12 trap, code=0 >Stopped at _tulip_txput+0x111: movl _PTmap(,%eax,4),%edx 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. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message