Bug 2492029 - 100% CPU usage after upgrading from 1.9.22 to 1.9.24 (in updates-testing) and rebooting
Summary: 100% CPU usage after upgrading from 1.9.22 to 1.9.24 (in updates-testing) and...
Keywords:
Status: ON_QA
Alias: None
Product: Fedora
Classification: Fedora
Component: haveged
Version: 43
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Jiri Hladky
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-06-23 22:35 UTC by Rudd-O DragonFear
Modified: 2026-08-05 00:26 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Rudd-O DragonFear 2026-06-23 22:35:45 UTC
An strace of the spinning haveged shows this:

```
accept4(0, NULL, NULL, SOCK_CLOEXEC|SOCK_NONBLOCK) = -1 ENOTSOCK (Socket operation on non-socket)
pselect6(4, [0], [3], NULL, {tv_sec=2, tv_nsec=0}, {sigmask=[], sigsetsize=8}) = 1 (in [0], left {tv_sec=1, tv_nsec=999999519})
```

It's doing that in a loop.

Downgrading to 1.9.22 resolves the problem.

Reproducible: Always

Steps to Reproduce:
1.upgrade to new version in updates-testing
2.reboot
3.observe with top
Actual Results:
100% CPU

Expected Results:
normal system operation

Comment 1 Rudd-O DragonFear 2026-06-23 22:36:27 UTC
Nothing in the journal says anything useful about haveged.

Comment 2 Rudd-O DragonFear 2026-06-23 22:36:49 UTC
Correction: only ONE message since boot in the log from haveged:

Jun 23 22:18:51 fedora haveged[256]: haveged: fills: 1, generated: 512 K bytes, RNDADDENTROPY: 256

Comment 3 Fedora Update System 2026-06-24 08:57:36 UTC
FEDORA-2026-28f26f5294 (haveged-1.9.26-1.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-28f26f5294

Comment 4 Fedora Update System 2026-06-24 08:57:43 UTC
FEDORA-2026-5ddd0941a8 (haveged-1.9.26-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-5ddd0941a8

Comment 5 Fedora Update System 2026-06-24 08:57:47 UTC
FEDORA-EPEL-2026-e15fb7f042 (haveged-1.9.26-1.el10_2) has been submitted as an update to Fedora EPEL 10.2.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-e15fb7f042

Comment 6 Fedora Update System 2026-06-24 08:57:53 UTC
FEDORA-EPEL-2026-e6d245c837 (haveged-1.9.26-1.el10_3) has been submitted as an update to Fedora EPEL 10.3.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-e6d245c837

Comment 7 Fedora Update System 2026-06-24 08:57:58 UTC
FEDORA-EPEL-2026-4245f60523 (haveged-1.9.26-1.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-4245f60523

Comment 8 Jiri Hladky 2026-06-24 10:48:56 UTC
Thank you for the bug report!
  
Root cause: socket_fd was declared as a global int socket_fd; in havegecmd.c, which defaults to 0. With the new --no-command flag added in v1.9.24, socket initialization is skipped, so socket_fd stays at 0. The daemon loop checks if 
  (socket_fd >= 0) and enters accept4(0, ...), spinning on stdin (fd 0) in a tight loop.

Fix (v1.9.26): Initialize socket_fd = -1 so the daemon loop correctly skips the accept path when command mode is disabled.

  - Upstream release: https://github.com/jirka-h/haveged/releases/tag/v1.9.26
  - Bodhi update (F44): https://bodhi.fedoraproject.org/updates/FEDORA-2026-28f26f5294
  - Updates also submitted for F43, EPEL 10.2, EPEL 10, and EPEL 9.

Could you help to verify the fix once the update appears in updates-testing?

Comment 9 Fedora Update System 2026-06-25 16:30:36 UTC
FEDORA-2026-28f26f5294 has been pushed to the Fedora 44 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-28f26f5294`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-28f26f5294

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2026-06-25 16:35:17 UTC
FEDORA-EPEL-2026-e6d245c837 has been pushed to the Fedora EPEL 10.3 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-e6d245c837

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 11 Fedora Update System 2026-06-25 16:40:53 UTC
FEDORA-EPEL-2026-4245f60523 has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-4245f60523

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 12 Fedora Update System 2026-06-25 16:41:32 UTC
FEDORA-EPEL-2026-e15fb7f042 has been pushed to the Fedora EPEL 10.2 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-e15fb7f042

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 13 Fedora Update System 2026-06-25 16:54:35 UTC
FEDORA-2026-5ddd0941a8 has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-5ddd0941a8`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-5ddd0941a8

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 14 Fedora Update System 2026-08-05 00:25:05 UTC
FEDORA-EPEL-2026-e15fb7f042 (haveged-1.9.26-1.el10_2) has been pushed to the Fedora EPEL 10.2 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 15 Fedora Update System 2026-08-05 00:26:31 UTC
FEDORA-EPEL-2026-4245f60523 (haveged-1.9.26-1.el9) has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.