[Bug 267193] devel/gettext-tools: msgmerge -q /dev/null /dev/null hangs uninterruptedly on amd64 in kvm

From: <bugzilla-noreply_at_freebsd.org>
Date: Wed, 09 Nov 2022 23:01:12 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267193

Kubilay Kocak <koobs@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Product|Base System                 |Ports & Packages
          Component|kern                        |Individual Port(s)
           Keywords|                            |needs-qa
           Severity|Affects Only Me             |Affects Some People
                 CC|                            |elizabeth.jennifer.myers@gm
                   |                            |ail.com
            Version|13.1-RELEASE                |Latest
              Flags|                            |maintainer-feedback?(elizab
                   |                            |eth.jennifer.myers@gmail.co
                   |                            |m),
                   |                            |maintainer-feedback?(tijl@F
                   |                            |reeBSD.org)

--- Comment #1 from Kubilay Kocak <koobs@FreeBSD.org> ---
^Triage: devel/gettext-tools maintainer re-assigned to virtualization@
(nobody), this issue will be difficult to progress without a coordinator /
someone to assist in isolation.


In the absence of positive evidence of a root cause in base, the component as
reported (devel/gettext-tools) is more appropriate until we have that. If and
when we have that, we can create a dependent base issue to track resolution
there.

As far as additional information / debugging that might help isolate, things I
can think of:

- Assuming 'KVM' means this is a FreeBSD guest on another OS, full details of
the host system / environment

- run msgmerge under truss, and providing that trace log as an attachment,
which might provide some hints as to whats going on.

- test msgmerge under latest 12.4-RELEASE and 14-CURRENT images, to see if and
how behaviour differs.

- provide a full `pkg version -v` output (as an attachment), of the software
versions necessary in the reproduction case

- provide a full /var/run/dmesg.boot (as an attachment), of the system details
of the reproduction case

@Tijl As maintainer, we'd appreciate any assistance/clues/advice to help
progress the issue. Can you think of any other things that might be handy to
isolate?

-- 
You are receiving this mail because:
You are the assignee for the bug.