Thanks for the reply / advice but the timeshift to RAM is a basic functionality which I can't 'live' without.
It looks that latest freeze on RPi 4B / 4G happened when there're still a plenty of free RAM and there was no obvious reason for OOM killer to be activated (I know such cases were reported on earlier - 32 bit - kernel and should be already fixed now).
But I wanted to point out that now it's a worse case (than earlier) due to several minutes complete freeze after OOM event.
Content embedded from external sources will not be displayed without your consent.
Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.
Also encountered on another RPi 4B / 4G, running LE Nightly 20210928.
Content embedded from external sources will not be displayed without your consent.
Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.
It's a very annoying behaviour as it takes several minutes until LE returns to operation and there are intensive (perhaps write) operations with storage. It looks it appears more likely when the TV channel with high bitrate is played.
The same issue after upgrading to LE 11 Nightly 20210928 with Kodi 20.0-ALPHA1 (19.90.101).
I am not able to point out what's the difference but affected channels have no Teletext stream and Kodi with Tvheadend 43 can't use DVB subtitles in this case to display them online (despite it's detected that subtitles are there as they can be turned on/off and they are also recorded properly).
The same issue after upgrading Tvheadend service 4.3 (Alpha) to 10.80.0.102 package (4.3-1979). Hopefully the incompatibility will be fixed in some further Kodi release.
I have experienced several times a strange issue on current LE 11 Nightlies, installed on RPi 4B / 2GB at external HDD, connected through USB/SATA adapter. TVheadend server 4.3 + TVheadend client used.
It's a more or less random freeze of LE (did not even respond to PING, SSH console was frozen as well, no response to remote control and during that time there was an intensive HDD activity) and it looks it's related to TimeShift function which activated oom-killer.
After some time (up to several minutes) the LE usually starts responding again, even the SSH console starts where it stopped responding (without disconnection).
There are also some random issues with audio - sometimes audio does not start when I switch the channel - it's necessary to switch to another channel and back. Sometimes (usually when the live stream has a temporary corruption due to bad signal) it leads to freeze playing (a percentage circle appears on display and stops somewhere between 0-100%). Using TimeShift to move back or forward is usually possible (even though the TimeShift pointer gets confused and does not work correctly until stopped / started or switch to another channel). When I got back, the stream was playng until the problematic point where it freezed again. Unfortunately I don't have a stream recorded as it's not possible to save the TimeShift data (configured to use RAM only).
This is a part of kernel log, showing the several attempts to shift back before the freeze point:
Content embedded from external sources will not be displayed without your consent.
Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.
I can confirm BCM2835 is reported in pure original RPi 4B and perhaps (due to reasonable pricing) it's not very likely there are some fake devices ever but who knows...
OK, I see... Your English is maybe even better then mine, it's not my first language as well...
Well, there are 2 basic options how 'deep' the RPi 4B's shutdown can be. It depends on bootloader configuration.
You can check your current config with: vcgencmd bootloader_config command.
When you change the default option POWER_OFF_ON_HALT=0 to POWER_OFF_ON_HALT=1, you could connect a LED in serie with resistor (about 500 - 1000 Ohm) to unused USB port. So it turns off when the RPi is completely down.
Yeah I understand but sometimes there are very strange things between 2 specific devices / OS releases... I don't know much how SMB protocol works but I think it's a bit complex. And recently I was facing to a strange issue with LE on RPi serving files to Windows client...
OK, perhaps I don't understand the specific use case properly as from my perspective there's no need to see a rolling text on display...
I am using RPi 4B as well and in my case the display stops receiving HDMI signal when I turn off LE. So I believe it's a sufficient indication (among others possible - for instance I am using GPIOs + LEDs + buttons to see the current state or to shut down the device).
It depends on which HW you are using... Usually when you shutdown LE, it turns off the device which is running on. And there are usually some status LEDs so you should see the current status.
If the request is more sophisticated, perhaps the shutdown script could be upgraded to do another (than currently {in}visible) indication...
Would gladly change 2GB model for the same memory but earlier revision
Well, unfortunately it won't work ;-). Despite I don't currently use IPTV, I wouldn't replace my earlier RPi revisions ( which are working fine for all of my use cases) with newer devices with the same memory size (and with a known issues).
Also it's maybe possible a fake / clone RPi 4B devices are yet on the market... Try to find a trusted Raspberry distributor who can perhaps help with the HW release.
Another chance could be that some further kernel fix could fix an application issue in future...
The Raspicontroller (Android tool) identifies all three LE's as BCM2835 but my Pi-hole running Raspi OS on identical RPi4/4GB is identified as BCM2711.
(The tool says that LE's OS isn't supported...)
All has identical PCB's with same revision.
Edit:
Checked within LE (System Info): It clearly says HW: BCM2835, Rev: c03114
Display More
Yeah I understand. But it's not so simple... Here is what I meant: