From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 14:00:23 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 02F9337B430; Fri, 4 Apr 2003 14:00:23 -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 C52D843F93; Fri, 4 Apr 2003 14:00:20 -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]) h34M5Nea000984; Fri, 4 Apr 2003 16:05:23 -0600 (CST) (envelope-from conrads@ip68-14-60-78.no.no.cox.net) Received: (from conrads@localhost)h34M5M95000983; Fri, 4 Apr 2003 16:05:22 -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: <20030404163136.GQ1750@elvis.mu.org> Date: Fri, 04 Apr 2003 16:05:22 -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: Fri, 04 Apr 2003 22:00:23 -0000 On 04-Apr-2003 Maxime Henrion wrote: > Conrad Sabatier wrote: >> Having had the same experiences as others described here recently with >> the >> fxp stuff, I'm just wondering if it's safe now to cvsup and try it >> again. >> I only have one machine here and if my net interface fails, I'm totally >> screwed. :-) > > It should. If it doesn't, I'm interested in knowing it. :-) > > Cheers, > Maxime 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. -- Conrad Sabatier - "In Unix veritas"