From: Eric Volker <evolker@gmail.com>
To: "Gábor Stefanik" <netrolller.3d@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: b43 driver hang with bcm4318
Date: Tue, 19 Jan 2010 20:56:53 -0600 [thread overview]
Message-ID: <1263956213.2316.4.camel@fwdell4550> (raw)
In-Reply-To: <69e28c911001191800t23bab697q6354b07656f78a29@mail.gmail.com>
On Wed, 2010-01-20 at 03:00 +0100, Gábor Stefanik wrote:
> Please load b43 with verbose debug messages enabled (use the "verbose"
> module parameter - check modinfo for the exact value for full debug
> output), and post the resulting logs.
Loaded b43 with verbose=3 to get debug output. The driver hung much more
quickly with debug output enabled. After about 30 seconds of pinging the
AP became unresponsive, though it was still beaconing. Should I post the
logs to the list, or is there somewhere else they should go?
Thanks,
Eric Volker
next prev parent reply other threads:[~2010-01-20 2:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 1:40 b43 driver hang with bcm4318 Eric Volker
2010-01-20 2:00 ` Gábor Stefanik
2010-01-20 2:56 ` Eric Volker [this message]
2010-01-20 3:15 ` Gábor Stefanik
-- strict thread matches above, loose matches on Subject: below --
2010-01-23 22:22 Eric Volker
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=1263956213.2316.4.camel@fwdell4550 \
--to=evolker@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=netrolller.3d@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