Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 31 Mar 1999 01:40:31 -0800 (PST)
From:      nadir@burka.netvision.net.il
To:        freebsd-gnats-submit@freebsd.org
Subject:   kern/32165: kernel tries to initialize xl driver in 3.1-STABLE (as of 3/30/1999) and fails reporting: "xl: couldn't map port"
Message-ID:  <19990331094031.75BB714EC8@hub.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         32165
>Category:       kern
>Synopsis:       kernel tries to initialize xl driver in 3.1-STABLE (as of 3/30/1999) and fails reporting: "xl: couldn't map port"
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Nov 21 07:00:00 PST 2001
>Closed-Date:    Wed Jun 23 16:43:14 PDT 1999
>Last-Modified:  Wed Jun 23 16:43:14 PDT 1999
>Originator:     Noor Dawod
>Release:        3.1-STABLE
>Organization:
ActiveWeb Internet Solutions, Ltd.
>Environment:
FreeBSD www.somedomain.com 3.1-STABLE  FreeBSD 3.1-STABLE #6: Wed Mar 31 10:56:37 IDT 1999  root@www.somedomain.com:/usr/src/sys/compile/WWW  i386
>Description:
I installed a new system on a P-II 350Mhz system, with AHA-2940 W/UW SCSI adapter. I installed FreeBSD 3.1-RELEASE the first time, and then I did a cvsup and upgraded to 3.1-STABLE (3/30/1999), compiled the kernel with no problems, and then rebooted.

In the previous installation of FreeBSD (3.1-RELEASE) the xl driver worked fine, and auto-negotiated the network and installed the driver. After upgrading, the xl driver "sees" the card, identifies it, but when trying to install the driver, reports: "xl: couldn't map port".

I tried changing a #define line in /usr/src/sys/pci/if_xl.c to use memory mapped instead of PIO mode, and recompiled. This time, the driver reported: "xl: couldn't map memory".

>How-To-Repeat:
Like I explain above, install 3.1-RELEASE, use cvsup to upgrade to 3.1-STABLE (for 3/30/1999) and then recompile the kernel. This time, the xl driver will not work.

Hardware includes also an AHA-2940 W/UW SCSI adapter.
>Fix:
Tried, but couldn't fix it ;(

>Release-Note:
>Audit-Trail:

From: Gregory Bond <gnb@itga.com.au>
To: nadir@burka.netvision.net.il
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: kern/10886: kernel tries to initialize xl driver in 3.1-STABLE (as of 3/30/1999) and fails reporting: "xl: couldn't map port" 
Date: Thu, 01 Apr 1999 13:26:38 +1000

 I've just (199904010200 Z) cvsup'd and make world'd and made a new
 kernel and the xl0 driver works fine for me:
 	xl0: <3Com 3c905B Fast Etherlink XL 10/100BaseTX> rev 0x00 int a irq 11 on pci0.17.0
 	xl0: Ethernet address: 00:10:5a:a9:84:33
 	xl0: autoneg complete, link status good (full-duplex, 100Mbps)
 
 hellcat$ ident /usr/src/sys/pci/if_xl*
 /usr/src/sys/pci/if_xl.c:
      $Id: if_xl.c,v 1.22.2.4 1999/03/27 20:45:55 wpaul Exp $
      $Id: if_xl.c,v 1.22.2.4 1999/03/27 20:45:55 wpaul Exp $
 
 /usr/src/sys/pci/if_xlreg.h:
      $Id: if_xlreg.h,v 1.9.2.1 1999/03/27 20:45:56 wpaul Exp $
 
 

From: Noor Dawod <nadir@burka.netvision.net.il>
To: Gregory Bond <gnb@itga.com.au>
Cc: freebsd-gnats-submit@FreeBSD.ORG,
	Bill Paul <wpaul@ctr.columbia.edu>
