From owner-freebsd-hardware@FreeBSD.ORG Sun Nov 1 16:02:59 2009 Return-Path: Delivered-To: hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7E6DD106568B; Sun, 1 Nov 2009 16:02:59 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id D72848FC21; Sun, 1 Nov 2009 16:02:58 +0000 (UTC) Received: by bwz5 with SMTP id 5so5494763bwz.3 for ; Sun, 01 Nov 2009 08:02:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=WjwLp+2Sqk1Am7y4GLTLR0tqCONZ9iF8PcPRNBv5+HI=; b=TmFHdSmLOLpEcyq4vjSMuMosP74T1YiA7zMwcxFpBDWJNIyG9yE2Ig65oFVfijdUZO vxchcDZ4BZH9zIzGfi5GDzOPfD4KcmUe6kfPSUbWuOPPzCJ/2xaUsPdJ8i9YKx+JBLG6 r8agJhc5LMGwbiiJuJuBek2+mVOhwpMby1rX0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=nKYiGGZJspf4869jOzx9s8sNxUn3wU3+1V10XYLwgb73NJr9bJ5EHI9bH8m/7TXL/2 hIq8wh3tZWa1jVo595KvZfTVtb3yDrOdi9aSTfsfc/v89xxTfeRCvCMA+JOYzq+o/TA0 Wf5LCq8Iwe3HMi2i9rmXBeR5Vvo06d6UnCrvY= MIME-Version: 1.0 Received: by 10.102.13.21 with SMTP id 21mr1648642mum.100.1257091377604; Sun, 01 Nov 2009 08:02:57 -0800 (PST) In-Reply-To: <3a142e750910310916labe85e5ke804386a834c49c8@mail.gmail.com> References: <9bbcef730910310830s43237918g1489beb1fe9fae9a@mail.gmail.com> <3a142e750910310916labe85e5ke804386a834c49c8@mail.gmail.com> Date: Sun, 1 Nov 2009 17:02:57 +0100 Message-ID: <3a142e750911010802l1a4183edh9d92eabdc21ab661@mail.gmail.com> From: Paul B Mahol To: Ivan Voras Content-Type: text/plain; charset=ISO-8859-1 Cc: stable@freebsd.org, hardware@freebsd.org Subject: Re: hostapd "deauthenticated due to local deauth request" X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Nov 2009 16:02:59 -0000 On 10/31/09, Paul B Mahol wrote: > On 10/31/09, Ivan Voras wrote: >> I'm trying to setup an AP with a run0 interface on latest 8-STABLE but >> apparently 802.11 association fails: >> >> Oct 31 16:21:30 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE >> 802.11: associated >> Oct 31 16:21:33 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE >> 802.11: deauthenticated due to local deauth request >> Oct 31 16:21:33 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE >> 802.11: deassociated >> Oct 31 16:21:35 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE >> 802.11: associated >> Oct 31 16:21:38 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE >> 802.11: deauthenticated due to local deauth request >> Oct 31 16:21:38 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE >> 802.11: deassociated >> >> etc. Apparently the client never comes to the phase to receive DHCP >> address. >> >> The client in this case is WinXP and the setup did work with 7-STABLE, >> though with a bug in the rum driver which caused regular kernel panics >> on the AP. >> > > I tried same one with rum(4) as AP and ndis(4) as client on same > machine(some version of 8.0 - CURRENT). ndis client (configured via > wpa_supplicant) > would keep auth and deauth all the time. > I came to conclusion that rum is broken. But I think I remmember that > bwi(4) (as a client) > did not have such problem ... (I will test again to see) Well, I tried again and I got similar output like yours if I use wrong password. And with correct password client reauth all the time, maybe I need to setup ndis_events(8) .... From owner-freebsd-hardware@FreeBSD.ORG Thu Nov 5 15:35:40 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6392A1065676 for ; Thu, 5 Nov 2009 15:35:40 +0000 (UTC) (envelope-from cowens@greatbaysoftware.com) Received: from portcityhosting.com (bayringfw.portcityweb.com [64.140.243.92]) by mx1.freebsd.org (Postfix) with ESMTP id 155CA8FC23 for ; Thu, 5 Nov 2009 15:35:39 +0000 (UTC) Received: from [127.0.0.1] ([173.14.128.81]) by portcityhosting.com with MailEnable ESMTP; Thu, 5 Nov 2009 09:55:38 -0500 X-WatchGuard-Mail-Exception: Allow Message-ID: <4AF2E837.2080705@greatbaysoftware.com> Date: Thu, 05 Nov 2009 09:59:03 -0500 From: Charles Owens MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Content-Type: multipart/mixed; boundary="------------090406090007070503090905" X-WatchGuard-AntiVirus: part scanned. clean action=allow X-ME-Bayesian: 0.000000 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: kern/139654: CD-boot failure on newer IBM server X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2009 15:35:40 -0000 This is a multi-part message in MIME format. --------------090406090007070503090905 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-WatchGuard-AntiVirus: part scanned. clean action=allow Hello, As detailed in the PR, we are unable to get FreeBSD (7.1) to boot with an IBM System x3250 M2 server. I'm not sure what steps to take next, and would greatly appreciate assistance. We've also submitted kern/139653 which deal with different hardware (HP) and is not quite as critical (very poor performance, as opposed to complete failure)... any suggestions with this also welcome. PR links: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/139654 http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/139653 Thanks very much, Charles -- **Charles Owens** *Great Bay Software**|** *www.GreatBaySoftware.com**** --------------090406090007070503090905-- From owner-freebsd-hardware@FreeBSD.ORG Sat Nov 7 08:47:02 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7CC08106566B for ; Sat, 7 Nov 2009 08:47:02 +0000 (UTC) (envelope-from simon@optinet.com) Received: from cobra.acceleratedweb.net (cobra-gw.acceleratedweb.net [207.99.79.37]) by mx1.freebsd.org (Postfix) with SMTP id 145C88FC14 for ; Sat, 7 Nov 2009 08:47:01 +0000 (UTC) Received: (qmail 73211 invoked by uid 110); 7 Nov 2009 08:20:20 -0000 Received: from unknown (HELO desktop1) (simon@optinet.com@69.113.73.210) by cobra.acceleratedweb.net with SMTP; 7 Nov 2009 08:20:20 -0000 From: "Simon" To: "freebsd-hardware@freebsd.org" Date: Sat, 07 Nov 2009 03:20:23 -0400 Priority: Normal X-Mailer: PMMail 2000 Professional (2.20.2717) For Windows 2000 (5.1.2600;3) In-Reply-To: <49D5FFA7.3090408@collaborativefusion.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <20091107084702.7CC08106566B@hub.freebsd.org> Subject: Re: [Fwd: Re: amr driver issues in 7.1-RELEASE] X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Nov 2009 08:47:02 -0000 On Fri, 03 Apr 2009 08:23:03 -0400, Steve Polyack wrote: >> It appears this has not been fixed in 7.1-p4 I've been waiting to upgrade due >> to this but was forced after latest root exploit was found recently. Upon MySQL >> upgrade, running mysql_upgrade which upgrades and checks all the tables, >> I got 2 of these messages while a large ,1.4G, mysql table was being dumped >> to array so it could be repaired. I don't know what to make of this error and >> are not sure if it could be safely ignored. >> >> amr0: Too many retries on command 0xc71ceaa8. Controller is likely dead >> amr0: Too many retries on command 0xc71cdce8. Controller is likely dead >> >> Thank you in advance! >> >> -Simon >> >> >We still see these as well. I've also been ensured that these are >harmless messages. As far as I can tell from my own investigation, the >behavior has not changed other than the addition of tracking of how many >retries there have been when submitting commands to the controller. >When the controller mailbox is "busy", the driver must wait before >submitting a command. If the driver has to retry 1000 times twice >within one second, it logs the messages you are seeing. This logging >was simply not present before 7.1. >As I've said and been told, the message is harmless if your machine is >still responding. I just wanted to follow up and let the list know my instance of this error was being caused by faulty drives. If you get this message, I would be concerned. Backup your data and run every single drive connected to this controller via manufacturer's diagnostic full test. A single faulty drive in RAID setup can cause mediocre performance and this error to show up. -Simon