Date: Tue, 28 Feb 2006 00:32:52 +0100 From: Claude Buisson <cbuisson@nerim.net> To: "M. Warner Losh" <imp@bsdimp.com> Cc: freebsd-stable@freebsd.org, laszlokaroly@tvnetwork.hu Subject: Re: Bug(?) in cardbus code MFC'd to RELENG_6 on 30 January Message-ID: <44038C24.9000706@nerim.net> In-Reply-To: <20060227.161333.130238674.imp@bsdimp.com> References: <44036EA8.1090104@tvnetwork.hu> <20060227.161333.130238674.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
M. Warner Losh wrote: > I was unaware of this problem. It may be related to other problems > that have surfaced in some code I recently MFC'd. > > Warner > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > Perharps, it is the same problem I got with a dc card one week ago, and which seemingly did not interested anyone. Using black magic, I solved it by putting: hw.cbb.start_32_io="0x4000" in my loader.conf... I found it by googling, and trying a trick used for a different card, in a different computer, with a different version of FreeBSD ! I do not know why it works, but it works... Is there somewhere a tool or a set of procedures to diagnostic/solve this kind of port allocation problems, which manifest itself with different kind of messages (as I found when trying the same card on another computer) ?? Claude Buisson
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44038C24.9000706>