[Prism54-devel] [Bug 53] kernel BUG at oid_mgt.c:333

[bugzilla-daemon@mcgrof.com]

http://prism54.org/cgi-bin/bugzilla/show_bug.cgi?id=53





------- Additional Comments From mathiasb@email.dk  2004-05-18 06:22 -------
Hello. I still have kernel bugs quite frequently. they look like this:

------------[ cut here ]------------
kernel BUG at drivers/net/wireless/prism54/oid_mgt.c:492!
invalid operand: 0000 [#1]
PREEMPT
CPU:    0
EIP:    0060:[<dd9522b2>]    Not tainted
EFLAGS: 00210206
EIP is at mgt_get_request+0x2d2/0x2f0 [prism54]
eax: 00000003   ebx: 00000120   ecx: db2b4a20   edx: 00000018
esi: 00000014   edi: d0923520   ebp: 00000000   esp: da0bde6c
ds: 007b   es: 007b   ss: 0068
Process iwconfig (pid: 7782, threadinfo=da0bc000 task=da111360)
Stack: d80d4bc0 00000000 12000003 00000000 00000004 da0bde94 12000003 00000000
       db4fdf60 fffffffb 00000000 da0bded0 db2b4a20 d0923520 00000000 dd94e6dc
       db2b4a20 00000018 00000014 00000000 da0bded0 00000000 00000001 ffffffff
Call Trace:
 [<dd94e6dc>] prism54_get_encode+0x12c/0x1d0 [prism54]
 [<c03c7d46>] wireless_process_ioctl+0x236/0x8c0
 [<c011a080>] do_page_fault+0x340/0x53c
 [<dd94e5b0>] prism54_get_encode+0x0/0x1d0 [prism54]
 [<c03bddfd>] dev_ioctl+0x2bd/0x3e0
 [<c03b4910>] sock_ioctl+0x2d0/0x300
 [<c016a4d3>] sys_ioctl+0xf3/0x2a0
 [<c0119d40>] do_page_fault+0x0/0x53c
 [<c010b41b>] syscall_call+0x7/0xb

Code: 0f 0b ec 01 40 4a 95 dd e9 6f fd ff ff 0f 0b eb 01 40 4a 95

------------[ cut here ]------------
kernel BUG at drivers/net/wireless/prism54/oid_mgt.c:492!
invalid operand: 0000 [#1]
PREEMPT
CPU:    0
EIP:    0060:[<dd9522b2>]    Not tainted
EFLAGS: 00210206
EIP is at mgt_get_request+0x2d2/0x2f0 [prism54]
eax: 00000003   ebx: 00000120   ecx: da746a20   edx: 00000018
esi: 00000014   edi: d08c6740   ebp: 00000000   esp: cdc75e6c
ds: 007b   es: 007b   ss: 0068
Process iwconfig (pid: 7339, threadinfo=cdc74000 task=cf550660)
Stack: d7eb16c0 00000000 12000003 00000000 00000004 cdc75e94 12000003 00000000
       db325f80 fffffffb 00000000 cdc75ed0 da746a20 d08c6740 00000000 dd94e6dc
       da746a20 00000018 00000014 00000000 cdc75ed0 00000000 00000001 ffffffff
Call Trace:
 [<dd94e6dc>] prism54_get_encode+0x12c/0x1d0 [prism54]
 [<c03c7d46>] wireless_process_ioctl+0x236/0x8c0
 [<c011a080>] do_page_fault+0x340/0x53c
 [<dd94e5b0>] prism54_get_encode+0x0/0x1d0 [prism54]
 [<c03bddfd>] dev_ioctl+0x2bd/0x3e0
 [<c03b4910>] sock_ioctl+0x2d0/0x300
 [<c016a4d3>] sys_ioctl+0xf3/0x2a0
 [<c0119d40>] do_page_fault+0x0/0x53c
 [<c010b41b>] syscall_call+0x7/0xb

Code: 0f 0b ec 01 40 4a 95 dd e9 6f fd ff ff 0f 0b eb 01 40 4a 95


I posted two of them, as i thought it might help. Is there any ongoing activity
on trying to fix this bug? i assume its some kind of memory corruption as it has
a comment "/* memory has been freed */" in the code where it bugs...?




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.