Problem connecting to wireless on ubuntu/mac airport extreme

Vijay Boyapati vijayb at gmail.com
Tue Nov 22 17:48:00 UTC 2011


Hi Avi, I tried the "quick temporary fix" suggested on the page (doing the
modprobe), but that just gave me an error and turned wireless off
completely, so I was reluctant to doing anything permanent to the kernel.
Apologies the dmesg was cutoff. There's a 40k limit to message size, so I
had to keep cutting until the message got through. Here's the end of the
dmesg:

[  791.272507] usbhid: USB HID core driver
[  795.383248] iwlagn 0000:0d:00.0: Aggregation not enabled for tid 1
because load = 0
[  866.979619] usb 3-4: USB disconnect, address 2
[  915.015730] iwlagn 0000:0d:00.0: Stopping AGG while state not ON or starting
[  915.240655] cfg80211: All devices are disconnected, going to
restore regulatory settings
[  915.240669] cfg80211: Restoring regulatory settings
[  915.240681] cfg80211: Calling CRDA to update world regulatory domain
[  915.248540] cfg80211: Ignoring regulatory request Set by core since
the driver uses its own custom regulatory domain
[  915.248551] cfg80211: World regulatory domain updated:
[  915.248555] cfg80211:     (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[  915.248562] cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz),
(300 mBi, 2000 mBm)
[  915.248568] cfg80211:     (2457000 KHz - 2482000 KHz @ 20000 KHz),
(300 mBi, 2000 mBm)
[  915.248573] cfg80211:     (2474000 KHz - 2494000 KHz @ 20000 KHz),
(300 mBi, 2000 mBm)
[  915.248578] cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz),
(300 mBi, 2000 mBm)
[  915.248583] cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz),
(300 mBi, 2000 mBm)
[  915.525607] wlan0: authenticate with 00:1b:63:2b:8d:ed (try 1)
[  915.527874] wlan0: authenticated
[  915.527963] wlan0: associate with 00:1b:63:2b:8d:ed (try 1)
[  915.531381] wlan0: RX AssocResp from 00:1b:63:2b:8d:ed (capab=0x431
status=0 aid=3)
[  915.531390] wlan0: associated
[  915.534292] cfg80211: Calling CRDA for country: US
[  915.542213] cfg80211: Updating information on frequency 2412 MHz
for a 20 MHz width channel with regulatory rule:
[  915.542223] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (300 mBi, 2700 mBm)
[  915.542229] cfg80211: Updating information on frequency 2417 MHz
for a 20 MHz width channel with regulatory rule:
[  915.542235] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (300 mBi, 2700 mBm)
[  915.542240] cfg80211: Updating information on frequency 2422 MHz
for a 20 MHz width channel with regulatory rule:
[  915.542245] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (300 mBi, 2700 mBm)
[  915.542250] cfg80211: Updating information on frequency 2427 MHz
for a 20 MHz width channel with regulatory rule:
[  915.542256] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (300 mBi, 2700 mBm)
[  915.542260] cfg80211: Updating information on frequency 2432 MHz
for a 20 MHz width channel with regulatory rule:
[  915.542266] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (300 mBi, 2700 mBm)
[  915.542270] cfg80211: Updating information on frequency 2437 MHz
for a 20 MHz width channel with regulatory rule:
[  915.542276] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (300 mBi, 2700 mBm)
[  915.542280] cfg80211: Updating information on frequency 2442 MHz
for a 20 MHz width channel with regulatory rule:
[  915.542286] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (300 mBi, 2700 mBm)
[  915.542290] cfg80211: Updating information on frequency 2447 MHz
for a 20 MHz width channel with regulatory rule:
[  915.542296] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (300 mBi, 2700 mBm)
[  915.542300] cfg80211: Updating information on frequency 2452 MHz
for a 20 MHz width channel with regulatory rule:
[  915.542306] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (300 mBi, 2700 mBm)
[  915.542310] cfg80211: Updating information on frequency 2457 MHz
for a 20 MHz width channel with regulatory rule:
[  915.542316] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (300 mBi, 2700 mBm)
[  915.542320] cfg80211: Updating information on frequency 2462 MHz
for a 20 MHz width channel with regulatory rule:
[  915.542326] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (300 mBi, 2700 mBm)
[  915.542330] cfg80211: Disabling freq 2467 MHz
[  915.542334] cfg80211: Disabling freq 2472 MHz
[  915.542340] cfg80211: Regulatory domain changed to country: US
[  915.542343] cfg80211:     (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[  915.542350] cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz),
(300 mBi, 2700 mBm)
[  915.542355] cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz),
(300 mBi, 1700 mBm)
[  915.542360] cfg80211:     (5250000 KHz - 5330000 KHz @ 40000 KHz),
(300 mBi, 2000 mBm)
[  915.542365] cfg80211:     (5490000 KHz - 5600000 KHz @ 40000 KHz),
(300 mBi, 2000 mBm)
[  915.542371] cfg80211:     (5650000 KHz - 5710000 KHz @ 40000 KHz),
(300 mBi, 2000 mBm)
[  915.542376] cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz),
(300 mBi, 3000 mBm)
[  970.832858] ------------[ cut here ]------------
[  970.832882] WARNING: at
/build/buildd/linux-2.6.38/net/sched/sch_generic.c:256
dev_watchdog+0x2a0/0x2b0()
[  970.832887] Hardware name: HP Pavilion dv6 Notebook PC
[  970.832892] NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
[  970.832896] Modules linked in: usbhid hid aesni_intel cryptd
aes_x86_64 aes_generic parport_pc ppdev snd_hda_codec_hdmi
snd_hda_codec_idt joydev binfmt_misc arc4 snd_hda_intel snd_hda_codec
iwlagn snd_hwdep i915 snd_pcm snd_seq_midi snd_rawmidi iwlcore
snd_seq_midi_event mac80211 snd_seq uvcvideo hp_wmi sparse_keymap
videodev snd_timer psmouse drm_kms_helper v4l2_compat_ioctl32 fglrx(P)
cfg80211 drm snd_seq_device snd serio_raw rts_pstor(C) i2c_algo_bit
soundcore snd_page_alloc video hp_accel lis3lv02d input_polldev lp
parport ahci xhci_hcd r8169 libahci
[  970.832980] Pid: 0, comm: swapper Tainted: P         C
2.6.38-8-generic #42-Ubuntu
[  970.832985] Call Trace:
[  970.832989]  <IRQ>  [<ffffffff81065cef>] ? warn_slowpath_common+0x7f/0xc0
[  970.833009]  [<ffffffff81065de6>] ? warn_slowpath_fmt+0x46/0x50
[  970.833019]  [<ffffffff814ef450>] ? dev_watchdog+0x2a0/0x2b0
[  970.833031]  [<ffffffff81013a85>] ? native_sched_clock+0x15/0x70
[  970.833040]  [<ffffffff81013ae9>] ? sched_clock+0x9/0x10
[  970.833048]  [<ffffffff8108ea9d>] ? sched_clock_cpu+0xbd/0x110
[  970.833056]  [<ffffffff814ef1b0>] ? dev_watchdog+0x0/0x2b0
[  970.833067]  [<ffffffff81074964>] ? call_timer_fn+0x44/0x130
[  970.833075]  [<ffffffff814ef1b0>] ? dev_watchdog+0x0/0x2b0
[  970.833084]  [<ffffffff81075fb4>] ? run_timer_softirq+0x134/0x280
[  970.833093]  [<ffffffff8102c85d>] ? lapic_next_event+0x1d/0x30
[  970.833100]  [<ffffffff8106d538>] ? __do_softirq+0xa8/0x1c0
[  970.833111]  [<ffffffff810983ef>] ? tick_program_event+0x1f/0x30
[  970.833118]  [<ffffffff8100cf1c>] ? call_softirq+0x1c/0x30
[  970.833125]  [<ffffffff8100ea45>] ? do_softirq+0x65/0xa0
[  970.833132]  [<ffffffff8106d755>] ? irq_exit+0x85/0x90
[  970.833142]  [<ffffffff815cafb0>] ? smp_apic_timer_interrupt+0x70/0x9b
[  970.833150]  [<ffffffff8100c9d3>] ? apic_timer_interrupt+0x13/0x20
[  970.833154]  <EOI>  [<ffffffff81098310>] ? tick_dev_program_event+0x40/0x100
[  970.833171]  [<ffffffff8133685a>] ? intel_idle+0xca/0x120
[  970.833178]  [<ffffffff81336839>] ? intel_idle+0xa9/0x120
[  970.833190]  [<ffffffff814a3bda>] ? cpuidle_idle_call+0xaa/0x1b0
[  970.833203]  [<ffffffff8100a266>] ? cpu_idle+0xa6/0xf0
[  970.833210]  [<ffffffff815a9205>] ? rest_init+0x75/0x80
[  970.833221]  [<ffffffff81acac8b>] ? start_kernel+0x3f5/0x400
[  970.833231]  [<ffffffff81aca388>] ? x86_64_start_reservations+0x132/0x136
[  970.833239]  [<ffffffff81aca253>] ? zap_identity_mappings+0x3e/0x41
[  970.833248]  [<ffffffff81aca458>] ? x86_64_start_kernel+0xcc/0xdb
[  970.833253] ---[ end trace 705b7b8584bf326e ]---
[  970.873044] r8169 0000:07:00.0: eth0: link up


On Tue, Nov 22, 2011 at 1:59 AM, Avi Greenbury <lists at avi.co> wrote:

> Vijay Boyapati wrote:
>
> > >> A friend who's a linux sysadmin suggested this when he saw the
> > >> output of my dmesg (which I paste below):
> > >>
> > >> "Definitely see some kernel debug stuff going on. It's probably a
> > >> bug with the N protocol. Try disabling N as indicated here:
> > >> http://www.thinkwiki.org/wiki/Intel_Centrino_Wireless-N_1000
> > >>
> > >> I think I had something like that happen once upon a time. This
> > >> will scale you back to G speeds (54Mbps), but probably will be
> > >> stable."
> > >>
>
>
> I can't see any dmesg, but in any case, did disbling N have any effect
> at all?
>
> --
> Avi
>
> --
> ubuntu-users mailing list
> ubuntu-users at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20111122/b4b06b92/attachment.html>


More information about the ubuntu-users mailing list