Raspberry Pi builtin WiFi keeps crashing

[jamesh]

It is very easy to make it go wrong; have an mqtt broker running and subscribe to a topic, where another client periodically publishes the currrent time (that's how I do it). Between a couple of minutes and a few days, the wifi drivers crash ...

kind regards,

Jos

Problem is a few days is too long, we really need a mechanism that shows the issue much faster and more reliably. Case in point, I have only ever seen the mailbox issue once or twice in the last year, whereas others see it all the time. Makes it fantastically difficult to track down. hence my request above.

That, and I have no idea what a mqtt broker is so would have no idea how to set it up.

And I don''t know what the 'mailbox issue' is, so we're even I'm afraid I have to let this pass to a more knowledgeable person; still: I never had any problems at all with Jessie on a pi3 ... I guess I was just lucky ...

kind regards,

Jos

Is suspect you were, although there may have been driver changes that have affected stability. Generally, only bug fixes go into the driver, but its also possible a fix for one thing has exposed another problem elsewhere.

All the bugs in the linked thread have been around since the Pi was released. We've found and fixed a couple, the mailbox issue is, I hope, one of the last. It indicates that the firmware on the wireless chip has crashed/died in some way, so is not something we can fix here, it must be done by Cypress.

[SamStarfall]

I think I have a setup that will reproduce the issue reliably and quickly.
I am using a PI 3 Model B as a wireless bridge, so I can connect an ethernet wired computer, NAS and printer to my wireless LAN.
This worked surprisingly well, good throughput and reliable (for the few days it has been running), so i got adventurous...
I then added a SAMBA share to the PI, so that I could access a photo archive using a Samsung tablet running Ghost Commander. This is a prelude to trying out piwigo photo gallery.
Simple browsing of the smb file lists did not cause any problem, but any attempt to transfer a set of files and it errors within seconds.
Watching the kern.log output showed the dreaded mailbox error:
...
Dec 9 12:21:57 raspberrypi3 kernel: [ 7.199948] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1
Dec 9 12:23:20 raspberrypi3 kernel: [ 89.982598] random: crng init done # <<<--- file transfer started after this point.
Dec 9 12:24:08 raspberrypi3 kernel: [ 138.808547] brcmfmac: brcmf_sdio_hostmail: Unknown mailbox data content: 0x40012

My PI is not bog standard - I have I2C enabled and an external RTC connected. My wireless LAN is also an el cheapo generic thing, so it may not help.
Things I have tried:
A different power supply - no change.
I rebooted the PI and tried an old iPad runing FileExplorer to view the photos stored on the pi - no problem for the couple of minutes it took to browse 30 or so photos. I then picked up the Samsung tablet (a little 7 inch model - SM-T113), and the PI errored within a second of attempting to view the first file.
I then set the max data rate on my wireless LAN to 2Mbit, and it worked OK ! Awfully slow though. I then bumped the speed up to 5.5M, and the PI errors as before.
If you could point me towards the test firmware, I would be happy to gather some debug output.

Cheers,
Warrick.

[JosAH]

still: I never had any problems at all with Jessie on a pi3 ... I guess I was just lucky ...

Is suspect you were, although there may have been driver changes that have affected stability. Generally, only bug fixes go into the driver, but its also possible a fix for one thing has exposed another problem elsewhere.

All the bugs in the linked thread have been around since the Pi was released. We've found and fixed a couple, the mailbox issue is, I hope, one of the last. It indicates that the firmware on the wireless chip has crashed/died in some way, so is not something we can fix here, it must be done by Cypress.

First your remark had me baffled; next I fired up my old pi/3 (running Jessie) and it kept running for days again, flawlessly; my new pi/3 (runing Stretch) crashed a couple of times again in the mean time; I really don't know what's wrong here. What I do know is that the pi/3 running Stretch is completely useless for wifi. btw any progress with Cypress yet?

kind regards,

Jos

[jamesh]

For those wishing to try the debug firmware, please PM me and I will send it to you, see link for how to use it.

viewtopic.php?f=28&t=196018#p1244026


As for progress from Cypress, we have attracted their attention, and they are asking for more debug results from the latest firmware. We will probably get a SS device here as they seem to be a common factor, so at least we can try and replicate here.

[SamStarfall]

Here is the full dmesg dump, the mail box error occurs at the end when I attempted to upload a 6meg photo to PIs samba share.
Note that I had to rebuild the relevant kernel modules with debug enabled to see the debug messages.
Let me know if there is any more testing you want done.

cheers.

Code: Select all

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.9.35-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #1014 SMP Fri Jun 30 14:47:43 BST 2017
[    0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt:Machine model: Raspberry Pi 3 Model B Rev 1.2
[    0.000000] cma: Reserved 8 MiB at 0x35800000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] On node 0 totalpages: 221184
[    0.000000] free_area_init_node: node 0, pgdat 80c6ee40, node_mem_map b505e000
[    0.000000]   Normal zone: 1944 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 221184 pages, LIFO batch:31
[    0.000000] percpu: Embedded 14 pages/cpu @b5018000 s25600 r8192 d23552 u57344
[    0.000000] pcpu-alloc: s25600 r8192 d23552 u57344 alloc=14*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 219240
[    0.000000] Kernel command line: 8250.nr_uarts=1 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3dc00000 vc_mem.mem_size=0x3f000000  dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=PARTUUID=0e687f1b-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 855096K/884736K available (7168K kernel code, 484K rwdata, 2012K rodata, 1024K init, 778K bss, 21448K reserved, 8192K cma-reserved)
[    0.000000] Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    vmalloc : 0xb6800000 - 0xff800000   (1168 MB)
    lowmem  : 0x80000000 - 0xb6000000   ( 864 MB)
    modules : 0x7f000000 - 0x80000000   (  16 MB)
      .text : 0x80008000 - 0x80800000   (8160 kB)
      .init : 0x80b00000 - 0x80c00000   (1024 kB)
      .data : 0x80c00000 - 0x80c79014   ( 485 kB)
       .bss : 0x80c7b000 - 0x80d3da64   ( 779 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000] 	Build-time adjustment of leaf fanout to 32.
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] arm_arch_timer: Architected cp15 timer(s) running at 19.20MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
[    0.000010] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
[    0.000026] Switching to timer-based delay loop, resolution 52ns
[    0.000339] Console: colour dummy device 80x30
[    0.001236] console [tty1] enabled
[    0.001292] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000)
[    0.001361] pid_max: default: 32768 minimum: 301
[    0.001723] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.001767] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.002790] Disabling cpuset control group subsystem
[    0.002984] CPU: Testing write buffer coherency: ok
[    0.003055] ftrace: allocating 22390 entries in 66 pages
[    0.054324] CPU0: update cpu_capacity 1024
[    0.054391] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.054488] Setting up static identity map for 0x100000 - 0x100034
[    0.056734] CPU1: update cpu_capacity 1024
[    0.056742] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.057464] CPU2: update cpu_capacity 1024
[    0.057470] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[    0.058136] CPU3: update cpu_capacity 1024
[    0.058143] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[    0.058226] Brought up 4 CPUs
[    0.058399] SMP: Total of 4 processors activated (153.60 BogoMIPS).
[    0.058428] CPU: All CPU(s) started in HYP mode.
[    0.058454] CPU: Virtualization extensions available.
[    0.059266] devtmpfs: initialized
[    0.070375] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4
[    0.070693] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.070754] futex hash table entries: 1024 (order: 4, 65536 bytes)
[    0.071313] pinctrl core: initialized pinctrl subsystem
[    0.072241] NET: Registered protocol family 16
[    0.074529] DMA: preallocated 1024 KiB pool for atomic coherent allocations
[    0.083418] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[    0.083467] hw-breakpoint: maximum watchpoint size is 8 bytes.
[    0.083634] Serial: AMBA PL011 UART driver
[    0.085533] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
[    0.086078] uart-pl011 3f201000.serial: could not find pctldev for node /soc/gpio@7e200000/uart0_pins, deferring probe
[    0.154915] bcm2835-dma 3f007000.dma: DMA legacy API manager at b680f000, dmachans=0x1
[    0.156782] SCSI subsystem initialized
[    0.156960] usbcore: registered new interface driver usbfs
[    0.157062] usbcore: registered new interface driver hub
[    0.157178] usbcore: registered new device driver usb
[    0.163870] raspberrypi-firmware soc:firmware: Attached to firmware from 2017-07-03 14:16
[    0.165288] clocksource: Switched to clocksource arch_sys_counter
[    0.212109] VFS: Disk quotas dquot_6.6.0
[    0.212221] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.212448] FS-Cache: Loaded
[    0.212720] CacheFiles: Loaded
[    0.224923] NET: Registered protocol family 2
[    0.225867] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.226004] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    0.226215] TCP: Hash tables configured (established 8192 bind 8192)
[    0.226328] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.226395] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.226630] NET: Registered protocol family 1
[    0.227067] RPC: Registered named UNIX socket transport module.
[    0.227099] RPC: Registered udp transport module.
[    0.227127] RPC: Registered tcp transport module.
[    0.227154] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.228126] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available
[    0.230440] workingset: timestamp_bits=14 max_order=18 bucket_order=4
[    0.246609] FS-Cache: Netfs 'nfs' registered for caching
[    0.247612] NFS: Registering the id_resolver key type
[    0.247662] Key type id_resolver registered
[    0.247690] Key type id_legacy registered
[    0.250136] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
[    0.250282] io scheduler noop registered
[    0.250313] io scheduler deadline registered (default)
[    0.250622] io scheduler cfq registered
[    0.256320] BCM2708FB: allocated DMA memory f5910000
[    0.256375] BCM2708FB: allocated DMA channel 0 @ b680f000
[    0.265862] Console: switching to colour frame buffer device 82x26
[    0.273298] Serial: 8250/16550 driver, 1 ports, IRQ sharing enabled
[    0.277156] bcm2835-rng 3f104000.rng: hwrng registered
[    0.279541] vc-cma: Videocore CMA driver
[    0.281804] vc-cma: vc_cma_base      = 0x00000000
[    0.284141] vc-cma: vc_cma_size      = 0x00000000 (0 MiB)
[    0.286479] vc-cma: vc_cma_initial   = 0x00000000 (0 MiB)
[    0.288897] vc-mem: phys_addr:0x00000000 mem_base=0x3dc00000 mem_size:0x3f000000(1008 MiB)
[    0.308462] brd: module loaded
[    0.319383] loop: module loaded
[    0.321452] Loading iSCSI transport class v2.0-870.
[    0.324064] usbcore: registered new interface driver smsc95xx
[    0.326275] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[    0.556471] Core Release: 2.80a
[    0.558509] Setting default values for core params
[    0.560599] Finished setting default values for core params
[    0.763104] Using Buffer DMA mode
[    0.765214] Periodic Transfer Interrupt Enhancement - disabled
[    0.767417] Multiprocessor Interrupt Enhancement - disabled
[    0.769663] OTG VER PARAM: 0, OTG VER FLAG: 0
[    0.771865] Dedicated Tx FIFOs mode
[    0.774333] WARN::dwc_otg_hcd_init:1032: FIQ DMA bounce buffers: virt = 0xb5904000 dma = 0xf5904000 len=9024
[    0.778801] FIQ FSM acceleration enabled for :
Non-periodic Split Transactions
Periodic Split Transactions
High-Speed Isochronous Endpoints
Interrupt/Control Split Transaction hack enabled
[    0.790160] dwc_otg: Microframe scheduler enabled
[    0.790210] WARN::hcd_init_fiq:459: FIQ on core 1 at 0x8058ef90
[    0.792517] WARN::hcd_init_fiq:460: FIQ ASM at 0x8058f300 length 36
[    0.794840] WARN::hcd_init_fiq:486: MPHI regs_base at 0xb687a000
[    0.797191] dwc_otg 3f980000.usb: DWC OTG Controller
[    0.799506] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
[    0.801861] dwc_otg 3f980000.usb: irq 62, io mem 0x00000000
[    0.804179] Init: Port Power? op_state=1
[    0.806452] Init: Power Port (0)
[    0.808830] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    0.811140] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.813441] usb usb1: Product: DWC OTG Controller
[    0.815709] usb usb1: Manufacturer: Linux 4.9.35-v7+ dwc_otg_hcd
[    0.817981] usb usb1: SerialNumber: 3f980000.usb
[    0.821064] hub 1-0:1.0: USB hub found
[    0.823268] hub 1-0:1.0: 1 port detected
[    0.826023] dwc_otg: FIQ enabled
[    0.826028] dwc_otg: NAK holdoff enabled
[    0.826032] dwc_otg: FIQ split-transaction FSM enabled
[    0.826046] Module dwc_common_port init
[    0.826277] usbcore: registered new interface driver usb-storage
[    0.828608] mousedev: PS/2 mouse device common for all mice
[    0.831698] bcm2835-wdt 3f100000.watchdog: Broadcom BCM2835 watchdog timer
[    0.834232] bcm2835-cpufreq: min=600000 max=1200000
[    0.836905] sdhci: Secure Digital Host Controller Interface driver
[    0.839218] sdhci: Copyright(c) Pierre Ossman
[    0.841741] sdhost-bcm2835 3f202000.sdhost: could not get clk, deferring probe
[    0.846309] mmc-bcm2835 3f300000.mmc: could not get clk, deferring probe
[    0.848851] sdhci-pltfm: SDHCI platform and OF driver helper
[    0.853904] ledtrig-cpu: registered to indicate activity on CPUs
[    0.856574] hidraw: raw HID events driver (C) Jiri Kosina
[    0.859247] usbcore: registered new interface driver usbhid
[    0.861704] usbhid: USB HID core driver
[    0.864950] vchiq: vchiq_init_state: slot_zero = 0xb5980000, is_master = 0
[    0.869203] Initializing XFRM netlink socket
[    0.871741] NET: Registered protocol family 17
[    0.874330] Key type dns_resolver registered
[    0.877201] Registering SWP/SWPB emulation handler
[    0.880372] registered taskstats version 1
[    0.883172] vc-sm: Videocore shared memory driver
[    0.885697] [vc_sm_connected_init]: start
[    0.888614] [vc_sm_connected_init]: end - returning 0
[    0.896075] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud = 0) is a PL011 rev2
[    1.860040] console [ttyAMA0] enabled
[    1.867711] sdhost: log_buf @ b5907000 (f5907000)
[    1.945314] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
[    1.955389] mmc-bcm2835 3f300000.mmc: mmc_debug:0 mmc_debug2:0
[    1.963563] mmc-bcm2835 3f300000.mmc: DMA channel allocated
[    1.992159] Indeed it is in host mode hprt0 = 00021501
[    2.085414] of_cfs_init
[    2.086847] random: fast init done
[    2.095749] of_cfs_init: OK
[    2.101106] Waiting for root device PARTUUID=0e687f1b-02...
[    2.104375] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[    2.105954] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    2.107525] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    2.110335] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[    2.175690] mmc0: host does not support reading read-only switch, assuming write-enable
[    2.192636] mmc0: new high speed SDHC card at address aaaa
[    2.200940] mmcblk0: mmc0:aaaa ACLCD 29.7 GiB
[    2.207463] usb 1-1: new high-speed USB device number 2 using dwc_otg
[    2.216402] Indeed it is in host mode hprt0 = 00001101
[    2.288239]  mmcblk0: p1 p2
[    2.309044] mmc1: new high speed SDIO card at address 0001
[    2.396636] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[    2.409124] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[    2.427995] devtmpfs: mounted
[    2.435047] Freeing unused kernel memory: 1024K (80b00000 - 80c00000)
[    2.445594] usb 1-1: New USB device found, idVendor=0424, idProduct=9514
[    2.454753] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    2.465210] hub 1-1:1.0: USB hub found
[    2.471504] hub 1-1:1.0: 5 ports detected
[    2.724735] systemd[1]: systemd 215 running in system mode. (+PAM +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP -APPARMOR)
[    2.743782] systemd[1]: Detected architecture 'arm'.
[    2.805340] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[    2.864340] NET: Registered protocol family 10
[    2.872966] systemd[1]: Inserted module 'ipv6'
[    2.883835] systemd[1]: Set hostname to <raspberrypi3>.
[    2.891921] systemd[1]: Initializing machine ID from random generator.
[    2.901360] systemd[1]: Installed transient /etc/machine-id file.
[    2.935866] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
[    2.945447] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    2.958250] smsc95xx v1.0.5
[    2.968416] uart-pl011 3f201000.serial: no DMA platform data
[    3.059092] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:a5:51:68
[    3.272033] systemd[1]: Cannot add dependency job for unit regenerate_ssh_host_keys.service, ignoring: Unit regenerate_ssh_host_keys.service failed to load: No such file or directory.
[    3.300211] systemd[1]: Expecting device dev-ttyAMA0.device...
[    3.312245] systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
[    3.325744] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    3.549003] i2c /dev entries driver
[    3.712803] systemd-udevd[133]: starting version 215
[    4.038501] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
[    4.321651] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
[    4.327243] rtc-ds1307 1-0068: rtc core: registered ds3231 as rtc0
[    4.328680] usbcore: registered new interface driver brcmfmac
[    4.471971] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[    4.544064] brcmfmac: Firmware version = wl0: Sep 19 2017 06:03:25 version 7.45.41.46 (r666254 CY-mb_dbg) FWID 01-743d4989
[    4.605882] brcmfmac: CONSOLE: hndarm_armr addr: 0x18003000, cr4_idx: 0
[    4.605891] brcmfmac: CONSOLE: 000000.001 
[    4.605899] brcmfmac: CONSOLE: RTE (SDIO-CDC) 7.45.41.46 (r666254 CY-mb_dbg) on BCM43430 r1 @ 37.4/81.6/81.6MHz
[    4.605905] brcmfmac: CONSOLE: 000000.001 sdpcmdcdc0: Broadcom SDPCMD CDC driver
[    4.605912] brcmfmac: CONSOLE: 000000.005 reclaim section 0: Returned 47716 bytes to the heap
[    4.605918] brcmfmac: CONSOLE: 000000.007 wlc_bmac_info_init: host_enab 1
[    4.605927] brcmfmac: CONSOLE: 000000.026 wl0: Broadcom BCM43430 802.11 Wireless Controller 7.45.41.46 (r666254 CY-mb_dbg)
[    4.605932] brcmfmac: CONSOLE: 000000.026 TCAM: 256 used: 183 exceed:0
[    4.605939] brcmfmac: CONSOLE: 000000.028 reclaim section 1: Returned 81308 bytes to the heap
[    4.605945] brcmfmac: CONSOLE: 000000.028 sdpcmd_dpc: Enable
[    4.605952] brcmfmac: CONSOLE: 000000.035 wl0: wlc_enable_probe_req: state down, deferring setting of host flags
[    4.605960] brcmfmac: CONSOLE: 000000.071 wl0: wlc_enable_probe_req: state down, deferring setting of host flags
[    4.605968] brcmfmac: CONSOLE: 000000.072 wl0: wlc_enable_probe_req: state down, deferring setting of host flags
[    4.882031] systemd-journald[136]: Received request to flush runtime journal from PID 1
[    5.495479] ip_tables: (C) 2000-2006 Netfilter Core Team
[    5.508931] nf_conntrack version 0.5.0 (14336 buckets, 57344 max)
[    5.807759] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[    5.808268] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    5.935632] brcmfmac: CONSOLE: 000001.403 wl0: wl_open
[    5.949829] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[    5.949860] brcmfmac: power management disabled
[    5.965807] brcmfmac: CONSOLE: 000001.433 wl0: wlc_enable_probe_req: state down, deferring setting of host flags
[    6.553815] Adding 102396k swap on /var/swap.  Priority:-1 extents:6 across:1388540k SSFS
[    7.075661] brcmfmac: CONSOLE: 000002.550 wl_nd_ra_filter_clear_cache: Enter..
[    7.159683] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[    7.562202] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[    7.562974] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1
[   82.250024] random: crng init done
[  106.495821] brcmfmac: CONSOLE:    0000: 54 44 4c 53 20 50 4d 4b 54 40 ad 4e 2b 12 b8 27 
[  106.495831] brcmfmac: CONSOLE: 000101.987   0010: eb f0 04 3d 00 e0 4c 53 71 c7 
[  106.495838] brcmfmac: CONSOLE: 000101.988 wlc_set_ra_hw: ra == primary, swap in null_ether
[  106.512694] brcmfmac: brcmf_sdio_hostmail: Unknown mailbox data content: 0x40012
[  106.525814] brcmfmac: CONSOLE: 000102.005 
[  106.525820] brcmfmac: CONSOLE: FWID 01-743d4989
[  106.525824] brcmfmac: CONSOLE: flags 1
[  106.525829] brcmfmac: CONSOLE: 000102.005 
[  106.525836] brcmfmac: CONSOLE: TRAP c(6fcd8): pc 820f8e, lr b559, sp 6fd2c, cpsr 2000000c, spsr 21000010
[  106.525843] brcmfmac: CONSOLE: 000102.005   r0 6ad6c, r1 1, r2 6fe94, r3 9500, r4 1, r5 6ad6c, r6 6fe94
[  106.525851] brcmfmac: CONSOLE: 000102.005   r7 6fd9c, r8 0, r9 0, r10 6ad6c, r11 6fe1c, r12 ffffffff
[  106.525855] brcmfmac: CONSOLE: 000102.005 
[  106.525861] brcmfmac: CONSOLE:    sp+0 0006ad6c 00000001 0006fe94 00009500
[  106.525867] brcmfmac: CONSOLE: 000102.006   sp+10 ffffffff 0000b559 00820f8e 21000010
[  106.525871] brcmfmac: CONSOLE: 
[  106.525876] brcmfmac: CONSOLE: 000102.006 sp+14 0000b559
[  106.525881] brcmfmac: CONSOLE: 000102.006 sp+34 00034203
[  106.525886] brcmfmac: CONSOLE: 000102.006 sp+bc 00011993
[  106.525891] brcmfmac: CONSOLE: 000102.006 sp+cc 0001bfb7
[  106.525896] brcmfmac: CONSOLE: 000102.006 sp+134 0000466b
[  106.525901] brcmfmac: CONSOLE: 000102.006 sp+14c 000052db
[  106.525906] brcmfmac: CONSOLE: 000102.006 sp+1ac 0001c1eb
[  106.525911] brcmfmac: CONSOLE: 000102.006 sp+1e4 00020ac1
[  106.525916] brcmfmac: CONSOLE: 000102.006 sp+20c 00007eb5
[  106.525921] brcmfmac: CONSOLE: 000102.006 sp+22c 000027d1
[  106.525926] brcmfmac: CONSOLE: 000102.006 sp+23c 00002efd
[  106.525931] brcmfmac: CONSOLE: 000102.006 sp+244 000020d1
[  106.525936] brcmfmac: CONSOLE: 000102.006 sp+290 00002ab3
[  106.525941] brcmfmac: CONSOLE: 000102.006 sp+2b0 00002ab3
[  106.525946] brcmfmac: CONSOLE: 000102.006 sp+2c0 000022c3

