Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Boot/reboot/shutdown splash screen #1

Closed
agherzan opened this issue Feb 12, 2016 · 8 comments
Closed

Boot/reboot/shutdown splash screen #1

agherzan opened this issue Feb 12, 2016 · 8 comments
Assignees

Comments

@agherzan
Copy link
Contributor

agherzan commented Feb 12, 2016

Steps to reproduce issue

Connect to the HDMI connected to a monitor
Boot the device

Expected result

Resin logo splash screen should be visible

Actual result

RaspberryPi: No splash screen at boot

Other information

Reported by: Andrei Gherzan

Test configuration: RaspberryPi

Test case number: TC07

Test run: https://resinio.testlodge.com/projects/16238/runs/192879?tab=2&run_section_id=168778&executed_case_id=9333888#executed_case_9333888

@agherzan agherzan added the bug label Feb 12, 2016
@agherzan agherzan changed the title Splash Boot/reboot/shutdown splash screen Feb 12, 2016
@telphan
Copy link
Contributor

telphan commented Mar 4, 2016

Is this issue present on Raspberrypi or Raspberrypi2?

@agherzan
Copy link
Contributor Author

agherzan commented Mar 4, 2016

Rpi1

@telphan
Copy link
Contributor

telphan commented Mar 4, 2016

Well, this is not exactly a bug. The reason for the splash not showing on rpi1 is slow hardware. It takes too long to show the splash. Therefore the boot finishes before plymouth has a chance of showing splash.

@agherzan
Copy link
Contributor Author

agherzan commented Mar 4, 2016

Yes. We are aware of this but maybe we could optimize boot to inject the splash service sooner in the boot seq services?

@telphan
Copy link
Contributor

telphan commented Mar 4, 2016

There is only one way that springs to mind, but that involves making use of an initramfs.

@agherzan agherzan added prio/medium and removed bug labels Jun 6, 2016
@lurch
Copy link

lurch commented Oct 12, 2016

The new version of Raspbian includes a splashscreen, maybe there's code you can borrow from there?

@agherzan
Copy link
Contributor Author

Sounds interesting. We will take a look on this.

@agherzan
Copy link
Contributor Author

This issue was moved to balena-os/balena-os#71

@floion floion mentioned this issue Oct 11, 2017
floion added a commit that referenced this issue Feb 27, 2020
This new boot firmware fixes the following error on rpi4 that
occurs when playing video in a continuous loop:

INFO: task kworker/2:2:319 blocked for more than 120 seconds.
Tainted: G         C        4.19.66 #1
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message
kworker/2:2     D    0   319      2 0x00000028
Workqueue: events dbs_work_handler
Call trace:
__switch_to+0xa8/0xe8
__schedule+0x254/0x850
schedule+0x38/0x98
schedule_timeout+0x324/0x458
wait_for_common+0x148/0x170
wait_for_completion+0x28/0x38
rpi_firmware_transaction+0xa0/0xf0
rpi_firmware_property_list+0x108/0x268
rpi_firmware_property+0x78/0xf8
bcm2835_cpufreq_clock_property.constprop.2+0x54/0x88
bcm2835_cpufreq_driver_target_index+0xa4/0x128
__cpufreq_driver_target+0x1a0/0x588
od_dbs_update+0x140/0x1a0
dbs_work_handler+0x44/0x78
process_one_work+0x1ec/0x458
worker_thread+0x48/0x430
kthread+0x130/0x138
ret_from_fork+0x10/0x1c

Changelog-entry: Update the boot firmware to 20200220 drop so we fix a rpi4 kernel issue when doing video playback in a continuous loop
Signed-off-by: Florin Sarbu <florin@balena.io>
floion added a commit that referenced this issue Feb 27, 2020
This new boot firmware fixes the following error on rpi4 that
occurs when playing video in a continuous loop:

INFO:  task kworker/2:2:319 blocked for more than 120 seconds.
       Tainted: G         C        4.19.66 #1
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kworker/2:2     D    0   319      2 0x00000028
Workqueue:  events dbs_work_handler
Call trace:
__switch_to+0xa8/0xe8
__schedule+0x254/0x850
schedule+0x38/0x98
schedule_timeout+0x324/0x458
wait_for_common+0x148/0x170
wait_for_completion+0x28/0x38
rpi_firmware_transaction+0xa0/0xf0
rpi_firmware_property_list+0x108/0x268
rpi_firmware_property+0x78/0xf8
bcm2835_cpufreq_clock_property.constprop.2+0x54/0x88
bcm2835_cpufreq_driver_target_index+0xa4/0x128
__cpufreq_driver_target+0x1a0/0x588
od_dbs_update+0x140/0x1a0
dbs_work_handler+0x44/0x78
process_one_work+0x1ec/0x458
worker_thread+0x48/0x430
kthread+0x130/0x138
ret_from_fork+0x10/0x1c

Changelog-entry: Update the boot firmware to 20200220 drop so we fix a rpi4 kernel issue when doing video playback in a continuous loop
Signed-off-by: Florin Sarbu <florin@balena.io>
floion added a commit that referenced this issue Feb 27, 2020
This new boot firmware fixes the following error on rpi4 that
occurs when playing video in a continuous loop:

INFO:task kworker/2:2:319 blocked for more than 120 seconds.
       Tainted: G         C        4.19.66 #1
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kworker/2:2     D    0   319      2 0x00000028
Workqueue:events dbs_work_handler
Call trace:
__switch_to+0xa8/0xe8
__schedule+0x254/0x850
schedule+0x38/0x98
schedule_timeout+0x324/0x458
wait_for_common+0x148/0x170
wait_for_completion+0x28/0x38
rpi_firmware_transaction+0xa0/0xf0
rpi_firmware_property_list+0x108/0x268
rpi_firmware_property+0x78/0xf8
bcm2835_cpufreq_clock_property.constprop.2+0x54/0x88
bcm2835_cpufreq_driver_target_index+0xa4/0x128
__cpufreq_driver_target+0x1a0/0x588
od_dbs_update+0x140/0x1a0
dbs_work_handler+0x44/0x78
process_one_work+0x1ec/0x458
worker_thread+0x48/0x430
kthread+0x130/0x138
ret_from_fork+0x10/0x1c

Changelog-entry: Update the boot firmware to 20200220 drop so we fix a rpi4 kernel issue when doing video playback in a continuous loop
Signed-off-by: Florin Sarbu <florin@balena.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants