Bug 2326710

Summary: Boot in VirtualBox env: agetty segfaults
Product: [Fedora] Fedora Reporter: George R. Goffe <grgoffe>
Component: util-linuxAssignee: Karel Zak <kzak>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 42CC: jamacku, j, kdudka, kzak, lnykryn, zbyszek
Target Milestone: ---Keywords: Upgrades
Target Release: ---Flags: kzak: mirror+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: util-linux-2.40.4-10.fc42 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2026-02-13 01:47:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description George R. Goffe 2024-11-16 20:37:22 UTC 
[ 5890.609215] agetty[45601]: segfault at 0 ip 00007fc13dd6b430 sp 00007fff10554d48 error 4 in libc.so.6[167430,7fc13dc04000+16e000] likely on CPU 0 (core 0, socket 0)
[ 5890.613976] Code: d2 0f 84 b7 0f 00 00 48 83 fa 01 0f 84 b9 0f 00 00 49 89 d3 89 f1 89 f8 48 83 e1 3f 48 83 e0 3f 83 f9 30 77 45 83 f8 30 77 40 <f3> 0f 6f 0f f3 0f 6f 16 66 0f ef c0 66 0f 74 c1 66 0f 74 ca 66 0f
[ 5906.346811] agetty[45658]: segfault at 0 ip 00007fe64a339430 sp 00007fff2ff61ae8 error 4 in libc.so.6[167430,7fe64a1d2000+16e000] likely on CPU 1 (core 1, socket 0)
[ 5906.349537] Code: d2 0f 84 b7 0f 00 00 48 83 fa 01 0f 84 b9 0f 00 00 49 89 d3 89 f1 89 f8 48 83 e1 3f 48 83 e0 3f 83 f9 30 77 45 83 f8 30 77 40 <f3> 0f 6f 0f f3 0f 6f 16 66 0f ef c0 66 0f 74 c1 66 0f 74 ca 66 0f
[ 5912.586706] agetty[45744]: segfault at 0 ip 00007f434425e430 sp 00007ffc2c279548 error 4 in libc.so.6[167430,7f43440f7000+16e000] likely on CPU 1 (core 1, socket 0)
[ 5912.589318] Code: d2 0f 84 b7 0f 00 00 48 83 fa 01 0f 84 b9 0f 00 00 49 89 d3 89 f1 89 f8 48 83 e1 3f 48 83 e0 3f 83 f9 30 77 45 83 f8 30 77 40 <f3> 0f 6f 0f f3 0f 6f 16 66 0f ef c0 66 0f 74 c1 66 0f 74 ca 66 0f
[ 5921.114570] agetty[45807]: segfault at 0 ip 00007f19198cf430 sp 00007ffd01f1f618 error 4 in libc.so.6[167430,7f1919768000+16e000] likely on CPU 0 (core 0, socket 0)
[ 5921.119133] Code: d2 0f 84 b7 0f 00 00 48 83 fa 01 0f 84 b9 0f 00 00 49 89 d3 89 f1 89 f8 48 83 e1 3f 48 83 e0 3f 83 f9 30 77 45 83 f8 30 77 40 <f3> 0f 6f 0f f3 0f 6f 16 66 0f ef c0 66 0f 74 c1 66 0f 74 ca 66 0f


Reproducible: Always

Steps to Reproduce:
1.right after boot; I wasn't doing anythng except for preparing to login
2.
3.
Actual Results:  
see details


