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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>> Just an update (thanks to Fernando in pointing this out)
>> 0x87000000, 0x600000, fails with same error
>> 0x88000000, 0x600000, fails with same error
>Wrong attempt!!
>Should have tried:
>0x87100000, 0x600000 - this worked
>> 0x87000000, 0x700000 - went thru 300 odd iterations without error!!
>This means that if I keep end address constant, it is fine.. with this >hypothesis, I tried
>0x87200000, 0x500000 - this also worked

However 0x87100000, 0x500000 also works that is the same end address than 0x87000000, 0x600000. so maybe the hypothesis is no right. 

Regards,
Fernando.

-----Original Message-----
From: Menon, Nishanth 
Sent: Thursday, March 12, 2009 10:58 AM
To: Menon, Nishanth; Guzman Lugo, Fernando; linux-omap@xxxxxxxxxxxxxxx
Cc: Kanigeri, Hari; Woodruff, Richard; Lakhani, Amish; Gupta, Ramesh; Ameya Palande
Subject: RE: ioremap bug? (was RE: DSPBRIDGE: segmentation fault after reloading dspbridge several times due to a memory leak.)

> -----Original Message-----
> From: Menon, Nishanth
> Sent: Thursday, March 12, 2009 6:53 PM
> To: Menon, Nishanth; Guzman Lugo, Fernando; linux-omap@xxxxxxxxxxxxxxx
> Cc: Kanigeri, Hari; Woodruff, Richard; Lakhani, Amish; Gupta, Ramesh;
> Ameya 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-owner@xxxxxxxxxxxxxxx [mailto:linux-omap-
> > owner@xxxxxxxxxxxxxxx] On Behalf Of Menon, Nishanth
> > Sent: Thursday, March 12, 2009 6:40 PM
> > To: Guzman Lugo, Fernando; linux-omap@xxxxxxxxxxxxxxx
> > 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.
> >
> > I duplicated this with the following dummy driver which ioremaps as per
> > the same allocations that the bridge driver would have done:
> >
> > #include <linux/kernel.h>
> > #include <linux/module.h>
> > #include <linux/slab.h>
> > #include <linux/mm.h>
> > #include <linux/dma-mapping.h>
> >
> > #define BASE 0x87000000
> > #define SIZE 0x600000
> >
> Just an update (thanks to Fernando in pointing this out)
> 0x87000000, 0x600000, fails with same error
> 0x88000000, 0x600000, fails with same error
Wrong attempt!!
Should have tried:
0x87100000, 0x600000 - this worked
> 0x87000000, 0x700000 - went thru 300 odd iterations without error!!
This means that if I keep end address constant, it is fine.. with this hypothesis, I tried
0x87200000, 0x500000 - this also worked

Implying the start address and size of the first allocation in my dummy driver did not have a factor in the test failure, but just the end address of the ioremap!

Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux