Subject: Re: port-i386/33492: wi(4) crash
To: None <port-i386-maintainer@netbsd.org, gnats-admin@netbsd.org,>
From: Matthias Drochner <M.Drochner@fz-juelich.de>
List: netbsd-bugs
Date: 05/18/2006 11:20:02
The following reply was made to PR port-i386/33492; it has been noted by GNATS.
From: Matthias Drochner <M.Drochner@fz-juelich.de>
To: gnats-bugs@NetBSD.org
Cc: port-i386-maintainer@NetBSD.org, gnats-admin@NetBSD.org,
netbsd-bugs@NetBSD.org, abrasive@axdf.net
Subject: Re: port-i386/33492: wi(4) crash
Date: Thu, 18 May 2006 09:44:17 +0200
abrasive@axdf.net said:
> > > pcic0: port 0x300-0x30f
> pcic0: port 0x400-0x43f
Sorry, I did copy & paste the wrong line. I wanted to
cite the line with 0x400.
What I suspect is that the addresses 0x400+ are not usable, either
because used by some other device, or due to aliasing.
(It is just above the 10-bit boundary.)
The pcic@isa code tries to find out whether only 10 bits
are decoded and selects the io range 300+ or 400+
accordingly. What I don't understand is why the first socket
gets a 300 address and the second a 400. Something must
override the initial range.
You could try some PCMCIOVERBOSE and PCICDEBUG options to
get some more information.
best regards
Matthias