[jamesh]

Thanks, that look really useful, I have passed it on to Cypress.

[jamesh]

We've also had a bug report on the github that has a possible workaround that I like people to try. This may not be applicable to all users, but i am not sure myself what these options do, but will try and find out.

In hostapd.conf

comment out the line

Code: Select all

wpa_pairwise=TKIP

and replace it with this:

Code: Select all

rsn_pairwise=CCMP

Please report back if it makes the mailbox issue go away.

Thanks.

EDIT: Here are the details on those options - which mean very little to me..

# Set of accepted cipher suites (encryption algorithms) for pairwise keys
# (unicast packets). This is a space separated list of algorithms:
# CCMP = AES in Counter mode with CBC-MAC (CCMP-128)
# TKIP = Temporal Key Integrity Protocol
# CCMP-256 = AES in Counter mode with CBC-MAC with 256-bit key
# GCMP = Galois/counter mode protocol (GCMP-128)
# GCMP-256 = Galois/counter mode protocol with 256-bit key
# Group cipher suite (encryption algorithm for broadcast and multicast frames)
# is automatically selected based on this configuration. If only CCMP is
# allowed as the pairwise cipher, group cipher will also be CCMP. Otherwise,
# TKIP will be used as the group cipher. The optional group_cipher parameter can
# be used to override this automatic selection.
#
# (dot11RSNAConfigPairwiseCiphersTable)
# Pairwise cipher for WPA (v1) (default: TKIP)
#wpa_pairwise=TKIP CCMP
# Pairwise cipher for RSN/WPA2 (default: use wpa_pairwise value)
#rsn_pairwise=CCMP

