Skip to contentSkip to conversation

WARNING at net/wireless/reg.c when wireless network is disconnected

DISCUSSION Thomas Bächler 3 participants 5 messages Aug 4, 2010 – Aug 5, 2010

lore
Share & tools
lore
#0 lore raw

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
Modules linked in: hidp rfcomm sco bnep l2cap bridge stp llc microcode

cpufreq_ondemand tun btusb bluetooth uvcvideo videodev tpm_infineon v4l2_compat_ioctl32 arc4 snd_seq_dummy snd_seq_oss ecb snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_hda_codec_intelhdmi snd_mixer_oss snd_hda_codec_realtek snd_hda_intel snd_hda_codec ath9k snd_hwdep kvm_intel ath9k_common kvm snd_pcm ath9k_hw snd_timer snd tpm_tis ehci_hcd ath sdhci_pci acpi_cpufreq sdhci soundcore mac80211 freq_table mmc_core tpm cfg80211 usbcore snd_page_alloc tpm_bios e1000e mperf led_class psmouse sr_mod iTCO_wdt sg evdev toshiba_acpi toshiba_bluetooth cdrom battery ac thermal processor rfkill nls_base rtc_cmos rtc_core rtc_lib fpu aesni_intel cryptd aes_x86_64 aes_generic xts gf128mul dm_crypt dm_mod sd_mod ahci libahci libata scsi_mod ext4 mbcache jbd2 crc16 i915 drm_kms_helper drm i2c_algo_bit cfbcopyarea video backlight output cfbimgblt cfbfillrect intel_agp agpgart
Pid: 15, comm: events/0 Not tainted 2.6.35 #28

Call Trace:
 [<ffffffff8103e98b>] ? warn_slowpath_common+0x7b/0xc0
 [<ffffffffa0337760>] ? disconnect_work+0x0/0x30 [cfg80211]
 [<ffffffff8103ea85>] ? warn_slowpath_fmt+0x45/0x50
 [<ffffffffa0337760>] ? disconnect_work+0x0/0x30 [cfg80211]
 [<ffffffffa0325163>] ? regulatory_hint_disconnect+0x1b3/0x230 [cfg80211]
 [<ffffffffa0337760>] ? disconnect_work+0x0/0x30 [cfg80211]
 [<ffffffff81052df8>] ? worker_thread+0x158/0x230
 [<ffffffff810574d0>] ? autoremove_wake_function+0x0/0x30
 [<ffffffff81052ca0>] ? worker_thread+0x0/0x230
 [<ffffffff8105703e>] ? kthread+0x8e/0xa0
 [<ffffffff810032d4>] ? kernel_thread_helper+0x4/0x10
 [<ffffffff81056fb0>] ? kthread+0x0/0xa0
 [<ffffffff810032d0>] ? kernel_thread_helper+0x0/0x10
---[ end trace cbb09501d5faaa20 ]---
#1 lore raw
Quoted 6 lines · Thomas Bächler

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.

Quoted 8 lines

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

Signature · 2 lines
John W. Linville		Someday the world will need a hero, and you
[email protected]			might be all we have.  Be ready.
#2 lore raw

Am 04.08.2010 15:49, schrieb John W. Linville:

Quoted 16 lines · Thomas Bächler
Quoted 6 lines

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.

Quoted 8 lines

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

Quoted 3 lines

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:

$ dmesg | grep cfg80211:\ Calling\ CRDA
cfg80211: Calling CRDA to update world regulatory domain
cfg80211: Calling CRDA for country: de
cfg80211: Calling CRDA for country: DE
cfg80211: Calling CRDA to update world regulatory domain
cfg80211: Calling CRDA for country: DE
cfg80211: Calling CRDA to update world regulatory domain
cfg80211: Calling CRDA for country: DE
cfg80211: Calling CRDA to update world regulatory domain
cfg80211: Calling CRDA for country: DE
cfg80211: Calling CRDA to update world regulatory domain
cfg80211: Calling CRDA for country: DE
cfg80211: Calling CRDA to update world regulatory domain
cfg80211: Calling CRDA for country: DE

The AP has been playing with the regdom as well, I lost track of what has been set where in this mess.

#3 lore raw
Quoted 21 lines · Thomas Bächler

Am 04.08.2010 15:49, schrieb John W. Linville:

Quoted 16 lines · Thomas Bächler
Quoted 6 lines

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.

Quoted 8 lines

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

Quoted 3 lines

Perhaps you need to set the regdomain as "DE" rather than "de"?

John

Quoted 7 lines

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.

Quoted 15 lines
$ dmesg | grep cfg80211:\ Calling\ CRDA
cfg80211: Calling CRDA to update world regulatory domain
cfg80211: Calling CRDA for country: de
cfg80211: Calling CRDA for country: DE
cfg80211: Calling CRDA to update world regulatory domain
cfg80211: Calling CRDA for country: DE
cfg80211: Calling CRDA to update world regulatory domain
cfg80211: Calling CRDA for country: DE
cfg80211: Calling CRDA to update world regulatory domain
cfg80211: Calling CRDA for country: DE
cfg80211: Calling CRDA to update world regulatory domain
cfg80211: Calling CRDA for country: DE
cfg80211: Calling CRDA to update world regulatory domain
cfg80211: Calling CRDA for country: DE
Quoted 2 lines

The AP has been playing with the regdom as well, I lost track of what has been set where in this mess.

The AP is probably sending a country IE that indicates "DE".

John

Signature · 2 lines
John W. Linville		Someday the world will need a hero, and you
[email protected]			might be all we have.  Be ready.
#4 lore raw
Quoted 26 lines · John W. Linville
Quoted 25 lines · Thomas Bächler

Am 04.08.2010 15:49, schrieb John W. Linville:

Quoted 16 lines · Thomas Bächler
Quoted 6 lines

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.

Quoted 8 lines

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

Quoted 3 lines

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.

Quoted 5 lines
Quoted 3 lines

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