Bug 1590557 - Intermittently hangs on restart with systemd-journald failed to send WATCHDOG=1 notification message
Summary: Intermittently hangs on restart with systemd-journald failed to send WATCHDOG...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 29
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-12 21:11 UTC by Ralph E Kenyon Jr
Modified: 2019-02-21 21:06 UTC (History)
20 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-02-21 21:06:06 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
message file covering before and after crash. (7.86 MB, text/plain)
2018-06-12 21:38 UTC, Ralph E Kenyon Jr
no flags Details

Description Ralph E Kenyon Jr 2018-06-12 21:11:38 UTC
Description of problem: 
When I select restart while default user is logged in on X-window (Wayland is disable)

Version-Release number of selected component
 4.16.13-200.fc27.x86_64 #1 GNU/Linux

How reproducible:
occasional

Steps to Reproduce:
1. When logged in to the x-window display (wayland disabled) click restart
2. see: systemd-journald failed to send WATCHDOG=1 notification message Transport endpoint is not connected
3. press and hold power button to restart.

Actual results:

system hangs shutting down

Expected results:

normal shutdown and restart.

Additional info:

I have not noticed the problem if I log out of the user prior to restarting.

Comment 1 Ralph E Kenyon Jr 2018-06-12 21:38:09 UTC
Created attachment 1450651 [details]
message file covering before and after crash.

I'm not sure if the actual crash was before the restart or something that happened during reboot, so including the messages file.

Hope it helps.

Comment 2 Justin M. Forbes 2018-07-23 15:02:04 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 27 kernel bugs.

Fedora 27 has now been rebased to 4.17.7-100.fc27.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 28, and are still experiencing this issue, please change the version to Fedora 28.

If you experience different issues, please open a new bug report for those.

Comment 4 Laura Abbott 2018-10-01 21:24:52 UTC
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 27 kernel bugs.
 
Fedora 27 has now been rebased to 4.18.10-100.fc27.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 28 or Fedora 29, and are still experiencing this issue, please change the version to Fedora 28 or 29.
 
If you experience different issues, please open a new bug report for those.

Comment 5 Ralph E Kenyon Jr 2018-10-05 00:22:25 UTC
I have upgraded to Fedora 28.
So far I have not seen this bug in Fedora 28.

Comment 6 Laura Abbott 2018-10-05 00:44:19 UTC
Thanks for letting us know

Comment 7 Pablo Iranzo Gómez 2019-01-15 08:05:14 UTC
I've F29 with 4.19.13-300 on x86_64 and I do see systemd-journald 'dmesg' entries with Failed to send WATCHDOG=1 notification message. Transport endpoint is not connected

Comment 8 Justin M. Forbes 2019-01-29 16:13:16 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 29 kernel bugs.

Fedora 29 has now been rebased to 4.20.5-200.fc29.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

Comment 9 Justin M. Forbes 2019-02-21 21:06:06 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.


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