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

bugzilla-daemon@mcgrof.com bugzilla-daemon@mcgrof.com
Fri, 20 Feb 2004 15:21:09 +0000 (UTC)


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





------- Additional Comments From atrueba@mailandnews.com  2004-02-20 15:21 -------
Well, here it goes.

(Kernel 2.6.3, gcc 3.3.3-Debian prerelease, module date 20/02/2004)
<-------------------------- Syslog --------------------------->

(card plug)

Feb 20 15:51:00 localhost kernel: Loaded prism54 driver, version 1.0.2.2
Feb 20 15:51:00 localhost kernel: PCI: Enabling device 0000:02:00.0 (0000 -> 0002)
Feb 20 15:51:00 localhost kernel: latency timer: 0
Feb 20 15:51:00 localhost kernel: prism54: pci_set_master(pdev)
Feb 20 15:51:00 localhost kernel: PCI Memory remapped to 0x00000000
Feb 20 15:51:00 localhost kernel: islpci_alloc_memory
Feb 20 15:51:00 localhost kernel: eth1: prism54 driver detected card model: SMC2835W
 
(ifconfig eth1 up)
 
Feb 20 15:51:32 localhost kernel: eth1: islpci_open()
Feb 20 15:51:32 localhost kernel: eth1: resetting device...
Feb 20 15:51:32 localhost kernel: eth1: uploading firmware...
Feb 20 15:51:32 localhost kernel: isl38xx_upload_firmware(0xdda6b000, 0x11380000)
Feb 20 15:51:33 localhost kernel: eth1: firmware uploaded done, now triggering
reset...
Feb 20 15:51:33 localhost kernel: IRQ: Init flag, device initialized

Feb 20 15:51:33 localhost kernel: Device is in active state
Feb 20 15:51:33 localhost kernel: IRQ: Update flag
Feb 20 15:51:33 localhost kernel: IRQ: Update flag
Feb 20 15:51:33 localhost kernel: Received frame in Management Queue
Feb 20 15:51:33 localhost kernel: Wake up Mgmt Queue

(last 5 lines repeated 18 times)

Feb 20 15:51:33 localhost kernel: eth1: mgt_commit has failed. Restart the     
           device

(The following messages were generated while trying some "iwconfig eth1", but
appeared while the card was idle too)

Feb 20 15:51:33 localhost kernel: Device is in active state
Feb 20 15:51:33 localhost kernel: IRQ: Update flag
Feb 20 15:51:33 localhost kernel: IRQ: Update flag
Feb 20 15:51:33 localhost kernel: Received frame in Management Queue
Feb 20 15:51:33 localhost kernel: Wake up Mgmt Queue
Feb 20 15:51:33 localhost kernel: skb offset 2 wds 0
Feb 20 15:51:33 localhost kernel: memmove d7cac804 d7cac802 90
Feb 20 15:51:33 localhost kernel: Device is in active state
Feb 20 15:51:33 localhost kernel: IRQ: Update flag
Feb 20 15:51:33 localhost kernel: cleanup skb d9dd4cc0 skb->data d7cac804
skb->len 90 truesize 1688
Feb 20 15:51:34 localhost kernel:  <7>skb offset 2 wds 0
Feb 20 15:51:34 localhost kernel: memmove c94d7804 c94d7802 78
Feb 20 15:51:34 localhost kernel: Device is in active state
Feb 20 15:51:34 localhost kernel: IRQ: Update flag
Feb 20 15:51:34 localhost kernel: cleanup skb d9dd4cc0 skb->data c94d7804
skb->len 78 truesize 280
Feb 20 15:51:35 localhost kernel:  <7>skb offset 2 wds 0
Feb 20 15:51:35 localhost kernel: memmove c94d7804 c94d7802 70
Feb 20 15:51:35 localhost kernel: Device is in active state
Feb 20 15:51:35 localhost kernel: IRQ: Update flag
Feb 20 15:51:35 localhost kernel: cleanup skb c94dab40 skb->data c94d7804
skb->len 70 truesize 280
Feb 20 15:51:39 localhost kernel:  <7>skb offset 2 wds 0
Feb 20 15:51:39 localhost kernel: memmove c94d7804 c94d7802 70
Feb 20 15:51:39 localhost kernel: Device is in active state
Feb 20 15:51:43 localhost kernel: skb offset 2 wds 0
Feb 20 15:51:43 localhost kernel: memmove cb3df604 cb3df602 70

Feb 20 15:51:43 localhost kernel: Device is in active state
 Feb 20 15:51:49 localhost kernel: IRQ: Update flag
