Bug 260692 - shutdown -r now stops the server, but it does not boot
Summary: shutdown -r now stops the server, but it does not boot
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 12.3-RELEASE
Hardware: amd64 Any
: --- Affects Some People
Assignee: freebsd-bugs (Nobody)
URL:
Keywords: needs-qa
Depends on:
Blocks:
 
Reported: 2021-12-25 22:14 UTC by Claudio Eichenberger
Modified: 2023-11-09 05:56 UTC (History)
3 users (show)

See Also:


Attachments
FreeBSD 12.2 dmesg file (14.27 KB, text/plain)
2021-12-25 22:14 UTC, Claudio Eichenberger
no flags Details
shutdown -p now (287.15 KB, image/jpeg)
2021-12-28 15:11 UTC, Claudio Eichenberger
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Claudio Eichenberger 2021-12-25 22:14:01 UTC
Created attachment 230409 [details]
FreeBSD 12.2 dmesg file

Dear Support,
Concerns: HPE ProLiant DL325 Gen10 Server, AMD EPYC 7371
The command "shutdown -r now" worked with FreeBSD 12.0, 12.1, and 12.2
During upgrade to 12.3, "shutdown -r now" still worked after the first "freebsd-update install", but after the second "freebsd-update install" the server didn't boot any more.
I then installed a vanilla 12.3 from memory stick but it doesn't help, the server doesn't boot any more after "shutdown -r now".
What happens, the server shuts down, then it stays turned on, but the screen remains black.
I've finally again installed a 12.2 and the command "shutdown -r now" works perfectly.
I've annexed a 12.2 dmesg.
Many thanks in advance for your help
Kind regards
Claudio
Comment 1 Graham Perrin freebsd_committer freebsd_triage 2021-12-27 14:06:28 UTC
(In reply to Claudio Eichenberger from comment #0)

> … shuts down, then it stays turned on …

Did it respond properly to halt and power off? 

    shutdown -p now

At what level is firmware? 

<https://support.hpe.com/hpesc/public/docDisplay?docId=a00050521en_us&docLocale=en_US>

<https://support.hpe.com/connect/s/product?language=en_US&tab=driversAndSoftware&kmpmoid=1010868978>
Comment 2 Claudio Eichenberger 2021-12-27 15:37:15 UTC
(In reply to Graham Perrin from comment #1)

I'm not 100% sure, but I think I did an

    init 0

and it shut down correctly.

To be sure, I cannot test immediately "shutdown -p now" as meanwhile it's running 12.2 again.

By the way, I'd checked server's health and everything was fine.

I've never updated firmware!
Comment 3 Claudio Eichenberger 2021-12-28 15:11:56 UTC
Created attachment 230497 [details]
shutdown -p now
Comment 4 Claudio Eichenberger 2021-12-28 15:14:26 UTC
Comment on attachment 230497 [details]
shutdown -p now

I've upgraded to 12.3 and did a
 
        shutdown -p now
 
The system did not power off cf. attached file shutdown.jpg
Comment 5 Claudio Eichenberger 2022-01-10 21:59:06 UTC
I've installed the latest firmware, but the problem remains.
Comment 6 Claudio Eichenberger 2022-02-12 09:38:36 UTC
(In reply to Graham Perrin from comment #1)

During upgrade from 12.2 to 12.3, after the first 'freebsd-update install' the server still boots, but after the second 'freebsd-update install' no more.

By the way, with 12.3 I can see that all boxes, not just this 'AMD EPYC 7371', signal the following problem during shutdown:

cannot unmount '/var/log': device busy
Comment 7 Claudio Eichenberger 2022-02-24 17:58:53 UTC
Having seen your comments in https://forums.freebsd.org/threads/cannot-unmount-messages-appear-during-the-shutdown-after-upgrade-from-12-2-p12-to-12-3-p1.83958/ I removed # KEYWORD: shutdown from /etc/rc.d/zfs so there's no more the message cannot unmount '/var/log': device busy during shutdown, but that does not solve the problem.

Using LiveCD 12.3 or 13.0 and doing a shutdown -r now does not work either.

The box worked fine with 12.0, 12.1, and 12.2, but since it flunks.

Have you got any idea what it could be?
Comment 8 Claudio Eichenberger 2023-06-25 03:14:14 UTC
FreeBSD 13.0 had the problem too
FreeBSD 13.1 had the problem too
FreeBSD 13.2 is fine : shutdown really turns the server off and an init 6 reboots it
Comment 9 Tatsuki Makino 2023-06-25 08:29:01 UTC
I didn't pay much attention to it :)

I have had this problem in my 12.x-STABLE environment since probably the same time.
What I know is that we have to wait about 5-7 minutes for it to run, not that a reboot or power off doesn't run.
Also, if we reboot or power off with little disk access, there is almost no such waiting time. But this is unclear.
Comment 10 Graham Perrin freebsd_committer freebsd_triage 2023-06-25 10:13:16 UTC
(In reply to Tatsuki Makino from comment #9)

Claudio, do you find the same, if you wait the same length of time (or longer)?
Comment 11 Graham Perrin freebsd_committer freebsd_triage 2023-06-25 10:14:45 UTC
… assuming that you still have a 12.⋯ boot environment …
Comment 12 Claudio Eichenberger 2023-06-26 07:03:30 UTC
I can not confirm for the 12.- boot environment, all my boxes are now on 13.2.

But if I remember right, 12.2, 13.0 and 13.1 never turned off, even not after hours.
Comment 13 Tatsuki Makino 2023-11-09 05:56:46 UTC
I ran stable/12-n236231-53c5e2732978 for 92 days and 5 hours and shutdown -p, it powered off in about 2 minutes from the output of usb devices disconnect.
I don't see the connection between it's uptime and the time it has to wait for it to turn off.

From now on it is 6a0891c6ebb7 :)