RE: ioremap bug? (was RE: DSPBRIDGE: segmentation fault after reloading dspbridge several times due to a memory leak.)

2009-03-12 Thread Menon, Nishanth
; linux-omap@vger.kernel.org Cc: Kanigeri, Hari; Woodruff, Richard; Lakhani, Amish; Gupta, Ramesh; Ameya Palande Subject: ioremap bug? (was RE: DSPBRIDGE: segmentation fault after reloading dspbridge several times due to a memory leak.) console output where you can see the address increasing

RE: ioremap bug? (was RE: DSPBRIDGE: segmentation fault after reloading dspbridge several times due to a memory leak.)

2009-03-12 Thread Menon, Nishanth
, Ramesh; Ameya Palande Subject: ioremap bug? (was RE: DSPBRIDGE: segmentation fault after reloading dspbridge several times due to a memory leak.) console output where you can see the address increasing. I duplicated this with the following dummy driver which ioremaps as per the same

RE: ioremap bug? (was RE: DSPBRIDGE: segmentation fault after reloading dspbridge several times due to a memory leak.)

2009-03-12 Thread Guzman Lugo, Fernando
Palande Subject: RE: ioremap bug? (was RE: DSPBRIDGE: segmentation fault after reloading dspbridge several times due to a memory leak.) -Original Message- From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap- ow...@vger.kernel.org] On Behalf Of Menon, Nishanth Sent: Thursday

Re: ioremap bug? (was RE: DSPBRIDGE: segmentation fault after reloading dspbridge several times due to a memory leak.)

2009-03-12 Thread Kevin Hilman
Menon, Nishanth n...@ti.com writes: -Original Message- From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap- ow...@vger.kernel.org] On Behalf Of Guzman Lugo, Fernando Sent: Thursday, March 12, 2009 2:04 AM To: linux-omap@vger.kernel.org Subject: DSPBRIDGE: segmentation fault

RE: ioremap bug? (was RE: DSPBRIDGE: segmentation fault after reloading dspbridge several times due to a memory leak.)

2009-03-12 Thread Menon, Nishanth
after reloading dspbridge several times due to a memory leak.) Which of these physical addresses causes an increasing virtual address? The addresses in the 0x48xx (L4, L4_WKUP) range should just trigger static mapping via the arch-specific ioremap, so those should always map to the same

RE: ioremap bug? (was RE: DSPBRIDGE: segmentation fault after reloading dspbridge several times due to a memory leak.)

2009-03-12 Thread Woodruff, Richard
Kevin, Some more isolation: The l-o master branch does not have an issue, only the pm branch seems to have the problem - probably some commit(s?) missing in pm branch. Since bridge is based off the pm branch, wont make sense to regress on it :(. This rings a bell from a couple months back.

RE: ioremap bug? (was RE: DSPBRIDGE: segmentation fault after reloading dspbridge several times due to a memory leak.)

2009-03-12 Thread Menon, Nishanth
: segmentation fault after reloading dspbridge several times due to a memory leak.) Some more isolation: The l-o master branch does not have an issue, only the pm branch seems to have the problem - probably some commit(s?) missing in pm branch. Since bridge is based off the pm branch, wont make

RE: ioremap bug? (was RE: DSPBRIDGE: segmentation fault after reloading dspbridge several times due to a memory leak.)

2009-03-12 Thread Menon, Nishanth
Kevin, Richard, -Original Message- From: Menon, Nishanth snip -Original Message- From: Woodruff, Richard Sent: Thursday, March 12, 2009 9:33 PM snip This rings a bell from a couple months back. I've not followed the thread but recall a recent fix to ioremap.