[JosAH]

Where is that file stored?

kind regards,

Jos

[SurferTim]

Where is that file stored?

I'm not certain what he means. hostapd is for those using the wifi as an AP. Is that what you are doing?

Edit: I believe the correct file to check would be /etc/wpa_supplicant/wpa_supplicant.conf. You would have to look up the correct format to enter what was suggested.

[jamesh]

Yes, the originator of the work around was using the Pi as an AP - sorry I should have been more explicit.

Not sure if there is a similar option on wpa_supplicant - probably.

[SamStarfall]

I just tried setting my wireless router to WPA2 -TKIP only (disabling AES) and the PI wireless chip did not crash !
The PI is connecting to a generic wireless router in client mode, serving up a samba share, and a little Samsung tablet is being used to browse the samba share.
I have no idea how reliable it will be, and I would prefer to NOT leave it on TKIP as it is not considered to be secure these days, but it does sort of narrow it down a bit.
Just to reiterate, WPA2-TKIP works, WPA2-AES does not, at least when using a Samsung tablet to access large files (greater than 2 Meg) on the PIs samba share. As before, an old iPad running FileExplorer causes no problems.

cheers.

[JosAH]

Enabling TKIP contradicts what James(h) wrote: disable TKIP. I agree that TKIP is not very secure though ... TKIP encryption is officially obsolete (as WEP encryption is).