[ 5890.609215] agetty[45601]: segfault at 0 ip 00007fc13dd6b430 sp 00007fff10554d48 error 4 in libc.so.6[167430,7fc13dc04000+16e000] likely on CPU 0 (core 0, socket 0)
[ 5890.613976] Code: d2 0f 84 b7 0f 00 00 48 83 fa 01 0f 84 b9 0f 00 00 49 89 d3 89 f1 89 f8 48 83 e1 3f 48 83 e0 3f 83 f9 30 77 45 83 f8 30 77 40 <f3> 0f 6f 0f f3 0f 6f 16 66 0f ef c0 66 0f 74 c1 66 0f 74 ca 66 0f
[ 5906.346811] agetty[45658]: segfault at 0 ip 00007fe64a339430 sp 00007fff2ff61ae8 error 4 in libc.so.6[167430,7fe64a1d2000+16e000] likely on CPU 1 (core 1, socket 0)
[ 5906.349537] Code: d2 0f 84 b7 0f 00 00 48 83 fa 01 0f 84 b9 0f 00 00 49 89 d3 89 f1 89 f8 48 83 e1 3f 48 83 e0 3f 83 f9 30 77 45 83 f8 30 77 40 <f3> 0f 6f 0f f3 0f 6f 16 66 0f ef c0 66 0f 74 c1 66 0f 74 ca 66 0f
[ 5912.586706] agetty[45744]: segfault at 0 ip 00007f434425e430 sp 00007ffc2c279548 error 4 in libc.so.6[167430,7f43440f7000+16e000] likely on CPU 1 (core 1, socket 0)
[ 5912.589318] Code: d2 0f 84 b7 0f 00 00 48 83 fa 01 0f 84 b9 0f 00 00 49 89 d3 89 f1 89 f8 48 83 e1 3f 48 83 e0 3f 83 f9 30 77 45 83 f8 30 77 40 <f3> 0f 6f 0f f3 0f 6f 16 66 0f ef c0 66 0f 74 c1 66 0f 74 ca 66 0f
[ 5921.114570] agetty[45807]: segfault at 0 ip 00007f19198cf430 sp 00007ffd01f1f618 error 4 in libc.so.6[167430,7f1919768000+16e000] likely on CPU 0 (core 0, socket 0)
[ 5921.119133] Code: d2 0f 84 b7 0f 00 00 48 83 fa 01 0f 84 b9 0f 00 00 49 89 d3 89 f1 89 f8 48 83 e1 3f 48 83 e0 3f 83 f9 30 77 45 83 f8 30 77 40 <f3> 0f 6f 0f f3 0f 6f 16 66 0f ef c0 66 0f 74 c1 66 0f 74 ca 66 0f
Comment 1 Lukáš Nykrýn 2024-11-18 10:31:52 UTC 
This does not look like an initscripts bug. agetty is part of util-linux so let's try it there, but I would expect that there is something really wrong in the system. If you are an experienced user, I would suggest stopping the boot in the initrd, checking the disk and trying to reinstall related packages (util-linux, glibc,...). From the initrd you might also be able to check the logs and something there might indicate what is wrong.
Comment 2 George R. Goffe 2024-11-21 01:01:32 UTC 
Lukáš

Thanks for responding.

Can you point me to where I can find out about stopping the system in initrd please?

This VM is REALLY close to the system I use every day... The problem doesn't exist on this system... So, I would guess that the problem is in the emulation or whatever VirtualBox "really" does that isn't EXACTLY like how the "real" hardware behaves.

Best regards,

George...
Comment 3 George R. Goffe 2024-12-10 02:51:56 UTC 
Howdy,

Is this another "rawhide" mystery? Something has changed and I'm no longer receiving these messages.

Wtfover.

George...
Comment 4 Karel Zak 2025-02-25 11:52:49 UTC 
It's very probably an agetty issue https://github.com/util-linux/util-linux/pull/3425. It's visible only in some cases when agetty is executed with "-" instead of the terminal name, and libc cannot convert the file descriptor to the tty name.

I'll backport the patch to Fedora.
Comment 5 Aoife Moloney 2025-02-26 13:16:49 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle.
Changing version to 42.
Comment 6 Jason Tibbitts 2025-05-14 18:11:21 UTC 
I'm seeing this as well on a new F42 install in a VM running under KVM (managed by libvirtd).  agetty segfaults a few times at boot (presumably trying to start on a serial console) but I still get a login prompt on the spice console.  It looks like this is understood but I'll include some information just in case.

dmesg shows this (a few times as new ones are spawned):

[   19.139842] agetty[915]: segfault at 0 ip 00007f77d41cd8f7 sp 00007fff14ac9778 error 4 in libc.so.6[1678f7,7f77d4066000+16f000] likely on CPU 1 (core 0, socket 1)
[   19.139855] Code: 44 00 00 48 83 e6 f0 48 83 e7 f0 ba ff ff 00 00 45 31 c0 83 e1 0f 83 e0 0f 66 0f ef c0 39 c1 74 32 77 07 41 89 d0 91 48 87 f7 <66> 0f 6f 17 66 0f 6f 0e 4c 8d 48 0f 49 29 c9 4c 8d 15 f3 46 05 00

