From: Michael Buesch <mb@bu3sch.de>
To: Martin Fuzzey <mfuzzey@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: b43: firmware loading problem and sleeping BUG
Date: Fri, 6 Nov 2009 19:31:13 +0100 [thread overview]
Message-ID: <200911061931.16509.mb@bu3sch.de> (raw)
In-Reply-To: <ba4215e10911061027t413d2c34g8ad66a7982f7c43c@mail.gmail.com>
On Friday 06 November 2009 19:27:17 Martin Fuzzey wrote:
> [ 109.690000] b43-phy0 ERROR: Firmware file "b43/pcm5.fw" format error.
> So any suggestions on figuring out what is going on?
Your userspace firmware helper (I guess it's not udev on your device?)
might be throwing crap at the kernel.
--
Greetings, Michael.
next prev parent reply other threads:[~2009-11-06 18:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 16:19 b43: firmware loading problem and sleeping BUG Martin Fuzzey
2009-11-06 17:22 ` Michael Buesch
2009-11-06 18:27 ` Martin Fuzzey
2009-11-06 18:31 ` Michael Buesch [this message]
2009-11-09 15:46 ` Martin Fuzzey
2009-11-06 19:08 ` Michael Buesch
2009-11-06 20:45 ` Michael Buesch
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=200911061931.16509.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=linux-wireless@vger.kernel.org \
--cc=mfuzzey@gmail.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 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).