From: Christian Lamparter <chunkeey@googlemail.com>
To: Piotr Kaczorek <kacz0r1984@o2.pl>
Cc: linux-wireless@vger.kernel.org
Subject: Re: p54pci randomly fails to load on boot
Date: Thu, 8 Nov 2012 14:28:01 +0100 [thread overview]
Message-ID: <201211081428.01221.chunkeey@googlemail.com> (raw)
In-Reply-To: <509BA46B.40601@o2.pl>
On Thursday, November 08, 2012 01:24:11 PM Piotr Kaczorek wrote:
> We're using miniPCI WiFi cards in our mini-PC's:
> 00:02.0 Network controller: Intersil Corporation ISL3886 [Prism
> Javelin/Prism Xbow] (rev 01)
>
> OS is Debian Lenny with 'custom' kernel (3.2.24 from kernel.org).
>
> The WiFi cards usually work without problems except that from time to
> time they don't start during the boot up process. Here's what I found in
> logs:
> Nov 7 05:12:24 hostname kernel: [ 21.323335] ieee80211 phy0: FW rev
> 2.13.25.0 - Softmac protocol 5.9
> Nov 7 05:12:24 hostname kernel: [ 21.323435] ieee80211 phy0:
> cryptographic accelerator WEP:YES, TKIP:YES, CCMP:YES
> Nov 7 05:12:24 hostname kernel: [ 22.567542] ieee80211 phy0: Cannot
> boot firmware!
> Nov 7 05:12:24 hostname kernel: [ 22.567843] p54pci: probe of
> 0000:00:02.0 failed with error -110
>
> Anybody got an idea why firmware might not have loaded (and did without
> any changes after next reboot 24hrs later)?
-110 is TIMEDOUT and the firmware simply failed to respond "in time". You could
try to increase the timeout [see attached patch] or give the firmware a second
chance.
> Is this a hardware problem with WiFi card (we had few that didn't work
> at all 'out of the box')? Maybe a problem with 'hard disk' (we are using
> Compact Flash cards)?
No, I don't think that your harddisk replacement (compact flash cards) would
cause such a problem. If you can, try the patch and clean up the dust
(connectors and on the card itself - at least this works for my pcmcia cards).
About the cards which "refused" to work: Do you know if these were even
recognized by the system [lspci -vvnn]?
BTW: What happens if you try to reload the module after it failed the first time?
Does it suddenly work? Or do you have to do a warm/cold reboot/restart to get it
working again?
Regards,
Chr
---
diff --git a/drivers/net/wireless/p54/p54pci.c b/drivers/net/wireless/p54/p54pci.c
index b439079..e7a403d 100644
--- a/drivers/net/wireless/p54/p54pci.c
+++ b/drivers/net/wireless/p54/p54pci.c
@@ -128,7 +128,7 @@ static int p54p_upload_firmware(struct ieee80211_hw *dev)
udelay(10);
/* wait for the firmware to boot properly */
- mdelay(100);
+ mdelay(200);
return 0;
}
prev parent reply other threads:[~2012-11-08 13:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-08 12:24 p54pci randomly fails to load on boot Piotr Kaczorek
2012-11-08 13:28 ` Christian Lamparter [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=201211081428.01221.chunkeey@googlemail.com \
--to=chunkeey@googlemail.com \
--cc=kacz0r1984@o2.pl \
--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;
as well as URLs for NNTP newsgroup(s).