Tiny Core Base > Raspberry Pi

Pizero wifi crashes after a few minutes

(1/2) > >>

piran:
So,
I'm running a USB webcam from a pizero and doing some opencv manipulation on the iamges and serving the over flask. It works absolutely fine for a while but then the wifi stops working. doing a sudo wifi.sh will either say that there is no wifi adapter or the the wifi doesn't support scanning.
This only appear to happen if X is running, if  I drop out to the commandline then it keeps running just fine, so I can work with that, not sure where to go with the log files to work out a longer term solution.

mocore:


idk / perhaps
this "regular warnings mmc1 timeout waiting for hardware cmd interrupt #1556 " @ https://github.com/raspberrypi/firmware/issues/1556
issue has  the same log message as neterr2.txt [line:29]  ( could be your issue is some how related ....)
 ... that msg appears to stem from sdcard firmware driver ???

 + https://github.com/raspberrypi/firmware/issues/1556#issuecomment-816209634

--- Quote ---FYI there is a patch being upstreamed that provides a workaround to a hitherto unknown (to us) feature of the BCM2711 SDHCI controller.

--- End quote ---

sounds like fun  :o

could be worth trying the suggested fix?
,.. all though the few others who attempt to test reported mixed results 

may well be worth posting ur logs/err report to that issue

if the problem is between kernel & firmware
(afaik) the ppl who need to know are more likely to be reading https://github.com/raspberrypi/firmware/issues
than to signup/longing and down load  the logs from core forum (imho)

perhaps also relevant ( from neterr.txt, quoted so any one searching similar might find relevant txt!! )

--- Quote ---[ 1102.569585] mmc1: card 0001 removed
[ 1102.720594] mmc1: new high speed SDIO card at address 000

--- End quote ---
 


--- Quote ---[   48.742358] Xorg[4354]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
[  487.183525] brcmfmac: brcmf_sdio_readframes: RXHEADER FAILED: -110
[  487.183556] brcmfmac: brcmf_sdio_rxfail: abort command, terminate frame, send NAK
...
[ 1170.905604] brcmfmac: mmc_submit_one: CMD53 sg block write failed -110
[ 1170.905674] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
...
[ 1170.908330] brcmfmac: brcmf_sdio_hdparse: seq 188: max tx seq number error
[ 1181.150770] mmc1: Timeout waiting for hardware interrupt.
[ 1181.150903] brcmfmac: mmc_submit_one: CMD53 sg block write failed -110
[ 1181.150941] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
[ 1181.151845] brcmfmac: brcmf_sdio_hdparse: seq 244: max tx seq number error
[ 1181.152122] brcmfmac: brcmf_sdio_hdparse: HW header checksum error
[ 1181.152136] brcmfmac: brcmf_sdio_rxfail: terminate frame
...
[ 1200.257590] [drm:validate_tile_binning_config [vc4]] *ERROR* Failed to allocate binner memory: -12

--- End quote ---


** disclaimer i have no clue , just guess work , potentially barking up the wrong tree  ;)


--- Quote from: piran on December 11, 2024, 10:11:38 AM ---This only appear to happen if X is running, if 

--- End quote ---

which X version
which kernel version
what picore ...
ect

mocore:


--- Quote ---[ 1101.929557] CPU: 1 PID: 77 Comm: kworker/u13:0 Tainted: G         C         6.6.47-piCore-v8 #21
[ 1101.929577] Hardware name: Raspberry Pi Zero 2 W Rev 1.0 (DT)

--- End quote ---


 http://tinycorelinux.net/www/15.x/aarch64/releases/RPi/src/kernel/6.6.47-piCore-v8_.config


--- Quote from: mocore on December 11, 2024, 11:28:23 AM ---
which X version
which kernel version
what picore ...
ect

--- End quote ---

...what power supply !!!!  ( how many amps! )

piran:
Thank you for your help, it gives me some things to dig around with. I'll let you know if I get anywhere

piran:

--- Quote from: mocore on December 11, 2024, 06:00:59 PM ---
...what power supply !!!!  ( how many amps! )

--- End quote ---

Good call, it turns out to be the power supply, tried various different powers and it worked until I ran the program which put a little more stress on the system. Some just rebooted at that point.

Using a meaty powersupply and the problem has gone. Thanks

Navigation

[0] Message Index

[#] Next page