From owner-freebsd-stable@FreeBSD.ORG Sun Jul 13 12:37:24 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4052F1065673 for ; Sun, 13 Jul 2008 12:37:24 +0000 (UTC) (envelope-from gaijin.k@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.31]) by mx1.freebsd.org (Postfix) with ESMTP id E69BA8FC0A for ; Sun, 13 Jul 2008 12:37:23 +0000 (UTC) (envelope-from gaijin.k@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so1893001ywe.13 for ; Sun, 13 Jul 2008 05:37:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.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:content-transfer-encoding; bh=znogMzf6HOswGs7l90mJgesoh1NxZQgMB0M9i3R0pSs=; b=mlmBZ63Fo+RUMSyEcIGbr3Ce44zu2iEwir051mcTTHFdXx4GhicGYq3i1MKEp7RLzL eN2x/waDkPvJ9vn+X9bgAuUPx7TW2Pj3nGfJyg/tRYS2pmQuDttSRWM97zMVTlr4B8DX r4C8/V6iYq6IysZu8KmPKOC5FT13Y5ofLQtjA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=JiMW1WjRb3UrbXwZNLOuJlhWzvRFl/972ILY1G+4gg+wLwKylZdSoA0YPNLCq2DvE9 kJnyIk4N8m7Kb5jF16U2vVxwG13QmaKgNpQ/V3Re4bUaUZIeQHKxnZOMW97ioxYhPeKi tbsYu6YlR/6PFpBASESnRjwveoCVXPuUNzCwg= Received: by 10.150.137.9 with SMTP id k9mr3730993ybd.203.1215952643229; Sun, 13 Jul 2008 05:37:23 -0700 (PDT) Received: from ?10.0.3.231? ( [70.111.175.14]) by mx.google.com with ESMTPS id 34sm4300222yxm.0.2008.07.13.05.37.21 (version=SSLv3 cipher=RC4-MD5); Sun, 13 Jul 2008 05:37:22 -0700 (PDT) From: "Alexandre \"Sunny\" Kovalenko" To: Martin In-Reply-To: <20080713112117.7d3ff6c6@web.de> References: <20080713112117.7d3ff6c6@web.de> Content-Type: text/plain; charset=utf-8 Date: Sun, 13 Jul 2008 08:37:14 -0400 Message-Id: <1215952634.1731.3.camel@RabbitsDen> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit Cc: stable@freebsd.org, Sam Leffler Subject: Re: Hard(?) lock when reassociating ath with wpa_supplicant on RELENG_7 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: Sun, 13 Jul 2008 12:37:24 -0000 On Sun, 2008-07-13 at 11:21 +0200, Martin wrote: > Hi Sam, > > do you know if there is anything done about cbb(4)? I have many > wireless adapters with ath(4), but only the one based on PCMCIA is > making problems on FreeBSD. > > I cannot boot my notebook with the device inserted into the port, or it > will render the system unusable (100% load on cbb(4)). > > And all I can see is the following: > Jul 12 14:58:39 link kernel: ath0: ath_chan_set: unable to reset channel 1 (2412 Mhz, flags 0x480 hal flags 0xc0), hal status 0 > Jul 12 14:58:40 link kernel: ath0: ath_chan_set: unable to reset channel 6 (2437 Mhz, flags 0x480 hal flags 0xc0), hal status 3233070656 > Jul 12 14:58:41 link kernel: ath0: ath_chan_set: unable to reset channel 7 (2442 Mhz, flags 0x480 hal flags 0xc0), hal status 3233070656 > Jul 12 14:58:42 link kernel: ath0: ath_chan_set: unable to reset channel 2 (2417 Mhz, flags 0x480 hal flags 0xc0), hal status 0 > Jul 12 14:58:43 link kernel: ath0: ath_chan_set: unable to reset channel 3 (2422 Mhz, flags 0x480 hal flags 0xc0), hal status 0 > Jul 12 14:58:44 link kernel: ath0: ath_chan_set: unable to reset channel 4 (2427 Mhz, flags 0x480 hal flags 0xc0), hal status 3233070656 > Jul 12 14:58:45 link kernel: ath0: ath_chan_set: unable to reset channel 5 (2432 Mhz, flags 0x480 hal flags 0xc0), hal status 0 > Jul 12 14:58:45 link kernel: ath0: ath_chan_set: unable to reset channel 8 (2447 Mhz, flags 0x480 hal flags 0xc0), hal status 0 > Jul 12 14:58:46 link kernel: ath0: ath_chan_set: unable to reset channel 9 (2452 Mhz, flags 0x480 hal flags 0xc0), hal status 0 > Jul 12 14:58:47 link kernel: ath0: ath_chan_set: unable to reset channel 10 (2457 Mhz, flags 0x480 hal flags 0xc0), hal status 0 > Jul 12 14:58:52 link kernel: ath0: device timeout > Jul 12 14:58:52 link kernel: ath0: ath_reset: unable to reset hardware; hal status 3231908395 > Jul 12 14:58:58 link kernel: ath0: ath_chan_set: unable to reset channel 1 (2412 Mhz, flags 0x480 hal flags 0xc0), hal status 3233070656 > Jul 12 14:58:59 link kernel: ath0: ath_chan_set: unable to reset channel 6 (2437 Mhz, flags 0x480 hal flags 0xc0), hal status 0 > Jul 12 14:59:00 link kernel: ath0: ath_chan_set: unable to reset channel 7 (2442 Mhz, flags 0x480 hal flags 0xc0), hal status 0 > Jul 12 14:59:01 link kernel: ath0: ath_chan_set: unable to reset channel 2 (2417 Mhz, flags 0x480 hal flags 0xc0), hal status 0 > Jul 12 14:59:01 link kernel: ath0: ath_chan_set: unable to reset channel 3 (2422 Mhz, flags 0x480 hal flags 0xc0), hal status 3289233408 > Jul 12 14:59:02 link kernel: ath0: ath_chan_set: unable to reset channel 4 (2427 Mhz, flags 0x480 hal flags 0xc0), hal status 0 > Jul 12 14:59:03 link kernel: ath0: ath_chan_set: unable to reset channel 5 (2432 Mhz, flags 0x480 hal flags 0xc0), hal status 0 > Jul 12 14:59:04 link kernel: ath0: ath_chan_set: unable to reset channel 8 (2447 Mhz, flags 0x480 hal flags 0xc0), hal status 0 > Jul 12 14:59:05 link kernel: ath0: ath_chan_set: unable to reset channel 9 (2452 Mhz, flags 0x480 hal flags 0xc0), hal status 0 > Jul 12 14:59:06 link kernel: ath0: ath_chan_set: unable to reset channel 10 (2457 Mhz, flags 0x480 hal flags 0xc0), hal status 0 > Jul 12 14:59:10 link kernel: ath0: device timeout > Jul 12 14:59:10 link kernel: ath0: ath_reset: unable to reset hardware; hal status 3231908395 > Jul 12 14:59:11 link kernel: ath0: ath_chan_set: unable to reset channel 1 (2412 Mhz, flags 0x480 hal flags 0xc0), hal status 3233070656 > Jul 12 14:59:12 link kernel: ath0: ath_chan_set: unable to reset channel 6 (2437 Mhz, flags 0x480 hal flags 0xc0), hal status 0 > Jul 12 14:59:13 link kernel: ath0: ath_chan_set: unable to reset channel 7 (2442 Mhz, flags 0x480 hal flags 0xc0), hal status 3233070656 > Jul 12 14:59:14 link kernel: ath0: ath_chan_set: unable to reset channel 2 (2417 Mhz, flags 0x480 hal flags 0xc0), hal status 0 > Jul 12 14:59:15 link kernel: ath0: ath_chan_set: unable to reset channel 3 (2422 Mhz, flags 0x480 hal flags 0xc0), hal status 0 > Jul 12 14:59:16 link kernel: ath0: unable to reset hardware; hal status 3868687084 > Jul 12 14:59:16 link kernel: ath0: ath_chan_set: unable to reset channel 4 (2427 Mhz, flags 0x480 hal flags 0xc0), hal status 0 > Jul 12 14:59:17 link kernel: ath0: ath_chan_set: unable to reset channel 11 (2462 Mhz, flags 0x480 hal flags 0xc0), hal status 3828804624 > Jul 12 14:59:22 link kernel: ath0: unable to reset hardware; hal status 3868539700 > Jul 12 14:59:32 link kernel: ath0: unable to reset hardware; hal status 3868539700 > Jul 12 14:59:42 link kernel: ath0: unable to reset hardware; hal status 3868539700 > Jul 12 15:00:22 link last message repeated 4 times > Jul 12 15:00:32 link kernel: ath0: unable to reset hardware; hal status 3868539700 > Jul 12 15:00:42 link kernel: ath0: unable to reset hardware; hal status 3868539700 > Jul 12 15:00:52 link kernel: ath0: unable to reset hardware; hal status 3868539700 > > > wpa_supplicant is trying to access the card and switching channels, I > suppose. > > A workaround that I'm using all the time is: > 1) boot the notebook without the PCMCIA card > 2) after gdm appears, insert the card > > Also see: > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/120376 > > In this PR I also described that you can panic the system, > while trying to fix the situation by reinserting the card. > But I found out, that you can always panic the system when > ejecting the card and wpa_supplicant is running. > You can panic the box by unloading if_ath.ko while wpa_supplicant is running on any form factor, so this one is not specific to the removable devices. -- Alexandre "Sunny" Kovalenko (Олександр Коваленко)