[Prism54-devel] XG-901 troubles after 15 minutes
Bob Beers
bob.beers at gmail.com
Thu May 5 21:31:43 UTC 2005
Hello list,
I have a ZCom XG-901 which seems fine in Master and managed mode,
but craps out after ~15 minutes, even with minimal traffic on the wireless
side, only one windows station associated. Removeing and reinserting
module does bring it back.
This may be similar to problem in BUG 116, but I'm using
kernel 2.6.10 and prism54 driver from same, and firmware 1.0.4.3.
It's pretty easy to replicate, can I provide some more data?
iwconfig says no wireless extensions after the failure.
-bash-3.00# lspci -s 00:09 -v -v
00:09.0 Class 0280: 1260:3890 (rev 01)
Subsystem: 17cf:0020
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 80 (2500ns min, 7000ns max), cache line size 08
Interrupt: pin A routed to IRQ 11
Region 0: Memory at d0000000 (32-bit, non-prefetchable) [size=8K]
Capabilities: [dc] Power Management version 1
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
I'll put my dmesg and /var/log/debug output below:
-bash-3.00# dmesg
Linux version 2.6.10 (bbeers at alakazam) (gcc version 3.3.4) #23 Mon May
2 16:34:50 EDT 2005
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 0000000000095400 (usable)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 0000000004000000 (usable)
BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved)
64MB LOWMEM available.
On node 0 totalpages: 16384
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 12288 pages, LIFO batch:3
HighMem zone: 0 pages, LIFO batch:1
DMI not present.
Built 1 zonelists
Kernel command line: auto BOOT_IMAGE=EdgeIAD_rt ro root=100 ramdisk=32768
Initializing CPU#0
PID hash table entries: 512 (order: 9, 8192 bytes)
Detected 266.674 MHz processor.
Using tsc for high-res timesource
Console: colour dummy device 80x25
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 51644k/65536k available (1975k kernel code, 13432k reserved,
601k data, 164k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay loop... 523.26 BogoMIPS (lpj=261632)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: After generic identify, caps: 00808131 01818131 00000000 00000000
CPU: After vendor identify, caps: 00808131 01818131 00000000 00000000
CPU: After all inits, caps: 00808131 00818131 00000000 00000001
CPU: NSC Unknown stepping 01
Checking 'hlt' instruction... OK.
checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
Freeing initrd memory: 9812k freed
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xfc41d, last bus=0
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
Linux Plug and Play Support v0.97 (c) Adam Belay
SCSI subsystem initialized
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Device 00:95 not found by BIOS
apm: BIOS not found.
Initializing Cryptographic API
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
vesafb: probe of vesafb0 failed with error -6
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Real Time Clock Driver v1.12
i8042.c: Can't read CTR while initializing i8042.
Serial: 8250/16550 driver $Revision: 1.90 $ 48 ports, IRQ sharing enabled
ttyS0 at I/O 0x3f8 (irq = 4) is a NS16550A
ttyS1 at I/O 0x2f8 (irq = 0) is a NS16550A
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
elevator: using anticipatory as default io scheduler
Floppy drive(s): fd0 is 720k, fd1 is 720k
floppy0: no floppy controllers found
RAMDISK driver initialized: 16 RAM disks of 32768K size 1024 blocksize
divert: not allocating divert_blk for non-ethernet device lo
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Probing IDE interface ide0...
ide0: Wait for ready failed before probe !
Probing IDE interface ide1...
ide1: Wait for ready failed before probe !
Probing IDE interface ide2...
ide2: Wait for ready failed before probe !
Probing IDE interface ide3...
ide3: Wait for ready failed before probe !
Probing IDE interface ide4...
ide4: Wait for ready failed before probe !
Probing IDE interface ide5...
ide5: Wait for ready failed before probe !
ide-floppy driver 0.99.newide
NFTL driver: nftlcore.c $Revision: 1.97 $, nftlmount.c $Revision: 1.40 $
DiskOnChip found at 0xc8000
DiskOnChip 2000 responds to DWORD access
Detected 1 chips per floor.
NAND device: Manufacturer ID: 0x98, Chip ID: 0x73 (Toshiba NAND 16MiB
3,3V 8-bit)
Found DiskOnChip ANAND Media Header at 0x10000
Found DiskOnChip ANAND Media Header at 0x14000
DataOrgID = ANAND
NumEraseUnits = 1020
FirstPhysicalEUN = 4
FormattedSize = 16318464
UnitSizeFactor = 0
UnitSizeFactor=0x00 detected. Correct value is assumed to be 0xff.
Bad block table at page 129, version 0x55
Bad block table at page 161, version 0x55
nftla: nftla1 nftla2
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.0:USB HID core driver
mice: PS/2 mouse device common for all mice
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind 8192)
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 164k freed
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
eepro100.c:v1.09j-t 9/29/99 Donald Becker
http://www.scyld.com/network/eepro100.html
eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V.
Savochkin <saw at saw.sw.com.sg> and others
eth0: OEM i82557/i82558 10/100 Ethernet, 00:50:C2:0F:F3:00, IRQ 12.
Receiver lock-up bug exists -- enabling work-around.
Board assembly 177503-103, Physical connectors present: BNC
Primary interface chip i82553-A/B PHY #7.
Secondary interface chip i82555.
General self-test: passed.
Serial sub-system self-test: passed.
Internal registers self-test: passed.
ROM checksum self-test: passed (0xd0a6c714).
Receiver lock-up workaround activated.
divert: allocating divert_blk for eth0
eth1: OEM i82557/i82558 10/100 Ethernet, 00:50:C2:0F:F3:01, IRQ 10.
Receiver lock-up bug exists -- enabling work-around.
Board assembly 177503-103, Physical connectors present: BNC
Primary interface chip i82553-A/B PHY #7.
Secondary interface chip i82555.
General self-test: passed.
Serial sub-system self-test: passed.
Internal registers self-test: passed.
ROM checksum self-test: passed (0xd0a6c714).
Receiver lock-up workaround activated.
divert: allocating divert_blk for eth1
Loaded prism54 driver, version 1.2
divert: allocating divert_blk for eth2
wlan0: resetting device...
wlan0: uploading firmware...
wlan0: firmware version: 1.0.4.3
wlan0: firmware upload complete
wlan0: interface reset complete
ip_tables: (C) 2000-2002 Netfilter core team
ip_conntrack version 2.1 (512 buckets, 4096 max) - 300 bytes per conntrack
wd1100: module license 'unspecified' taints kernel.
SC1x00 Watchdog driver by Inprimis Technolgies.
wd1100.c: a few hacks by erich.titl at think.ch
vhub driver vhub 13.
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
NETDEV WATCHDOG: wlan0: transmit timed out
wlan0: tx_timeout, scheduling a reset
wlan0: resetting device...
wlan0: uploading firmware...
wlan0: firmware version: 1.0.4.3
wlan0: firmware upload complete
wlan0: timeout waiting for mgmt response 1000, triggering device
wlan0: timeout waiting for mgmt response 900, triggering device
wlan0: timeout waiting for mgmt response 800, triggering device
wlan0: timeout waiting for mgmt response 700, triggering device
wlan0: timeout waiting for mgmt response 600, triggering device
wlan0: timeout waiting for mgmt response 500, triggering device
wlan0: timeout waiting for mgmt response 400, triggering device
wlan0: timeout waiting for mgmt response 300, triggering device
wlan0: timeout waiting for mgmt response 200, triggering device
wlan0: timeout waiting for mgmt response 100, triggering device
wlan0: timeout waiting for mgmt response
wlan0: mgt_commit_list: failure. oid=ff020008 err=-110
wlan0: timeout waiting for mgmt response 1000, triggering device
wlan0: timeout waiting for mgmt response 900, triggering device
wlan0: timeout waiting for mgmt response 800, triggering device
NETDEV WATCHDOG: wlan0: transmit timed out
wlan0: tx_timeout
wlan0: timeout waiting for mgmt response 700, triggering device
wlan0: timeout waiting for mgmt response 600, triggering device
wlan0: timeout waiting for mgmt response 500, triggering device
wlan0: timeout waiting for mgmt response 400, triggering device
wlan0: timeout waiting for mgmt response 300, triggering device
wlan0: timeout waiting for mgmt response 200, triggering device
wlan0: timeout waiting for mgmt response 100, triggering device
wlan0: timeout waiting for mgmt response
wlan0: mgt_commit_list: failure. oid=ff020003 err=-110
wlan0: timeout waiting for mgmt response 1000, triggering device
wlan0: timeout waiting for mgmt response 900, triggering device
wlan0: timeout waiting for mgmt response 800, triggering device
wlan0: timeout waiting for mgmt response 700, triggering device
wlan0: timeout waiting for mgmt response 600, triggering device
wlan0: timeout waiting for mgmt response 500, triggering device
wlan0: timeout waiting for mgmt response 400, triggering device
wlan0: timeout waiting for mgmt response 300, triggering device
wlan0: timeout waiting for mgmt response 200, triggering device
wlan0: timeout waiting for mgmt response 100, triggering device
wlan0: timeout waiting for mgmt response
wlan0: mgt_commit_list: failure. oid=10000000 err=-110
wlan0: timeout waiting for mgmt response 1000, triggering device
wlan0: timeout waiting for mgmt response 900, triggering device
wlan0: timeout waiting for mgmt response 800, triggering device
NETDEV WATCHDOG: wlan0: transmit timed out
wlan0: tx_timeout
wlan0: timeout waiting for mgmt response 700, triggering device
wlan0: timeout waiting for mgmt response 600, triggering device
wlan0: timeout waiting for mgmt response 500, triggering device
wlan0: timeout waiting for mgmt response 400, triggering device
wlan0: timeout waiting for mgmt response 300, triggering device
wlan0: timeout waiting for mgmt response 200, triggering device
wlan0: timeout waiting for mgmt response 100, triggering device
wlan0: timeout waiting for mgmt response
wlan0: mgt_commit_list: failure. oid=17000007 err=-110
wlan0: mgmt tx queue is still full
wlan0: mgt_commit_list: failure. oid=19000001 err=-12
wlan0: mgmt tx queue is still full
wlan0: mgt_commit_list: failure. oid=10000002 err=-12
wlan0: mgmt tx queue is still full
wlan0: mgt_commit_list: failure. oid=19000004 err=-12
wlan0: mgmt tx queue is still full
wlan0: mgt_commit_list: failure. oid=12000000 err=-12
wlan0: mgmt tx queue is still full
wlan0: mgt_commit_list: failure. oid=12000001 err=-12
wlan0: mgmt tx queue is still full
wlan0: mgt_commit_list: failure. oid=12000002 err=-12
wlan0: mgmt tx queue is still full
wlan0: mgt_commit_list: failure. oid=12000004 err=-12
wlan0: mgmt tx queue is still full
wlan0: mgt_commit_list: failure. oid=12000005 err=-12
wlan0: mgmt tx queue is still full
wlan0: mgt_commit_list: failure. oid=12000006 err=-12
wlan0: mgmt tx queue is still full
wlan0: mgt_commit_list: failure. oid=12000007 err=-12
wlan0: mgmt tx queue is still full
wlan0: mgt_commit_list: failure. oid=12000003 err=-12
wlan0: mgmt tx queue is still full
wlan0: mgt_commit_list: failure. oid=150007e0 err=-12
wlan0: mgmt tx queue is still full
wlan0: mgt_commit_list: failure. oid=ff02000c err=-12
wlan0: mgmt tx queue is still full
wlan0: mgt_commit_list: failure. oid=ff020003 err=-12
wlan0: mgmt tx queue is still full
wlan0: mgt_update_addr: failure
wlan0: mgt_commit: failure
wlan0: interface reset failure
prism54: Your card/socket may be faulty, or IRQ line too busy :(
NETDEV WATCHDOG: wlan0: transmit timed out
wlan0: tx_timeout, scheduling a reset
wlan0: resetting device...
wlan0: uploading firmware...
wlan0: firmware version: 1.0.4.3
wlan0: firmware upload complete
wlan0: timeout waiting for mgmt response 1000, triggering device
wlan0: timeout waiting for mgmt response 900, triggering device
wlan0: timeout waiting for mgmt response 800, triggering device
wlan0: timeout waiting for mgmt response 700, triggering device
wlan0: timeout waiting for mgmt response 600, triggering device
wlan0: timeout waiting for mgmt response 500, triggering device
wlan0: timeout waiting for mgmt response 400, triggering device
wlan0: timeout waiting for mgmt response 300, triggering device
wlan0: timeout waiting for mgmt response 200, triggering device
wlan0: timeout waiting for mgmt response 100, triggering device
wlan0: timeout waiting for mgmt response
wlan0: mgt_commit_list: failure. oid=ff020008 err=-110
wlan0: timeout waiting for mgmt response 1000, triggering device
wlan0: timeout waiting for mgmt response 900, triggering device
wlan0: timeout waiting for mgmt response 800, triggering device
wlan0: timeout waiting for mgmt response 700, triggering device
NETDEV WATCHDOG: wlan0: transmit timed out
wlan0: tx_timeout
wlan0: timeout waiting for mgmt response 600, triggering device
wlan0: timeout waiting for mgmt response 500, triggering device
-bash-3.00#
bash-3.00# cat /var/log/debug
Jan 1 00:01:24 rt_hay kernel: On node 0 totalpages: 16384
Jan 1 00:01:24 rt_hay kernel: DMA zone: 4096 pages, LIFO batch:1
Jan 1 00:01:24 rt_hay kernel: Normal zone: 12288 pages, LIFO batch:3
Jan 1 00:01:24 rt_hay kernel: HighMem zone: 0 pages, LIFO batch:1
Jan 1 00:01:24 rt_hay kernel: Calibrating delay loop... 523.26
BogoMIPS (lpj=261632)
Jan 1 00:01:24 rt_hay kernel: CPU: After generic identify, caps:
00808131 01818131 00000000 00000000
Jan 1 00:01:24 rt_hay kernel: CPU: After vendor identify, caps:
00808131 01818131 00000000 00000000
Jan 1 00:01:24 rt_hay kernel: CPU: After all inits, caps:
00808131 00818131 00000000 00000001
Jan 1 00:01:24 rt_hay kernel: divert: not allocating divert_blk for
non-ethernet device lo
Jan 1 00:01:24 rt_hay kernel: Probing IDE interface ide0...
Jan 1 00:01:24 rt_hay kernel: ide0: Wait for ready failed before probe !
Jan 1 00:01:24 rt_hay kernel: Probing IDE interface ide1...
Jan 1 00:01:24 rt_hay kernel: ide1: Wait for ready failed before probe !
Jan 1 00:01:24 rt_hay kernel: Probing IDE interface ide2...
Jan 1 00:01:24 rt_hay kernel: ide2: Wait for ready failed before probe !
Jan 1 00:01:24 rt_hay kernel: Probing IDE interface ide3...
Jan 1 00:01:24 rt_hay kernel: ide3: Wait for ready failed before probe !
Jan 1 00:01:24 rt_hay kernel: Probing IDE interface ide4...
Jan 1 00:01:24 rt_hay kernel: ide4: Wait for ready failed before probe !
Jan 1 00:01:24 rt_hay kernel: Probing IDE interface ide5...
Jan 1 00:01:24 rt_hay kernel: ide5: Wait for ready failed before probe !
Jan 1 00:01:24 rt_hay kernel: Detected 1 chips per floor.
Jan 1 00:01:24 rt_hay kernel: Bad block table at page 129, version 0x55
Jan 1 00:01:24 rt_hay kernel: Bad block table at page 161, version 0x55
Jan 1 00:01:24 rt_hay kernel: divert: allocating divert_blk for eth0
Jan 1 00:01:24 rt_hay kernel: divert: allocating divert_blk for eth1
Jan 1 00:01:24 rt_hay kernel: divert: allocating divert_blk for eth2
Jan 1 00:01:24 rt_hay kernel: wlan0: resetting device...
Jan 1 00:01:24 rt_hay kernel: wlan0: uploading firmware...
Jan 1 00:01:24 rt_hay kernel: wlan0: firmware version: 1.0.4.3
Jan 1 00:01:24 rt_hay kernel: wlan0: firmware upload complete
Jan 1 00:01:24 rt_hay kernel: wlan0: interface reset complete
May 5 20:55:38 rt_hay kernel: wlan0: resetting device...
May 5 20:55:38 rt_hay kernel: wlan0: uploading firmware...
May 5 20:55:38 rt_hay kernel: wlan0: firmware version: 1.0.4.3
May 5 20:55:38 rt_hay kernel: wlan0: firmware upload complete
May 5 20:55:38 rt_hay kernel: wlan0: timeout waiting for mgmt
response 1000, triggering device
May 5 20:55:38 rt_hay kernel: wlan0: timeout waiting for mgmt
response 900, triggering device
May 5 20:55:38 rt_hay kernel: wlan0: timeout waiting for mgmt
response 800, triggering device
May 5 20:55:38 rt_hay kernel: wlan0: timeout waiting for mgmt
response 700, triggering device
May 5 20:55:39 rt_hay kernel: wlan0: timeout waiting for mgmt
response 600, triggering device
May 5 20:55:39 rt_hay kernel: wlan0: timeout waiting for mgmt
response 500, triggering device
May 5 20:55:39 rt_hay kernel: wlan0: timeout waiting for mgmt
response 400, triggering device
May 5 20:55:39 rt_hay kernel: wlan0: timeout waiting for mgmt
response 300, triggering device
May 5 20:55:39 rt_hay kernel: wlan0: timeout waiting for mgmt
response 200, triggering device
May 5 20:55:39 rt_hay kernel: wlan0: timeout waiting for mgmt
response 100, triggering device
May 5 20:55:39 rt_hay kernel: wlan0: timeout waiting for mgmt
response 1000, triggering device
May 5 20:55:39 rt_hay kernel: wlan0: timeout waiting for mgmt
response 900, triggering device
May 5 20:55:39 rt_hay kernel: wlan0: timeout waiting for mgmt
response 800, triggering device
May 5 20:55:39 rt_hay kernel: wlan0: timeout waiting for mgmt
response 700, triggering device
May 5 20:55:40 rt_hay kernel: wlan0: timeout waiting for mgmt
response 600, triggering device
May 5 20:55:40 rt_hay kernel: wlan0: timeout waiting for mgmt
response 500, triggering device
May 5 20:55:40 rt_hay kernel: wlan0: timeout waiting for mgmt
response 400, triggering device
May 5 20:55:40 rt_hay kernel: wlan0: timeout waiting for mgmt
response 300, triggering device
May 5 20:55:40 rt_hay kernel: wlan0: timeout waiting for mgmt
response 200, triggering device
May 5 20:55:40 rt_hay kernel: wlan0: timeout waiting for mgmt
response 100, triggering device
May 5 20:55:40 rt_hay kernel: wlan0: timeout waiting for mgmt
response 1000, triggering device
May 5 20:55:40 rt_hay kernel: wlan0: timeout waiting for mgmt
response 900, triggering device
May 5 20:55:40 rt_hay kernel: wlan0: timeout waiting for mgmt
response 800, triggering device
May 5 20:55:40 rt_hay kernel: wlan0: timeout waiting for mgmt
response 700, triggering device
May 5 20:55:41 rt_hay kernel: wlan0: timeout waiting for mgmt
response 600, triggering device
May 5 20:55:41 rt_hay kernel: wlan0: timeout waiting for mgmt
response 500, triggering device
May 5 20:55:41 rt_hay kernel: wlan0: timeout waiting for mgmt
response 400, triggering device
May 5 20:55:41 rt_hay kernel: wlan0: timeout waiting for mgmt
response 300, triggering device
May 5 20:55:41 rt_hay kernel: wlan0: timeout waiting for mgmt
response 200, triggering device
May 5 20:55:41 rt_hay kernel: wlan0: timeout waiting for mgmt
response 100, triggering device
May 5 20:55:41 rt_hay kernel: wlan0: timeout waiting for mgmt
response 1000, triggering device
May 5 20:55:41 rt_hay kernel: wlan0: timeout waiting for mgmt
response 900, triggering device
May 5 20:55:41 rt_hay kernel: wlan0: timeout waiting for mgmt
response 800, triggering device
May 5 20:55:41 rt_hay kernel: wlan0: timeout waiting for mgmt
response 700, triggering device
May 5 20:55:42 rt_hay kernel: wlan0: timeout waiting for mgmt
response 600, triggering device
May 5 20:55:42 rt_hay kernel: wlan0: timeout waiting for mgmt
response 500, triggering device
May 5 20:55:42 rt_hay kernel: wlan0: timeout waiting for mgmt
response 400, triggering device
May 5 20:55:42 rt_hay kernel: wlan0: timeout waiting for mgmt
response 300, triggering device
May 5 20:55:42 rt_hay kernel: wlan0: timeout waiting for mgmt
response 200, triggering device
May 5 20:55:42 rt_hay kernel: wlan0: timeout waiting for mgmt
response 100, triggering device
May 5 20:55:42 rt_hay kernel: wlan0: mgt_commit: failure
May 5 20:57:58 rt_hay kernel: wlan0: resetting device...
May 5 20:57:58 rt_hay kernel: wlan0: uploading firmware...
May 5 20:57:58 rt_hay kernel: wlan0: firmware version: 1.0.4.3
May 5 20:57:58 rt_hay kernel: wlan0: firmware upload complete
May 5 20:57:58 rt_hay kernel: wlan0: timeout waiting for mgmt
response 1000, triggering device
May 5 20:57:58 rt_hay kernel: wlan0: timeout waiting for mgmt
response 900, triggering device
May 5 20:57:58 rt_hay kernel: wlan0: timeout waiting for mgmt
response 800, triggering device
May 5 20:57:58 rt_hay kernel: wlan0: timeout waiting for mgmt
response 700, triggering device
May 5 20:57:59 rt_hay kernel: wlan0: timeout waiting for mgmt
response 600, triggering device
May 5 20:57:59 rt_hay kernel: wlan0: timeout waiting for mgmt
response 500, triggering device
May 5 20:57:59 rt_hay kernel: wlan0: timeout waiting for mgmt
response 400, triggering device
May 5 20:57:59 rt_hay kernel: wlan0: timeout waiting for mgmt
response 300, triggering device
May 5 20:57:59 rt_hay kernel: wlan0: timeout waiting for mgmt
response 200, triggering device
May 5 20:57:59 rt_hay kernel: wlan0: timeout waiting for mgmt
response 100, triggering device
May 5 20:57:59 rt_hay kernel: wlan0: timeout waiting for mgmt
response 1000, triggering device
May 5 20:57:59 rt_hay kernel: wlan0: timeout waiting for mgmt
response 900, triggering device
May 5 20:57:59 rt_hay kernel: wlan0: timeout waiting for mgmt
response 800, triggering device
May 5 20:57:59 rt_hay kernel: wlan0: timeout waiting for mgmt
response 700, triggering device
May 5 20:58:00 rt_hay kernel: wlan0: timeout waiting for mgmt
response 600, triggering device
May 5 20:58:00 rt_hay kernel: wlan0: timeout waiting for mgmt
response 500, triggering device
May 5 20:58:00 rt_hay kernel: wlan0: timeout waiting for mgmt
response 400, triggering device
May 5 20:58:00 rt_hay kernel: wlan0: timeout waiting for mgmt
response 300, triggering device
May 5 20:58:00 rt_hay kernel: wlan0: timeout waiting for mgmt
response 200, triggering device
May 5 20:58:00 rt_hay kernel: wlan0: timeout waiting for mgmt
response 100, triggering device
May 5 20:58:00 rt_hay kernel: wlan0: timeout waiting for mgmt
response 1000, triggering device
May 5 20:58:00 rt_hay kernel: wlan0: timeout waiting for mgmt
response 900, triggering device
May 5 20:58:00 rt_hay kernel: wlan0: timeout waiting for mgmt
response 800, triggering device
May 5 20:58:00 rt_hay kernel: wlan0: timeout waiting for mgmt
response 700, triggering device
May 5 20:58:01 rt_hay kernel: wlan0: timeout waiting for mgmt
response 600, triggering device
May 5 20:58:01 rt_hay kernel: wlan0: timeout waiting for mgmt
response 500, triggering device
May 5 20:58:01 rt_hay kernel: wlan0: timeout waiting for mgmt
response 400, triggering device
May 5 20:58:01 rt_hay kernel: wlan0: timeout waiting for mgmt
response 300, triggering device
May 5 20:58:01 rt_hay kernel: wlan0: timeout waiting for mgmt
response 200, triggering device
May 5 20:58:01 rt_hay kernel: wlan0: timeout waiting for mgmt
response 100, triggering device
May 5 20:58:01 rt_hay kernel: wlan0: timeout waiting for mgmt
response 1000, triggering device
May 5 20:58:01 rt_hay kernel: wlan0: timeout waiting for mgmt
response 900, triggering device
May 5 20:58:01 rt_hay kernel: wlan0: timeout waiting for mgmt
response 800, triggering device
May 5 20:58:01 rt_hay kernel: wlan0: timeout waiting for mgmt
response 700, triggering device
May 5 20:58:02 rt_hay kernel: wlan0: timeout waiting for mgmt
response 600, triggering device
May 5 20:58:02 rt_hay kernel: wlan0: timeout waiting for mgmt
response 500, triggering device
May 5 20:58:02 rt_hay kernel: wlan0: timeout waiting for mgmt
response 400, triggering device
May 5 20:58:02 rt_hay kernel: wlan0: timeout waiting for mgmt
response 300, triggering device
May 5 20:58:02 rt_hay kernel: wlan0: timeout waiting for mgmt
response 200, triggering device
May 5 20:58:02 rt_hay kernel: wlan0: timeout waiting for mgmt
response 100, triggering device
May 5 20:58:02 rt_hay kernel: wlan0: mgt_commit: failure
-bash-3.00#
Thanks,
-Bob
More information about the Prism54-devel
mailing list