linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Forest Bond <forest@alittletooquiet.net>
To: Michael Buesch <mb@bu3sch.de>
Cc: bcm43xx-dev@lists.berlios.de, linux-wireless@vger.kernel.org,
	John Linville <linville@tuxdriver.com>
Subject: Re: b43: Everybody with PHY TX error, please try
Date: Mon, 3 Nov 2008 20:39:56 -0500	[thread overview]
Message-ID: <20081104013956.GB483@storm.local.network> (raw)
In-Reply-To: <200810242032.04295.mb@bu3sch.de>

[-- Attachment #1: Type: text/plain, Size: 2073 bytes --]

Hi,

On Fri, Oct 24, 2008 at 08:32:04PM +0200, Michael Buesch wrote:
> Everybody with PHY TX error, please try updated firmware from
> ftp://ftp.linksys.com/opensourcecode/wrt610n/1.00.00.018/wrt610n_v1.00.00.018_us.tgz
> (Yeah, big tarball. It's 87MB)

Sorry, I'm arriving to this late.  I'm seeing the following:

[30447.008408] __ratelimit: 2795 callbacks suppressed
[30447.008466] b43-phy0 ERROR: PHY transmission error
[30447.008496] b43-phy0 ERROR: PHY transmission error
[30447.008523] b43-phy0 ERROR: PHY transmission error
[30447.008551] b43-phy0 ERROR: PHY transmission error
[30447.008577] b43-phy0 ERROR: PHY transmission error
[30447.008606] b43-phy0 ERROR: PHY transmission error
[30447.008634] b43-phy0 ERROR: PHY transmission error
[30447.008662] b43-phy0 ERROR: PHY transmission error
[30447.008690] b43-phy0 ERROR: PHY transmission error
[30447.384079] b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
[30447.500347] b43-pci-bridge 0000:02:00.0: PCI: Disallowing DAC for device
[30447.500376] b43-phy0: DMA mask fallback from 64-bit to 32-bit
[30447.526191] Registered led device: b43-phy0::tx
[30447.526960] Registered led device: b43-phy0::rx
[30447.527543] Registered led device: b43-phy0::radio
[30454.780114] wlan1: No ProbeResp from current AP 00:1e:2a:e4:de:84 - assume out of range
[30455.681012] wlan1: authenticate with AP 00:1e:2a:e4:de:84
[30455.682225] wlan1: authenticate with AP 00:1e:2a:e4:de:84
[30455.684847] wlan1: authenticated
[30455.684873] wlan1: associate with AP 00:1e:2a:e4:de:84
[30455.688707] wlan1: RX ReassocResp from 00:1e:2a:e4:de:84 (capab=0x411 status=0 aid=1)
[30455.688730] wlan1: associated

This happens repeatedly during file transfers.  Everything is quite slow.  You
can see that the device was reset.

Will the firmware upgrade fix this?  Must I be running the latest b43 driver to
use the new firmware?

I'm on Ubuntu 8.10 with kernel version 2.6.27-7-generic.

Thanks,
Forest
-- 
Forest Bond
http://www.alittletooquiet.net
http://www.pytagsfs.org

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2008-11-04  3:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-24 18:32 b43: Everybody with PHY TX error, please try Michael Buesch
2008-10-25  7:08 ` Artem Antonov
2008-11-04  1:39 ` Forest Bond [this message]
2008-11-06  1:00 ` Bernhard Schmidt
2008-11-06 12:16 ` Johannes Berg
2008-11-06 12:46 ` Przemek Kulczycki
2008-11-06 13:15   ` Johannes Berg
  -- strict thread matches above, loose matches on Subject: below --
2008-10-26 17:51 Ronald

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=20081104013956.GB483@storm.local.network \
    --to=forest@alittletooquiet.net \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mb@bu3sch.de \
    /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).