From: Ivo van Doorn <ivdoorn@gmail.com>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
rt2400-devel@lists.sourceforge.net
Subject: Re: rt2500pci: rt2500pci_bbp_read: Error - BBPCSR register busy. Read failed.
Date: Tue, 19 Aug 2008 20:03:44 +0200 [thread overview]
Message-ID: <200808192003.45072.IvDoorn@gmail.com> (raw)
In-Reply-To: <20080819173524.GA4708@steel.home>
Hi,
> The rt2500 driver in 2.6.27-rc3 (v2.6.27-rc3-552-g3c3a15a) constantly
> produces a lot of this messages in log (slowdown quite noticable):
>
> kernel: phy0 -> rt2500pci_bbp_read: Error - BBPCSR register busy. Read failed.
> kernel: phy0 -> rt2500pci_bbp_write: Error - BBPCSR register busy. Write failed.
> last message repeated 40 times
> kernel: phy0 -> rt2500pci_rf_write: Error - RFCSR register busy. Write failed.
> last message repeated 7 times
> kernel: phy0 -> rt2500pci_bbp_write: Error - BBPCSR register busy. Write failed.
This is a bad sign, the slowdown is expected since the driver is continuously looping
waiting for the registers to become available. Did this PCI card work in the past, and
if so with what driver?
Does this card work on another PC, or does the windows or legacy driver work with
this card?
(Yes, all suggestions above imply suspicion about the hardware itself rather then the driver)
Ivo
> The card is a RaLink RT2500 PCI (not mini-PCI, it is a normal desktop
> system, Gigabyte GA-8IPE1000 motherboard):
>
> 02:04.0 Ethernet controller: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01)
> Subsystem: Micro-Star International Co., Ltd. Unknown device 6834
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR+
> Latency: 32, Cache Line Size: 32 bytes
> Interrupt: pin A routed to IRQ 11
> Region 0: Memory at fa000000 (32-bit, non-prefetchable) [size=8K]
> Capabilities: [40] Power Management version 2
> Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>
> The system is a P4 with HT enabled (and active). The .config is below:
next prev parent reply other threads:[~2008-08-19 18:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 17:35 rt2500pci: rt2500pci_bbp_read: Error - BBPCSR register busy. Read failed Alex Riesen
2008-08-19 18:03 ` Ivo van Doorn [this message]
2008-08-19 18:19 ` Alex Riesen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200808192003.45072.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=raa.lkml@gmail.com \
--cc=rt2400-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox