Date: Sun, 30 May 2004 16:59:35 -0400 (EDT) From: Bryan Liesner <bryan@kishka.net> To: Paul Murphy <paul.murphy@cogeco.ca> Cc: nate@root.org Subject: Re: reboot and shutdown don't work, suspect acpi Message-ID: <20040530165322.X519@gravy.kishka.net> In-Reply-To: <20040530162034.7f87326a@earth.upton.net> References: <20040529112604.00w4kckcoc8ww80c@www.sweetdreamsracing.biz> <1085930332.781.1.camel@taxman> <20040530113052.A819@gravy.kishka.net> <20040530162034.7f87326a@earth.upton.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 30 May 2004, Paul Murphy wrote: > On Sun, 30 May 2004 11:52:07 -0400 (EDT) > Bryan Liesner <bryan@kishka.net> wrote: > >> On Sun, 30 May 2004, Stefan Ehmann wrote: >> >>> On Sat, 2004-05-29 at 17:26, Kenneth Culver wrote: >>>> Hi, >>>> Ever since the recent acpi commits, reboot and shutdown no >>> longer work on my> machine (asus k8v deluxe mobo, athlon 64). The >>> machine gets to "Uptime: 1m34s"> (the time is just made up) and >>> hangs. The only way to fix this is to do a hard> reset by pushing the >>> computer's reset button. Any ideas? >>> >>> Just a short me too (ASUS A7V8X-X). >> >> Asus motherboards seem to be a common factor. I'm seeing this here too >> with an Asus A7V266-E. >> > > Ditto, Elitegroup L7VMM3 > I was taking a closer look and the acpi commits seem fine. Using all of the lastest sources and then reverting i386/i386/intr_machdep.c back to 1.5 seems to alleviate the problem. It was checked in around the same time as all of those acpi commits. -- ============================================================= = Bryan D. Liesner LeezSoft Communications, Inc. = = A subsidiary of LeezSoft Inc. = = bryan@kishka.net Home of the Gipper = =============================================================
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040530165322.X519>