From owner-freebsd-stable@FreeBSD.ORG Thu May 12 06:15:17 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 079E81065670 for ; Thu, 12 May 2011 06:15:17 +0000 (UTC) (envelope-from rickvanderzwet@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id C463B8FC0C for ; Thu, 12 May 2011 06:15:16 +0000 (UTC) Received: by iyj12 with SMTP id 12so1349996iyj.13 for ; Wed, 11 May 2011 23:15:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=YSLSJYc1JliYctyZHI7foanxn12m0ukTk0ffz1/fn+4=; b=ZRRr2tc6qCpjHAqRc0DDyEHgtgkAvRTKHkW0QgVUh8V+4qhzULUtf3vTDczHFSuPmY RJ3MfFL84fLitF54GiB/Id0wu852un5bgGRV/NuE4uo60o/IhR1jI0lHsyuOswwiJXhN Bk8CFqTcdO7JtXwPYVKi4blYbFWjilEpjtODA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=O16ZWYBJjPwmilOp9NH9YBu5RANf9Hg6Fl8lLkiYKxmk0lhOSRAcNpg9QlIdUpxWZv oyhF3ZpDWsqUwit/fVzM0QvP4LiPN3Srxx6PnnFoHJJESiVztShZU/v4zFTgK2kFGRVh bwo1O3KEs6j0HPiQxhHx4r+acHQB7ctk4i26M= MIME-Version: 1.0 Received: by 10.43.131.130 with SMTP id hq2mr1739704icc.90.1305179197290; Wed, 11 May 2011 22:46:37 -0700 (PDT) Sender: rickvanderzwet@gmail.com Received: by 10.231.146.211 with HTTP; Wed, 11 May 2011 22:46:37 -0700 (PDT) In-Reply-To: <20110511084913.GG96423@laa.zp.ua> References: <20110511084913.GG96423@laa.zp.ua> Date: Thu, 12 May 2011 07:46:37 +0200 X-Google-Sender-Auth: 3nZKoHJHTeid6_QA9wioZdYqf6Q Message-ID: From: Rick van der Zwet To: Lystopad Olexandr Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: wi0 and adhoc X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 May 2011 06:15:17 -0000 2011/5/11 Lystopad Olexandr : > I have two freebsd boxes with 4.11 (yes, really!). They both > serve wifi adhoc link (wi0 + pcic0: ) during many > years with no problems. One box has died, and I change it to > new one with 8.0-rel. New box have cbb0 and same wi0 card. So, > now I have two boxes 4.11 and 8.0. Both with wi0 devices detected. [snip: ifconfig] > # ifconfig wlan0 list caps > drivercaps=3D10301 > cryptocaps=3D1 > > pciconf -lvc: > ... > cbb0@pci0:2:9:0: =A0 =A0 =A0 =A0class=3D0x060700 card=3D0x14101524 chip= =3D0x14101524 rev=3D0x01 hdr=3D0x02 > =A0 =A0vendor =A0 =A0 =3D 'ENE Technology Inc' > =A0 =A0device =A0 =A0 =3D 'CardBus Controller (CB-1420)' > =A0 =A0class =A0 =A0 =A0=3D bridge > =A0 =A0subclass =A0 =3D PCI-CardBus > =A0 =A0cap 01[a0] =3D powerspec 1 =A0supports D0 D1 D2 D3 =A0current D0 > ... > > dmesg: > wi0: at port 0x100-0x13f irq 17 functi= on 0 config 1 on pccard0 > wi0: [ITHREAD] > wi0: device timeout > wi0: device timeout > wi0: record read mismatch, rid=3Dfd44, got=3Dfc80 > wi0: device timeout > .... Interesting it does not seems to be able to fetch the firmware information of the card. As it would normally list something like: wi0: mem 0xa0000000-0xa0000fff irq 10 at device 16.0 on= pci0 wi0: [ITHREAD] wi0: using RF:PRISM2.5 MAC:ISL3874A(Mini-PCI) wi0: Intersil Firmware: Primary (1.1.1), Station (1.8.2) wi0: Ethernet address: 00:02:6f:4a:cd:f5 > my questions are: > 1. why txpower 0 in 8.0 box? > 2. why too many ``device timeout'' messages in dmesg on 8.0 box? > 3. why all pings lost in that link? Usually the firmware on the card is this biggest issue, causing the card not getting detected, generating all the device timeout messages. Running new firmware seems to fix it for a while. ```man 4 wi''' lists the minimum required versions. Some firmware upgrade hints are listed over here: http://www.wirelessleiden.nl/projects/nodefactory/ticket/23 We had 200+ wi(4) cards running in our Wireless Metropolitan Network and where running into the same walls as you did, every new release issued more problems with those wi(4) cards. By the end we desired to replace them all by ath(4) based cards (active development on the driver :-)). Br. /Rick --=20 http://wirelessleiden.nl