hostap_pci: wifi0: detected fid change

[Jar]

On 1.4.2012 12:58, Jar wrote:
> Hello,
>
> I am used the hostap_pci driver as Access Point for many years now for
> my Prism 2.5 PCI card. Now the following messages are started to appear
> to dmesg.
>
> ...
> ...
> wifi0: detected fid change (try=0, reg=0044): 0000 0134 0134
> wifi0: detected fid change (try=0, reg=0044): 015e 015e 89e7
> wifi0: detected fid change (try=0, reg=0044): 0000 0188 0188
> wifi0: detected fid change (try=0, reg=0044): 0000 0149 0149
> ...
> ...
>
> And usually after those messages and after some days or hours, the card
> stops to working, then there are also other error messages (something
> like Card timed out! Resetting card). After that situation I have to
> reboot the PC to get it working again.
>
> I am wondering if this is caused by some hardware problem. Maybe my
> prism card is becoming the end of it's life?

Dmesg shows like this:

------------[ cut here ]------------
WARNING: at net/sched/sch_generic.c:261 dev_watchdog+0x26d/0x280() (Not 
tainted)
Hardware name: ProLiant DL145 G2
NETDEV WATCHDOG: wifi0 (hostap_pci): transmit queue 0 timed out
Modules linked in: usb_storage des_generic md4 nls_utf8 cifs cryptd 
aes_x86_64 aes_generic lib80211_crypt_ccmp nfsd lockd nfs_acl 
auth_rpcgss exportfs autofs4 smsc47m192 hwmon_vid ipmi_devintf ipmi_si 
ipmi_msghandler sunrpc cpufreq_ondemand powernow_k8 freq_table mperf 
michael_mic arc4 ecb lib80211_crypt_tkip act_police sch_ingress cls_u32 
sch_sfq sch_htb iptable_mangle xt_DSCP ipt_MASQUERADE nf_nat_irc 
nf_nat_ftp iptable_nat nf_nat ipt_REJECT xt_mac nf_conntrack_ipv4 
nf_defrag_ipv4 xt_state nf_conntrack_irc nf_conntrack_ftp nf_conntrack 
iptable_filter ip_tables ipv6 hostap_pci hostap lib80211 tg3 sg 
microcode k8temp amd64_edac_mod edac_core edac_mce_amd shpchp 
i2c_nforce2 i2c_core ext4 mbcache jbd2 sd_mod crc_t10dif sata_nv 
pata_acpi ata_generic pata_amd dm_mirror dm_region_hash dm_log dm_mod 
[last unloaded: scsi_wait_scan]
Pid: 0, comm: swapper Not tainted 2.6.32-220.7.1.el6.x86_64 #1
Call Trace:
  <IRQ>  [<ffffffff81069a17>] ? warn_slowpath_common+0x87/0xc0
  [<ffffffff81069b06>] ? warn_slowpath_fmt+0x46/0x50
  [<ffffffff8144a60d>] ? dev_watchdog+0x26d/0x280
  [<ffffffff8107bbe5>] ? internal_add_timer+0xb5/0x110
  [<ffffffff8144a3a0>] ? dev_watchdog+0x0/0x280
  [<ffffffff8107c7f7>] ? run_timer_softirq+0x197/0x340
  [<ffffffff810a0b20>] ? tick_sched_timer+0x0/0xc0
  [<ffffffff8102af2d>] ? lapic_next_event+0x1d/0x30
  [<ffffffff81072001>] ? __do_softirq+0xc1/0x1d0
  [<ffffffff81095610>] ? hrtimer_interrupt+0x140/0x250
  [<ffffffff8100c24c>] ? call_softirq+0x1c/0x30
  [<ffffffff8100de85>] ? do_softirq+0x65/0xa0
  [<ffffffff81071de5>] ? irq_exit+0x85/0x90
  [<ffffffff814f4eb0>] ? smp_apic_timer_interrupt+0x70/0x9b
  [<ffffffff8100bc13>] ? apic_timer_interrupt+0x13/0x20
  <EOI>  [<ffffffff810375eb>] ? native_safe_halt+0xb/0x10
  [<ffffffff810147dd>] ? default_idle+0x4d/0xb0
  [<ffffffff81009e06>] ? cpu_idle+0xb6/0x110
  [<ffffffff814e5ffc>] ? start_secondary+0x202/0x245
---[ end trace 552bef3955975b6d ]---
wifi0 Tx timed out! Resetting card
wifi0: CMD=0011 EVSTAT=0000 OFFSET0=0000 OFFSET1=0000 SWSUPPORT0=8a32
wifi0: scheduled card reset
hostap_pci: wifi0: resetting card
wifi0: Original COR value: 0x32
prism2_hw_init: initialized in 195 ms
...
...

So any clues, should I switch to another hardware?

-- 
Best Regards, Jar