From owner-freebsd-current@FreeBSD.ORG Tue Oct 19 11:48:26 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3406B16A4CE for ; Tue, 19 Oct 2004 11:48:26 +0000 (GMT) Received: from lazir.toya.net.pl (lazir.toya.net.pl [217.113.224.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 451D143D2D for ; Tue, 19 Oct 2004 11:48:25 +0000 (GMT) (envelope-from imachine@toya.net.pl) Received: from localhost (unknown [192.168.120.26]) by lazir.toya.net.pl (TOYAnet MailServer) with ESMTP id 409788BD2C; Tue, 19 Oct 2004 13:48:24 +0200 (CEST) Received: from lazir.toya.net.pl ([192.168.120.25]) by localhost (agregat [192.168.120.26]) (amavisd-new, port 10024) with ESMTP id 14419-01; Tue, 19 Oct 2004 13:48:22 +0200 (CEST) Received: from [192.168.0.2] (unknown [217.113.236.116]) by lazir.toya.net.pl (TOYAnet MailServer) with ESMTP id F1C778BD12; Tue, 19 Oct 2004 13:48:22 +0200 (CEST) From: Mateusz =?iso-8859-2?Q?J=EAdrasik?= To: freebsd-current@freebsd.org In-Reply-To: References: <20040924151635.GA2710@lazir.toya.net.pl> <1098090180.86430.48.camel@creative> Content-Type: text/plain; charset=iso8859-2 Message-Id: <1098186601.52844.2.camel@creative> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Tue, 19 Oct 2004 13:50:03 +0200 Content-Transfer-Encoding: 8bit X-TOYA-AV: AntyVir-Skaner at toya.net.pl cc: Phil Brennan Subject: Re: 5.3-BETA3 and up acpi fails with ABIT BH-6 motherboard X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Oct 2004 11:48:26 -0000 W li¶cie z Pon, 18-10-2004, godz. 11:32, Phil Brennan pisze: > I always had to disable acpi on my abit be6 and be6-II, I think abit > bx boards from that era have faulty acpi implementations. It works flawlessly on 5.2.1 and 5.3 up to BETA3. > Just disable > acpi in the bios, or boot freebsd without acpi, and all will be well. This is what I am doing right now, tho I would not attempt at calling that a solution. Cheers, Mateusz. > > On Mon, 18 Oct 2004 11:03:01 +0200, Mateusz Jędrasik > wrote: > > W li¶cie z Pi±, 24-09-2004, godz. 17:16, None pisze: > > > > > > > hello, > > > > > > since BETA3 of 5.3 enabling acpi hard locks my machine on boot. > > > > > > here is the exact message jotted down on paper from the boot screen: > > > > > > > > > Fatal trap 12: page fault while in kernel mode > > > > > > fault virtual address = 0x24 > > > fault code = supervisor read, page not present > > > instruction provider = 0x8:0xc04e35d6 > > > stack pointer = 0x10:0xc0c2198c > > > frame pointer = 0x10:0xc0c2198c > > > code segment = base 0x0, limit 0xfffff, type 0x1b /or 0x16/ > > > = DPL 0, pres 1, def32 1, gran 1 > > > processor eflags = interrupt enabled, resume, IOPL:0 > > > current process = 0 (swapper) > > > trap number = 12 > > > > > > panic: page fault > > > > > > Uptime > > > > > > shutting down ACPI > > > > > > > > > i attach my dmesg without acpi on beta5 /its broken since beta3, i > > > unfrotunately have no longer sources for beta2 so cannot reproduce any > > > messages/, and also i attach some info here from the dmesg with acpi > > > enabled on beta5 - mainly the acpi0 info from it. > > > > > > it reads: > > > > > > acpi0: > > > acpi0: reservation at f00000, 40000 (3) failed > > > acpi0: reservation at f00000, 7ef0000 (3) failed > > > > > > the second value im not too sure on cuz it scrolls really > > > fast - i videocammed the boot process :D and still searched it but i > > > cannot really read clearly the info of the small screen on the camera, > > > its a really oldskool one :] > > > > > > cheers i hope it helps solving some problems :]] > > > > > > //imachine > > > > I also would like to mention that I have done an acpidump (acpidump -t > > -d). > > > > I attach it with this reply to my post. > > > > I hope maybe someone reads this as the acpi issue is terrible. I am > > willing to provide any information regarding this. BTW, i now run -BETA7 > > and the error persists. > > > > cheers,