From owner-freebsd-drivers@FreeBSD.ORG Sun Apr 13 02:44:03 2008 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2DA231065671 for ; Sun, 13 Apr 2008 02:44:03 +0000 (UTC) (envelope-from gpmusketeer@hotmail.com) Received: from bay0-omc3-s8.bay0.hotmail.com (bay0-omc3-s8.bay0.hotmail.com [65.54.246.208]) by mx1.freebsd.org (Postfix) with ESMTP id 0C4B78FC1D for ; Sun, 13 Apr 2008 02:44:03 +0000 (UTC) (envelope-from gpmusketeer@hotmail.com) Received: from BAY109-W24 ([64.4.19.124]) by bay0-omc3-s8.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Sat, 12 Apr 2008 19:32:03 -0700 Message-ID: X-Originating-IP: [60.48.75.173] From: paul pang To: Date: Sun, 13 Apr 2008 10:32:03 +0800 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 13 Apr 2008 02:32:03.0469 (UTC) FILETIME=[8F05E3D0:01C89D0E] Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: wpi make error* X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Apr 2008 02:44:03 -0000 I have 20071102-freebsd-wpi.tar.gz install successfully but this is the i= fconfig message wpi0: flags=3D8803 metric 0 mtu 1500 ether 00:13:02:bf:92:f8 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier ssid "" channel 1 (2412 Mhz 11b) authmode OPEN privacy OFF txpower 50 bmiss 7 scanvalid 60 bintval 0 Note that: no carrier. and dmesg stated wpi0: mem 0xd8000000-0xd8000fff irq 17 at d= evice 0.0 on pci3 bus_dmamem_alloc failed to align memory properly. ................ bus_dmamem_alloc failed to align memory properly. wpi0: Ethernet address: 00:13:02:bf:92:f8 wpi0: [ITHREAD] wpi0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps wpi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps wpi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbp= s 36Mbps 48Mbps 54Mbps wpifw: You need to read the LICENSE file in /usr/share/doc/legal/intel_wpi/= . wpifw: If you agree with the license, set legal.intel_wpi.license_ack=3D1 i= n /boot/loader.conf. module_register_init: MOD_LOAD (wpifw_fw, 0xc4f6d520, 0) error 1 firmware_get: failed to load firmware image wpifw wpi0: could not load firmware image 'wpifw' wpi0: A problem occurred loading the firmware to the driver ukbd0: at uhub2 port 1 (addr 2) disconnected ukbd0: detached uhid0: at uhub2 port 1 (addr 2) disconnected uhid0: detached ukbd0: on uhub2 kbd2 at ukbd0 uhid0: on uhub2 wpi0: detached wpi0: mem 0xd8000000-0xd8000fff irq 17 at d= evice 0.0 on pci3 wpi0: Driver Revision 20071102 wpi0: Hardware Revision (0x801) bus_dmamem_alloc failed to align memory properly. ................................. bus_dmamem_alloc failed to align memory properly. adding chan 1 flags=3D0x2b maxpwr=3D15, offset 2 adding chan 2 flags=3D0x2b maxpwr=3D15, offset 4 adding chan 3 flags=3D0x2b maxpwr=3D15, offset 6 adding chan 4 flags=3D0x2b maxpwr=3D15, offset 8 adding chan 5 flags=3D0x2b maxpwr=3D15, offset 10 adding chan 6 flags=3D0x2b maxpwr=3D15, offset 12 adding chan 7 flags=3D0x2b maxpwr=3D15, offset 14 adding chan 8 flags=3D0x2b maxpwr=3D15, offset 16 adding chan 9 flags=3D0x2b maxpwr=3D15, offset 18 adding chan 10 flags=3D0x2b maxpwr=3D15, offset 20 adding chan 11 flags=3D0x2b maxpwr=3D14, offset 22 adding chan 36 flags=3D0xa1 maxpwr=3D14, offset 23 adding chan 40 flags=3D0xa1 maxpwr=3D14, offset 24 adding chan 44 flags=3D0xa1 maxpwr=3D14, offset 25 adding chan 48 flags=3D0xa1 maxpwr=3D14, offset 26 adding chan 52 flags=3D0xb1 maxpwr=3D14, offset 27 adding chan 56 flags=3D0xb1 maxpwr=3D14, offset 28 adding chan 60 flags=3D0xb1 maxpwr=3D14, offset 29 adding chan 64 flags=3D0xb1 maxpwr=3D14, offset 30 adding chan 149 flags=3D0x21 maxpwr=3D16, offset 31 adding chan 153 flags=3D0x21 maxpwr=3D16, offset 32 adding chan 157 flags=3D0x21 maxpwr=3D16, offset 33 adding chan 161 flags=3D0x21 maxpwr=3D16, offset 34 adding chan 165 flags=3D0x21 maxpwr=3D16, offset 35 power group 0: chan=3D1 maxpwr=3D47 temp=3D-187 sample 0: index=3D13 power=3D43 sample 1: index=3D29 power=3D30 sample 2: index=3D47 power=3D10 sample 3: index=3D58 power=3D-1 sample 4: index=3D77 power=3D-19 power group 1: chan=3D44 maxpwr=3D51 temp=3D-191 sample 0: index=3D12 power=3D42 sample 1: index=3D19 power=3D35 sample 2: index=3D32 power=3D21 sample 3: index=3D43 power=3D11 sample 4: index=3D77 power=3D-22 power group 2: chan=3D64 maxpwr=3D51 temp=3D-189 sample 0: index=3D12 power=3D43 sample 1: index=3D20 power=3D35 sample 2: index=3D33 power=3D22 sample 3: index=3D44 power=3D13 sample 4: index=3D77 power=3D-18 power group 3: chan=3D116 maxpwr=3D48 temp=3D-188 sample 0: index=3D12 power=3D36 sample 1: index=3D20 power=3D27 sample 2: index=3D36 power=3D11 sample 3: index=3D48 power=3D0 sample 4: index=3D77 power=3D-27 power group 4: chan=3D153 maxpwr=3D48 temp=3D-186 sample 0: index=3D10 power=3D35 sample 1: index=3D20 power=3D23 sample 2: index=3D32 power=3D11 sample 3: index=3D42 power=3D3 sample 4: index=3D77 power=3D-28 wpi0: Regulatory Domain: MoW1 wpi0: Hardware Type: B wpi0: Hardware Revision: ? wpi0: SKU does support 802.11a wpi0: Ethernet address: 00:13:02:bf:92:f8 wpi0: [ITHREAD] wpi0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps wpi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps wpi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbp= s 36Mbps 48Mbps 54Mbps wpi0: timeout resetting Tx ring 1 wpi0: timeout resetting Tx ring 3 wpi0: timeout resetting Tx ring 4 NEWSTATE:INIT firmware_get: failed to load firmware image wpifw wpi0: could not load firmware image 'wpifw' wpi0: A problem occurred loading the firmware to the driver NEWSTATE:INIT firmware_get: failed to load firmware image wpifw wpi0: could not load firmware image 'wpifw' wpi0: A problem occurred loading the firmware to the driver While i have this in my loader.conf=20 if_ath_load["YES" if_wpi_load=3D"YES" wlan_load=3D"YES" wlan_wep_load=3D"YES" wlan_ccmp_load=3D"YES" wlan_tkip_load=3D"YES" legal.intel_wpi.license_ack=3D1 wpifw_load=3D"YES" but why it still ask me to set the license? _________________________________________________________________ Help Splitzo Sally Before It=92s Too Late!=20 http://www.thegirlwhosplitinto5.com/= From owner-freebsd-drivers@FreeBSD.ORG Mon Apr 14 10:07:36 2008 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9C0FE106564A for ; Mon, 14 Apr 2008 10:07:36 +0000 (UTC) (envelope-from tevans.uk@googlemail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.169]) by mx1.freebsd.org (Postfix) with ESMTP id 22ABE8FC28 for ; Mon, 14 Apr 2008 10:07:35 +0000 (UTC) (envelope-from tevans.uk@googlemail.com) Received: by ug-out-1314.google.com with SMTP id y2so450056uge.37 for ; Mon, 14 Apr 2008 03:07:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:cc:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer; bh=jhyPHy8+RGKhFzvU+h41HRo/1nEFPUn61It/vVDfUuA=; b=HZpOhtd+aKo09122oR0F6HvxaVRPU5RHpxg2IRxGMNlCgGevoZOdN/jpqHkl3FdLKsGxt+g6w5cxsHYXfP5kCoBK8iA9/MM0Q4iyvQ5a2x81cTacNDPjPYWS7axKQWnqroES05FIgiJuA6u04HHH9BFsmDj51QS6Ga+FOUSzUSM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer; b=xeHSzBM1QBrEZHu6sqb98pLjm/5JxUb9yfr/qpHI+FmJnGf2IpMZwlV14x4bucc+/7hWpek4ikGA4DTPPtauDCpOIBhtsWrW23xPKqE2aWFv+RTqoYdgs2QthrieN5xxZq4zvPLT69bMfCD205q5ojJ60k4AMf5HKCrTcNu0rig= Received: by 10.66.217.20 with SMTP id p20mr3651398ugg.51.1208166032551; Mon, 14 Apr 2008 02:40:32 -0700 (PDT) Received: from ?127.0.0.1? ( [217.206.187.80]) by mx.google.com with ESMTPS id j8sm5757023gvb.10.2008.04.14.02.40.30 (version=SSLv3 cipher=RC4-MD5); Mon, 14 Apr 2008 02:40:31 -0700 (PDT) From: Tom Evans To: paul pang In-Reply-To: References: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-pphaVDAmARbSID5nj17U" Date: Mon, 14 Apr 2008 10:40:28 +0100 Message-Id: <1208166028.8904.27.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.10.2 FreeBSD GNOME Team Port Cc: freebsd-drivers@freebsd.org Subject: Re: wpi make error* X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Apr 2008 10:07:36 -0000 --=-pphaVDAmARbSID5nj17U Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sun, 2008-04-13 at 10:32 +0800, paul pang wrote: > I have 20071102-freebsd-wpi.tar.gz install successfully but this is the = ifconfig message I wouldn't use some ancient snapshot of wpi. There have been significant reliability and performance improvements made to the driver in CURRENT/RELENG_7 . If you are running 7.0, update to RELENG_7. >=20 > wpi0: flags=3D8803 metric 0 mtu 1500 > ether 00:13:02:bf:92:f8 > media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) > status: no carrier > ssid "" channel 1 (2412 Mhz 11b) > authmode OPEN privacy OFF txpower 50 bmiss 7 scanvalid 60 bintval= 0 >=20 > Note that: no carrier. >=20 > and dmesg stated >=20 > wpi0: mem 0xd8000000-0xd8000fff irq 17 at= device 0.0 on pci3 > bus_dmamem_alloc failed to align memory properly. > ................ > bus_dmamem_alloc failed to align memory properly. >=20 > While i have this in my loader.conf=20 >=20 > if_ath_load["YES" > if_wpi_load=3D"YES" > wlan_load=3D"YES" > wlan_wep_load=3D"YES" > wlan_ccmp_load=3D"YES" > wlan_tkip_load=3D"YES" > legal.intel_wpi.license_ack=3D1 > wpifw_load=3D"YES" >=20 > but why it still ask me to set the license? >=20 >=20 The bus_dmamem_alloc messages are harmless. Have you rebooted since adding legal.intel_wpi.license_ack=3D1 to boot loader.conf? Is it in your kernel environment?=20 kenv | grep wpi If it isn't, unload the modules, and do kenv legal.intel_wpi.license_ack=3D1 I'd also strongly recommend moving to a version that has wpi by default - ie RELENG_7 - and re-report any problems you have. It is quite likely that it will work much more smoothly with these fixes, which are on RELENG_7 and not RELENG_7_0. FreeBSD src repository Modified files: (Branch: RELENG_7) sys/dev/wpi if_wpi.c if_wpireg.h if_wpivar.h=20 Log: MFC if_wpi.c r1.9-10, if_wpireg.h r1.3, if_wpivar.h r1.2 =20 Update wpi(4) with stability fixes - remove second taskqueue - busdma 16k alignment workaround - use busdma instead of external mbuf storage on Rx - locking fixes - net80211 state change fixes - improve scanning reliability - improve radio hw switch interaction - consolidate callouts Cheers Tom --=-pphaVDAmARbSID5nj17U Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQBIAyaIlcRvFfyds/cRAiTTAKCsuqRU5b9bkzW53l9gGNtHVUNhoACfYIl1 DASsANrx7giNivXxFu8Aa2c= =zfvN -----END PGP SIGNATURE----- --=-pphaVDAmARbSID5nj17U-- From owner-freebsd-drivers@FreeBSD.ORG Wed Apr 16 09:00:51 2008 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B6914106566C for ; Wed, 16 Apr 2008 09:00:51 +0000 (UTC) (envelope-from sogabe@iij.ad.jp) Received: from otm-mgo00.iij.ad.jp (otm-mgo00.iij.ad.jp [210.138.20.174]) by mx1.freebsd.org (Postfix) with ESMTP id 6C39F8FC13 for ; Wed, 16 Apr 2008 09:00:51 +0000 (UTC) (envelope-from sogabe@iij.ad.jp) DKIM-Signature: v=1;a=rsa-sha256;c=relaxed/simple;d=iij.ad.jp;h=Message-ID: Date:From:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding; i= sogabe@iij.ad.jp; s=omgo0; t=1208335148; x=1209544748; bh=kL48KWo7H9PWCbblNR9oAOv iVR5rajtMehQkC2UhJQI=; b=nYhpwcVAIHZcY5P94QCgcIM5mf8z9Pnze94IQEQ4nBvR9RZ3OelIz oQ9zYcPK/DUlh0UgJn/zkg6hbmbycWZSM+EZuJ6WDJAQyFuJoctkNxoE/kluq7F4cvUoPw3P8hagL /rB3yvyBBRA3d9MwUYmU+OUpQgHmwgF+Gvdv1YQNc=; Received: OTM-MO(otm-mgo00) id m3G8d8DK078685; Wed, 16 Apr 2008 17:39:08 +0900 (JST) Received: OTM-MIX(otm-mix00) id m3G8d8Sj081054; Wed, 16 Apr 2008 17:39:08 +0900 (JST) Received: from [192.168.184.115] ([192.168.184.115]) by rsmtp.iij.ad.jp (OTM-MR/rsmtp01) id m3G8d7xv044139 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 16 Apr 2008 17:39:08 +0900 (JST) Message-ID: <4805BBA7.60806@iij.ad.jp> Date: Wed, 16 Apr 2008 17:41:11 +0900 From: Sogabe Takashi User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: freebsd-drivers@freebsd.org Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Subject: question: workaround for AX88190 (dev/ed/if_ed.c) X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Apr 2008 09:00:51 -0000 Hi all, Does anyone know what kind of problems about following workaround-code? I read asix datasheets, but corresponding problem is not described. (in sys/dev/ed/if_ed.c) /* * Ethernet interface interrupt processor */ void edintr(void *arg) { ... /* * XXX workaround for AX88190 * We limit this to 5000 iterations. At 1us per inb/outb, * this translates to about 15ms, which should be plenty * of time, and also gives protection in the card eject * case. */ if (sc->chip_type == ED_CHIP_TYPE_AX88190) { count = 5000; /* 15ms */ while (count-- && (ed_nic_inb(sc, ED_P0_ISR) & isr)) { ed_nic_outb(sc, ED_P0_ISR,0); ed_nic_outb(sc, ED_P0_ISR,isr); } if (count == 0) break; } ... } -- sogabe@iij.ad.jp From owner-freebsd-drivers@FreeBSD.ORG Wed Apr 16 16:29:21 2008 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CA4CA106566C for ; Wed, 16 Apr 2008 16:29:21 +0000 (UTC) (envelope-from pisymbol@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.30]) by mx1.freebsd.org (Postfix) with ESMTP id 7520C8FC25 for ; Wed, 16 Apr 2008 16:29:21 +0000 (UTC) (envelope-from pisymbol@gmail.com) Received: by yw-out-2324.google.com with SMTP id 2so1406876ywt.13 for ; Wed, 16 Apr 2008 09:29:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition; bh=cbeNwuoe5GWVXOURQKZVNT8I/2XRz4LBqBuN304PsOI=; b=E875QjB6tWXW0+CeEWuohnlR2k5uTQZdEdbp13sIyIkmqMiv8VgKmJge9ZEtZGxXOfJIzyeQZUn40xMg6okUxzTf/L081eAwlh2lVo9042Kr4Sat5PQ8NuWUssZD9SZ4oTrn+8+zMMK5NSihLfMu/JZYlxFkxq8ds9vWhKzUhkU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition; b=dPuiWP3r7NmJPEdcBFsmbijz4s8uuEsprBI4jbNMjpUCFcUH9ci/bFblTaHQTklN1VCvzFDxnkdrh9bMO/PDJEOmLz+i1TPtjX593Rc2GDSVaZ/X8qNxWi6V3BI+lf4s/slwAcPbXYvCEBpOteqmcFhFjgf2W3ElziP6jMYUW2o= Received: by 10.150.49.15 with SMTP id w15mr361375ybw.101.1208363359508; Wed, 16 Apr 2008 09:29:19 -0700 (PDT) Received: by 10.151.15.21 with HTTP; Wed, 16 Apr 2008 09:29:19 -0700 (PDT) Message-ID: <3c0b01820804160929i76cc04fdy975929e2a04c0368@mail.gmail.com> Date: Wed, 16 Apr 2008 12:29:19 -0400 From: "Alexander Sack" To: freebsd-drivers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: freebsd-net@freebsd.org, freebsd-hackers@freebsd.org Subject: bge dropping packets issue X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Apr 2008 16:29:22 -0000 Hello: Sorry for cross posting but this seems to be both a driver and network/kernel issue so I figure I actually thought all lists seemed appropriate. I'm investigating an issue we are seeing with 6.1-RELEASE and the bge driver dropping packets sporadically at 100MBps speed. The machine is a 2-way Intel dual-core running 64-bit FreeBSD-6.1 Release with SMP/8GB RAM. I would post dmesg but currently I'm running a test and has a lot of instrumentation in it. Anyway, what I'm seeing with a SmartBit traffic generator connected to 4 bge cards (all BCOM_DEVICEID_BCM5704C) is sporadic packet drops as recorded by the firmware in its statistics structure (as pulled out by bge_tick()), i.e. this isn't malloc starvation of allocating mbuf clusters, etc. The firmware seems to just drop packets occasionally (depending on workload). Its get mainly aggravated when heavy disk I/O occurs from generating a network report which entails gzip'ing a very large dumpfile in /tmp and then anonymously ftping it via another interface (em). DEVICE_POLLING is being used: # sysctl -a | grep kern.polling kern.polling.idlepoll_sleeping: 1 kern.polling.stalled: 3 kern.polling.suspect: 1023 kern.polling.phase: 0 kern.polling.enable: 1 kern.polling.handlers: 6 kern.polling.residual_burst: 0 kern.polling.pending_polls: 0 kern.polling.lost_polls: 24436 kern.polling.short_ticks: 592 kern.polling.reg_frac: 20 kern.polling.user_frac: 50 kern.polling.idle_poll: 0 kern.polling.each_burst: 32 kern.polling.burst_max: 1000 kern.polling.burst: 1000 After looking at the driver for a bit, I believe the issue maybe from RX chain starvation which causes the firmware to drop packets when bge_rxeof() can not keep up. The driver uses a global locking scheme which may contribute to some of these robustness issues (this is a generalization on my part without hard facts so take it with a grain of salt, I just notice things like bge_tick() being called every cycle and competing with the ISR when it may not have too or may not have too for its entire duration, updating stats for example). My main question is currently the RX chain slots are set to a global define BGE_SSLOTS (if_bgedevreg.h) which is 256. Technically this card I believe can do up to 512 slots and the comment above said these are tunable yet not exposed via SYSCTL. Does anyone know why its not 512 by default? Is there any harm in setting it to 512 instead of 256? Why not make it tunable (512 as max)? I've increased the SSLOTS to 512 so there are more RX chain slots available (as I currently understand it, I don't have specs) and the kern.polling.each_burst to 150 (max) in an effort to try to keep the BGE driver in bge_rxeof() and to experiment a bit! This is the first exposure to this code so be gentle! :D! Has anyone seen this problem before with bge? Am I barking up the wrong tree with my initial investigation? Does anyone know if its even possible to achieve 100% packet capture with bge at its supported speeds (10/100/1000)? Thanks! -aps From owner-freebsd-drivers@FreeBSD.ORG Wed Apr 16 16:55:52 2008 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B4D321065673 for ; Wed, 16 Apr 2008 16:55:52 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id AB8918FC26 for ; Wed, 16 Apr 2008 16:55:52 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 637241A4D84; Wed, 16 Apr 2008 09:39:38 -0700 (PDT) Date: Wed, 16 Apr 2008 09:39:38 -0700 From: Alfred Perlstein To: Sogabe Takashi Message-ID: <20080416163938.GM95731@elvis.mu.org> References: <4805BBA7.60806@iij.ad.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4805BBA7.60806@iij.ad.jp> User-Agent: Mutt/1.4.2.3i Cc: freebsd-drivers@freebsd.org Subject: Re: question: workaround for AX88190 (dev/ed/if_ed.c) X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Apr 2008 16:55:52 -0000 I think the driver developer found the card buggy and wanted to give it a longer try to clear the status bits, but if it just flat out refuses to clear status, then it just aborts. * Sogabe Takashi [080416 02:00] wrote: > Hi all, > > Does anyone know what kind of problems about following > workaround-code? > > I read asix datasheets, but corresponding problem is not > described. > > (in sys/dev/ed/if_ed.c) > /* > * Ethernet interface interrupt processor > */ > void > edintr(void *arg) > { > ... > /* > * XXX workaround for AX88190 > * We limit this to 5000 iterations. At 1us per inb/outb, > * this translates to about 15ms, which should be plenty > * of time, and also gives protection in the card eject > * case. > */ > if (sc->chip_type == ED_CHIP_TYPE_AX88190) { > count = 5000; /* 15ms */ > while (count-- && (ed_nic_inb(sc, ED_P0_ISR) & isr)) { > ed_nic_outb(sc, ED_P0_ISR,0); > ed_nic_outb(sc, ED_P0_ISR,isr); > } > if (count == 0) > break; > } > ... > } > > -- > sogabe@iij.ad.jp > _______________________________________________ > freebsd-drivers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-drivers > To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@freebsd.org" -- - Alfred Perlstein From owner-freebsd-drivers@FreeBSD.ORG Wed Apr 16 17:41:19 2008 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9F87A10656FD for ; Wed, 16 Apr 2008 17:41:19 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from parsely.rain.com (parsely.rain.com [199.26.172.196]) by mx1.freebsd.org (Postfix) with ESMTP id 38C118FC16 for ; Wed, 16 Apr 2008 17:41:18 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from sopwith.solgatos.com (uucp@localhost) by parsely.rain.com (8.11.4/8.11.4) with UUCP id m3GHfDl56312; Wed, 16 Apr 2008 10:41:13 -0700 (PDT) (envelope-from freebsd@sopwith.solgatos.com) Received: from localhost by sopwith.solgatos.com (8.8.8/6.24) id RAA23071; Wed, 16 Apr 2008 17:32:50 GMT Message-Id: <200804161732.RAA23071@sopwith.solgatos.com> To: "Alexander Sack" In-reply-to: Your message of "Wed, 16 Apr 2008 12:29:19 EDT." <3c0b01820804160929i76cc04fdy975929e2a04c0368@mail.gmail.com> Date: Wed, 16 Apr 2008 10:32:50 +0100 From: Dieter Cc: freebsd-net@freebsd.org, freebsd-drivers@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: bge dropping packets issue X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Apr 2008 17:41:19 -0000 > I'm investigating an issue we are seeing with 6.1-RELEASE and the bge > driver dropping packets sporadically at 100MBps speed. > Its get mainly aggravated when heavy disk I/O occurs > Has anyone seen this problem before with bge? Am I barking up the > wrong tree with my initial investigation? Does anyone know if its > even possible to achieve 100% packet capture with bge at its supported > speeds (10/100/1000)? I had a similar problem with bge and 6.0-RELEASE. Bge works great for me in 6.2-RELEASE. So far 7.0-RELEASE looks good as well (bge-wise, I do have unresolved issues with 7). My app is TCP, cranking the TCP receive buffer way up helped, as did turning off Nagle. My bge is 1000, but connected at 100 since that is what the other end is. I saw problems at less than 20 Mbps. There is still a problem that other drivers can lock out bge for too long. For example kern/118093: firewire bus reset. From owner-freebsd-drivers@FreeBSD.ORG Wed Apr 16 18:20:35 2008 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A68341065679 for ; Wed, 16 Apr 2008 18:20:35 +0000 (UTC) (envelope-from pisymbol@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.28]) by mx1.freebsd.org (Postfix) with ESMTP id 508178FC1C for ; Wed, 16 Apr 2008 18:20:35 +0000 (UTC) (envelope-from pisymbol@gmail.com) Received: by yw-out-2324.google.com with SMTP id 2so1436584ywt.13 for ; Wed, 16 Apr 2008 11:20:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=gWce5972bEgiQU0Qe0OxMbA8rvfNAm3oVFyxzVaPFIs=; b=iAUmo1iSjg/sFIwharPCZkD4hVnlne4H5qYV9arouVxiFWL/Ohe/PWCgl/r+eshjoPzaaYoNRwsT1wgVJ1KCuRpbRmmWk0O7xpCYhx1AetU7DHoX9rUPqEjWjbY6IiJ+lTDrLNlIHXhLp0apTJzaDIs+qsUoPNf0AQH4d0BxJ54= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=UKKeh78Hy0q3aWAULJgqcdI/fvsKtw/151AmO4oV/EvssU+tcxhdpLXZ9onS0Bu+fE/ByyRznmIsZP3w8YsQA3ewwLcsX8GDmE2OLwYy1Pi1k2lG0w2wX5Y2lvp0Mst4YnbKQdtYSIEU9/GTCWMIUqrKo+70CKn/89J5H9OcYuQ= Received: by 10.151.85.20 with SMTP id n20mr553514ybl.28.1208370027256; Wed, 16 Apr 2008 11:20:27 -0700 (PDT) Received: by 10.151.15.21 with HTTP; Wed, 16 Apr 2008 11:20:27 -0700 (PDT) Message-ID: <3c0b01820804161120udb54ab3tea4bf7baade0061f@mail.gmail.com> Date: Wed, 16 Apr 2008 14:20:27 -0400 From: "Alexander Sack" To: Dieter In-Reply-To: <200804161732.RAA23071@sopwith.solgatos.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3c0b01820804160929i76cc04fdy975929e2a04c0368@mail.gmail.com> <200804161732.RAA23071@sopwith.solgatos.com> Cc: freebsd-net@freebsd.org, freebsd-drivers@freebsd.org, Jung-uk Kim , freebsd-hackers@freebsd.org Subject: Re: bge dropping packets issue X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Apr 2008 18:20:35 -0000 Dieter: Thanks, at 20Mbps! That's pretty aweful. JK: Thanks again. Wow, I searched the list and didn't see much discussion with respect to bge and packet loss! I will try the rest of that patch including pushing the TCP receive buffer up (though I don't think that's going to help in this case). The above is based on just looking at code.... I guess some follow-up questions would be: 1) Why isn't BGE_SSLOTS tunable (to a point)? Why can't that be added the driver? I noticed that CURRENT has added a lot more SYSCTL information. Moreover it seems the Linux driver can set it up to 1024. 2) bge_tick() uses the same global mutex for its callout as the rest of the driver. Moreover, it really doesn't have to hold it while updating statistics, they are reads of volatile registers anyway (blocking the ISR doesn't prevent the firmware from updating its stat struct). Would there be any interest in using a separate mutex for the callout itself and then just hold the lock for the other small calls (bge_asf_driver_up(), bge_watchdog())? I'm experimenting with right now just dropping the BGE mutex around the bge_stats_update() calls to give more time to bge_rxeof() to drain rx_bd's. I admit that bge_tick doesn't do a whole lot but it seems this driver is very sensitive to resource starvation and I'm trying to get the BGE driver to drain as much rx_bd's as possible to avoid drops due to the firmware having no place to put them! 3) How does interrupt non-DEVICE_POLLING perform? Thanks guys! -aps On Wed, Apr 16, 2008 at 5:32 AM, Dieter wrote: > > I'm investigating an issue we are seeing with 6.1-RELEASE and the bge > > driver dropping packets sporadically at 100MBps speed. > > > > Its get mainly aggravated when heavy disk I/O occurs > > > > Has anyone seen this problem before with bge? Am I barking up the > > wrong tree with my initial investigation? Does anyone know if its > > even possible to achieve 100% packet capture with bge at its supported > > speeds (10/100/1000)? > > I had a similar problem with bge and 6.0-RELEASE. Bge works great for > me in 6.2-RELEASE. So far 7.0-RELEASE looks good as well (bge-wise, > I do have unresolved issues with 7). > > My app is TCP, cranking the TCP receive buffer way up helped, as did > turning off Nagle. > > My bge is 1000, but connected at 100 since that is what the other end is. > I saw problems at less than 20 Mbps. > > There is still a problem that other drivers can lock out bge for too long. > For example kern/118093: firewire bus reset. > From owner-freebsd-drivers@FreeBSD.ORG Wed Apr 16 19:20:16 2008 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 787B6106564A; Wed, 16 Apr 2008 19:20:16 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 356E58FC1D; Wed, 16 Apr 2008 19:20:16 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.2/8.14.1) with ESMTP id m3GJJPQb024027; Wed, 16 Apr 2008 13:19:25 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Wed, 16 Apr 2008 13:20:24 -0600 (MDT) Message-Id: <20080416.132024.1649777798.imp@bsdimp.com> To: alfred@freebsd.org From: "M. Warner Losh" In-Reply-To: <20080416163938.GM95731@elvis.mu.org> References: <4805BBA7.60806@iij.ad.jp> <20080416163938.GM95731@elvis.mu.org> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-drivers@freebsd.org Subject: Re: question: workaround for AX88190 (dev/ed/if_ed.c) X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Apr 2008 19:20:17 -0000 In message: <20080416163938.GM95731@elvis.mu.org> Alfred Perlstein writes: : I think the driver developer found the card buggy and wanted : to give it a longer try to clear the status bits, but if it : just flat out refuses to clear status, then it just aborts. Some versions of silicon seem to be better than others at this as well. Some cards need it, but most don't. Warner : * Sogabe Takashi [080416 02:00] wrote: : > Hi all, : > : > Does anyone know what kind of problems about following : > workaround-code? : > : > I read asix datasheets, but corresponding problem is not : > described. : > : > (in sys/dev/ed/if_ed.c) : > /* : > * Ethernet interface interrupt processor : > */ : > void : > edintr(void *arg) : > { : > ... : > /* : > * XXX workaround for AX88190 : > * We limit this to 5000 iterations. At 1us per inb/outb, : > * this translates to about 15ms, which should be plenty : > * of time, and also gives protection in the card eject : > * case. : > */ : > if (sc->chip_type == ED_CHIP_TYPE_AX88190) { : > count = 5000; /* 15ms */ : > while (count-- && (ed_nic_inb(sc, ED_P0_ISR) & isr)) { : > ed_nic_outb(sc, ED_P0_ISR,0); : > ed_nic_outb(sc, ED_P0_ISR,isr); : > } : > if (count == 0) : > break; : > } : > ... : > } : > : > -- : > sogabe@iij.ad.jp : > _______________________________________________ : > freebsd-drivers@freebsd.org mailing list : > http://lists.freebsd.org/mailman/listinfo/freebsd-drivers : > To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@freebsd.org" : : -- : - Alfred Perlstein : _______________________________________________ : freebsd-drivers@freebsd.org mailing list : http://lists.freebsd.org/mailman/listinfo/freebsd-drivers : To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@freebsd.org" : : From owner-freebsd-drivers@FreeBSD.ORG Thu Apr 17 05:54:19 2008 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 489361065671 for ; Thu, 17 Apr 2008 05:54:19 +0000 (UTC) (envelope-from Benjamin.Close@clearchain.com) Received: from ipmail01.adl6.internode.on.net (ipmail01.adl6.internode.on.net [203.16.214.146]) by mx1.freebsd.org (Postfix) with ESMTP id 6B8BA8FC12 for ; Thu, 17 Apr 2008 05:54:17 +0000 (UTC) (envelope-from Benjamin.Close@clearchain.com) Received: from ppp121-45-53-166.lns11.adl2.internode.on.net (HELO mail.clearchain.com) ([121.45.53.166]) by ipmail01.adl6.internode.on.net with ESMTP; 17 Apr 2008 15:24:15 +0930 Received: from [192.168.155.54] (taurus.internal.clearchain.com [192.168.155.54]) (authenticated bits=0) by mail.clearchain.com (8.14.2/8.14.2) with ESMTP id m3H5rOJY075702 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Apr 2008 15:23:24 +0930 (CST) (envelope-from Benjamin.Close@clearchain.com) Message-ID: <4806E604.5060501@clearchain.com> Date: Thu, 17 Apr 2008 15:24:12 +0930 From: Benjamin Close User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: paul pang References: In-Reply-To: X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV version 0.93, clamav-milter version 0.93 on pegasus.clearchain.com X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-3.0 (mail.clearchain.com [192.168.154.1]); Thu, 17 Apr 2008 15:23:24 +0930 (CST) Cc: freebsd-drivers@freebsd.org Subject: Re: wpi make error* X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Apr 2008 05:54:19 -0000 Hi Paul, Whilst I agree with Tom you should use the latest version of wpi, the problem you have is due to not building/installing the firmware module. ie: Assuming you extracted the tarball to /tmp/wpi do: cd /tmp/wpi/sys/modules/wpifw make make install Cheers, Benjamin paul pang wrote: > I have 20071102-freebsd-wpi.tar.gz install successfully but this is the ifconfig message > > wpi0: flags=8803 metric 0 mtu 1500 > ether 00:13:02:bf:92:f8 > media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) > status: no carrier > ssid "" channel 1 (2412 Mhz 11b) > authmode OPEN privacy OFF txpower 50 bmiss 7 scanvalid 60 bintval 0 > > Note that: no carrier. > > and dmesg stated > > wpi0: mem 0xd8000000-0xd8000fff irq 17 at device 0.0 on pci3 > bus_dmamem_alloc failed to align memory properly. > ................ > bus_dmamem_alloc failed to align memory properly. > wpi0: Ethernet address: 00:13:02:bf:92:f8 > wpi0: [ITHREAD] > wpi0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps > wpi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps > wpi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps > wpifw: You need to read the LICENSE file in /usr/share/doc/legal/intel_wpi/.. > wpifw: If you agree with the license, set legal.intel_wpi.license_ack=1 in /boot/loader.conf. > module_register_init: MOD_LOAD (wpifw_fw, 0xc4f6d520, 0) error 1 > firmware_get: failed to load firmware image wpifw > wpi0: could not load firmware image 'wpifw' > wpi0: A problem occurred loading the firmware to the driver > ukbd0: at uhub2 port 1 (addr 2) disconnected > ukbd0: detached > uhid0: at uhub2 port 1 (addr 2) disconnected > uhid0: detached > ukbd0: on uhub2 > kbd2 at ukbd0 > uhid0: on uhub2 > wpi0: detached > wpi0: mem 0xd8000000-0xd8000fff irq 17 at device 0.0 on pci3 > wpi0: Driver Revision 20071102 > wpi0: Hardware Revision (0x801) > bus_dmamem_alloc failed to align memory properly. > ................................. > bus_dmamem_alloc failed to align memory properly. > adding chan 1 flags=0x2b maxpwr=15, offset 2 > adding chan 2 flags=0x2b maxpwr=15, offset 4 > adding chan 3 flags=0x2b maxpwr=15, offset 6 > adding chan 4 flags=0x2b maxpwr=15, offset 8 > adding chan 5 flags=0x2b maxpwr=15, offset 10 > adding chan 6 flags=0x2b maxpwr=15, offset 12 > adding chan 7 flags=0x2b maxpwr=15, offset 14 > adding chan 8 flags=0x2b maxpwr=15, offset 16 > adding chan 9 flags=0x2b maxpwr=15, offset 18 > adding chan 10 flags=0x2b maxpwr=15, offset 20 > adding chan 11 flags=0x2b maxpwr=14, offset 22 > adding chan 36 flags=0xa1 maxpwr=14, offset 23 > adding chan 40 flags=0xa1 maxpwr=14, offset 24 > adding chan 44 flags=0xa1 maxpwr=14, offset 25 > adding chan 48 flags=0xa1 maxpwr=14, offset 26 > adding chan 52 flags=0xb1 maxpwr=14, offset 27 > adding chan 56 flags=0xb1 maxpwr=14, offset 28 > adding chan 60 flags=0xb1 maxpwr=14, offset 29 > adding chan 64 flags=0xb1 maxpwr=14, offset 30 > adding chan 149 flags=0x21 maxpwr=16, offset 31 > adding chan 153 flags=0x21 maxpwr=16, offset 32 > adding chan 157 flags=0x21 maxpwr=16, offset 33 > adding chan 161 flags=0x21 maxpwr=16, offset 34 > adding chan 165 flags=0x21 maxpwr=16, offset 35 > power group 0: chan=1 maxpwr=47 temp=-187 > sample 0: index=13 power=43 > sample 1: index=29 power=30 > sample 2: index=47 power=10 > sample 3: index=58 power=-1 > sample 4: index=77 power=-19 > power group 1: chan=44 maxpwr=51 temp=-191 > sample 0: index=12 power=42 > sample 1: index=19 power=35 > sample 2: index=32 power=21 > sample 3: index=43 power=11 > sample 4: index=77 power=-22 > power group 2: chan=64 maxpwr=51 temp=-189 > sample 0: index=12 power=43 > sample 1: index=20 power=35 > sample 2: index=33 power=22 > sample 3: index=44 power=13 > sample 4: index=77 power=-18 > power group 3: chan=116 maxpwr=48 temp=-188 > sample 0: index=12 power=36 > sample 1: index=20 power=27 > sample 2: index=36 power=11 > sample 3: index=48 power=0 > sample 4: index=77 power=-27 > power group 4: chan=153 maxpwr=48 temp=-186 > sample 0: index=10 power=35 > sample 1: index=20 power=23 > sample 2: index=32 power=11 > sample 3: index=42 power=3 > sample 4: index=77 power=-28 > wpi0: Regulatory Domain: MoW1 > wpi0: Hardware Type: B > wpi0: Hardware Revision: ? > wpi0: SKU does support 802.11a > wpi0: Ethernet address: 00:13:02:bf:92:f8 > wpi0: [ITHREAD] > wpi0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps > wpi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps > wpi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps > wpi0: timeout resetting Tx ring 1 > wpi0: timeout resetting Tx ring 3 > wpi0: timeout resetting Tx ring 4 > NEWSTATE:INIT > firmware_get: failed to load firmware image wpifw > wpi0: could not load firmware image 'wpifw' > wpi0: A problem occurred loading the firmware to the driver > NEWSTATE:INIT > firmware_get: failed to load firmware image wpifw > wpi0: could not load firmware image 'wpifw' > wpi0: A problem occurred loading the firmware to the driver > > While i have this in my loader.conf > > if_ath_load["YES" > if_wpi_load="YES" > wlan_load="YES" > wlan_wep_load="YES" > wlan_ccmp_load="YES" > wlan_tkip_load="YES" > legal.intel_wpi.license_ack=1 > wpifw_load="YES" > > but why it still ask me to set the license? > > > _________________________________________________________________ > Help Splitzo Sally Before It’s Too Late! > http://www.thegirlwhosplitinto5.com/_______________________________________________ > freebsd-drivers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-drivers > To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@freebsd.org" > From owner-freebsd-drivers@FreeBSD.ORG Thu Apr 17 21:16:26 2008 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CC5E9106566B for ; Thu, 17 Apr 2008 21:16:26 +0000 (UTC) (envelope-from lev@nupfel.de) Received: from schatten.darksystem.net (schatten.darksystem.net [88.198.51.7]) by mx1.freebsd.org (Postfix) with ESMTP id 466878FC15 for ; Thu, 17 Apr 2008 21:16:26 +0000 (UTC) (envelope-from lev@nupfel.de) Received: from schatten.darksystem.net (localhost [127.0.0.1]) by schatten.darksystem.net (Postfix) with ESMTP id 3B845727E6F; Thu, 17 Apr 2008 23:16:24 +0200 (CEST) X-Spam-Status: No, hits=1.1 required=5.0 tests=AWL, BAYES_00, RCVD_IN_DSBL, RCVD_IN_PBL, RCVD_IN_SORBS_DUL, RDNS_DYNAMIC X-Spam-Check-By: schatten.darksystem.net Received: from port-212-202-192-115.dynamic.qsc.de (HELO mail.nupfel.de) (212.202.192.115) (smtp-auth username lev, mechanism plain) by schatten.darksystem.net (qpsmtpd/0.32) with ESMTP; Thu, 17 Apr 2008 23:15:30 +0200 Received: from localhost (localhost [127.0.0.1]) by mail.nupfel.de (Postfix) with ESMTP id EEE0C1A21909; Thu, 17 Apr 2008 23:15:28 +0200 (CEST) X-Virus-Scanned: amavisd-new at nupfel.de Received: from mail.nupfel.de ([127.0.0.1]) by localhost (mail.nupfel.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pr9dNWokhcKc; Thu, 17 Apr 2008 23:15:27 +0200 (CEST) Received: from lain (lain.navi.wired [192.168.0.40]) by mail.nupfel.de (Postfix) with ESMTP id 12DB51A21908; Thu, 17 Apr 2008 23:15:27 +0200 (CEST) Date: Thu, 17 Apr 2008 23:15:16 +0200 From: Tobias Kirschstein To: "Tofig Suleymanov" Message-ID: <20080417231516.42883d5b@lain> In-Reply-To: <342414370804060210u149240cdwd0f1070b883e7c8a@mail.gmail.com> References: <20080325223539.GH4783@nupfel.de> <342414370803261129u337ad526wf67839cc30c942ad@mail.gmail.com> <20080327164843.GB9146@nupfel.de> <342414370804060210u149240cdwd0f1070b883e7c8a@mail.gmail.com> Organization: NIC.BLA X-Mailer: Claws Mail 3.3.1 (GTK+ 2.12.8; amd64-portbld-freebsd8.0) X-Face: "\j?x](l|]4p?-1Bf@!wN<&p=$.}^k-HgL}cJKbQZ3r#Ar]\%U(#6}'?<3s7%(%(gxJxxcR nSNPNr*/^~StawWU9KDJ-CT0k$f#@t2^K&BS_f|?ZV/.7Q Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAGFBMVEX+/v7++v6YOTrq8PCcuIX989UvOSj++v0BNCbpAAAAB3RJTUUHsQwfFzs7RBhzUQAAAhJJREFUOI1dU8GOqzAMNKIoV1bvwD1i0ysqrHplIdBrVSX7ATSbd03VVvn9tQNtQy0hjAdn7LED4AAcPtWm9RV+MPSfxhBLx9ajd6X/ngB6/mTwnRSZua7i7Ca+0ctZKo4Qmz+JY13X6I3nFZBxIYW1PbgfQ5RP8g0XlltEWGf3cV03joYpRnFbvYDKbXjZlXyyhEZA4lI+cN3NaVXE4VKjSwTExO10eTEkkJVqIAD5z0nUBQJluQDRSQjcrBiHAJxZlAH5CUMBMC7OcJ4LMQNnxhZ1HYPscMc6J4UlWRMNwzOpCcAHKSICd1EDn83abdREIbXsHkD1OinP1aCUCOEVRaa1lMcvywUWdYgk13JQUpYNKmvXQ8Kw5ML9YI5h8SakctBc7E/IYuLhYd/zZIk+1gM1vNweQBvHE0j+oYah3sMqAytQYlZk6+ANaaawJdu3OFzYGMZ3iGpa3qMlq9ZH0VZTgrCtw/ngdYkEIIpSbP1bWQAdFdX9vocBdkH2qVjVmuMu3gI5rjs814EUdrCZgWlPaxZZ3RiLFUtr+ud0PXwp2dnQSNXgePt6AZpBj6UMJ7VQkzN4utVeaSW1Dhn/kblGrKeMvNGnzwX4zuEDarYz1KdPtR60Gul0Gued+515SJXhCsl+Tx/3kY/UDvicPll9mfu50t3tvQ/thZpJYgeuwdSKNJ6tCD98MCgoxLDaPxbwqqwPWaWiAAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-drivers@freebsd.org Subject: Re: hdaps (accelerator) driver for thinkpads X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Apr 2008 21:16:26 -0000 hi tofig, On Sun, 6 Apr 2008 14:10:20 +0500 "Tofig Suleymanov" wrote: > sorry for being so late. i'm sorry too. have been on vacation for the last weeks and had no time to check my email. > Looking at accelraw_dev.c around line 128 I've noticed that you do not > initialize the mutex before acquiring a lock with mtx_lock. I've made > a simple patch which adds a mtx_init before locking operations. Please > download it to your accel source root directory from here > http://www.freebsd.az/other/accel.patch and execute: patch < > accel.patch thank you very much for your help! your patch showed me where the error really was. i forgot to init the mutex in the accel_attach() function, because the old lock was destroyed after exiting accel_probe()... now all devices seem to work fine :) > I can confirm that accelgraph display tool and X mouse interface are > working. X mouse movement seem to be too sensitive though. yes you are right, i adjusted the default sensitivity and the mouse is very smoothy now ;) i also plan to have a sysctl for this or is there any default location for general mouse device sensitivity? now here you can find the current snapshot location: http://www.nupfel.de/data/hdaps.tar.gz there is also a svn repository, but this is not public at the moment (will be soon): https://svn.nupfel.de/x60t/hdaps my next step will be to improve the shock detection algorithm and to implement instant hard drive head parking... let's see what i get done, every help is welcome :) happy testing! -- ciao, lev From owner-freebsd-drivers@FreeBSD.ORG Fri Apr 18 03:18:42 2008 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BC2BD106564A for ; Fri, 18 Apr 2008 03:18:42 +0000 (UTC) (envelope-from sogabe@iij.ad.jp) Received: from otm-mgo00.iij.ad.jp (otm-mgo00.iij.ad.jp [210.138.20.174]) by mx1.freebsd.org (Postfix) with ESMTP id 4AD1C8FC1B for ; Fri, 18 Apr 2008 03:18:42 +0000 (UTC) (envelope-from sogabe@iij.ad.jp) DKIM-Signature: v=1;a=rsa-sha256;c=relaxed/simple;d=iij.ad.jp;h=Message-ID: Date:From:MIME-Version:To:Subject:References:In-Reply-To:Content-Type: Content-Transfer-Encoding;i=sogabe@iij.ad.jp;s=omgo0;t=1208488721;x= 1209698321; bh=mVUF0L19zFR5cOgA/dmccw8HTizvtwd0TVvlHHF8Z1o=; b=Jk1wu0D6DOcTV6GV SgkGyU/1+/n50o/tkXRkkXm8jQVv8ihH70CjiyATKfzd8ir4ECj9ZMV6gcHdX2zFo+JGqGNsK1XYd opNRIipsre6YSOv6XJ84NUUqH9uUsoHLMyfrPMQY9iBGqiveiNhH8u+oZeSPTCzftZB7gTogJBjnM c=; Received: OTM-MO(otm-mgo00) id m3I3IfX5078054; Fri, 18 Apr 2008 12:18:41 +0900 (JST) Received: OTM-MIX(otm-mix01) id m3I3IeQD075295; Fri, 18 Apr 2008 12:18:40 +0900 (JST) Received: from [192.168.184.115] ([192.168.184.115]) by rsmtp.iij.ad.jp (OTM-MR/rsmtp01) id m3I3Ie9J073138 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Fri, 18 Apr 2008 12:18:40 +0900 (JST) Message-ID: <4808138D.2040408@iij.ad.jp> Date: Fri, 18 Apr 2008 12:20:45 +0900 From: Sogabe Takashi User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: freebsd-drivers@freebsd.org References: <4805BBA7.60806@iij.ad.jp> <20080416163938.GM95731@elvis.mu.org> <20080416.132024.1649777798.imp@bsdimp.com> In-Reply-To: <20080416.132024.1649777798.imp@bsdimp.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: question: workaround for AX88190 (dev/ed/if_ed.c) X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Apr 2008 03:18:42 -0000 I see buggy cards must be around here.. I think any other AX series(ax88796, etc.) may have similler bugs, but I don't know how to confirm them. Thanks, -- sogabe@iij.ad.jp > In message: <20080416163938.GM95731@elvis.mu.org> > Alfred Perlstein writes: > : I think the driver developer found the card buggy and wanted > : to give it a longer try to clear the status bits, but if it > : just flat out refuses to clear status, then it just aborts. > > Some versions of silicon seem to be better than others at this as > well. Some cards need it, but most don't. > > Warner > > > : * Sogabe Takashi [080416 02:00] wrote: > : > Hi all, > : > > : > Does anyone know what kind of problems about following > : > workaround-code? > : > > : > I read asix datasheets, but corresponding problem is not > : > described. > : > > : > (in sys/dev/ed/if_ed.c) > : > /* > : > * Ethernet interface interrupt processor > : > */ > : > void > : > edintr(void *arg) > : > { > : > ... > : > /* > : > * XXX workaround for AX88190 > : > * We limit this to 5000 iterations. At 1us per inb/outb, > : > * this translates to about 15ms, which should be plenty > : > * of time, and also gives protection in the card eject > : > * case. > : > */ > : > if (sc->chip_type == ED_CHIP_TYPE_AX88190) { > : > count = 5000; /* 15ms */ > : > while (count-- && (ed_nic_inb(sc, ED_P0_ISR) & isr)) { > : > ed_nic_outb(sc, ED_P0_ISR,0); > : > ed_nic_outb(sc, ED_P0_ISR,isr); > : > } > : > if (count == 0) > : > break; > : > } > : > ... > : > } > : > > : > -- > : > sogabe@iij.ad.jp From owner-freebsd-drivers@FreeBSD.ORG Fri Apr 18 03:56:50 2008 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E7801065675 for ; Fri, 18 Apr 2008 03:56:50 +0000 (UTC) (envelope-from olihc17@yahoo.com) Received: from web53812.mail.re2.yahoo.com (web53812.mail.re2.yahoo.com [206.190.39.55]) by mx1.freebsd.org (Postfix) with SMTP id 164768FC1F for ; Fri, 18 Apr 2008 03:56:49 +0000 (UTC) (envelope-from olihc17@yahoo.com) Received: (qmail 30206 invoked by uid 60001); 18 Apr 2008 03:56:49 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID; b=D8M9q9A30hDCVaUeTYa2xwt9xKdKpe9rFg6RgCG3mTbnIGUgUzjNgS7f3jzioO9QJ10gNvcCB7ghPcRzMS9c/fkswV0WtACXCHPPvhfSTgthw7Xwj0QKaGvE0+iMr9TJDueNhueV3FiHdeawakspHoyaMBMuIjeHbN+mY6NLWi4=; X-YMail-OSG: fe3_yqAVM1lF8uq9C75uNpTAe6b6yFjD.dvfFvcOszNg5gsKJVTkquVqTC_hF9sgzT9LSyHFMZ.k0Y.cU5dxPKM7MzI9tjHv4nC83vSytsvOKT9wQbc2Ail0jwo- Received: from [202.73.172.6] by web53812.mail.re2.yahoo.com via HTTP; Thu, 17 Apr 2008 20:56:49 PDT X-Mailer: YahooMailRC/902.40 YahooMailWebService/0.7.185 Date: Thu, 17 Apr 2008 20:56:49 -0700 (PDT) From: chilo To: freebsd-hardware@freebsd.org, freebsd-drivers@freebsd.org MIME-Version: 1.0 Message-ID: <367917.29366.qm@web53812.mail.re2.yahoo.com> Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Freebsd 7 amd64 need clarification on SAS controller X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Apr 2008 03:56:50 -0000 We currently have a box that have this specs for freebsd 7 64 bit: Dual Core Intel XEON processor 5000 1333MHZ Intel 5000 chipset family 1 GB min fully buffered memory 4 x 146GB SAS drives Lan Intel 82563EB dual port controller LSI 1068 SAS Contoller I have a LSI 1068 SAS controller but on my dmesg.boot this is the output: mfi0: mem 0xb8b00000-0xb8b0ffff,0xb8900000-0xb891ffff irq 18 at device 14.on pci4 mfi0: Megaraid SAS driver Ver 2.00 I've checked the freebsd site and the LSI 106x family should have mpt drivers but my dmesg.boot says mfi. Also there is this hptrr: HPT RocketRAID controller driver v1.1 (Feb 24 2008 10:34:18) hptrr: no controller detected. Since I do not have a HPT RocketRAID controller why does it still load in on the boot up? is there an explanation for this? Will I have any problems if I push freebsd 7 64 bit on this box? Any advice would be appreciated. Thanks. Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ From owner-freebsd-drivers@FreeBSD.ORG Fri Apr 18 04:53:03 2008 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 12B7D106566C; Fri, 18 Apr 2008 04:53:03 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from parsely.rain.com (parsely.rain.com [199.26.172.196]) by mx1.freebsd.org (Postfix) with ESMTP id 180318FC2A; Fri, 18 Apr 2008 04:53:00 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from sopwith.solgatos.com (uucp@localhost) by parsely.rain.com (8.11.4/8.11.4) with UUCP id m3I4qMJ57423; Thu, 17 Apr 2008 21:52:22 -0700 (PDT) (envelope-from freebsd@sopwith.solgatos.com) Received: from localhost by sopwith.solgatos.com (8.8.8/6.24) id EAA11612; Fri, 18 Apr 2008 04:48:59 GMT Message-Id: <200804180448.EAA11612@sopwith.solgatos.com> To: chilo In-reply-to: Your message of "Thu, 17 Apr 2008 20:56:49 PDT." <367917.29366.qm@web53812.mail.re2.yahoo.com> Date: Thu, 17 Apr 2008 21:48:59 +0100 From: Dieter Cc: freebsd-drivers@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Freebsd 7 amd64 need clarification on SAS controller X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Apr 2008 04:53:03 -0000 > Also there is this > > hptrr: HPT RocketRAID controller driver v1.1 (Feb 24 2008 > 10:34:18) > hptrr: no controller detected. > > Since I do not have a HPT RocketRAID controller why does it still load in on the boot up? > > is there an explanation for this? Comment out the line device hptrr # Highpoint RocketRAID 17xx, 22xx, 23xx, 25xx in your kernel config file, build and install a new kernel, and the confusing message should go away. From owner-freebsd-drivers@FreeBSD.ORG Fri Apr 18 19:05:12 2008 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C26F11065673 for ; Fri, 18 Apr 2008 19:05:12 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id A5C2A8FC0C for ; Fri, 18 Apr 2008 19:05:12 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unknown [208.65.91.234]) by elvis.mu.org (Postfix) with ESMTP id 5B2FE1A4D8D; Fri, 18 Apr 2008 12:05:12 -0700 (PDT) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.14.2/8.14.2) with ESMTP id m3IJ4lQJ068097; Fri, 18 Apr 2008 15:04:59 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Rick Hunnicutt Date: Fri, 18 Apr 2008 13:15:58 -0400 User-Agent: KMail/1.9.7 References: <261819.76704.qm@web37603.mail.mud.yahoo.com> In-Reply-To: <261819.76704.qm@web37603.mail.mud.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200804181315.58659.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Fri, 18 Apr 2008 15:04:59 -0400 (EDT) X-Virus-Scanned: ClamAV 0.91.2/6831/Fri Apr 18 12:09:18 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-drivers@freebsd.org Subject: Re: New driver writer X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Apr 2008 19:05:12 -0000 On Thursday 10 April 2008 11:15:24 pm Rick Hunnicutt wrote: > Thanks John. I'm mucking my way around pretty well now. I noticed the drivers in the kernel directory have symbol files. When I build my driver, it is striped and no symbol file is gerneated. Is ther a trick to do this? Use 'make DEBUG=-g' when building the module. > Also, kgdb in the the 7.0 release doesn't seem to support add-kld... Is there an easy way to upgrade this? Just grab the kgdb sources from RELENG_7 and apply the to your 7.0 tree and build a new kgdb. It is also probably safe to just grab a kgdb binary from a newer 7.x snapshot directly. -- John Baldwin From owner-freebsd-drivers@FreeBSD.ORG Fri Apr 18 19:05:24 2008 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C1A7106566C; Fri, 18 Apr 2008 19:05:24 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id F20A78FC12; Fri, 18 Apr 2008 19:05:23 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unknown [208.65.91.234]) by elvis.mu.org (Postfix) with ESMTP id AF8D81A4D8E; Fri, 18 Apr 2008 12:05:23 -0700 (PDT) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.14.2/8.14.2) with ESMTP id m3IJ4lQO068097; Fri, 18 Apr 2008 15:05:12 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hardware@freebsd.org Date: Fri, 18 Apr 2008 14:42:51 -0400 User-Agent: KMail/1.9.7 References: <367917.29366.qm@web53812.mail.re2.yahoo.com> In-Reply-To: <367917.29366.qm@web53812.mail.re2.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200804181442.51848.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Fri, 18 Apr 2008 15:05:12 -0400 (EDT) X-Virus-Scanned: ClamAV 0.91.2/6831/Fri Apr 18 12:09:18 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-drivers@freebsd.org Subject: Re: Freebsd 7 amd64 need clarification on SAS controller X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Apr 2008 19:05:24 -0000 On Thursday 17 April 2008 11:56:49 pm chilo wrote: > We currently have a box that have this specs for freebsd 7 64 bit: > > Dual Core Intel XEON processor 5000 1333MHZ > Intel 5000 chipset family > 1 GB min fully buffered memory > 4 x 146GB SAS drives > Lan Intel 82563EB dual port controller > LSI 1068 SAS Contoller > > I have a LSI 1068 SAS controller but on my dmesg.boot this is the output: > > mfi0: mem 0xb8b00000-0xb8b0ffff,0xb8900000-0xb891ffff irq 18 at device 14.on pci4 > mfi0: Megaraid SAS driver Ver 2.00 > > I've checked the freebsd site and the LSI 106x family should have mpt drivers but my dmesg.boot says mfi. No, mfi is correct. Assuming you want to do RAID you will be much happier with mfi(4) (a real RAID controller with on-board cache and optional battery back-up, etc.) compared to mpt(4) anyway. -- John Baldwin