kind regards,

Jos

[jamesh]

It does sort of point the finger at it being an encryption issue though. I've passed the data on to Cypress.

[JosAH]

What surprises me is that not many more people suffer from this bad wireless firmwsre/driver. I'd expected that these forums would be flooded ... was there a stretch distribution that didn't suffer from this problem? My old Jessie runs ok, and my (out of the box) Stretch distribution crashes multiple times per day. The pi/3 is unusable as it is now (for me).

I feel tempted to reinstall Jessie again and forget all about that Stretch stuff; itr isn't ready for the public yet; no matter if it is 'so soft for your hands'.

kind regards,

Jos

[superbob666]

What surprises me is that not many more people suffer from this bad wireless firmwsre/driver. I'd expected that these forums would be flooded ... was there a stretch distribution that didn't suffer from this problem? My old Jessie runs ok, and my (out of the box) Stretch distribution crashes multiple times per day. The pi/3 is unusable as it is now (for me).

I feel tempted to reinstall Jessie again and forget all about that Stretch stuff; itr isn't ready for the public yet; no matter if it is 'so soft for your hands'.

kind regards,

Jos

I did try using the wireless, but as you said it is not usable. No option except, to use wired. I hope this gets fixed soon

[SurferTim]

If you are using your internal wifi as an AP, mine ran fine for days on end without a fail.

