On Sun, Apr 17, 2011 at 13:19, sakthi selvam wrote:
> Dear all,
>
> Thanks for your suggestion. Finally, I identified the
> solution for the permanent issued I faced after loading my kernel module.
> The solution is the kernel macro; 'USE_IMMEDIATE' has to be defined (to be
> given
Dear all,
Thanks for your suggestion. Finally, I identified the
solution for the permanent issued I faced after loading my kernel module.
The solution is the kernel macro; 'USE_IMMEDIATE' has to be defined (to be
given as -DUSE_IMMEDIATE along with compiler flags) during compilatio
Hi sakthi,
On Wed, Mar 23, 2011 at 10:08 PM, sakthi selvam wrote:
> Dear All,
>
> Need your assistance:
>
> Currently I am using Wind River Linux distribution OS with kernel
> version 2.6.27.39 and Wind River version pne-3. After loading of my
> kernel module, I found it was permanent in the kern
On Thu, Mar 24, 2011 at 02:47:15PM +0700, Kacrut wrote:
> On 03/24/2011 01:38 PM, Mulyadi Santosa wrote:
> > On Thu, Mar 24, 2011 at 12:08, sakthi selvam wrote:
> >> But in my case, cleanup module also available in memory, after loading
> >> the module. I used to check using the file in /proc/kall
On 03/24/2011 01:38 PM, Mulyadi Santosa wrote:
> On Thu, Mar 24, 2011 at 12:08, sakthi selvam wrote:
>> But in my case, cleanup module also available in memory, after loading
>> the module. I used to check using the file in /proc/kallsyms for the
>> availability of cleanup module in memory.
> AFAI
On Thu, Mar 24, 2011 at 12:08, sakthi selvam wrote:
> But in my case, cleanup module also available in memory, after loading
> the module. I used to check using the file in /proc/kallsyms for the
> availability of cleanup module in memory.
AFAIK, such thing could happen due to certain data struct
