On Monday, June 16, 2014 1:08:21 PM UTC+4, Hans de Goede wrote:
> Hi Arend,
> 
> 
> 
> On 06/16/2014 10:41 AM, Arend van Spriel wrote:
> 
> > On 15-06-14 14:04, [email protected] wrote:
> 
> >> On Sun, Jun 15, 2014 at 6:25 AM, Hans de Goede <[email protected]> wrote:
> 
> >>> Hi,
> 
> >>>
> 
> >>> On 06/14/2014 02:47 PM, Александр Берсенев wrote:
> 
> >>>> Hi,
> 
> >>>>
> 
> >>>> I have wifi working on cubietruck, but after several minutes of operation
> 
> >>>> it stops work. The kernel was compiled from the latest sunxi-devel branch
> 
> >>>> of linux-sunxi repo.
> 
> >>>>
> 
> >>>> Ifconfig says that wlan1 is running, but all operation fails by timeout.
> 
> >>>>
> 
> >>>> # iwlist wlan1 scan
> 
> >>>> wlan1     Interface doesn't support scanning : Connection timed out
> 
> >>>>
> 
> >>>> # time iwconfig wlan1
> 
> >>>> wlan1     IEEE 802.11bgn  ESSID:off/any
> 
> >>>>            Mode:Managed  Access Point: Not-Associated
> 
> >>>>            Retry short limit:7   RTS thr:off   Fragment thr:off
> 
> >>>>            Encryption key:off
> 
> >>>>            Power Management:off
> 
> >>>>
> 
> >>>> real    0m4.999s
> 
> >>>> user    0m0.000s
> 
> >>>> sys     0m0.010s
> 
> >>>>
> 
> >>>>
> 
> >>>> Each second two messages appears in dmesg:
> 
> >>>> brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x0a020, err:
> 
> >>>> -110
> 
> >>>> brcmfmac: brcmf_sdio_dpc: failed backplane access over SDIO, halting
> 
> >>>> operation
> 
> >>>>
> 
> >>>> More related messages:
> 
> >>>> brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
> 
> >>>> brcmfmac: brcmf_fil_cmd_data: Failed err=-110
> 
> >>>> brcmfmac: brcmf_cfg80211_get_tx_power: error (-110)
> 
> >>>> brcmfmac: brcmf_do_escan: error (-110)
> 
> >>>> brcmfmac: brcmf_cfg80211_scan: scan error (-110)
> 
> >>>>
> 
> >>>> The command rmmod brcmfmac never finishes.
> 
> >>>>
> 
> >>>> Also, when wifi stops work, mmc error messages repeat in dmesg:
> 
> >>>> [  245.780430] sunxi-mmc 1c12000.mmc: smc 1 err, cmd 53, RD SBE !!
> 
> >>>
> 
> >>> Right, this is the infamous SBE error, a known issue, for which I've been
> 
> >>> unable to find a fix. Any help with fixing this is very much welcome.
> 
> >>>
> 
> >>> After the first SBE error any commands reading data from the device
> 
> >>> will fail with a DTO error. But it is the first SBE error which seems
> 
> >>> to kill things. I've reviewed the sunxi-mmc code countless times and tried
> 
> >>> various approaches (such as resetting the entire mmc controller) to work
> 
> >>> around this, but all without success.
> 
> >>
> 
> >> Does Broadcom know what this is, or do they have a better way to debug it?
> 
> > 
> 
> > Where can I find the linux-sunxi repo? github?
> 
> 
> 
> You should be able to reproduce this with the upstream 3.16-rc1 kernel which
> 
> should have all the necessary bits. I say should because I've not rebased
> 
> my tree yet, so I'm not 100% sure yet.
> 
> 
> 
> Note this will get you support for the sdio brcmfmac module without oob 
> interrupts,
> 
> but the SBE problem exhibits itself both with and without oob interrupts.
> 
> 
> 
> Alternatively you could use:
> 
> https://github.com/jwrdegoede/linux-sunxi/commits/sunxi-devel
> 
> 
> 
> Which currently is 3.15 + a set of sunxi patches, this one does do oob irq
> 
> support. I plan to rebase this on top of 3.16 (which should cause most patches
> 
> to get dropped) + forse-push during the coming days.
> 
> 
> 
> Or you can use:
> 
> https://github.com/linux-sunxi/linux-sunxi/commits/sunxi-devel
> 
> 
> 
> Which currently holds the same 
> https://github.com/jwrdegoede/linux-sunxi/commits/sunxi-devel
> 
> and won't get rebased to 3.16 until 3.16 has proven to at least be somewhat
> 
> usable. Basically this is a copy of 
> https://github.com/jwrdegoede/linux-sunxi/commits/sunxi-devel
> 
> which gets updated somewhat more conservatively.
> 
> 
> 
> Regards,
> 
> 
> 
> Hans


Yup, mainline 3.16.1 the same thing!

  Maxim

-- 
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to