From owner-freebsd-current  Thu Sep  2 17:31:39 1999
Delivered-To: freebsd-current@freebsd.org
Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33])
	by hub.freebsd.org (Postfix) with ESMTP id E261115602
	for <freebsd-current@FreeBSD.ORG>; Thu,  2 Sep 1999 17:31:34 -0700 (PDT)
	(envelope-from luoqi@watermarkgroup.com)
Received: (from luoqi@localhost)
	by lor.watermarkgroup.com (8.8.8/8.8.8) id UAA02922;
	Thu, 2 Sep 1999 20:24:35 -0400 (EDT)
	(envelope-from luoqi)
Date: Thu, 2 Sep 1999 20:24:35 -0400 (EDT)
From: Luoqi Chen <luoqi@watermarkgroup.com>
Message-Id: <199909030024.UAA02922@lor.watermarkgroup.com>
To: dfr@nlsystems.com, luoqi@watermarkgroup.com
Subject: Re: Problems with the sound card.
Cc: arthur@tucows.com, freebsd-current@FreeBSD.ORG, nick.hibma@jrc.it
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> That's exactly what I have. This is just so weird. I am now reading the
> debug register chapter of intel's manual, it is virtually impossible to
> pinpoint the location by single-stepping through the code...
> 
The debug register trick worked, and the discovery was quite unexpected:
because the isa bus is hanging off the pci bus, bus_release_resource()
call by a isa device, eventually reaches the pci_release_resource(),
where the device is blindly assumed to be a pci device and its isa_device
struct overwritten as if it were a struct pci_devinfo. pci_release_resource()
should check for pass-thru releases.

-lq


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message