Feb 20 15:51:49 localhost kernel: IRQ: Update flag
Feb 20 15:51:49 localhost kernel: Received frame in Management Queue
Feb 20 15:51:49 localhost kernel: Wake up Mgmt Queue

(repeated 5 more times)

Feb 20 15:51:49 localhost kernel: mgt_get_request(0x12000000): received data
length was bigger ^I^I       than expected (62 > 4). Memory is probably
corrupted... <7>Device is in active state
Feb 20 15:51:49 localhost kernel: IRQ: Update flag
Feb 20 15:51:49 localhost kernel: IRQ: Update flag
Feb 20 15:51:49 localhost kernel: Received frame in Management Queue
Feb 20 15:51:49 localhost kernel: Wake up Mgmt Queue

(15 times)

Feb 20 15:51:56 localhost kernel: eth1: Out of memory, cannot handle oid 0x53540042
Feb 20 15:51:56 localhost kernel: eth1: timeout waiting for mgmt response 1000,
trigging device
Feb 20 15:51:56 localhost kernel: Device is in active state
Feb 20 15:51:57 localhost kernel: eth1: timeout waiting for mgmt response

Feb 20 15:52:03 localhost kernel: Device is in active state
Feb 20 15:52:03 localhost kernel: IRQ: Update flag
Feb 20 15:52:03 localhost kernel: IRQ: Update flag
Feb 20 15:52:03 localhost kernel: Received frame in Management Queue
Feb 20 15:52:03 localhost kernel: Wake up Mgmt Queue

(31 more times)

Feb 20 15:52:04 localhost kernel: ------------[ cut here ]------------
Feb 20 15:52:04 localhost kernel: kernel BUG at
/usr/src/prism54-cvs-latest/ksrc/oid_mgt.c:333!
Feb 20 15:52:04 localhost kernel: invalid operand: 0000 [#1]
Feb 20 15:52:04 localhost kernel: CPU:    0
Feb 20 15:52:04 localhost kernel: EIP:    0060:[_end+494659780/1070244880]   
Not tainted
Feb 20 15:52:04 localhost kernel: EFLAGS: 00010206
Feb 20 15:52:04 localhost kernel: EIP is at mgt_get_request+0x284/0x2a0 [prism54]
Feb 20 15:52:04 localhost kernel: eax: 00000003   ebx: c5ea3ec4   ecx: d00c2220
  edx: 00000018
Feb 20 15:52:04 localhost kernel: esi: 00000120   edi: 00000014   ebp: 00000000
  esp: c5ea3e64
Feb 20 15:52:04 localhost kernel: ds: 007b   es: 007b   ss: 0068
Feb 20 15:52:04 localhost kernel: Process iwconfig (pid: 2493,
threadinfo=c5ea2000 task=d44012a0)
Feb 20 15:52:04 localhost kernel: Stack: d925c7c0 00000000 12000003 00000000
00000004 c5ea3e88 12000003 00000000
Feb 20 15:52:04 localhost kernel:        fffffffb 00000000 c5ea3ec4 d00c2220
d3b577e0 00000000 ddb0e939 d00c2220
Feb 20 15:52:04 localhost kernel:        00000018 00000014 00000000 c5ea3ec4
00000000 00000001 ffffffff 00000014
Feb 20 15:52:04 localhost kernel: Call Trace:
Feb 20 15:52:04 localhost kernel:  [_end+494644553/1070244880]
prism54_get_encode+0x129/0x1d0 [prism54]
Feb 20 15:52:04 localhost kernel:  [wireless_process_ioctl+631/2080]
wireless_process_ioctl+0x277/0x820
Feb 20 15:52:04 localhost kernel:  [_end+494644256/1070244880]
prism54_get_encode+0x0/0x1d0 [prism54]
Feb 20 15:52:04 localhost kernel:  [dev_load+37/112] dev_load+0x25/0x70
Feb 20 15:52:04 localhost kernel:  [dev_ioctl+640/912] dev_ioctl+0x280/0x390
Feb 20 15:52:04 localhost kernel:  [sock_ioctl+640/688] sock_ioctl+0x280/0x2b0
Feb 20 15:52:04 localhost kernel:  [sys_ioctl+243/656] sys_ioctl+0xf3/0x290
Feb 20 15:52:04 localhost kernel:  [do_page_fault+0/1292] do_page_fault+0x0/0x50c
Feb 20 15:52:04 localhost kernel:  [syscall_call+7/11] syscall_call+0x7/0xb
Feb 20 15:52:04 localhost kernel:
Feb 20 15:52:04 localhost kernel: Code: 0f 0b 4d 01 60 45 b1 dd e9 bd fd ff ff
0f 0b 4c 01 60 45 b1

<------------------- End syslog ----------------------------->




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