Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

psplash-default cpu hogging

Description

During the latest testing of master psplash-default process was observed to hog 1 core at 100% on Upsquared. The process seems to be stuck in a some sort of a loop.

using perf ftrace to trace the process produced 46MB log file for 1 second, the file attached is compressed

attaching dmesg and journal

—

This behavior was also observed during testing cycle of halibut 8.0.6 on h3ulcb, splash-quit service failed to stop:

-- Logs begin at Wed 2020-03-18 21:35:09 UTC, end at Thu 2020-03-19 09:56:34 UTC. -- Mar 18 21:35:11 h3ulcb systemd[1]: Starting Terminate Psplash Boot Screen... Mar 18 21:35:12 h3ulcb systemd[1]: psplash-quit.service: Main process exited, code=exited, status=255/n/a Mar 18 21:35:12 h3ulcb systemd[1]: psplash-quit.service: Failed with result 'exit-code'. Mar 18 21:35:12 h3ulcb systemd[1]: Failed to start Terminate Psplash Boot Screen.

 

 

Environment

None

Attachments

5
  • 17 Mar 2020, 11:42 PM
  • 17 Mar 2020, 11:42 PM
  • 16 Mar 2020, 11:55 PM
  • 16 Mar 2020, 11:55 PM
  • 16 Mar 2020, 11:54 PM

Activity

Edi Feschiyan 
August 24, 2021 at 6:20 AM

The commits that Scott pushed are working and this was fixed, I haven't seen psplash hog the cpu again since then.

Jan-Simon Moeller 
October 12, 2020 at 8:20 PM

Do we need to follow-up ?

Jan-Simon Moeller 
March 31, 2020 at 12:52 PM

What was the psplash issue again ?

Edi Feschiyan 
March 17, 2020 at 11:41 PM
(edited)

Fixed

Details

Assignee

Reporter

Contract ID

Hardware Platform(s) Affected

Intel Upsquare

Components

Affects versions

Priority

Created March 16, 2020 at 11:54 PM
Updated August 31, 2021 at 3:22 PM
Resolved August 24, 2021 at 6:20 AM

Flag notifications