Actions
Bug #2167
openshutdown/reboot fails after uptime msg
Start date:
Due date:
% Done:
0%
Estimated time:
Description
I've mentioned this on IRC a few times, so I thought I'd make it official with
a bug report.
My DragonFly x86_64 machine (AMD Phenom II X4 955) has four partitions, and I
can boot into FreeBSD, NetBSD, and OpenBSD as well. Those three BSDs have no
problems with "reboot" and "shutdown" commands. They work as expected.
Typing shutdown -p or reboot will cause DragonFly to freeze after the uptime
message. Sephe had me tweak something and I believe concluded there was some
interference by the ehci module causing the lock up.
In any case, not having the ability to remotely reboot the server is a medium-
sized problem and it would be nice if DragonFly could support this machine as
the other BSDs do.
Actions