Closed angelofraietta closed 1 year ago
The VC4 OpenGL driver is still described as "experimental" by the Raspberry Foundation. This explains why. I have written my observations here: https://github.com/Stellarium/stellarium/wiki/Raspberry-Pi
I observed a similar problem around GPU memory when using the DSS layer. Our "official" platforms are x86/x64 systems. You are cordially invited to help improving its stability on Raspberry Pi /ARM as well.
Do you get crashing on the same script? I had trouble with installing messa. If you have it crashing the same, then I will know it is not just the environment I have built under.
Thanks -- Dr Angelo Fraietta A.Eng, A.Mus.A, BA(Hons), Ph.D.
Home Page http://www.smartcontroller.com.au/
There are those who seek knowledge for the sake of knowledge - that is CURIOSITY There are those who seek knowledge to be known by others - that is VANITY There are those who seek knowledge in order to serve - that is LOVE Bernard of Clairvaux (1090 - 1153)
On Fri, Nov 16, 2018 at 10:01 AM Georg Zotti notifications@github.com wrote:
The VC4 OpenGL driver is still described as "experimental" by the Raspberry Foundation. This explains why. I have written my observations here: https://github.com/Stellarium/stellarium/wiki/Raspberry-Pi
I observed a similar problem around GPU memory when using the DSS layer. Our "official" platforms are x86/x64 systems. You are cordially invited to help improving its stability on Raspberry Pi /ARM as well.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Stellarium/stellarium/issues/550#issuecomment-439221867, or mute the thread https://github.com/notifications/unsubscribe-auth/AFKcNXL4MzqSMFLGrWLH7UQ-Qtdi5Umyks5uvfJXgaJpZM4Yja1h .
I recently installed Raspbian/NOOBS and then again followed the instructions on our wiki which I grabbed from anholt. Building drm and mesa worked flawlessly. Sorry, cannot test again on this RasPi3 before about December 15.
I did run again from the instructions and it did compile fine. It appears that that crash is happening with other programs, indicating the experimental Open GL as you suggested. I would appreciate if you could try running that script when you get the chance in December.
-- Dr Angelo Fraietta A.Eng, A.Mus.A, BA(Hons), Ph.D.
Home Page http://www.smartcontroller.com.au/
There are those who seek knowledge for the sake of knowledge - that is CURIOSITY There are those who seek knowledge to be known by others - that is VANITY There are those who seek knowledge in order to serve - that is LOVE Bernard of Clairvaux (1090 - 1153)
On Tue, Nov 20, 2018 at 11:24 AM Georg Zotti notifications@github.com wrote:
I recently installed Raspbian/NOOBS and then again followed the instructions on our wiki which I grabbed from anholt. Building drm and mesa worked flawlessly. Sorry, cannot test again on this RasPi3 before about December 15.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Stellarium/stellarium/issues/550#issuecomment-440091118, or mute the thread https://github.com/notifications/unsubscribe-auth/AFKcNeI24uNbkcFzsM5PwK3yCBoEEDQZks5uw0vPgaJpZM4Yja1h .
Hmm, seems I did not say exactly which December... :-)
double_stars.ssc runs perfectly on my RPi4 (4GB RAM) on current Raspbian Buster.
However, on the RPi3+, it fails quite soon with access violation. dmesg shows tons of errors:
[drm:vc4_bo_create [vc4]] *ERROR* Failed to allocate from CMA:
There are a few bug discussions in the RPi fora, e.g. https://www.raspberrypi.org/forums/viewtopic.php?t=223363, however I have not found a solution that works.
I switched off DSO images on my next test, and - voilà - it worked. So there is an issue with texture memory, and the ever growing collection of DSO images will not make things easier. Probably we must provide a little script for texture minimisation (convert all to 128x128px, or provide a reduced collection?) However, I wonder why texture allocation, or rather unsuccessful allocation, is not handled more gracefully?
This is a good task for the community to participate in the contribution into Stellarium. Who wants to help us?
@angelofraietta @gzotti is the problem still alive?
OK, just ran the script twice on my RPi3B+ with Raspbian 10 (buster) and its Stellarium 0.18.3. No issues. Then I saw the background DSO images were switched off. Activated, ran, and -- boom. Memory error. So yes, still active, and I doubt we can do anything here.
I have not yet updated this RPi3B+ to V11/Bullseye. I also did not self-compile here.
Update for current RPi3B+ Raspberry OS 11/Bullseye: Its repo provides Stellarium 0.20.4.
I have not stepped further into finetuning applications. Let's say RPi3 enjoys partial support...
Hello @angelofraietta!
OK, developers can reproduce the issue. Thanks for the report!
Hello @angelofraietta!
The bug or issue has been fixed! You may test it via building Stellarium from source code or wait the weekly development snapshot...
Hello @angelofraietta!
Please check the fresh version (development snapshot) of Stellarium: https://github.com/Stellarium/stellarium-data/releases/tag/weekly-snapshot
Hello @angelofraietta!
Please check the latest stable version of Stellarium: https://github.com/Stellarium/stellarium/releases/latest
Expected Behaviour
Stellarium will run complex displays without crashing
Actual Behaviour
Describe or maybe attach a screenshot? Find a link to a video showing it. I found that I can get same result running a script https://drive.google.com/file/d/1T6cfnYuQWCZZQtvNdP5xSiCQmGjgeyKd/view?usp=sharing
Steps to reproduce
This crashes on raspberry Pi. I first discovered bug when doing rapid remote control changes. I found I could reproduce crash consistently just by running the script double_stars.ssc
It does run some scripts OK, however, I get it to consitently fail on this script
It runs fine on both Mac and Windows - Just Raspberry Pi
System
Also tried with latest pull from github - crashes in slightly different place
Operating system: <Name, version number> This was tried with Raspbian stretch.
Graphics Card: <Manufacturer (likely Intel, NVidia, AMD?), Model (HD, Geforce, Radeon..., with model number), driver version?> This has been tested on Raspberry Pi 3B and Raspberry Pi 3B+
Open GL tested http://www.raspberryconnect.com/gamessoftware/item/314-trying_out_opengl_on_raspberry_pi_3
Logfile
If possible, attach the logfile
log.txt
from your user data directory. Look into the Guide for its location.You will notice in the journal below that this happens as it is crashing
Nov 16 08:46:37 hb-b827eb9089ee kernel: vc4-drm soc:gpu: failed to allocate buffer with size 5595136 Nov 16 08:46:37 hb-b827eb9089ee kernel: vc4-drm soc:gpu: failed to allocate buffer with size 16777216 Nov 16 08:46:37 hb-b827eb9089ee kernel: vc4-drm soc:gpu: failed to allocate buffer with size 16777216
SystemJournal.txt