From: "Alex Riesen" <raa.lkml@gmail.com>
To: "Ivo van Doorn" <ivdoorn@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: rt2500pci: rt2500pci_bbp_read: Error - BBPCSR register busy. Read failed.
Date: Tue, 19 Aug 2008 20:19:56 +0200 [thread overview]
Message-ID: <81b0412b0808191119y3fe473bbi43ca5524ff4d20ac@mail.gmail.com> (raw)
In-Reply-To: <200808192003.45072.IvDoorn@gmail.com>
2008/8/19 Ivo van Doorn <ivdoorn@gmail.com>:
>> 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?
It surely did, but I honestly don't remember what with. I'll try to bisect.
> Does this card work on another PC, or does the windows or legacy driver work with
> this card?
No Windows here, but see below
> (Yes, all suggestions above imply suspicion about the hardware itself rather then the driver)
Well, it used to crash some industrial board (I believe it was some
Boser, HS-series, with
this card in a PCI slot of its backplane). So you're not alone in your
suspicions (OTOH,
that board was known to misbehave itself).
I have no particular need for that card, so if someone wants it for
testing I gladly
part with it (and if you happen be in Germany, I'll just mail it).
prev parent reply other threads:[~2008-08-19 18:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 17:35 Alex Riesen
2008-08-19 18:03 ` Ivo van Doorn
2008-08-19 18:19 ` Alex Riesen [this message]
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=81b0412b0808191119y3fe473bbi43ca5524ff4d20ac@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=ivdoorn@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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
all inboxes | Powered by JetHome®