From imp@timing.com  Fri Aug 24 11:40:46 2001
Return-Path: <imp@timing.com>
Received: from Daffy.timing.com (daffy.timing.com [206.168.13.218])
	by hub.freebsd.org (Postfix) with ESMTP id 982B537B40D
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 24 Aug 2001 11:40:45 -0700 (PDT)
	(envelope-from imp@timing.com)
Received: from marvin.timing.com (root@marvin.timing.com [206.168.13.207])
	by Daffy.timing.com (8.9.3/8.9.3) with ESMTP id MAA20614
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 24 Aug 2001 12:40:45 -0600 (MDT)
	(envelope-from imp@timing.com)
Received: (from imp@localhost)
	by marvin.timing.com (8.11.6/8.9.3) id f7OIgfL09254;
	Fri, 24 Aug 2001 12:42:41 -0600 (MDT)
	(envelope-from imp)
Message-Id: <200108241842.f7OIgfL09254@marvin.timing.com>
Date: Fri, 24 Aug 2001 12:42:41 -0600 (MDT)
From: "M. Warner Losh" <imp@timing.com>
Reply-To: "M. Warner Losh" <imp@timing.com>
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: Bad iomem assigned in some cases.
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         30049
>Category:       kern
>Synopsis:       [f: 4.4] Bad iomem assigned in some cases.
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    imp
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Aug 24 11:50:00 PDT 2001
>Closed-Date:    Tue Jun 29 09:22:38 MDT 2004
>Last-Modified:  Tue Jun 29 09:22:38 MDT 2004
>Originator:     M. Warner Losh
>Release:        FreeBSD 4.4-RC
>Organization:
None
>Environment:
	Laptop
>Description:
> : nsp0 at port 0x240-0x24f iomem 0xc8800-0xc97ff irq 5 slot 0 on pccard0
> :                                ^^^^^^^^^^^^^^^
> Nothing should have changed in the memory allocation scheme.  The
> above address looks wrong to me.  Maybe it was with the addition of
> the orm device and that 0xc8000 was taken.  Maybe we're not aligning
> things properly (since the memory needs to be 4k aligned, iirc, at the
> bridge level).
> 
> Do you have a orm device?  If so, what does it say?

Yes,
jm3wud@cel% dmesg | grep orm
orm0: <Option ROMs> at iomem 0xc0000-0xc7fff,0xc8000-0xc87ff on isa0

But if my memory is correct, iomem used to be 0xd0000- something. And
the line,
memory  0xd4000  96k
in /etc/defautls/pccard.conf seems to be ignored,

From: Warner Losh <imp@harmony.village.org>
Date: Thu, 23 Aug 2001 01:55:30 -0600
> Maybe this patch will help?

Unfortunately, no. Dmesg was same,
nsp0 at port 0x240-0x24f iomem 0xc8800-0xc97ff irq 5 slot 0 on pccard0

The lines of PCIC from dmesg was as follows,

pcic2: <Vadem 469> at port 0x3e0-0x3e1 on isa0
pcic2: Polling mode
pccard0: <PC Card bus (classic)> on pcic2
pccard1: <PC Card bus (classic)> on pcic2

// Noriaki Mitsunaga //

>How-To-Repeat:

Insert a nsp into the sytem.  Or some other pccard that requires
memory mapped.  Notice that it appears to be ignoring your memory line
in pccard.conf.

>Fix:

None offered.

>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->imp 
Responsible-Changed-By: imp 
Responsible-Changed-When: Fri Aug 24 12:54:17 MDT 2001 
Responsible-Changed-Why:  
I'll deal. 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=30049 
State-Changed-From-To: open->closed 
State-Changed-By: imp 
State-Changed-When: Tue Jun 29 09:22:12 MDT 2004 
State-Changed-Why:  
I believe that I've fixed this. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=30049 
>Unformatted:
