- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi All,
We are using CYW43012 chipset with the following details:
Firmware version:
1.21 RC0.0
wl0: Feb 21 2022 07:19:28 version 13.10.271.283 (211da63 CY) FWID 01-18f4ac2
Driver Version:
Backported Linux Version v4.14.77-kong-RTM-rc8-0-ged6fa18
We have observed that after certain time, we are seeing SDIO -110 error as follows:
2022-05-04 02:44:53 SAMA5D2C3 kernel:[45542.850000] +++ should not come 470:atmel_i2s_switch_mck_generator
2022-05-04 02:45:01 SAMA5D2C3 crond[699]: pam_unix(crond:session): session opened for user root by (uid=0)
2022-05-04 02:45:01 SAMA5D2C3 CROND[700]: (root) CMD (/bin/date -u +%4Y%2m%2d%2H%2M%2S 2>/dev/null > /etc/timestamp)
2022-05-04 02:45:01 SAMA5D2C3 CROND[699]: pam_unix(crond:session): session closed for user root
2022-05-04 02:46:09 SAMA5D2C3 rsyslogd: -- MARK --
2022-05-04 02:46:15 SAMA5D2C3 kernel:[45624.750000] atmel_i2s f8050000.i2s: TX underrun on channel 0
2022-05-04 02:46:58 SAMA5D2C3 kernel:[45667.480000] atmel_i2s f8050000.i2s: TX underrun on channel 0
2022-05-04 02:48:58 SAMA5D2C3 kernel:[45787.500000] atmel_i2s f8050000.i2s: TX underrun on channel 0
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.300000] brcmfmac: brcmf_sdio_bus_sleep: error while changing bus sleep state -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.320000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x0a020, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.330000] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.350000] brcmfmac: brcmf_sdiod_regrw_helper: failed to write data F1@0x1000d, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.360000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x1001a, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.370000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x10019, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.390000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x1001a, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.400000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x10019, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.420000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x1001a, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.440000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x10019, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.440000] brcmfmac: brcmf_sdio_dpc: failed backplane access over SDIO, halting operation
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.560000] brcmfmac: brcmf_sdio_bus_sleep: error while changing bus sleep state -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.570000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x0a020, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.580000] brcmfmac: brcmf_sdio_dpc: failed backplane access over SDIO, halting operation
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.700000] brcmfmac: brcmf_sdio_bus_sleep: error while changing bus sleep state -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.720000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x0a020, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.730000] brcmfmac: brcmf_sdio_dpc: failed backplane access over SDIO, halting operation
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.950000] brcmfmac: brcmf_sdio_bus_sleep: error while changing bus sleep state -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.960000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x0a020, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.980000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F0@0x00003, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.990000] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45810.010000] brcmfmac: brcmf_sdiod_regrw_helper: failed to write data F1@0x1000d, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45810.020000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x1001a, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45810.040000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x10019, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45810.050000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x1001a, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45810.070000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x10019, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45810.080000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x1001a, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45810.100000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x10019, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45810.110000] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45810.120000] brcmfmac: brcmf_sdiod_regrw_helper: failed to write data F1@0x1000d, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45810.140000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x1001a, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45810.160000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x10019, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45810.170000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x1001a, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45810.190000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x10019, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45810.200000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x1001a, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45810.220000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x10019, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45810.220000] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
2022-05-04 02:49:21 SAMA5D2C3 kernel:[45810.240000] brcmfmac: brcmf_sdiod_regrw_helper: failed to write data F1@0x1000d, err: -110
2022-05-04 02:49:21 SAMA5D2C3 kernel:[45810.260000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x1001a, err: -110
2022-05-04 02:49:21 SAMA5D2C3 kernel:[45810.270000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x10019, err: -110
2022-05-04 02:49:21 SAMA5D2C3 kernel:[45810.290000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x1001a, err: -110
2022-05-04 02:49:21 SAMA5D2C3 kernel:[45810.300000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x10019, err: -110
2022-05-04 02:49:21 SAMA5D2C3 kernel:[45810.320000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x1001a, err: -110
2022-05-04 02:49:21 SAMA5D2C3 kernel:[45810.340000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x10019, err: -110
2022-05-04 02:49:21 SAMA5D2C3 kernel:[45810.340000] brcmfmac: brcmf_sdio_dpc: sdio ctrlframe tx failed err=-110
2022-05-04 02:49:21 SAMA5D2C3 kernel:[45810.350000] brcmfmac: brcmf_sdio_dpc: failed backplane access over SDIO, halting operation
2022-05-04 02:49:21 SAMA5D2C3 kernel:[45810.360000] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
This issue is frequently reproducible and any need asap is deeply appreciated.
Attached the complete log file for your reference.
Regards,
Rupesh
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @raks_99
Increasing BRCMF_SDIO_MAX_ACCESS_ERRORS value didn't help. We disabled CONFIG_PM_SLEEP to avoid SDIO sleep and wake up cycles and found that the issue was not able to be reproduced. For now we are proceeding with that as a stop gap solution as we are pressed on time for our production.
Regards,
Rupesh.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @rupesh_theatro ,
Let me check for this issue.
As one possible workaround, can you try increasing the value of the macro "BRCMF_SDIO_MAX_ACCESS_ERRORS" in "sdio.c" file from 20 (default ) to 100.
How do you restore the module after this issue occurs? by reloading the drivers?
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
No, we are currently rebooting our device for it to recover.
On a high level, what do you suspect to be the reason for this behavior?
Regards,
Rupesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I suspected that it could be due to SDIO access timeout errors. But in that case, it should have auto recovered.
Is this a regression in some newer versions of the firmware? In other words, are you seeing this issue after upgrading the driver/firmware from an older version to 13.10.271.283?
Best Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Previously we used CYW43455 chipset with which we are not seeing the issue, we recently moved to CYW43012 chipset with which we are seeing this issue.
We are using 4.9 kernel and the corresponding driver for that version.
Regards,
Rupesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @rupesh_theatro ,
Usually, these -110 errors can be ignored since they could be caused by delays in the SDIO bus. Can you share the SDIO mode configuration? You can cat /sys/kernel/debug/mmc<0 or 1>/ios to get it.
Also did "BRCMF_SDIO_MAX_ACCESS_ERRORS" limit help?
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @raks_99
Increasing BRCMF_SDIO_MAX_ACCESS_ERRORS value didn't help. We disabled CONFIG_PM_SLEEP to avoid SDIO sleep and wake up cycles and found that the issue was not able to be reproduced. For now we are proceeding with that as a stop gap solution as we are pressed on time for our production.
Regards,
Rupesh.