From: Tomasz Chmielewski <mangoo@wpkg.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: prism54: Out of memory, cannot handle oid, card/socket may be faulty, or IRQ line too busy
Date: Sat, 09 Feb 2008 11:00:34 +0100 [thread overview]
Message-ID: <47AD79C2.2050309@wpkg.org> (raw)
In-Reply-To: <20080208221009.GA2919@tuxdriver.com>
John W. Linville schrieb:
> On Fri, Feb 08, 2008 at 11:01:26PM +0100, Tomasz Chmielewski wrote:
>> I just wanted to use a mini-PCI card using a prism54 module - however, it
>> fails to bring the interface up with "Out of memory, cannot handle oid" and
>> "Your card/socket may be faulty, or IRQ line too busy" messages.
>
> I vaguely recall seeing an error like that when I used the wrong
> firmware. What firmware are you using?
So, I tried with 2.7.0.0.arm firmware, and it's the same:
# dmesg
Loaded prism54 driver, version 1.2
PCI: Fixing up device 0000:00:02.0
eth2: resetting device...
eth2: uploading firmware...
eth2: firmware version: 2.7.0.0
eth2: firmware upload complete
eth2: timeout waiting for mgmt response 250, triggering device
eth2: timeout waiting for mgmt response 225, triggering device
eth2: timeout waiting for mgmt response 200, triggering device
eth2: timeout waiting for mgmt response 175, triggering device
eth2: timeout waiting for mgmt response 150, triggering device
eth2: timeout waiting for mgmt response 125, triggering device
eth2: timeout waiting for mgmt response 100, triggering device
eth2: timeout waiting for mgmt response 75, triggering device
eth2: timeout waiting for mgmt response 50, triggering device
eth2: timeout waiting for mgmt response 25, triggering device
eth2: timeout waiting for mgmt response
eth2: mgt_commit_list: failure. oid=ff020008 err=-145
eth2: timeout waiting for mgmt response 250, triggering device
eth2: timeout waiting for mgmt response 225, triggering device
eth2: timeout waiting for mgmt response 200, triggering device
eth2: timeout waiting for mgmt response 175, triggering device
eth2: timeout waiting for mgmt response 150, triggering device
eth2: timeout waiting for mgmt response 125, triggering device
eth2: timeout waiting for mgmt response 100, triggering device
eth2: timeout waiting for mgmt response 75, triggering device
eth2: timeout waiting for mgmt response 50, triggering device
eth2: timeout waiting for mgmt response 25, triggering device
eth2: timeout waiting for mgmt response
eth2: mgt_commit_list: failure. oid=ff020003 err=-145
eth2: timeout waiting for mgmt response 250, triggering device
eth2: timeout waiting for mgmt response 225, triggering device
eth2: timeout waiting for mgmt response 200, triggering device
eth2: timeout waiting for mgmt response 175, triggering device
eth2: timeout waiting for mgmt response 150, triggering device
eth2: timeout waiting for mgmt response 125, triggering device
eth2: timeout waiting for mgmt response 100, triggering device
eth2: timeout waiting for mgmt response 75, triggering device
eth2: timeout waiting for mgmt response 50, triggering device
eth2: timeout waiting for mgmt response 25, triggering device
eth2: timeout waiting for mgmt response
eth2: mgt_commit_list: failure. oid=10000000 err=-145
eth2: timeout waiting for mgmt response 250, triggering device
eth2: timeout waiting for mgmt response 225, triggering device
eth2: timeout waiting for mgmt response 200, triggering device
eth2: timeout waiting for mgmt response 175, triggering device
eth2: timeout waiting for mgmt response 150, triggering device
eth2: timeout waiting for mgmt response 125, triggering device
eth2: timeout waiting for mgmt response 100, triggering device
eth2: timeout waiting for mgmt response 75, triggering device
eth2: timeout waiting for mgmt response 50, triggering device
eth2: timeout waiting for mgmt response 25, triggering device
eth2: timeout waiting for mgmt response
eth2: mgt_commit_list: failure. oid=17000007 err=-145
eth2: mgmt tx queue is still full
eth2: mgt_commit_list: failure. oid=19000001 err=-12
eth2: mgmt tx queue is still full
eth2: mgt_commit_list: failure. oid=10000002 err=-12
eth2: mgmt tx queue is still full
eth2: mgt_commit_list: failure. oid=19000004 err=-12
eth2: mgmt tx queue is still full
eth2: mgt_commit_list: failure. oid=12000000 err=-12
eth2: mgmt tx queue is still full
eth2: mgt_commit_list: failure. oid=12000001 err=-12
eth2: mgmt tx queue is still full
eth2: mgt_commit_list: failure. oid=12000002 err=-12
eth2: mgmt tx queue is still full
eth2: mgt_commit_list: failure. oid=12000004 err=-12
eth2: mgmt tx queue is still full
eth2: mgt_commit_list: failure. oid=12000005 err=-12
eth2: mgmt tx queue is still full
eth2: mgt_commit_list: failure. oid=12000006 err=-12
eth2: mgmt tx queue is still full
eth2: mgt_commit_list: failure. oid=12000007 err=-12
eth2: mgmt tx queue is still full
eth2: mgt_commit_list: failure. oid=12000003 err=-12
eth2: mgmt tx queue is still full
eth2: mgt_commit_list: failure. oid=150007e0 err=-12
eth2: mgmt tx queue is still full
eth2: mgt_commit_list: failure. oid=ff02000c err=-12
eth2: mgmt tx queue is still full
eth2: mgt_commit_list: failure. oid=ff020003 err=-12
eth2: mgmt tx queue is still full
eth2: mgt_update_addr: failure
eth2: mgt_commit: failure
eth2: interface reset failure
prism54: Your card/socket may be faulty, or IRQ line too busy :(
--
Tomasz Chmielewski
http://wpkg.org
next prev parent reply other threads:[~2008-02-09 10:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 22:01 prism54: Out of memory, cannot handle oid, card/socket may be faulty, or IRQ line too busy Tomasz Chmielewski
2008-02-08 22:10 ` John W. Linville
2008-02-08 23:33 ` Tomasz Chmielewski
2008-02-09 10:00 ` Tomasz Chmielewski [this message]
2008-02-09 10:09 ` Tomasz Chmielewski
2008-02-10 1:27 ` Reinhard Biegel
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=47AD79C2.2050309@wpkg.org \
--to=mangoo@wpkg.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.