From owner-freebsd-current@FreeBSD.ORG  Thu Apr  3 12:55:55 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 C915D37B401
	for <current@freebsd.org>; Thu,  3 Apr 2003 12:55:55 -0800 (PST)
Received: from ns.altadena.net (ns.altadena.net [207.151.161.2])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 02F8743FD7
	for <current@freebsd.org>; Thu,  3 Apr 2003 12:55:53 -0800 (PST)
	(envelope-from pete@ns.altadena.net)
Received: from ns.altadena.net (localhost [127.0.0.1])
	by ns.altadena.net (8.12.6p2/8.12.3) with ESMTP id h33KtmLn011649
	for <current@freebsd.org>; Thu, 3 Apr 2003 12:55:48 -0800 (PST)
	(envelope-from pete@ns.altadena.net)
Received: (from pete@localhost)
	by ns.altadena.net (8.12.6p2/8.12.3/Submit) id h33KtmsX011648
	for current@freebsd.org; Thu, 3 Apr 2003 12:55:48 -0800 (PST)
	(envelope-from pete)
From: Pete Carah <pete@ns.altadena.net>
Message-Id: <200304032055.h33KtmsX011648@ns.altadena.net>
To: current@freebsd.org
Date: Thu, 3 Apr 2003 12:55:48 -0800 (PST)
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=iso8859-1
Content-Transfer-Encoding: 7bit
Subject: FXP breakage
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: Thu, 03 Apr 2003 20:55:56 -0000

This may be just my infamous vaio acting up again, but since the 
recent commit to fxp driver (Monday?) I get a panic on device probe
(page fault in kernel mode).

That and the way the pccbb act up (always return 0 for event and
status register reads, and don't reset pending interrupt on event reg
write) make me think that something is awry with the way acpi/pci 
allocate memory for the device windows.

I know there is something funny with the aml/asl since almost everything
ends up on irq 9 also...

I also sometimes see the lock order problem with pcm but mostly just missing
interrupts (choppy sound that comes out slow but in the right order).
PCM is responding to display interrupts...

-- Pete