Return-path: Received: from mail-gw0-f46.google.com ([74.125.83.46]:34909 "EHLO mail-gw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760518Ab0HESXG convert rfc822-to-8bit (ORCPT ); Thu, 5 Aug 2010 14:23:06 -0400 MIME-Version: 1.0 In-Reply-To: <20100804145258.GC17666@tuxdriver.com> References: <4C5950B7.4000802@archlinux.org> <20100804134908.GB17666@tuxdriver.com> <4C59790C.4010809@archlinux.org> <20100804145258.GC17666@tuxdriver.com> From: "Luis R. Rodriguez" Date: Thu, 5 Aug 2010 11:22:44 -0700 Message-ID: Subject: Re: WARNING at net/wireless/reg.c when wireless network is disconnected To: "John W. Linville" Cc: =?UTF-8?Q?Thomas_B=C3=A4chler?= , linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org, Johannes Berg Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Wed, Aug 4, 2010 at 7:52 AM, John W. Linville wrote: > On Wed, Aug 04, 2010 at 04:28:28PM +0200, Thomas Bächler wrote: >> Am 04.08.2010 15:49, schrieb John W. Linville: >> > On Wed, Aug 04, 2010 at 01:36:23PM +0200, Thomas Bächler wrote: >> >> Hello, >> >> >> >> this warning has been around ever since I switched to 2.6.34, has >> >> accompanied me through the 2.6.35-rc* phase and is still there with >> >> 2.6.35. I didn't bother to report it so far, as there seems to be no harm. >> >> >> >> Whenever I disconnect/get disconnected from the wireless, I receive the >> >> below warning: >> >> >> >> ------------[ cut here ]------------ >> >> WARNING: at net/wireless/reg.c:272 >> >> regulatory_hint_disconnect+0x1b3/0x230 [cfg80211]() >> >> Hardware name: TECRA A11 >> >> Unexpected user alpha2: de >> > >> > Perhaps you need to set the regdomain as "DE" rather than "de"? >> > >> > John >> >> You are actually right. I did set it to "DE" with iw, but wpa_supplicant >> had a setting country="de". I just fixed that and will soon see if the >> problem disappears. >> >> Still, the warning shouldn't look like a bad kernel bug, but rather an >> advisory to the user to set something sane. What confuses me even more >> is that this has been set to DE afterwards: > > Perhaps we should just upcase the alpha2 value?  I'm not sure why we don't. It just needs to be implemented. Luis