Subject: Re: kern/10886: kernel tries to initialize xl driver in 3.1-STABLE (as of 3/30/1999) and fails reporting: "xl: couldn't map port" 
Date: Sat, 3 Apr 1999 10:44:26 +0200 (IST)

 On Thu, 1 Apr 1999, Gregory Bond wrote:
 
 > 
 > I've just (199904010200 Z) cvsup'd and make world'd and made a new
 > kernel and the xl0 driver works fine for me:
 > 	xl0: <3Com 3c905B Fast Etherlink XL 10/100BaseTX> rev 0x00 int a irq 11 on pci0.17.0
 > 	xl0: Ethernet address: 00:10:5a:a9:84:33
 > 	xl0: autoneg complete, link status good (full-duplex, 100Mbps)
 > 
 > hellcat$ ident /usr/src/sys/pci/if_xl*
 > /usr/src/sys/pci/if_xl.c:
 >      $Id: if_xl.c,v 1.22.2.4 1999/03/27 20:45:55 wpaul Exp $
 >      $Id: if_xl.c,v 1.22.2.4 1999/03/27 20:45:55 wpaul Exp $
 > 
 > /usr/src/sys/pci/if_xlreg.h:
 >      $Id: if_xlreg.h,v 1.9.2.1 1999/03/27 20:45:56 wpaul Exp $
 > 
 
   Hi folks,
 
   I know that you sure know what you're doing, but I am positive I know
 what I am doing. I ftp'ed the latest floppies from a snapshot server, then
 made two floppies: kernel and mfs. Then I booted the kernel, and
 surprisingly, the kernel DID NOT install the driver and the same "xl0:
 couldn't map port" message is still displaying.
 
   All the thing is that you must be missing something in the code as this
 exact machine works fine if I install 3.1-RELEASE and it autodetects and
 installs the driver.
 
   Whomever wants debugging messages/tests, tell me what, I'll send it.
 
   Noor
 
 
 

From: wpaul@ctr.columbia.edu (Bill Paul)
To: nadir@burka.netvision.net.il
Cc: freebsd-gnats-submit@freebsd.org, gnb@itga.com.au
Subject: Re: kern/10886: kernel tries to initialize xl driver in 3.1-STABLE (as of 3/30/1999) and fails reporting: "xl: couldn't map port
Date: Sat, 3 Apr 1999 10:32:20 -0500 (EST)

 Of all the gin joints in all the towns in all the world, Noor Dawod had
 to walk into mine and say:
 
 >   Hi folks,
 > 
 >   I know that you sure know what you're doing, but I am positive I know
 > what I am doing. I ftp'ed the latest floppies from a snapshot server, then
 > made two floppies: kernel and mfs. Then I booted the kernel, and
 > surprisingly, the kernel DID NOT install the driver and the same "xl0:
 > couldn't map port" message is still displaying.
 
 I'm pretty sure that the reason the driver worked before is that
 it was manually determining the I/O address to use by reading the
 PCI configuration registers on the card itself instead of going through
 pci_map_ports(). But using pci_map_ports() is the right thing to do
 and it clearly works for other people (including me, even on
 FreeBSD/alpha). The patch I sent you under separate cover restores the
 old behavior which should make it work again, however the problem
 is either a bug in the PCI support code or some peculiarity about
 your hardware. The xl driver itself is almost certainly not the real
 problem.
 
 The right thing to do is to add some debug code to pci.c or pci_compat.c
 and find out why pci_map_ports() _and_ pci_map_mem() both fail. What
 would also be helpful is if you could show the complete dmesg output
 from your system, with the -v boot flag if possible.
 
 -Bill
 
 -- 
 =============================================================================
 -Bill Paul            (212) 854-6020 | System Manager, Master of Unix-Fu
 Work:         wpaul@ctr.columbia.edu | Center for Telecommunications Research
 Home:  wpaul@skynet.ctr.columbia.edu | Columbia University, New York City
 =============================================================================
 "Mulder, toads just fell from the sky!" "I guess their parachutes didn't open."
 =============================================================================
 
State-Changed-From-To: open->closed 
State-Changed-By: msmith 
State-Changed-When: Wed Jun 23 16:42:44 PDT 1999 
State-Changed-Why:  
xl driver now has workaround for this case. 
>Unformatted:

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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990331094031.75BB714EC8>