From owner-freebsd-current@FreeBSD.ORG  Fri Apr  4 16:27:37 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 B103537B404
	for <freebsd-current@freebsd.org>;
	Fri,  4 Apr 2003 16:27:37 -0800 (PST)
Received: from elvis.mu.org (elvis.mu.org [192.203.228.196])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1E1E143FD7
	for <freebsd-current@freebsd.org>;
	Fri,  4 Apr 2003 16:27:37 -0800 (PST)	(envelope-from mux@freebsd.org)
Received: by elvis.mu.org (Postfix, from userid 1920)
	id 037102ED424; Fri,  4 Apr 2003 16:27:37 -0800 (PST)
Date: Sat, 5 Apr 2003 02:27:36 +0200
From: Maxime Henrion <mux@freebsd.org>
To: Conrad Sabatier <conrads@cox.net>
Message-ID: <20030405002736.GS1750@elvis.mu.org>
References: <20030404163136.GQ1750@elvis.mu.org>
	<XFMail.20030404160522.conrads@cox.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <XFMail.20030404160522.conrads@cox.net>
User-Agent: Mutt/1.4.1i
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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Apr 2003 00:27:38 -0000

Conrad Sabatier wrote:
> 
> 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
> 
> <groan> 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 ?

Cheers,
Maxime