Return-path: Received: from mx07-00252a01.pphosted.com ([62.209.51.214]:8625 "EHLO mx07-00252a01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1035436AbdEXNQ7 (ORCPT ); Wed, 24 May 2017 09:16:59 -0400 Received: from pps.filterd (m0102628.ppops.net [127.0.0.1]) by mx07-00252a01.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v4ODFxeY002058 for ; Wed, 24 May 2017 14:16:52 +0100 Received: from mail-wm0-f69.google.com (mail-wm0-f69.google.com [74.125.82.69]) by mx07-00252a01.pphosted.com with ESMTP id 2ajb6ya1tv-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=OK) for ; Wed, 24 May 2017 14:16:52 +0100 Received: by mail-wm0-f69.google.com with SMTP id x184so38387112wmf.14 for ; Wed, 24 May 2017 06:16:52 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <8ec01afb-7c9d-2cde-0007-b4d9fd2dbdbd@broadcom.com> References: <8ec01afb-7c9d-2cde-0007-b4d9fd2dbdbd@broadcom.com> From: James Hughes Date: Wed, 24 May 2017 14:16:50 +0100 Message-ID: (sfid-20170524_151709_995782_4FBDAEF0) Subject: Re: brcmfmac: brcm43430 Invalid mailbox value issue To: Arend van Spriel Cc: linux-wireless , Franky Lin , Hante Meuleman , brcm80211-dev-list.pdl@broadcom.com Content-Type: text/plain; charset="UTF-8" Sender: linux-wireless-owner@vger.kernel.org List-ID: On 24 May 2017 at 14:13, Arend van Spriel wrote: > On 24-05-17 14:50, James Hughes wrote: >> We are seeing an issue on Raspberry Pi which uses the bcm43430 chip. It's >> been tested up to 4.9 which still shows the issue (it's been there for some >> time, > 1yr). I'm trying to find someone who can test on 4.11 as I cannot >> replicate (The latest kernel we have that works on a Pi) >> >> It exhibits as a log entry, and subsequent death of wireless connectivity. >> >> "Unknown mailbox data content: 0x40012" >> >> Look at the driver code, it appears to be checking the return >> value from a mailbox (presumably the one to the chip firmware), which >> has the 0x4 in the top word which shouldn't be there. >> >> The driver simply adds a log entry, but otherwise ignores the situation. >> However, we see wireless failure from this point. >> >> Since I believe this value is being returned from the chip, I cannot >> investigate much further. The public datasheet is of no help. We do appear >> to be using the latest firmware file. >> >> I'm not sure how to proceed on this one. It would be interesting to know >> under what circumstances that value can be returned from the mailbox. >> >> More details can be found at the end of this github issue. >> >> https://github.com/raspberrypi/linux/issues/1342 > > Hi James, > > I looked through the issue on github and it seems you are getting -110 > (-ETIMEDOUT) on SDIO transfers. This could be a signal integrity issue > of the SDIO bus signals, which may happen if the RPi3 power supply can > not provide enough amps. So you could try to replicate it by > deliberately use a power supply below specs. > > I did not get my RPi3 going yet, but I can try next monday or so. Office > closed due to Ascension day. Do you know what SDIO host controller is > used on RPi3? I can check myself, but if you know the answer up front > let me know. > > Regards, > Arend Hi Arend, It's the one built in to the SoC (the bcm2835) and I believe is an Arasan device. If you need anything else (HW etc) please let me know. I'll try the low power setup you suggest. Might be the reason why I cannot replicate, I always use decent power supplies. James