[Prism54-devel] [Bug 53] New: kernel BUG at oid_mgt.c:333
bugzilla-daemon@mcgrof.com
bugzilla-daemon@mcgrof.com
Wed, 4 Feb 2004 17:35:47 +0000 (UTC)
http://prism54.org/cgi-bin/bugzilla/show_bug.cgi?id=53
Summary: kernel BUG at oid_mgt.c:333
Product: prim54
Version: 1.0.2.2
Platform: other
OS/Version: Linux 2.6
Status: NEW
Severity: normal
Priority: P2
Component: Device Driver
AssignedTo: prism54-devel@prism54.org
ReportedBy: atrueba@mailandnews.com
In the last few days (since january 29 or 30) I'm getting kernel BUGs at
ksrc/oid_mgt.c, line 333, just after some accesses to the device (iwconfig,
iwlist or so).
System: Debian GNU/Linux unstable
Kernel: 2.6.1
gcc: 3.3.3 Debian prerelease
Wireless-tools: 26+27pre9-2
Card: SMC2835W
<----------------------------------- Syslog ----------------------------------->
(card plug)
Feb 3 19:30:06 localhost pci.agent[872]: kernel driver prism54 already loaded
Feb 3 19:30:06 localhost kernel: Loaded prism54 driver, version 1.0.2.2
Feb 3 19:30:06 localhost kernel: PCI: Enabling device 0000:02:00.0 (0000 ->
0002)
Feb 3 19:30:06 localhost kernel: eth1: prism54 driver detected card model:
SMC2835W
(ifconfig eth1 up)
Feb 3 19:30:27 localhost kernel: eth1: islpci_open()
Feb 3 19:30:27 localhost kernel: eth1: resetting device...
Feb 3 19:30:27 localhost kernel: eth1: uploading firmware...
Feb 3 19:30:28 localhost kernel: eth1: firmware uploaded done, now triggering
reset...
Feb 3 19:30:28 localhost kernel: eth1: mgt_commit has failed. Restart
the device
(some time idle....)
(iwconfig)
(second iwconfig...)
Feb 3 19:30:44 localhost kernel: mgt_get_request(0x12000000): received data
length was bigger ^I^I than expected (62 > 4). Memory is probably
corrupted... ------------[ cut here ]------------
Feb 3 19:30:44 localhost kernel: kernel BUG at /usr/src/prism54-cvs-
latest/ksrc/oid_mgt.c:333!
Feb 3 19:30:44 localhost kernel: invalid operand: 0000 [#1]
Feb 3 19:30:44 localhost kernel: CPU: 0
Feb 3 19:30:44 localhost kernel: EIP: 0060:
[__crc___serio_register_port+2746957/4873734] Not tainted
Feb 3 19:30:44 localhost kernel: EFLAGS: 00010206
Feb 3 19:30:44 localhost kernel: EIP is at mgt_get_request+0x284/0x2a0
[prism54]
Feb 3 19:30:44 localhost kernel: eax: 00000003 ebx: d734becc ecx:
d9fe8200 edx: 00000018
Feb 3 19:30:44 localhost kernel: esi: 00000120 edi: 00000014 ebp:
00000000 esp: d734be6c
Feb 3 19:30:44 localhost kernel: ds: 007b es: 007b ss: 0068
Feb 3 19:30:44 localhost kernel: Process iwconfig (pid: 936,
threadinfo=d734a000 task=d6589360)
Feb 3 19:30:44 localhost kernel: Stack: d813f840 00000000 12000003 00000000
00000004 d734be90 12000003 00000000
Feb 3 19:30:44 localhost kernel: fffffffb 00000000 d734becc d9fe8200
d9c30e80 00000000 ddacf0c9 d9fe8200
Feb 3 19:30:44 localhost kernel: 00000018 00000014 00000000 d734becc
00000000 00000001 ffffffff 00000014
Feb 3 19:30:44 localhost kernel: Call Trace:
Feb 3 19:30:44 localhost kernel:
[__crc___serio_register_port+2733090/4873734] prism54_get_encode+0x129/0x1d0
[prism54]
Feb 3 19:30:44 localhost kernel: [wireless_process_ioctl+632/2080]
wireless_process_ioctl+0x278/0x820
Feb 3 19:30:44 localhost kernel: [do_page_fault+812/1292]
do_page_fault+0x32c/0x50c
Feb 3 19:30:44 localhost kernel:
[__crc___serio_register_port+2732793/4873734] prism54_get_encode+0x0/0x1d0
[prism54]
Feb 3 19:30:44 localhost kernel: [dev_load+37/112] dev_load+0x25/0x70
Feb 3 19:30:44 localhost kernel: [dev_ioctl+656/928] dev_ioctl+0x290/0x3a0
Feb 3 19:30:44 localhost kernel: [sock_ioctl+638/688] sock_ioctl+0x27e/0x2b0
Feb 3 19:30:44 localhost kernel: [sys_ioctl+243/656] sys_ioctl+0xf3/0x290
Feb 3 19:30:44 localhost kernel: [do_page_fault+0/1292]
do_page_fault+0x0/0x50c
Feb 3 19:30:44 localhost kernel: [syscall_call+7/11] syscall_call+0x7/0xb
Feb 3 19:30:44 localhost kernel:
Feb 3 19:30:44 localhost kernel: Code: 0f 0b 4d 01 80 41 ad dd e9 bd fd ff ff
0f 0b 4c 01 80 41 ad
<----------------- End syslog --------------------------------->
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.