From owner-freebsd-mobile@FreeBSD.ORG Wed Jan 19 22:03:22 2005 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 1027016A4CE for ; Wed, 19 Jan 2005 22:03:22 +0000 (GMT) Received: from postal3.es.net (postal3.es.net [198.128.3.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id D90C343D54 for ; Wed, 19 Jan 2005 22:03:21 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal3.es.net (Postal Node 3) with ESMTP (SSL) id IBA74465; Wed, 19 Jan 2005 14:03:21 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 4A2E95D08; Wed, 19 Jan 2005 14:03:21 -0800 (PST) X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: Robert Blacquiere In-reply-to: Your message of "Wed, 19 Jan 2005 20:56:36 +0100." <20050119195635.GC61467@bombur.guldan.demon.nl> Mime-Version: 1.0 Content-Type: multipart/mixed ; boundary="==_Exmh_10504690170" Date: Wed, 19 Jan 2005 14:03:21 -0800 From: "Kevin Oberman" Message-Id: <20050119220321.4A2E95D08@ptavv.es.net> cc: freebsd-mobile@FreeBSD.ORG Subject: Re: Xircom Realport Cardbus Ethernet 10/100 + Modem 56 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, 19 Jan 2005 22:03:22 -0000 This is a multipart MIME message. --==_Exmh_10504690170 Content-Type: text/plain; charset=us-ascii > Date: Wed, 19 Jan 2005 20:56:36 +0100 > From: Robert Blacquiere > Sender: owner-freebsd-mobile@freebsd.org > > Hi all, > > I've been using this cardbus card on and off for debugging cases. And > last time i've used it was with 5.2.1 system which worked perfect. But > after upgrading to 5.3 and 5.3S it seems to hang my system. I've got some > wireless 16 and 32 bit cards and all work. But this one failes badly. > > I got the dc0 and sio4 device which all worked. > > I've tried also using: > hw.pci.allow_unsupported_io_range=1 > and have to add the following to prevent issues with the irda port. > hw.cbb.start_16_io="0x140" > > Does any body know a possible solution? It's hard to get some debug info. > Tomorrow i'll try and get dumping and some dmesg output available. Here is a kludge to make it work. The problem is probably a combination of a driver bug and a problem with busdma. Scott Long has been looking into this, but I have not heard anything from him for a while, so I guess I'll need to jog his elbow. In any case, this patch should get you back on-line. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 --==_Exmh_10504690170 Content-Type: text/plain ; name="if_dc.diff"; charset=us-ascii Content-Description: if_dc.diff Content-Disposition: attachment; filename="if_dc.diff" --- if_dc.c~ Fri Oct 15 17:53:44 2004 +++ if_dc.c Mon Dec 20 14:22:48 2004 @@ -2151,8 +2151,8 @@ } /* Allocate a busdma tag for mbufs. */ - error = bus_dma_tag_create(NULL, PAGE_SIZE, 0, BUS_SPACE_MAXADDR_32BIT, - BUS_SPACE_MAXADDR, NULL, NULL, MCLBYTES * DC_TX_LIST_CNT, + error = bus_dma_tag_create(NULL, 1, 0, BUS_SPACE_MAXADDR_32BIT, + BUS_SPACE_MAXADDR, NULL, NULL, MCLBYTES, DC_TX_LIST_CNT, MCLBYTES, 0, NULL, NULL, &sc->dc_mtag); if (error) { printf("dc%d: failed to allocate busdma tag\n", unit); --==_Exmh_10504690170--