Edit: I've booted a RPi3 with Stretch 2017-11-29 version with a bridge AP. I'll let it run for a while and see if it fails.

[jamesh]

What surprises me is that not many more people suffer from this bad wireless firmwsre/driver. I'd expected that these forums would be flooded ... was there a stretch distribution that didn't suffer from this problem? My old Jessie runs ok, and my (out of the box) Stretch distribution crashes multiple times per day. The pi/3 is unusable as it is now (for me).

I feel tempted to reinstall Jessie again and forget all about that Stretch stuff; itr isn't ready for the public yet; no matter if it is 'so soft for your hands'.

kind regards,

Jos

It is odd, and seems to depend on some rather particular circumstances that we haven't quite narrowed down. For example, I have seen the mailbox issue once, about a year ago, and not seen it since. But others see it regularly.

It's not a Jessie vs Stretch thing - the firmware on the Wireless chip is the same in both. There are some changes in the Linux driver, but I believe they are all bug fixes for other issues.

As for Stretch not being ready, well, it's been in testing for months, especially if you include time spent on x86 before we starting with it.

I'll reiterate, I don't believe this issue is dependent on the distro version, it's dependent on the chip firmware and to a lesser extent, the linux kernel driver, and of course, you could have a newer kernel on Jessie than Stretch!

