On 2023/1/4 下午8:59, Michal Koutný wrote:
On Wed, Jan 04, 2023 at 07:13:59PM +0800, Heyi Guo
wrote:
Jan 04 16:10:57 ali2600 systemd[1]: Caught , dumped core as pid 7516.
Jan 04 16:10:57 ali2600 systemd[1]: Freezing execution.
Jan 04 16:10:57 ali2600 phosphor-dump-manager[7536]: Failed to list
On Wed, Jan 04, 2023 at 07:13:59PM +0800, Heyi Guo
wrote:
> Jan 04 16:10:57 ali2600 systemd[1]: Caught , dumped core as pid 7516.
> Jan 04 16:10:57 ali2600 systemd[1]: Freezing execution.
> Jan 04 16:10:57 ali2600 phosphor-dump-manager[7536]: Failed to list units:
> Transport endpoint is not
Hi Michal,
Actually we have upgraded systemd version to 250.5, but the issue will
still happen.
Navigating the journal log context of when the error message is first
printed, I found there is a SEGV fault of systemd-udevd:
Jan 04 16:10:40 ali2600 systemd[1]: Created slice Slice
On Wed, Jan 04, 2023 at 04:51:22PM +0800, Heyi Guo
wrote:
> The issue happened again, but the /proc/1/stack and
> /proc/$pid_of_dbus-broker/stack are both empty on our platform.
(You reported previously the version was v249 (which is behind the last
two upstream versions, so it may be a good
On 2022/12/1 下午9:57, Michal Koutný wrote:
Hello Heyi.
On Tue, Nov 29, 2022 at 12:44:12PM +0800, Heyi Guo
wrote:
Is there any known issue which will cause this problem? Or do you have any
suggestion on how to debug?
As written in the report, it looks like dbus-daemon or PID1 itself not
Thanks very much; we'll try to get the information when the issue
happens next time.
Heyi
On 2022/12/1 下午9:57, Michal Koutný wrote:
Hello Heyi.
On Tue, Nov 29, 2022 at 12:44:12PM +0800, Heyi Guo
wrote:
Is there any known issue which will cause this problem? Or do you have any
suggestion
Hello Heyi.
On Tue, Nov 29, 2022 at 12:44:12PM +0800, Heyi Guo
wrote:
> Is there any known issue which will cause this problem? Or do you have any
> suggestion on how to debug?
As written in the report, it looks like dbus-daemon or PID1 itself not
responding. Some insights may be obtained by
Hi all,
We are runing OpenBMC 2.11.0 release which is based on yocto Honister
and systemd 249.7 release, and we find systemctl hangs occasionally. The
phenomenon is just like the below issue:
https://github.com/openbmc/openbmc/issues/1097
systemctl command will always return timeout and
