linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Broadcom Linux <bcm43xx-dev@lists.berlios.de>,
	wireless <linux-wireless@vger.kernel.org>
Subject: PHY TRANSMISSION ERRORS
Date: Thu, 21 Aug 2008 13:36:50 -0500	[thread overview]
Message-ID: <48ADB5C2.2020203@lwfinger.net> (raw)

I recently switched from a BCM4312/1 to a BCM4311/2 PCIe card. Running 
the latest from wireless-testing, I began seeing the PHY TRANSMISSION 
ERROR storms. None had ever been seen for the BCM4312/1. Since booting 
2.6.26 from wireless-testing, none have been observed.

Is this a regression since 2.6.26, or are these errors really 
intermittent? If you see these, please tell me how frequently they 
occur, and as much about the behavior with kernel version as you know.

Thanks,

Larry

             reply	other threads:[~2008-08-21 18:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-21 18:36 Larry Finger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-02-05 17:45 PHY transmission errors Larry Finger

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=48ADB5C2.2020203@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=bcm43xx-dev@lists.berlios.de \
    --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).