All of lore.kernel.org
 help / color / mirror / Atom feed
From: xchetah <xchetah@gmail.com>
To: Oliver Neukum <oneukum@suse.com>, linux-usb@vger.kernel.org
Subject: Re: USB BUG on BCM6318
Date: Fri, 24 Apr 2020 01:20:44 +0300	[thread overview]
Message-ID: <cfe3c792-33ff-b4f8-635b-d4e60b632c8e@gmail.com> (raw)
In-Reply-To: <1587632815.23108.1.camel@suse.com>

On 4/23/20 12:06 PM, Oliver Neukum wrote:
> Am Mittwoch, den 22.04.2020, 19:45 +0300 schrieb xchetah:
>
> Hi,
>
> which kernel version?
>
>> the problem is that there’s no connectivity at all , I can connect to
>> the AP (only without encryption ) and the ssid doesn’t always show on my
>> mobile phone.
>> the usb port is working fine , I tried mounting a usb flash drive with
>> no problem.
>> also the adapter is working , I tried it on Orange pi , Raspberrypi ,
>> bcm6328 , all with openwrt installed on them and didn’t have any problem .
>> I guess it is something related to bcm6318 or its architecture code .
>> the onboard broadcom pci wifi is working .
>> I suspected that its a power problem so I added an external usb power ,
>> but with same issues.
>> also I tried openwrt 19 ,18 ,17 with same problem.
>> I’m also using two bcm6328 routers as point to point wifi 5ghz link with
>> Ralink RT5572 chipset ( rt2800usb driver ) withouyt any problem.
>> dmesg is filled with :
>>
>> [ 1269.191198] rt2800usb_tx_sta_fifo_read_completed: 13054 callbacks
>> suppressed
>> [ 1269.191239] ieee80211 phy1: rt2800usb_tx_sta_fifo_read_completed:
>> Warning - TX status read failed -32
> -EPIPE. Something is stalled. The cause is unknown. What is the very
> first error during the enumeration process?
>
> 	Regards
> 		Oliver
>
kernel version : 4.14.171 , also tried testing kernel 5.4 with the same
results.

there's no error during enumeration , errors occur as soon as I activate
the device in AP mode or client mode , if the device is doing nothing I
get no errors.

usb works fine with usb storage , I tried another adapter with rt2800 
driver and got the same exact problem.

Regards

Eyad



  reply	other threads:[~2020-04-23 22:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-22 16:45 USB BUG on BCM6318 xchetah
2020-04-23  9:06 ` Oliver Neukum
2020-04-23 22:20   ` xchetah [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-04-22  7:05 USB bug " xchetah

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=cfe3c792-33ff-b4f8-635b-d4e60b632c8e@gmail.com \
    --to=xchetah@gmail.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.