Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 3 Apr 1999 07:40:01 -0800 (PST)
From:      wpaul@ctr.columbia.edu (Bill Paul)
To:        freebsd-bugs@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
Message-ID:  <199904031540.HAA01092@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/10886; it has been noted by GNATS.

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."
 =============================================================================
 


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?199904031540.HAA01092>