From owner-freebsd-questions@FreeBSD.ORG Sun Sep 3 03:03:36 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D20DB16A4DD for ; Sun, 3 Sep 2006 03:03:36 +0000 (UTC) (envelope-from backyard1454-bsd@yahoo.com) Received: from web83103.mail.mud.yahoo.com (web83103.mail.mud.yahoo.com [216.252.101.32]) by mx1.FreeBSD.org (Postfix) with SMTP id 4E42443D49 for ; Sun, 3 Sep 2006 03:03:36 +0000 (GMT) (envelope-from backyard1454-bsd@yahoo.com) Received: (qmail 76716 invoked by uid 60001); 3 Sep 2006 03:03:35 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=SH4oZFx8ACITWQ5PC9NxoeqT7D2PNmjypV80g3ltwbmirCZ1y1SWC1sghzh5RrftxdSC/i9TUpAe+sX8Qo8z1nemLixeQXsDy0k+CT8+wxKdUymBcA6gHb7H3N6YWa40WclCnfQ/GZoY/M1fWbGuosbCYZXPKxdkoNJI50oPG9M= ; Message-ID: <20060903030335.76714.qmail@web83103.mail.mud.yahoo.com> Received: from [75.17.32.58] by web83103.mail.mud.yahoo.com via HTTP; Sat, 02 Sep 2006 20:03:34 PDT Date: Sat, 2 Sep 2006 20:03:34 -0700 (PDT) From: backyard To: bsd , Liste FreeBSD In-Reply-To: <2A7A706E-E19D-4E92-ADFA-29261AB532B5@todoo.biz> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Subject: Re: ACPI lock in the last "halt" process X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: backyard1454-bsd@yahoo.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Sep 2006 03:03:37 -0000 --- bsd wrote: > Hello, > > I have configured with a 6.1 RELEASE FreeBSD. > > When I am trying to shut down the computer - I reach > the prompt - all > processes seems to halt correctly - then the server > seems to be > stucked with the ACPI process indefinitely ?? > > First of all I don't know what ACPI is related to ? > > Second how could I avoid that problem in the future > ? > > > > --- > > Here are the info related to acpi on my dmesg log : > > > acpi_alloc_wakeup_handler: can't alloc wake memory > > acpi0: on motherboard > > acpi0: Power Button (fixed) > > acpi_timer0: <24-bit timer at 3.579545MHz> port > 0x408-0x40b on acpi0 > > cpu0: on acpi0 > > acpi_throttle0: on cpu0 > > cpu1: on acpi0 > > cpu2: on acpi0 > > cpu3: on acpi0 > > pcib0: port 0xcf8-0xcff on > acpi0 > > acpi_button0: on acpi0 > > sio0: <16550A-compatible COM port> port > 0x3f8-0x3ff irq 4 flags > > 0x10 on acpi0 > > atkbdc0: port > 0x60,0x64 irq 1 on acpi0 > > > Thanks. > > ________________________________________________ > «?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§ > ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯ > Gregober ---> PGP ID --> 0x1BA3C2FD > bsd @at@ todoo.biz > ________________________________________________ > «?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§ > ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯ > > P "Please consider your environmental responsibility > before printing > this e-mail" > > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" > what kind of computer is this? Do you have the latest BIOS installed on the computer in question? What BIOS version are you using? Did the machine do this on other releases or is this the first FreeBSD it has seen? ACPI is the most current flashier version of APM with some PNP thrown in; in laymens terms... It configures devices, provides power management, and allows the computer to setup hardware so specific versions of windows can or cannot use certain resources on the machine. Sometimes this does cause issues with the non-windows users because devices are left unconfigured or features disabled. Sometimes this leaves the hardcore users rewriting their ACPI to include support for FreeBSD natively or fix the errors that came with the ACPI from the OEM. shutdown puts in a system call to ACPI to shutoff the computer. That is why it matters. It seems like your system should shutdown properly due to the power button fixed line above. At least it not being able to properly shutdown is a known issue with the machine. Does the computer hard lock or do you mean you get stuck at a # prompt but no powerdown? shutdown now will bring you to single user mode shutdown -p now should (only in linux does it not for me...)shutdown the machine. to avoid this problem in the future you should fill in some of these blanks. Describe what: > > When I am trying to shut down the computer - I reach > the prompt - all > processes seems to halt correctly - then the server > seems to be > stucked with the ACPI process indefinitely ?? means exactly. I know its tricky to get verbatium what is going on, but when does it die? I had a dell with this problem, had to update the bios and turn on acpi for it to work right, would only halt the machine for me (shutdown -h now [turns off pc in linux... sorry tux is a new enemy...]) also a uname -a may be a nice thing to include. -brian