From owner-freebsd-current@FreeBSD.ORG Sat Apr 5 08:37:45 2003 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 319F437B401; Sat, 5 Apr 2003 08:37:45 -0800 (PST) Received: from ip68-14-60-78.no.no.cox.net (ip68-14-60-78.no.no.cox.net [68.14.60.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F8D943F3F; Sat, 5 Apr 2003 08:37:44 -0800 (PST) (envelope-from conrads@ip68-14-60-78.no.no.cox.net) Received: from ip68-14-60-78.no.no.cox.net (conrads@localhost [127.0.0.1]) h35GgmF2050606; Sat, 5 Apr 2003 10:42:48 -0600 (CST) (envelope-from conrads@ip68-14-60-78.no.no.cox.net) Received: (from conrads@localhost)h35Ggmcl050600; Sat, 5 Apr 2003 10:42:48 -0600 (CST) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20030405002736.GS1750@elvis.mu.org> Date: Sat, 05 Apr 2003 10:42:48 -0600 (CST) Organization: A Rag-Tag Band of Drug-Crazed Hippies From: Conrad Sabatier To: Maxime Henrion cc: freebsd-current@freebsd.org Subject: Re: So then, is fxp working OK again? 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: Sat, 05 Apr 2003 16:37:45 -0000 On 05-Apr-2003 Maxime Henrion wrote: > Conrad Sabatier wrote: >> >> Still no go. I'm still getting a panic in bus_dmamem_alloc(). >> Here's the info I copied down by hand: >> >> Fatal trap 12: page fault while in kernel mode >> fault virtual address = 0x24 >> fault code = supervisor read, page not present >> instruction pointer = 0x8:0xc0301639 >> stack pointer = 0x10:0xc053bd34 >> frame pointer = 0x10: 0xc053bd48 >> code segment = base 0x0, limit 0xfffff, type 0x1b >> = DPL 0, pres 1, def32 1, gran 1 >> processor eflags = interrupt enabled, resume, IOPL=0 >> current process = 0() >> kernel: type 12 trap, code = 0 >> Stopped at bus_dmamen_alloc+0x9 movl 0x24(%edx),%eax >> db>trace >> bus_dmamem_alloc(0, c04a8aa0, 1, c04a965c, ffffffff) at >> bus_dmamen_alloc+0x9 >> acpi_alloc_wakeup_handler(0, 532000, 532020, 532000, 0) >> at acpi_alloc_wakeup_handler+0xa9 >> mi_startup() at mi_startup+0x99 >> begin() at begin+0x2c >> db> >> >> Incidentally, I've been getting acpi initialization failures in the last >> umpteen kernels I've been through, but without panicing the machine. > > Could you post a complete stack trace? There's no fxp functions in this > (incomplete) trace. Are you sure the problem you're having now is fxp > related ? I think you're right. I built a GENERIC kernel, rebooted without the acpi module, and it's working fine. Finally, I was able to get acpidump to work properly, and created a new /boot/acpi_dsdt.aml file. About to attempt a normal boot now. Will let you know. -- Conrad Sabatier - "In Unix veritas"