[SurferTim]

I've been out for a few hours, and my ap/bridge is still working. How long does a failure normally take? Is it a temporary fail or do you need to reboot to get it working again. I want to know what to watch for.

Edit: It ran fine overnight.

[JosAH]

A couple of days ago I reinstalled Stretch again from scratch (version 29/11/2017) and my pi/3 runs fine ever since ... the previous installation crashed from within minutes until a couple of hours. Of course I'm happy now, but I didn't do anything different for those two installations:select the network from the menu and give it the presharred key; what can you do wrong?

kind regards,

Jos

[precesseur]

Well I do not know if this could help. But still. I had recently troubles to install Lyx (and thus LateX) on RPI3, Stretch, when I had no troubles before with RPI2 (and as far as remember with RPI3 Jessie but I cannot swear). It turns out that some the very large files, (you know LaTeX) were corrupted after download. I redid the install from several mirrors with different but similar results. I finally used a cable, disregarding wifi, and in a snap (well hallf an hour of donwnload, compilation and the like) I had a perfect installation. Yes, you say, as I said, its probably my intranet fault.
Except I had installed LyX LaTex here on several systems from Windoze to Linuxes proper and..Raspbian before. And now that I read this thread .. I wonder. At the least I suggest that 'installing LyX' may be a good WIFI trouble test.

