On 18-08-08 16:53, Gagan Grover wrote:
I am getting below problem. What is the reason behind this ?
Somebody probably forgot to release a lock.
[ ... ]
Modules linked in: dbg(U) ccp_ib(U) ccp(U) xpc4drvr(U) windrvr6(U) md5
ipv6 parport_pc lp parport autofs4 i2c_dev i2c_core nfs lockd nfs_acl
sunrpc rdma_ucd
Pid: 29040, comm: dbg_mr_create Tainted: PF 2.6.9-42.ELsmp
RIP: 0010:[<ffffffff80309dfa>] <ffffffff80309dfa>{schedule+2164}
RSP: 0018:0000010129527eb0 EFLAGS: 00010006
RAX: 00000012a1d00000 RBX: 0000010005d42030 RCX: 0000000000000003
RDX: ffffffff8051ad60 RSI: 0000010138a927f0 RDI: 0000010138a927f0
RBP: 0000010129527f70 R08: ffffffff803e1ee8 R09: 0000000000000000
R10: 0000000100000000 R11: 0000000000000021 R12: 0000010001045120
R13: 0000010138a927f0 R14: 00000100010447e0 R15: 00000100010547e0
FS: 0000002a95579b00(0000) GS:ffffffff804e5080(0000)
knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00000012221e5088 CR3: 0000000000101000 CR4: 00000000000006e0
Process dbg_mr_create (pid: 29040, threadinfo 0000010129526000, task
0000010138a927f0)
Stack: 0000010129538b88 0000001900000075 0000010138a927f0 0000000000000075
0000010001045a40 0000000037f05c80 0000010138a927f0 00000000055e8de4
000122486d3e5ad1 0000010138a927f0
Call Trace:<ffffffff80178e44>{filp_close+103}
<ffffffff801102d4>{sysret_careful+13}
And the somebody is probably one of those tainting modules. I believe
this is stuff from:
http://stefan.endrullis.de/en/xilinx_ise_7.1.html
Right? Looking at the linuxdrivers.tar.gz tarball I see binary archives
meaning we can't help with that here -- we don't have the source to look
for the problem. Any and all support will have to come from whomever
supplied you with it.
Rene.
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ
