NetBSD Problem Report #21906

Received: (qmail 23741 invoked by uid 605); 16 Jun 2003 20:24:06 -0000
Message-Id: <20030616202402.D9D9B7B79@yeah-baby.shagadelic.org>
Date: Mon, 16 Jun 2003 13:24:02 -0700 (PDT)
From: thorpej@shagadelic.org
Sender: gnats-bugs-owner@netbsd.org
Reply-To: thorpej@shagadelic.org
To: gnats-bugs@gnats.netbsd.org
Subject: pci_dma64_available() isn't quite right
X-Send-Pr-Version: 3.95

>Number:         21906
>Category:       kern
>Synopsis:       pci_dma64_available() isn't quite right
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    kern-bug-people
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Jun 16 20:25:00 +0000 2003
>Closed-Date:    Sun Sep 25 00:16:56 +0000 2016
>Last-Modified:  Sun Sep 25 00:16:56 +0000 2016
>Originator:     Jason R Thorpe
>Release:        NetBSD 1.6P
>Organization:
Wasabi Systems, Inc.
>Environment:


>Description:
	The pci_dma64_available() function is close, but not quite
	right.  In particular, it will fail if a system has < 4G of
	RAM, but some of that RAM is physically mapped above the 4G
	address boundary.

	I know of at least one system where this could be the case
	(the system is not available publicly at this time, sorry).

>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed
State-Changed-By: mrg@NetBSD.org
State-Changed-When: Sun, 25 Sep 2016 00:16:56 +0000
State-Changed-Why:
this function only appears to check if the pa_dmat64 tag is valid, so
i'm not sure what exactly is wrong about it.  it certainly works in
our usage of it in code.


>Unformatted:

Home	PR Database Search