Date: Mon, 22 Jun 2015 11:51:50 -0600 From: jd1008 <jd1008@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: How to test for memory corruption ? Message-ID: <55884B36.8000007@gmail.com> In-Reply-To: <CA%2ByaQw_Ba50ik7sKAGuLE1nXU3ba_rmZ_xBgj%2ByY53tNbt8H6w@mail.gmail.com> References: <CAGf2gkMkG6kpBfYnwL_MYrMGF6hKyEjGA2cHND6ZkyUkHWrnFQ@mail.gmail.com> <CA%2ByaQw_Ba50ik7sKAGuLE1nXU3ba_rmZ_xBgj%2ByY53tNbt8H6w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 06/22/2015 02:10 AM, Daniel Peyrolon wrote: > Hi, > > I have absolutely no idea, but maybe you can use DTrace for this? > > You could also print the location for each memory write. > > El sáb., 20 de junio de 2015 9:20, Pratik Singhal <ps06756@gmail.com> > escribió: > >> Hello, I have written code for adding support for DMA transfers for >> Allwinner A10 SoC (Cubieboard 1) in MMC driver/ >> >> I have tried transferring files to/from mmc card and verified that files >> are copied fine. >> Although, many times the kernel panics suddenly, after I transfer files. >> This does not happen If I use PIO to transfer data (PIO's code is tested >> and already committed to ~HEAD). Panics don't occur in the statements >> written for DMA transfer. >> >> I am suspecting that the problem is that the DMA transfer apart from >> writing where it is required, is overwriting other parts of the memory >> also. >> >> Is there any way, I can verify that this is/this is not the case ? >> >> Thank you, >> Pratik Singhal It would be helpful to the devs if you post a link to the source code of your dma support code and all the mods you made in support thereof.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55884B36.8000007>