Hi,

I am using wind river linux with 2.6 kernel version.
I have recompiled my kernel for 64bit. after recompilation, i am getting kernel trace while insmod of one of my module. but insmod returns 0, i.e. successful. To debug the issue, i added return 0 as first line in init function, but still i see traces.

Traces:
[ 41.338523] ------------[ cut here ]------------
[ 41.340001] WARNING: at /../third-party/src/linux/kernel/wrl3/linux-2.6.27_wrl30/kernel/res_counter.c:52 res_counter_uncharge_locked+0x30/0x48()
[ 41.340001] Pid: 127, comm: insmod Tainted: P 2.6.27.47 #1
[ 41.340001]
[ 41.340001] Call Trace:
[ 41.340001] [<ffffffff8023c220>] warn_on_slowpath+0x5d/0x84
[ 41.340001] [<ffffffff802406d1>] ? jiffies_to_msecs+0x9/0x11
[ 41.340001] [<ffffffff8039e095>] ? _raw_spin_unlock+0x83/0xd8
[ 41.340001] [<ffffffff80571b40>] ? _spin_unlock+0xe/0x10
[ 41.340001] [<ffffffff8029bf30>] ? unmap_vmas+0x5a9/0x801
[ 41.340001] [<ffffffff8026bee7>] res_counter_uncharge_locked+0x30/0x48
[ 41.340001] [<ffffffff8026bf2f>] res_counter_uncharge+0x30/0x44
[ 41.340001] [<ffffffff802b22d7>] memrlimit_cgroup_uncharge_as+0x2d/0x2f
[ 41.340001] [<ffffffff802a03ba>] exit_mmap+0x9c/0x10b
[ 41.340001] [<ffffffff80239efc>] mmput+0x41/0xb6
[ 41.340001] [<ffffffff8023df08>] exit_mm+0x107/0x113
[ 41.340001] [<ffffffff80571b13>] ? _spin_unlock_irq+0xe/0x11
[ 41.340001] [<ffffffff8023f8a2>] do_exit+0x257/0x894
[ 41.340001] [<ffffffff8057026c>] ? thread_return+0x3d/0xbc
[ 41.340001] [<ffffffff802a57de>] ? __vunmap+0x12/0xbe
[ 41.340001] [<ffffffff8023ff57>] do_group_exit+0x78/0xa5
[ 41.340001] [<ffffffff8023ff9b>] sys_exit_group+0x17/0x1b
[ 41.340001] [<ffffffff8022b008>] ia32_syscall_done+0x0/0x21
[ 41.340001]
[ 41.340001] ---[ end trace ee1fa00e6608182e ]---

Best Regards,
Pooja

tainted doesn't mean there is a failure but rather that there is something you might not be able to troubleshoot later.

There's a pretty good discussion of this at:
https://www.novell.com/support/kb/doc.php?id=3582750

Thank you for your reply.
You mean I can ignore these traces is it?
How do I make sure everything in kernel is fine n not going to affect anything else?
I am worried because I don't see these traces while running kernel with 32bit.

"Tainted" is purely informational.

A kernel oops means (in this case) the module being inserted is bad. Your module, your responsibility to fix it. Don't rely on 32 bit calls.
Kernel oops should never be ignored - especially when you caused it.

thank you syg00 for your reply.

In my module init function, i have return 0 as first line, hence i am not doing anything just return success.
Still i see these traces in dmesg.
"[ 41.340001] [<ffffffff8022b008>] ia32_syscall_done+0x0/0x21"
In above line, "ia32_syscall_done" is a 32bit function and we should be using different function call for 64bit is it?