From: "Patton, Schuyler" <spatton@ti.com>
To: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: new port seeing ipmid exiting with seg fault
Date: Mon, 29 Aug 2022 15:15:48 +0000 [thread overview]
Message-ID: <66a2cce533124f56b60f68f9f0b807af@ti.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3879 bytes --]
Hi all,
In our port the ipmid is exiting with a seg fault. Does anyone have any suggestions on what to look at or what the problem might be? I have included some info I collected from systemctl and journalctl. Thanks in advance for any pointers, suggestions.
root@evb-am62xx:~# systemctl status phosphor-ipmi-host
x phosphor-ipmi-host.service - Phosphor Inband IPMI
Loaded: loaded (/lib/systemd/system/phosphor-ipmi-host.service; enabled; vendor preset: enabled)
Drop-In: /lib/systemd/system/phosphor-ipmi-host.service.d
`-10-override.conf
Active: failed (Result: core-dump) since Mon 2022-08-29 15:01:40 UTC; 3min 8s ago
Duration: 1.163s
Process: 368 ExecStart=/usr/bin/env ipmid (code=dumped, signal=SEGV)
Main PID: 368 (code=dumped, signal=SEGV)
Aug 29 15:01:40 evb-am62xx systemd[1]: phosphor-ipmi-host.service: Scheduled restart job, restart counter is at 2.
Aug 29 15:01:40 evb-am62xx systemd[1]: Stopped Phosphor Inband IPMI.
Aug 29 15:01:40 evb-am62xx systemd[1]: phosphor-ipmi-host.service: Start request repeated too quickly.
Aug 29 15:01:40 evb-am62xx systemd[1]: phosphor-ipmi-host.service: Failed with result 'core-dump'.
Aug 29 15:01:40 evb-am62xx systemd[1]: Failed to start Phosphor Inband IPMI.
root@evb-am62xx:~# journalctl | grep ipmi
Jan 01 00:00:04 evb-am62xx systemd[1]: /lib/systemd/system/phosphor-ipmi-net@.socket:3: Invalid interface name, ignoring: sys-subsystem-net-devices-%i.device
Jan 01 00:00:04 evb-am62xx systemd[1]: Created slice Slice /system/phosphor-ipmi-net.
Aug 29 15:01:19 evb-am62xx systemd[1]: Listening on phosphor-ipmi-net@eth0.socket.
Aug 29 15:01:21 evb-am62xx ipmid[329]: JSON file not found
Aug 29 15:01:22 evb-am62xx systemd-coredump[339]: Process 334 (netipmid) of user 0 dumped core.
Aug 29 15:01:22 evb-am62xx systemd[1]: phosphor-ipmi-net@eth0.service: Main process exited, code=dumped, status=11/SEGV
Aug 29 15:01:22 evb-am62xx systemd[1]: phosphor-ipmi-net@eth0.service: Failed with result 'core-dump'.
Aug 29 15:01:23 evb-am62xx systemd-coredump[338]: Process 329 (ipmid) of user 0 dumped core.
Aug 29 15:01:23 evb-am62xx systemd[1]: phosphor-ipmi-host.service: Main process exited, code=dumped, status=11/SEGV
Aug 29 15:01:23 evb-am62xx systemd[1]: phosphor-ipmi-host.service: Failed with result 'core-dump'.
Aug 29 15:01:38 evb-am62xx systemd[1]: phosphor-ipmi-net@eth0.service: Scheduled restart job, restart counter is at 1.
Aug 29 15:01:38 evb-am62xx systemd[1]: phosphor-ipmi-host.service: Scheduled restart job, restart counter is at 1.
Aug 29 15:01:39 evb-am62xx systemd-coredump[373]: Process 370 (netipmid) of user 0 dumped core.
Aug 29 15:01:39 evb-am62xx systemd[1]: phosphor-ipmi-net@eth0.service: Main process exited, code=dumped, status=11/SEGV
Aug 29 15:01:39 evb-am62xx systemd[1]: phosphor-ipmi-net@eth0.service: Failed with result 'core-dump'.
Aug 29 15:01:39 evb-am62xx systemd-coredump[371]: Process 368 (ipmid) of user 0 dumped core.
Aug 29 15:01:39 evb-am62xx systemd[1]: phosphor-ipmi-host.service: Main process exited, code=dumped, status=11/SEGV
Aug 29 15:01:39 evb-am62xx systemd[1]: phosphor-ipmi-host.service: Failed with result 'core-dump'.
Aug 29 15:01:40 evb-am62xx systemd[1]: phosphor-ipmi-net@eth0.service: Scheduled restart job, restart counter is at 2.
Aug 29 15:01:40 evb-am62xx systemd[1]: phosphor-ipmi-host.service: Scheduled restart job, restart counter is at 2.
Aug 29 15:01:40 evb-am62xx systemd[1]: phosphor-ipmi-host.service: Start request repeated too quickly.
Aug 29 15:01:40 evb-am62xx systemd[1]: phosphor-ipmi-host.service: Failed with result 'core-dump'.
Aug 29 15:01:40 evb-am62xx systemd[1]: phosphor-ipmi-net@eth0.service: Job phosphor-ipmi-net@eth0.service/start failed with result 'dependency'.
Regards,
Schuyler Patton
Sitara MPU System Applications
Texas Instruments
[-- Attachment #2: Type: text/html, Size: 7652 bytes --]
next reply other threads:[~2022-08-29 15:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 15:15 Patton, Schuyler [this message]
2022-08-30 1:59 ` new port seeing ipmid exiting with seg fault Andrew Jeffery
2022-09-22 5:44 ` [EXTERNAL] " Patton, Schuyler
2022-09-23 0:06 ` Andrew Jeffery
2022-09-23 21:48 ` Patrick Williams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=66a2cce533124f56b60f68f9f0b807af@ti.com \
--to=spatton@ti.com \
--cc=openbmc@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.