From owner-freebsd-stable Thu Dec 20 14:59:24 2001 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 3C73937B416 for ; Thu, 20 Dec 2001 14:59:18 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBKMxGi79320; Thu, 20 Dec 2001 14:59:16 -0800 (PST) (envelope-from dillon) Date: Thu, 20 Dec 2001 14:59:16 -0800 (PST) From: Matthew Dillon Message-Id: <200112202259.fBKMxGi79320@apollo.backplane.com> To: Brady Montz Cc: Peter Jeremy , Chad David , Richard Nyberg , David Wolfskill , freebsd-stable@FreeBSD.ORG Subject: Re: 4.4-STABLE crashes - suspects new ata-driver over wd-drivers References: <200112172133.fBHLXJg39627@bunrab.catwhisker.org> <20011217144541.A45973@colnta.acns.ab.ca> <20011218094330.A10601@gromit.it.su.se> <200112180857.fBI8vNh68173@apollo.backplane.com> <20011218023630.A5190@ranger.acns.ab.ca> <200112181920.fBIJKRt70523@apollo.backplane.com> <200112190757.fBJ7veY02579@mail.hydrologue.com> <200112190732.fBJ7WFQ86868@apollo.backplane.com> <87u1ulq1a8.fsf@balestra.org> <200112202147.fBKLlGg78745@apollo.backplane.com> <20011221094727.F73243@gsmx07.alcatel.com.au> <200112210400.fBL40O009107@mail.hydrologue.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :I induced the crash by running "make clean; make buildworld" in one :infinite loop and "portsdb -Uu" in another. That string occurs in a :bunch of makefiles in /usr/ports. Some of the occurences in the core :are clearly from them, but many of them are surrounded by binary :data. I recursively grepped /usr/{src,obj,bin,ports} and :/usr/local/{bin,lib} and didn't find any binary files with that :string. My guess then is that it's from the memory image of a make :process. : :-- : Brady Montz This is soooo weird. The corruption is occuring in the vm_page_t itself, at least in the crash you sent me. The vm_page_t is a locked-down address in the kernel. It is not effecting the vm_page_t's around the one that got corrupted. The corruption does not appear to be on a page or device block boundry. I am at a loss as to how its getting there. Could you try playing with the DMA modes on your IDE hard drive? Try turning DMA off, for example, and see if the corruption still occurs. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message