Bug #2167
open
shutdown/reboot fails after uptime msg
0%
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.
Updated by dragonflybsd1 almost 14 years ago
00:40 <@sephe> well, its the pci write in the ehci shutdown hook cause the freeze
Updated by sepherosa almost 14 years ago
On Fri, Nov 25, 2011 at 2:46 PM, John Marino via Redmine
<bugtracker-admin@leaf.dragonflybsd.org> wrote:
Issue #2167 has been updated by John Marino.
00:40 <@sephe> well, its the pci write in the ehci shutdown hook cause the freeze
Well, there is a committed patch in freebsd for their old usb stack
concerning this shutdown freeze. However, I will have to note that I
tried this patch on one of my laptop w/ the shutdown problem; it
didn't work. But you could always try your luck :)
Best Regards,
sephe
----------------------------------------
Bug #2167: shutdown/reboot fails after uptime msg
http://bugs.dragonflybsd.org/issues/2167Author: John Marino
Status: New
Priority: Normal
Assignee:
Category:
Target version: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.--
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
--
Tomorrow Will Never Die
Updated by ak almost 14 years ago
I have this same problem on my desktop (reported in issue #2232).
I also tried the freebsd patch 1.36.2.4 but it didn't work - http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/usb/Attic/ehci.c?only_with_tag=RELENG_6
Now I just disable ehci by adding hint.ehci.0.disabled="1" to /boot/loader.conf