coredumpctl says:

           PID: 915 (agetty)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 11 (SEGV)
     Timestamp: Wed 2025-05-14 13:00:16 CDT (8min ago)
  Command Line: /sbin/agetty -o $'-- \\u' --noreset --noclear --keep-baud 115200,57600,38400,9600 - vt220
    Executable: /usr/bin/agetty
 Control Group: /system.slice/system-serial\x2dgetty.slice/serial-getty
          Unit: serial-getty
         Slice: system-serial\x2dgetty.slice
       Boot ID: 01fb0d65ff6d41958f6e216ac4f01130
    Machine ID: 96e568e46a9044afbe7964c3ab5e5614
      Hostname: rsync2.math.uh.edu
       Storage: /var/lib/systemd/coredump/core.agetty.0.01fb0d65ff6d41958f6e216ac4f01130.915.1747245616000000.zst (present)
  Size on Disk: 49.8K
       Package: util-linux/2.40.4-7.fc42
      build-id: 607eb896b03db1a02333bb3ecfcdd2302e7e8f52
       Message: Process 915 (agetty) of user 0 dumped core.

                Module /usr/bin/agetty from rpm util-linux-2.40.4-7.fc42.x86_64
                Module libcap.so.2 from rpm libcap-2.73-2.fc42.x86_64
                Module libsystemd.so.0 from rpm systemd-257.3-7.fc42.x86_64
                Stack trace of thread 915:
                #0  0x00007f77d41cd8f7 __strncmp_sse42 (libc.so.6 + 0x1678f7)
                #1  0x000055bd1eeec015 main (/usr/bin/agetty + 0x2015)
                #2  0x00007f77d40695f5 __libc_start_call_main (libc.so.6 + 0x35f5)
                #3  0x00007f77d40696a8 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x36a8)
                #4  0x000055bd1eeee4f5 _start (/usr/bin/agetty + 0x44f5)
                ELF object binary architecture: AMD x86-64
Comment 7 Jason Tibbitts 2025-11-14 15:48:10 UTC 
While this was never fixed in F42, I can verify that it has gone away in F43.
Comment 8 Karel Zak 2026-01-21 09:31:59 UTC 
We need to backport c69353a5e03779b4840f260ba52a7d2bb7b8943c in F42.
Comment 9 George R. Goffe 2026-01-21 18:26:20 UTC 
Karel,

Thanks for your responses above. They're appreciated.

Isn't FC 42 at EOL? 

As far as I'm concerned, this bug report can be retired.

My FC 42 died a month or so (of self-inflicted wounds, I'm afraid). I tried to re-install from the DVD I used when I first installed 42 but the end result was a FC44 system. I'm still digging out from the rubble. New and unexpected bugs... Oh how exciting... It's one of the things I live for... :-)

I found a panic in the newer kernel linux-6.19-rc5. I filed a bug in the RedHat Bugzilla just to provide information. I'm still trying to figure out their bug reporting environment... so no bug reports yet. I did find something wrong in their latest kernel (rc6) that seems to point to binutils... which led to a bug in building from their sourceware.org source repo. It never ends doesn't it?

Best regards and THANKS for all you do.

George...
Comment 10 Fedora Update System 2026-01-28 12:43:37 UTC 
FEDORA-2026-4e8253f339 (util-linux-2.40.4-10.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-4e8253f339
Comment 11 Fedora Update System 2026-01-29 01:51:50 UTC 
FEDORA-2026-4e8253f339 has been pushed to the Fedora 42 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-4e8253f339`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-4e8253f339

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 12 Fedora Update System 2026-02-13 01:47:44 UTC 
FEDORA-2026-4e8253f339 (util-linux-2.40.4-10.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 13 George R. Goffe 2026-02-14 01:14:30 UTC 
Howdy,

I am currently running FC45. 

Since writing this BR, I have not seen this problem so I think it should be closed.

Thanks,

George...