[superbob666]

A couple of days ago I reinstalled Stretch again from scratch (version 29/11/2017) and my pi/3 runs fine ever since ... the previous installation crashed from within minutes until a couple of hours. Of course I'm happy now, but I didn't do anything different for those two installations:select the network from the menu and give it the presharred key; what can you do wrong?

kind regards,

Jos

Can you provide link and did you do firmware or packages upgrade after installation.

[SurferTim]

Can you provide link and did you do firmware or packages upgrade after installation.

If you want an ap setup, then this is the instructions to do that. My bridged ap has been running since Monday without a problem.
https://github.com/SurferTim/documentat ... s-point.md

[superbob666]

Can you provide link and did you do firmware or packages upgrade after installation.

If you want an ap setup, then this is the instructions to do that. My bridged ap has been running since Monday without a problem.
https://github.com/SurferTim/documentat ... s-point.md

Thanks, but I am not using Raspberry PI as AP, I already have two APs in the house.
Did we get an update on this?

[jamesh]

Still under investigation.

[jamesh]

There is a new debug firmware from Cypress that needs running by those people who can replicate the issue. See here https://github.com/raspberrypi/linux/is ... -355931984

I can send the firmware to anyone who can spend the time running it up and reporting the issues, PM me with your email address so I can send it. Instructions on use are in the link above.

Need to ask you help because I am unable to replicate the problem here!