Date: Thu, 20 Dec 2001 20:25:49 -0800 From: Brady Montz <bradym@mail.hydrologue.com> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: Peter Jeremy <peter.jeremy@alcatel.com.au>, Chad David <davidc@acns.ab.ca>, Richard Nyberg <rnyberg@it.su.se>, David Wolfskill <david@catwhisker.org>, freebsd-stable@FreeBSD.ORG Subject: Re: 4.4-STABLE crashes - suspects new ata-driver over wd-drivers Message-ID: <200112210425.fBL4Pnk09252@mail.hydrologue.com> 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> <200112202259.fBKMxGi79320@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--text follows this line--
Matthew Dillon <dillon@apollo.backplane.com> writes:
> :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.
I'd had that thought as well. Seems a reasonably way for a misbehaving
driver to corrupt memory. I'll try that tonight.
However, being a recent convert to BSD, I don't know how to turn of
DMA. How do I?
--
Brady Montz
bradym@balestra.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200112210425.fBL4Pnk09252>