From owner-freebsd-mobile@FreeBSD.ORG Tue Jan 6 21:45:49 2004 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9749616A4CE for ; Tue, 6 Jan 2004 21:45:49 -0800 (PST) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F9EF43D2D for ; Tue, 6 Jan 2004 21:45:48 -0800 (PST) (envelope-from sam@errno.com) Received: from 66.127.85.91 ([66.127.85.91]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.9) with ESMTP id i075jgHQ091071 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 6 Jan 2004 21:45:46 -0800 (PST) (envelope-from sam@errno.com) From: Sam Leffler Organization: Errno Consulting To: Eric Anderson , freebsd-mobile@freebsd.org Date: Tue, 6 Jan 2004 21:49:40 -0800 User-Agent: KMail/1.5.3 References: <3FFB7DFA.1080601@centtech.com> In-Reply-To: <3FFB7DFA.1080601@centtech.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200401062149.40990.sam@errno.com> Subject: Re: Cardbus troubles on 5.2-CURRENT X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jan 2004 05:45:49 -0000 On Tuesday 06 January 2004 07:33 pm, Eric Anderson wrote: > I posted this to the -current mailing list earlier, and have mentioned > it several times in the past, but no response. Am I the only person > having troubles here? Cardbus used to at least fail gracefully (by not > understanding what card was inserted) instead of bombing my network card > (causing me to have to reboot). > > So here's the scoop - when I insert any cardbus card (but 16-bit pc > cards are fine, and don't have the problem), it seems to try to detect > it as a bge1 device, and destroys my working bge0 device (broadcom > gigabit ethernet). Here's the dmesg: > This is identical to the behaviour I see on my Dell i600m laptop. Warner is aware of it and understands what the root cause is, but solving it is (apparently) a bit involved. Sam