Re: 2.6.38-rc7, iwlagn crash

Re: 2.6.38-rc7, iwlagn crash

[John W. Linville]

Cc'ing Wey-yi and linux-wireless...anyone else having problems with
iwlagn and IBSS?

On Fri, Mar 04, 2011 at 03:27:22AM +0000, Mathias Burén wrote:
> Hi,
> 
> (please cc as not subscribed)
> 
> I'm running Ubuntu 10.10 and 2.6.38-020638rc7-generic #201103020909
> SMP Wed Mar 2 09:11:42 UTC 2011 x86_64 GNU/Linux from
> http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.38-rc7-natty/ . The
> machine is a Lenovo T510 with this chip:
> 
> 03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6200 (rev 35)
> 
>  I was trying to setup up an adhoc wifi connection between my phone
> and the laptop when I saw this in dmesg:
> 
> 
> [111474.461347] ------------[ cut here ]------------
> [111474.461377] WARNING: at
> /home/kernel-ppa/COD/linux/drivers/net/wireless/iwlwifi/iwl-core.c:1898
> iwl_mac_change_interface+0x12e/0x130 [iwlcore]()
> [111474.461382] Hardware name: 4384BB3
> [111474.461384] Modules linked in: nf_nat_h323 nf_conntrack_h323
> nf_nat_pptp nf_conntrack_pptp nf_conntrack_proto_gre nf_nat_proto_gre
> nf_nat_tftp nf_conntrack_tftp nf_nat_sip nf_conntrack_sip nf_nat_irc
> nf_nat_ftp cdc_acm usbhid hid xt_limit xt_tcpudp ipt_LOG
> ipt_MASQUERADE xt_DSCP ipt_REJECT nf_conntrack_irc nf_conntrack_ftp
> xt_state nls_iso8859_1 nls_cp437 vfat fat binfmt_misc vboxnetadp
> vboxnetflt vboxdrv microcode parport_pc ppdev iptable_nat nf_nat
> nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_mangle
> iptable_filter ip_tables x_tables uvcvideo snd_hda_codec_hdmi
> snd_hda_codec_conexant arc4 videodev v4l2_compat_ioctl32 snd_hda_intel
> snd_hda_codec snd_hwdep joydev snd_pcm hdaps thinkpad_ec iwlagn
> snd_seq_midi iwlcore psmouse snd_rawmidi snd_seq_midi_event mac80211
> snd_seq serio_raw tpm_tis tpm lp parport thinkpad_acpi tpm_bios nvram
> snd_timer snd_seq_device cfg80211 snd intel_ips soundcore
> snd_page_alloc sha256_generic aesni_intel cryptd aes_x86_64
> aes_generic dm_crypt usb_storage uas i915 ahci drm_kms_helper
> firewire_ohci e1000e libahci sdhci_pci firewire_core drm sdhci
> crc_itu_t i2c_algo_bit video
> [111474.461481] Pid: 1317, comm: wpa_supplicant Tainted: G        W
> 2.6.38-020638rc7-generic #201103020909
> [111474.461483] Call Trace:
> [111474.461492]  [<ffffffffa02e6c7e>] ?
> iwl_mac_change_interface+0x12e/0x130 [iwlcore]
> [111474.461497]  [<ffffffffa02e6c7e>] ?
> iwl_mac_change_interface+0x12e/0x130 [iwlcore]
> [111474.461507]  [<ffffffff81065430>] ? warn_slowpath_common+0x90/0xc0
> [111474.461510]  [<ffffffff8106547a>] ? warn_slowpath_null+0x1a/0x20
> [111474.461514]  [<ffffffffa02e6c7e>] ?
> iwl_mac_change_interface+0x12e/0x130 [iwlcore]
> [111474.461527]  [<ffffffffa02869ec>] ?
> ieee80211_runtime_change_iftype+0xdc/0x180 [mac80211]
> [111474.461535]  [<ffffffffa0286b85>] ?
> ieee80211_if_change_type+0xf5/0x120 [mac80211]
> [111474.461543]  [<ffffffffa028995b>] ?
> ieee80211_change_iface+0x3b/0x130 [mac80211]
> [111474.461551]  [<ffffffffa01bf898>] ?
> cfg80211_change_iface+0xe8/0x1c0 [cfg80211]
> [111474.461558]  [<ffffffffa01d78f6>] ?
> cfg80211_wext_siwmode+0xa6/0xf0 [cfg80211]
> [111474.461564]  [<ffffffff8158a4cb>] ? ioctl_standard_call+0x6b/0xf0
> [111474.461566]  [<ffffffff8158a460>] ? ioctl_standard_call+0x0/0xf0
> [111474.461569]  [<ffffffff81589882>] ? wireless_process_ioctl+0x102/0x130
> [111474.461571]  [<ffffffff8158afe0>] ? ioctl_private_call+0x0/0xa0
> [111474.461573]  [<ffffffff8158afe0>] ? ioctl_private_call+0x0/0xa0
> [111474.461575]  [<ffffffff8158a460>] ? ioctl_standard_call+0x0/0xf0
> [111474.461578]  [<ffffffff8158991c>] ? wext_ioctl_dispatch+0x6c/0x90
> [111474.461580]  [<ffffffff81589b66>] ? wext_handle_ioctl+0x46/0x90
> [111474.461585]  [<ffffffff814ad76a>] ? sockfd_lookup_light+0x4a/0x80
> [111474.461589]  [<ffffffff814c687b>] ? dev_ioctl+0x28b/0x2a0
> [111474.461591]  [<ffffffff814ad25f>] ? sock_ioctl+0xbf/0x280
> [111474.461594]  [<ffffffff811704bd>] ? vfs_ioctl+0x1d/0x50
> [111474.461596]  [<ffffffff81170f79>] ? do_vfs_ioctl+0x69/0x1d0
> [111474.461598]  [<ffffffff81171174>] ? sys_ioctl+0x94/0xa0
> [111474.461601]  [<ffffffff8100c002>] ? system_call_fastpath+0x16/0x1b
> [111474.461603] ---[ end trace fb86611b81442165 ]---
> [111474.464580] iwlagn 0000:03:00.0: Error: Response NULL in 'REPLY_ADD_STA'
> [111474.464586] iwlagn 0000:03:00.0: Adding station ff:ff:ff:ff:ff:ff failed.
> [111474.472777] wlan0: Selected IBSS BSSID 86:9f:24:fb:b0:44 based on
> configured SSID
> [111474.542468] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111474.543552] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111474.543809] wlan0: No active IBSS STAs - trying to scan for other
> IBSS networks with same SSID (merge)
> [111475.894906] wlan0: Selected IBSS BSSID 86:9f:24:fb:b0:44 based on
> configured SSID
> [111475.959248] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111475.960079] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111475.960195] wlan0: No active IBSS STAs - trying to scan for other
> IBSS networks with same SSID (merge)
> [111477.339405] wlan0: Selected IBSS BSSID 86:9f:24:fb:b0:44 based on
> configured SSID
> [111477.386319] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111477.387069] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111477.387213] wlan0: No active IBSS STAs - trying to scan for other
> IBSS networks with same SSID (merge)
> [111478.700588] wlan0: Selected IBSS BSSID 86:9f:24:fb:b0:44 based on
> configured SSID
> [111478.753591] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111478.754417] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111478.791333] wlan0: No active IBSS STAs - trying to scan for other
> IBSS networks with same SSID (merge)
> [111480.192722] wlan0: Selected IBSS BSSID 86:9f:24:fb:b0:44 based on
> configured SSID
> [111480.249724] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111480.250545] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111480.250695] wlan0: No active IBSS STAs - trying to scan for other
> IBSS networks with same SSID (merge)
> [111481.654631] wlan0: Selected IBSS BSSID 86:9f:24:fb:b0:44 based on
> configured SSID
> [111481.696438] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111481.697237] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111481.755643] wlan0: No active IBSS STAs - trying to scan for other
> IBSS networks with same SSID (merge)
> [111483.016561] wlan0: Selected IBSS BSSID 86:9f:24:fb:b0:44 based on
> configured SSID
> [111483.073672] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111483.074542] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111483.084848] wlan0: No active IBSS STAs - trying to scan for other
> IBSS networks with same SSID (merge)
> [111484.463193] wlan0: Selected IBSS BSSID 86:9f:24:fb:b0:44 based on
> configured SSID
> [111484.510342] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111484.511087] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111484.515897] wlan0: No active IBSS STAs - trying to scan for other
> IBSS networks with same SSID (merge)
> [111485.930848] wlan0: Selected IBSS BSSID 86:9f:24:fb:b0:44 based on
> configured SSID
> [111485.987148] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111485.988018] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111485.988177] wlan0: No active IBSS STAs - trying to scan for other
> IBSS networks with same SSID (merge)
> [111487.369539] wlan0: Selected IBSS BSSID 86:9f:24:fb:b0:44 based on
> configured SSID
> [111487.423704] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111487.424479] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111487.424621] wlan0: No active IBSS STAs - trying to scan for other
> IBSS networks with same SSID (merge)
> [111488.796752] wlan0: Selected IBSS BSSID 86:9f:24:fb:b0:44 based on
> configured SSID
> [111488.850445] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111488.851280] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111488.851502] wlan0: No active IBSS STAs - trying to scan for other
> IBSS networks with same SSID (merge)
> [111490.271484] wlan0: Selected IBSS BSSID 86:9f:24:fb:b0:44 based on
> configured SSID
> [111490.307285] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111490.308059] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111490.342785] wlan0: No active IBSS STAs - trying to scan for other
> IBSS networks with same SSID (merge)
> [111491.678358] wlan0: Selected IBSS BSSID 86:9f:24:fb:b0:44 based on
> configured SSID
> [111491.744236] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111491.745065] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111491.773720] wlan0: No active IBSS STAs - trying to scan for other
> IBSS networks with same SSID (merge)
> [111493.205384] wlan0: Selected IBSS BSSID 86:9f:24:fb:b0:44 based on
> configured SSID
> [111493.250872] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111493.251799] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111493.307372] wlan0: No active IBSS STAs - trying to scan for other
> IBSS networks with same SSID (merge)
> [111494.660506] wlan0: Selected IBSS BSSID 86:9f:24:fb:b0:44 based on
> configured SSID
> [111494.717399] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111494.718199] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111496.047915] wlan0: Trigger new scan to find an IBSS to join
> [111501.880336] wlan0: Trigger new scan to find an IBSS to join
> [111504.990820] wlan0: Creating new IBSS network, BSSID be:c7:fe:1c:61:99
> [111505.034037] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111505.034743] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111506.404722] wlan0: Trigger new scan to find an IBSS to join
> [111511.567631] wlan0: Trigger new scan to find an IBSS to join
> [111514.702225] wlan0: Creating new IBSS network, BSSID 46:d5:59:b4:0b:54
> [111514.752202] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111514.753078] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111516.083283] wlan0: Trigger new scan to find an IBSS to join
> [111521.585645] wlan0: Trigger new scan to find an IBSS to join
> [111524.617640] wlan0: Creating new IBSS network, BSSID b6:ca:41:c0:3e:bd
> [111524.660101] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111524.661059] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111525.980241] wlan0: Trigger new scan to find an IBSS to join
> [111531.296978] wlan0: Trigger new scan to find an IBSS to join
> [111534.328992] wlan0: Creating new IBSS network, BSSID d6:00:8a:56:93:99
> [111534.379572] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111534.380379] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111535.712405] wlan0: Trigger new scan to find an IBSS to join
> [111541.621646] wlan0: Trigger new scan to find an IBSS to join
> [111544.755981] wlan0: Creating new IBSS network, BSSID 72:06:bb:e2:44:34
> [111544.817710] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111544.818623] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111546.186140] wlan0: Trigger new scan to find an IBSS to join
> [111551.332991] wlan0: Trigger new scan to find an IBSS to join
> [111554.467270] wlan0: Creating new IBSS network, BSSID 2a:49:ae:30:50:9e
> [111554.533525] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111554.534350] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111555.904319] wlan0: Trigger new scan to find an IBSS to join
> [111561.555433] wlan0: Trigger new scan to find an IBSS to join
> [111564.587401] wlan0: Creating new IBSS network, BSSID aa:87:38:e5:ae:c0
> [111564.661200] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111564.662171] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111565.981796] wlan0: Trigger new scan to find an IBSS to join
> [111568.625818] iwlagn 0000:03:00.0: failed to remove IBSS station
> 00:00:00:00:00:00
> [111631.701608] ADDRCONF(NETDEV_UP): wlan0: link is not ready
> [111631.829391] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
> [111631.833307] wlan0: Trigger new scan to find an IBSS to join
> [111634.393859] iwlagn 0000:03:00.0: failed to remove IBSS station
> 00:00:00:00:00:00
> [111634.705546] wlan0: Trigger new scan to find an IBSS to join
> [111639.969168] wlan0: Trigger new scan to find an IBSS to join
> [111642.456143] wlan0: no IPv6 routers present
> [111643.095083] wlan0: Creating new IBSS network, BSSID ce:27:15:66:ab:a8
> [111643.095541] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111643.096508] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111644.424790] wlan0: Trigger new scan to find an IBSS to join
> [111649.672932] wlan0: Trigger new scan to find an IBSS to join
> [111652.806533] wlan0: Creating new IBSS network, BSSID fe:a3:87:bf:ed:2f
> [111652.812108] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111652.813077] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [111654.639431] iwlagn 0000:03:00.0: Error sending
> REPLY_TX_POWER_DBM_CMD: time out after 500ms.
> [111654.639443] iwlagn 0000:03:00.0: Error sending TX power (-110)
> [111654.639447] ------------[ cut here ]------------
> [111654.639477] WARNING: at
> /home/kernel-ppa/COD/linux/drivers/net/wireless/iwlwifi/iwl-core.c:1898
> iwl_mac_change_interface+0x12e/0x130 [iwlcore]()
> [111654.639482] Hardware name: 4384BB3
> [111654.639484] Modules linked in: nf_nat_h323 nf_conntrack_h323
> nf_nat_pptp nf_conntrack_pptp nf_conntrack_proto_gre nf_nat_proto_gre
> nf_nat_tftp nf_conntrack_tftp nf_nat_sip nf_conntrack_sip nf_nat_irc
> nf_nat_ftp cdc_acm usbhid hid xt_limit xt_tcpudp ipt_LOG
> ipt_MASQUERADE xt_DSCP ipt_REJECT nf_conntrack_irc nf_conntrack_ftp
> xt_state nls_iso8859_1 nls_cp437 vfat fat binfmt_misc vboxnetadp
> vboxnetflt vboxdrv microcode parport_pc ppdev iptable_nat nf_nat
> nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_mangle
> iptable_filter ip_tables x_tables uvcvideo snd_hda_codec_hdmi
> snd_hda_codec_conexant arc4 videodev v4l2_compat_ioctl32 snd_hda_intel
> snd_hda_codec snd_hwdep joydev snd_pcm hdaps thinkpad_ec iwlagn
> snd_seq_midi iwlcore psmouse snd_rawmidi snd_seq_midi_event mac80211
> snd_seq serio_raw tpm_tis tpm lp parport thinkpad_acpi tpm_bios nvram
> snd_timer snd_seq_device cfg80211 snd intel_ips soundcore
> snd_page_alloc sha256_generic aesni_intel cryptd aes_x86_64
> aes_generic dm_crypt usb_storage uas i915 ahci drm_kms_helper
> firewire_ohci e1000e libahci sdhci_pci firewire_core drm sdhci
> crc_itu_t i2c_algo_bit video
> [111654.639584] Pid: 1317, comm: wpa_supplicant Tainted: G        W
> 2.6.38-020638rc7-generic #201103020909
> [111654.639586] Call Trace:
> [111654.639594]  [<ffffffffa02e6c7e>] ?
> iwl_mac_change_interface+0x12e/0x130 [iwlcore]
> [111654.639599]  [<ffffffffa02e6c7e>] ?
> iwl_mac_change_interface+0x12e/0x130 [iwlcore]
> [111654.639605]  [<ffffffff81065430>] ? warn_slowpath_common+0x90/0xc0
> [111654.639608]  [<ffffffff8106547a>] ? warn_slowpath_null+0x1a/0x20
> [111654.639612]  [<ffffffffa02e6c7e>] ?
> iwl_mac_change_interface+0x12e/0x130 [iwlcore]
> [111654.639626]  [<ffffffffa02869ec>] ?
> ieee80211_runtime_change_iftype+0xdc/0x180 [mac80211]
> [111654.639633]  [<ffffffffa0286b85>] ?
> ieee80211_if_change_type+0xf5/0x120 [mac80211]
> [111654.639641]  [<ffffffffa028995b>] ?
> ieee80211_change_iface+0x3b/0x130 [mac80211]
> [111654.639650]  [<ffffffffa01bf898>] ?
> cfg80211_change_iface+0xe8/0x1c0 [cfg80211]
> [111654.639657]  [<ffffffffa01d78f6>] ?
> cfg80211_wext_siwmode+0xa6/0xf0 [cfg80211]
> [111654.639661]  [<ffffffff8158a4cb>] ? ioctl_standard_call+0x6b/0xf0
> [111654.639664]  [<ffffffff8158a460>] ? ioctl_standard_call+0x0/0xf0
> [111654.639666]  [<ffffffff81589882>] ? wireless_process_ioctl+0x102/0x130
> [111654.639668]  [<ffffffff8158afe0>] ? ioctl_private_call+0x0/0xa0
> [111654.639670]  [<ffffffff8158afe0>] ? ioctl_private_call+0x0/0xa0
> [111654.639672]  [<ffffffff8158a460>] ? ioctl_standard_call+0x0/0xf0
> [111654.639675]  [<ffffffff8158991c>] ? wext_ioctl_dispatch+0x6c/0x90
> [111654.639677]  [<ffffffff81589b66>] ? wext_handle_ioctl+0x46/0x90
> [111654.639680]  [<ffffffff814ad76a>] ? sockfd_lookup_light+0x4a/0x80
> [111654.639683]  [<ffffffff814c687b>] ? dev_ioctl+0x28b/0x2a0
> [111654.639685]  [<ffffffff814ad25f>] ? sock_ioctl+0xbf/0x280
> [111654.639688]  [<ffffffff811704bd>] ? vfs_ioctl+0x1d/0x50
> [111654.639690]  [<ffffffff81170f79>] ? do_vfs_ioctl+0x69/0x1d0
> [111654.639692]  [<ffffffff81171174>] ? sys_ioctl+0x94/0xa0
> [111654.639695]  [<ffffffff8100c002>] ? system_call_fastpath+0x16/0x1b
> [111654.639697] ---[ end trace fb86611b81442166 ]---
> 
> I think the crash happens when the phone attempts to get an IP, at
> least that's what the phone says right after/at the crash. Any ideas?
> 
> // Mathias
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

Re: 2.6.38-rc7, iwlagn crash

[wwguy]

On Fri, 2011-03-04 at 05:46 -0800, John W. Linville wrote:
> Cc'ing Wey-yi and linux-wireless...anyone else having problems with
> iwlagn and IBSS?
> 
> On Fri, Mar 04, 2011 at 03:27:22AM +0000, Mathias Burén wrote:
> > Hi,
> >
> > (please cc as not subscribed)
> >
> >
> >
> > I think the crash happens when the phone attempts to get an IP, at
> > least that's what the phone says right after/at the crash. Any ideas?
> >
> >
forwarding to my team to work on it, any additional information you can
provide?

It is in IBSS mode, do you have any information can shared with us on
your phone's model, setup, and ...
if you can load the module with debug=0x43fff and provide the dmesg log,
it will be very helpful

Thanks
Wey

Re: 2.6.38-rc7, iwlagn crash

[Mathias Burén]

On 4 March 2011 15:17, wwguy <wey-yi.w.guy@intel.com> wrote:
> On Fri, 2011-03-04 at 05:46 -0800, John W. Linville wrote:
>> Cc'ing Wey-yi and linux-wireless...anyone else having problems with
>> iwlagn and IBSS?
>>
>> On Fri, Mar 04, 2011 at 03:27:22AM +0000, Mathias Burén wrote:
>> > Hi,
>> >
>> > (please cc as not subscribed)
>> >
>> >
>> >
>> > I think the crash happens when the phone attempts to get an IP, at
>> > least that's what the phone says right after/at the crash. Any ideas?
>> >
>> >
> forwarding to my team to work on it, any additional information you can
> provide?
>
> It is in IBSS mode, do you have any information can shared with us on
> your phone's model, setup, and ...
> if you can load the module with debug=0x43fff and provide the dmesg log,
> it will be very helpful
>
> Thanks
> Wey
>
>
>

Hi,

The phone is a Samsung Galaxy S (with "modded" wpa_supplicant to see
adhoc networks). I created a new adhoc network in Ubuntu using the
NetworkManager applet, with SSID "UbuntuAdhoc", band "automatic",
BSSID (blank) and no security. Under IPV4 settings I set it to "Shared
to other computers". Unfortunately I get this when trying to load the
module with debug:

$ sudo modprobe -v iwlagn debug=0x43fff
insmod /lib/modules/2.6.38-020638rc7-generic/kernel/drivers/net/wireless/iwlwifi/iwlagn.ko
11n_disable=1 debug=0x43fff
FATAL: Error inserting iwlagn
(/lib/modules/2.6.38-020638rc7-generic/kernel/drivers/net/wireless/iwlwifi/iwlagn.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
[  447.551540] iwlagn: Unknown parameter `debug'

$ sudo modprobe -v iwlagn
insmod /lib/modules/2.6.38-020638rc7-generic/kernel/drivers/net/wireless/iwlwifi/iwlagn.ko
11n_disable=1


[  501.570685] iwlagn: Intel(R) Wireless WiFi Link AGN driver for
Linux, in-tree:
[  501.570688] iwlagn: Copyright(c) 2003-2010 Intel Corporation
[  501.570760] iwlagn 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[  501.570772] iwlagn 0000:03:00.0: setting latency timer to 64
[  501.570809] iwlagn 0000:03:00.0: Detected Intel(R) Centrino(R)
Advanced-N 6200 AGN, REV=0x74
[  501.580698] iwlagn 0000:03:00.0: device EEPROM VER=0x436, CALIB=0x6
[  501.580703] iwlagn 0000:03:00.0: Device SKU: 0Xb
[  501.580739] iwlagn 0000:03:00.0: Tunable channels: 13 802.11bg, 24
802.11a channels
[  501.580836] iwlagn 0000:03:00.0: irq 44 for MSI/MSI-X
[  501.583936] iwlagn 0000:03:00.0: loaded firmware version 9.221.4.1
build 25532
[  501.584236] cfg80211: Ignoring regulatory request Set by core since
the driver uses its own custom regulatory domain
[  501.584392] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'

Here I create the adhoc network in network manager:

[  536.509700] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  536.858139] cfg80211: Found new beacon on frequency: 2472 MHz (Ch 13) on phy0
[  536.947735] cfg80211: Found new beacon on frequency: 5180 MHz (Ch 36) on phy0
[  537.041220] cfg80211: Found new beacon on frequency: 5200 MHz (Ch 40) on phy0
[  537.079114] cfg80211: Found new beacon on frequency: 5220 MHz (Ch 44) on phy0
[  537.175392] cfg80211: Found new beacon on frequency: 5240 MHz (Ch 48) on phy0
[  538.973811] cfg80211: Found new beacon on frequency: 5745 MHz (Ch
149) on phy0
[  539.203969] cfg80211: Found new beacon on frequency: 5785 MHz (Ch
157) on phy0
[  539.289182] cfg80211: Found new beacon on frequency: 5805 MHz (Ch
161) on phy0
[  571.156548] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  599.156798] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[  599.161234] wlan0: Trigger new scan to find an IBSS to join
[  604.131831] wlan0: Trigger new scan to find an IBSS to join
[  607.103522] wlan0: Creating new IBSS network, BSSID 42:dd:e6:af:fb:19
[  607.104488] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[  607.105407] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[  608.501173] wlan0: Trigger new scan to find an IBSS to join
[  609.190883] wlan0: no IPv6 routers present
[  613.397068] wlan0: Trigger new scan to find an IBSS to join
[  616.303044] wlan0: Creating new IBSS network, BSSID ae:eb:cb:59:18:ec
[  616.313716] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[  616.314529] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[  617.681034] wlan0: Trigger new scan to find an IBSS to join
[  622.736806] wlan0: Trigger new scan to find an IBSS to join
[  625.708399] wlan0: Creating new IBSS network, BSSID 46:b6:a0:1b:c4:7f
[  625.761157] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[  625.762035] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[  627.438640] iwlagn 0000:03:00.0: Error sending REPLY_RXON_TIMING:
time out after 500ms.
[  627.438648] iwlagn 0000:03:00.0: Failed to send timing (-110)!
[  627.438651] ------------[ cut here ]------------
[  627.438668] WARNING: at
/home/kernel-ppa/COD/linux/drivers/net/wireless/iwlwifi/iwl-core.c:1898
iwl_mac_change_interface+0x12e/0x130 [iwlcore]()
[  627.438672] Hardware name: 4384BB3
[  627.438674] Modules linked in: nf_nat_h323 nf_conntrack_h323
nf_nat_pptp nf_conntrack_pptp nf_conntrack_proto_gre nf_nat_proto_gre
nf_nat_tftp nf_conntrack_tftp nf_nat_sip nf_conntrack_sip nf_nat_irc
nf_nat_ftp iwlagn iwlcore mac80211 cfg80211 xt_limit xt_tcpudp ipt_LOG
ipt_MASQUERADE xt_DSCP ipt_REJECT nf_conntrack_irc nf_conntrack_ftp
xt_state binfmt_misc vboxnetadp vboxnetflt vboxdrv microcode
parport_pc ppdev iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack
nf_defrag_ipv4 iptable_mangle iptable_filter ip_tables x_tables
snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_intel snd_hda_codec
snd_hwdep snd_pcm snd_seq_midi joydev snd_rawmidi hdaps thinkpad_ec
snd_seq_midi_event arc4 snd_seq snd_timer uvcvideo videodev
snd_seq_device psmouse v4l2_compat_ioctl32 thinkpad_acpi tpm_tis tpm
tpm_bios nvram lp serio_raw parport snd soundcore intel_ips
snd_page_alloc sha256_generic aesni_intel cryptd aes_x86_64
aes_generic dm_crypt usbhid hid i915 firewire_ohci ahci drm_kms_helper
e1000e libahci drm sdhci_pci firewire_core sdhci crc_itu_t
i2c_algo_bit video [last unloaded: cfg80211]
[  627.438764] Pid: 1203, comm: NetworkManager Not tainted
2.6.38-020638rc7-generic #201103020909
[  627.438767] Call Trace:
[  627.438778]  [<ffffffffa0294c7e>] ?
iwl_mac_change_interface+0x12e/0x130 [iwlcore]
[  627.438787]  [<ffffffffa0294c7e>] ?
iwl_mac_change_interface+0x12e/0x130 [iwlcore]
[  627.438796]  [<ffffffff81065430>] ? warn_slowpath_common+0x90/0xc0
[  627.438801]  [<ffffffff8106547a>] ? warn_slowpath_null+0x1a/0x20
[  627.438809]  [<ffffffffa0294c7e>] ?
iwl_mac_change_interface+0x12e/0x130 [iwlcore]
[  627.438827]  [<ffffffffa02589ec>] ?
ieee80211_runtime_change_iftype+0xdc/0x180 [mac80211]
[  627.438840]  [<ffffffffa0258b85>] ?
ieee80211_if_change_type+0xf5/0x120 [mac80211]
[  627.438854]  [<ffffffffa025b95b>] ?
ieee80211_change_iface+0x3b/0x130 [mac80211]
[  627.438865]  [<ffffffffa020a898>] ?
cfg80211_change_iface+0xe8/0x1c0 [cfg80211]
[  627.438877]  [<ffffffffa02228f6>] ? cfg80211_wext_siwmode+0xa6/0xf0
[cfg80211]
[  627.438884]  [<ffffffff8158a4cb>] ? ioctl_standard_call+0x6b/0xf0
[  627.438889]  [<ffffffff8158a460>] ? ioctl_standard_call+0x0/0xf0
[  627.438893]  [<ffffffff81589882>] ? wireless_process_ioctl+0x102/0x130
[  627.438898]  [<ffffffff8158afe0>] ? ioctl_private_call+0x0/0xa0
[  627.438902]  [<ffffffff8158afe0>] ? ioctl_private_call+0x0/0xa0
[  627.438907]  [<ffffffff8158a460>] ? ioctl_standard_call+0x0/0xf0
[  627.438911]  [<ffffffff8158991c>] ? wext_ioctl_dispatch+0x6c/0x90
[  627.438916]  [<ffffffff81589b66>] ? wext_handle_ioctl+0x46/0x90
[  627.438922]  [<ffffffff814c687b>] ? dev_ioctl+0x28b/0x2a0
[  627.438927]  [<ffffffff814ad25f>] ? sock_ioctl+0xbf/0x280
[  627.438933]  [<ffffffff811704bd>] ? vfs_ioctl+0x1d/0x50
[  627.438937]  [<ffffffff81170f79>] ? do_vfs_ioctl+0x69/0x1d0
[  627.438940]  [<ffffffff81171174>] ? sys_ioctl+0x94/0xa0
[  627.438945]  [<ffffffff8100c002>] ? system_call_fastpath+0x16/0x1b
[  627.438949] ---[ end trace c7a5b9f525294bcc ]---
[  627.552179] wlan0: Trigger new scan to find an IBSS to join

Hm, not much I can do without recompiling the module with debug
support? Is there a way I can do this without recompiling the kernel?

Kind regards,
// Mathias

Re: 2.6.38-rc7, iwlagn crash

[Mathias Burén]

On 4 March 2011 22:23, Mathias Burén <mathias.buren@gmail.com> wrote:
> On 4 March 2011 15:17, wwguy <wey-yi.w.guy@intel.com> wrote:
>> On Fri, 2011-03-04 at 05:46 -0800, John W. Linville wrote:
>>> Cc'ing Wey-yi and linux-wireless...anyone else having problems with
>>> iwlagn and IBSS?
>>>
>>> On Fri, Mar 04, 2011 at 03:27:22AM +0000, Mathias Burén wrote:
>>> > Hi,
>>> >
>>> > (please cc as not subscribed)
>>> >
>>> >
>>> >
>>> > I think the crash happens when the phone attempts to get an IP, at
>>> > least that's what the phone says right after/at the crash. Any ideas?
>>> >
>>> >
>> forwarding to my team to work on it, any additional information you can
>> provide?
>>
>> It is in IBSS mode, do you have any information can shared with us on
>> your phone's model, setup, and ...
>> if you can load the module with debug=0x43fff and provide the dmesg log,
>> it will be very helpful
>>
>> Thanks
>> Wey
>>
>>
>>
>
> Hi,
>
> The phone is a Samsung Galaxy S (with "modded" wpa_supplicant to see
> adhoc networks). I created a new adhoc network in Ubuntu using the
> NetworkManager applet, with SSID "UbuntuAdhoc", band "automatic",
> BSSID (blank) and no security. Under IPV4 settings I set it to "Shared
> to other computers". Unfortunately I get this when trying to load the
> module with debug:
>
> $ sudo modprobe -v iwlagn debug=0x43fff
> insmod /lib/modules/2.6.38-020638rc7-generic/kernel/drivers/net/wireless/iwlwifi/iwlagn.ko
> 11n_disable=1 debug=0x43fff
> FATAL: Error inserting iwlagn
> (/lib/modules/2.6.38-020638rc7-generic/kernel/drivers/net/wireless/iwlwifi/iwlagn.ko):
> Unknown symbol in module, or unknown parameter (see dmesg)
> [  447.551540] iwlagn: Unknown parameter `debug'
>
> $ sudo modprobe -v iwlagn
> insmod /lib/modules/2.6.38-020638rc7-generic/kernel/drivers/net/wireless/iwlwifi/iwlagn.ko
> 11n_disable=1
>
>
> [  501.570685] iwlagn: Intel(R) Wireless WiFi Link AGN driver for
> Linux, in-tree:
> [  501.570688] iwlagn: Copyright(c) 2003-2010 Intel Corporation
> [  501.570760] iwlagn 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
> [  501.570772] iwlagn 0000:03:00.0: setting latency timer to 64
> [  501.570809] iwlagn 0000:03:00.0: Detected Intel(R) Centrino(R)
> Advanced-N 6200 AGN, REV=0x74
> [  501.580698] iwlagn 0000:03:00.0: device EEPROM VER=0x436, CALIB=0x6
> [  501.580703] iwlagn 0000:03:00.0: Device SKU: 0Xb
> [  501.580739] iwlagn 0000:03:00.0: Tunable channels: 13 802.11bg, 24
> 802.11a channels
> [  501.580836] iwlagn 0000:03:00.0: irq 44 for MSI/MSI-X
> [  501.583936] iwlagn 0000:03:00.0: loaded firmware version 9.221.4.1
> build 25532
> [  501.584236] cfg80211: Ignoring regulatory request Set by core since
> the driver uses its own custom regulatory domain
> [  501.584392] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'
>
> Here I create the adhoc network in network manager:
>
> [  536.509700] ADDRCONF(NETDEV_UP): wlan0: link is not ready
> [  536.858139] cfg80211: Found new beacon on frequency: 2472 MHz (Ch 13) on phy0
> [  536.947735] cfg80211: Found new beacon on frequency: 5180 MHz (Ch 36) on phy0
> [  537.041220] cfg80211: Found new beacon on frequency: 5200 MHz (Ch 40) on phy0
> [  537.079114] cfg80211: Found new beacon on frequency: 5220 MHz (Ch 44) on phy0
> [  537.175392] cfg80211: Found new beacon on frequency: 5240 MHz (Ch 48) on phy0
> [  538.973811] cfg80211: Found new beacon on frequency: 5745 MHz (Ch
> 149) on phy0
> [  539.203969] cfg80211: Found new beacon on frequency: 5785 MHz (Ch
> 157) on phy0
> [  539.289182] cfg80211: Found new beacon on frequency: 5805 MHz (Ch
> 161) on phy0
> [  571.156548] ADDRCONF(NETDEV_UP): wlan0: link is not ready
> [  599.156798] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
> [  599.161234] wlan0: Trigger new scan to find an IBSS to join
> [  604.131831] wlan0: Trigger new scan to find an IBSS to join
> [  607.103522] wlan0: Creating new IBSS network, BSSID 42:dd:e6:af:fb:19
> [  607.104488] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [  607.105407] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [  608.501173] wlan0: Trigger new scan to find an IBSS to join
> [  609.190883] wlan0: no IPv6 routers present
> [  613.397068] wlan0: Trigger new scan to find an IBSS to join
> [  616.303044] wlan0: Creating new IBSS network, BSSID ae:eb:cb:59:18:ec
> [  616.313716] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [  616.314529] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [  617.681034] wlan0: Trigger new scan to find an IBSS to join
> [  622.736806] wlan0: Trigger new scan to find an IBSS to join
> [  625.708399] wlan0: Creating new IBSS network, BSSID 46:b6:a0:1b:c4:7f
> [  625.761157] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [  625.762035] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
> [  627.438640] iwlagn 0000:03:00.0: Error sending REPLY_RXON_TIMING:
> time out after 500ms.
> [  627.438648] iwlagn 0000:03:00.0: Failed to send timing (-110)!
> [  627.438651] ------------[ cut here ]------------
> [  627.438668] WARNING: at
> /home/kernel-ppa/COD/linux/drivers/net/wireless/iwlwifi/iwl-core.c:1898
> iwl_mac_change_interface+0x12e/0x130 [iwlcore]()
> [  627.438672] Hardware name: 4384BB3
> [  627.438674] Modules linked in: nf_nat_h323 nf_conntrack_h323
> nf_nat_pptp nf_conntrack_pptp nf_conntrack_proto_gre nf_nat_proto_gre
> nf_nat_tftp nf_conntrack_tftp nf_nat_sip nf_conntrack_sip nf_nat_irc
> nf_nat_ftp iwlagn iwlcore mac80211 cfg80211 xt_limit xt_tcpudp ipt_LOG
> ipt_MASQUERADE xt_DSCP ipt_REJECT nf_conntrack_irc nf_conntrack_ftp
> xt_state binfmt_misc vboxnetadp vboxnetflt vboxdrv microcode
> parport_pc ppdev iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack
> nf_defrag_ipv4 iptable_mangle iptable_filter ip_tables x_tables
> snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_intel snd_hda_codec
> snd_hwdep snd_pcm snd_seq_midi joydev snd_rawmidi hdaps thinkpad_ec
> snd_seq_midi_event arc4 snd_seq snd_timer uvcvideo videodev
> snd_seq_device psmouse v4l2_compat_ioctl32 thinkpad_acpi tpm_tis tpm
> tpm_bios nvram lp serio_raw parport snd soundcore intel_ips
> snd_page_alloc sha256_generic aesni_intel cryptd aes_x86_64
> aes_generic dm_crypt usbhid hid i915 firewire_ohci ahci drm_kms_helper
> e1000e libahci drm sdhci_pci firewire_core sdhci crc_itu_t
> i2c_algo_bit video [last unloaded: cfg80211]
> [  627.438764] Pid: 1203, comm: NetworkManager Not tainted
> 2.6.38-020638rc7-generic #201103020909
> [  627.438767] Call Trace:
> [  627.438778]  [<ffffffffa0294c7e>] ?
> iwl_mac_change_interface+0x12e/0x130 [iwlcore]
> [  627.438787]  [<ffffffffa0294c7e>] ?
> iwl_mac_change_interface+0x12e/0x130 [iwlcore]
> [  627.438796]  [<ffffffff81065430>] ? warn_slowpath_common+0x90/0xc0
> [  627.438801]  [<ffffffff8106547a>] ? warn_slowpath_null+0x1a/0x20
> [  627.438809]  [<ffffffffa0294c7e>] ?
> iwl_mac_change_interface+0x12e/0x130 [iwlcore]
> [  627.438827]  [<ffffffffa02589ec>] ?
> ieee80211_runtime_change_iftype+0xdc/0x180 [mac80211]
> [  627.438840]  [<ffffffffa0258b85>] ?
> ieee80211_if_change_type+0xf5/0x120 [mac80211]
> [  627.438854]  [<ffffffffa025b95b>] ?
> ieee80211_change_iface+0x3b/0x130 [mac80211]
> [  627.438865]  [<ffffffffa020a898>] ?
> cfg80211_change_iface+0xe8/0x1c0 [cfg80211]
> [  627.438877]  [<ffffffffa02228f6>] ? cfg80211_wext_siwmode+0xa6/0xf0
> [cfg80211]
> [  627.438884]  [<ffffffff8158a4cb>] ? ioctl_standard_call+0x6b/0xf0
> [  627.438889]  [<ffffffff8158a460>] ? ioctl_standard_call+0x0/0xf0
> [  627.438893]  [<ffffffff81589882>] ? wireless_process_ioctl+0x102/0x130
> [  627.438898]  [<ffffffff8158afe0>] ? ioctl_private_call+0x0/0xa0
> [  627.438902]  [<ffffffff8158afe0>] ? ioctl_private_call+0x0/0xa0
> [  627.438907]  [<ffffffff8158a460>] ? ioctl_standard_call+0x0/0xf0
> [  627.438911]  [<ffffffff8158991c>] ? wext_ioctl_dispatch+0x6c/0x90
> [  627.438916]  [<ffffffff81589b66>] ? wext_handle_ioctl+0x46/0x90
> [  627.438922]  [<ffffffff814c687b>] ? dev_ioctl+0x28b/0x2a0
> [  627.438927]  [<ffffffff814ad25f>] ? sock_ioctl+0xbf/0x280
> [  627.438933]  [<ffffffff811704bd>] ? vfs_ioctl+0x1d/0x50
> [  627.438937]  [<ffffffff81170f79>] ? do_vfs_ioctl+0x69/0x1d0
> [  627.438940]  [<ffffffff81171174>] ? sys_ioctl+0x94/0xa0
> [  627.438945]  [<ffffffff8100c002>] ? system_call_fastpath+0x16/0x1b
> [  627.438949] ---[ end trace c7a5b9f525294bcc ]---
> [  627.552179] wlan0: Trigger new scan to find an IBSS to join
>
> Hm, not much I can do without recompiling the module with debug
> support? Is there a way I can do this without recompiling the kernel?
>
> Kind regards,
> // Mathias
>

I've tried to recompile just the kernel module, but I get various
errors when I try to do so;


root@host:/usr/src/linux-headers-2.6.38-020638rc7# make mrproper && cp
/boot/config-2.6.38-020638rc7-generic .config && yes "" | make
oldconfig && make prepare && make scripts && make menuconfig
  CLEAN   .tmp_versions
  CLEAN   scripts/basic
  CLEAN   scripts/kconfig
  CLEAN   include/config include/generated
  CLEAN   .config .config.old include/linux/version.h
  HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/basic/docproc
  HOSTCC  scripts/kconfig/conf.o
  HOSTCC  scripts/kconfig/kxgettext.o
  SHIPPED scripts/kconfig/zconf.tab.c
  SHIPPED scripts/kconfig/lex.zconf.c
  SHIPPED scripts/kconfig/zconf.hash.c
  HOSTCC  scripts/kconfig/zconf.tab.o
  HOSTLD  scripts/kconfig/conf
scripts/kconfig/conf --oldconfig Kconfig
#
# configuration written to .config
#
scripts/kconfig/conf --silentoldconfig Kconfig
  CHK     include/linux/version.h
  UPD     include/linux/version.h
  CHK     include/generated/utsrelease.h
  UPD     include/generated/utsrelease.h
make[1]: *** No rule to make target `kernel/bounds.c', needed by
`kernel/bounds.s'.  Stop.
make: *** [prepare0] Error 2

I suppose I need the kernel source, but it's nowhere to be found here
( http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.38-rc7-natty )
so I'm not sure what to do next.

// Mathias

Re: 2.6.38-rc7, iwlagn crash

[Mathias Burén]

On 5 March 2011 03:45, Mathias Burén <mathias.buren@gmail.com> wrote:
> On 4 March 2011 22:23, Mathias Burén <mathias.buren@gmail.com> wrote:
>> On 4 March 2011 15:17, wwguy <wey-yi.w.guy@intel.com> wrote:
>>> On Fri, 2011-03-04 at 05:46 -0800, John W. Linville wrote:
>>>> Cc'ing Wey-yi and linux-wireless...anyone else having problems with
>>>> iwlagn and IBSS?
>>>>
>>>> On Fri, Mar 04, 2011 at 03:27:22AM +0000, Mathias Burén wrote:
>>>> > Hi,
>>>> >
>>>> > (please cc as not subscribed)
>>>> >
>>>> >
>>>> >
>>>> > I think the crash happens when the phone attempts to get an IP, at
>>>> > least that's what the phone says right after/at the crash. Any ideas?
>>>> >
>>>> >
>>> forwarding to my team to work on it, any additional information you can
>>> provide?
>>>
>>> It is in IBSS mode, do you have any information can shared with us on
>>> your phone's model, setup, and ...
>>> if you can load the module with debug=0x43fff and provide the dmesg log,
>>> it will be very helpful
>>>
>>> Thanks
>>> Wey
>>>
>>>
(snip)

I compiled my own kernel (downloaded 2.6.37-rc8 source, applied the
apparmor patch required for Ubuntu, copied over the config, make
oldconfig, enabled iwlwifi debug in menuconfig then compiled it),
booted it and loaded iwlagn with debug=0x43fff. Then I attempted the
same thing (Ubuntu Adhoc, no wireless security, trying to connect with
the phone).

The entire dmesg can be found here:
http://www.privatepaste.com/download/49e6ead6c7

Regards,
// Mathias

Re: 2.6.38-rc7, iwlagn crash

[Mathias Burén]

On 5 March 2011 09:45, Mathias Burén <mathias.buren@gmail.com> wrote:
> On 5 March 2011 03:45, Mathias Burén <mathias.buren@gmail.com> wrote:
>> On 4 March 2011 22:23, Mathias Burén <mathias.buren@gmail.com> wrote:
>>> On 4 March 2011 15:17, wwguy <wey-yi.w.guy@intel.com> wrote:
>>>> On Fri, 2011-03-04 at 05:46 -0800, John W. Linville wrote:
>>>>> Cc'ing Wey-yi and linux-wireless...anyone else having problems with
>>>>> iwlagn and IBSS?
>>>>>
>>>>> On Fri, Mar 04, 2011 at 03:27:22AM +0000, Mathias Burén wrote:
>>>>> > Hi,
>>>>> >
>>>>> > (please cc as not subscribed)
>>>>> >
>>>>> >
>>>>> >
>>>>> > I think the crash happens when the phone attempts to get an IP, at
>>>>> > least that's what the phone says right after/at the crash. Any ideas?
>>>>> >
>>>>> >
>>>> forwarding to my team to work on it, any additional information you can
>>>> provide?
>>>>
>>>> It is in IBSS mode, do you have any information can shared with us on
>>>> your phone's model, setup, and ...
>>>> if you can load the module with debug=0x43fff and provide the dmesg log,
>>>> it will be very helpful
>>>>
>>>> Thanks
>>>> Wey
>>>>
>>>>
> (snip)
>
> I compiled my own kernel (downloaded 2.6.37-rc8 source, applied the
> apparmor patch required for Ubuntu, copied over the config, make
> oldconfig, enabled iwlwifi debug in menuconfig then compiled it),
> booted it and loaded iwlagn with debug=0x43fff. Then I attempted the
> same thing (Ubuntu Adhoc, no wireless security, trying to connect with
> the phone).
>
> The entire dmesg can be found here:
> http://www.privatepaste.com/download/49e6ead6c7
>
> Regards,
> // Mathias
>

Sorry, I created that file with dmesg > file. Here's the actual dmesg
file from /var/log/dmesg :
http://stuff.dyndns.org/logs/dmesg-2.6.38-rc7-iwldebug-apparmor.log

// Mathias

Re: 2.6.38-rc7, iwlagn crash

[Johannes Berg]

On Sat, 2011-03-05 at 09:45 +0000, Mathias Burén wrote:

> I compiled my own kernel (downloaded 2.6.37-rc8 source, applied the
> apparmor patch required for Ubuntu, copied over the config, make
> oldconfig, enabled iwlwifi debug in menuconfig then compiled it),
> booted it and loaded iwlagn with debug=0x43fff. Then I attempted the
> same thing (Ubuntu Adhoc, no wireless security, trying to connect with
> the phone).
> 
> The entire dmesg can be found here:
> http://www.privatepaste.com/download/49e6ead6c7

So the warning is gone now?

johannes

Re: 2.6.38-rc7, iwlagn crash

[Mathias Burén]

On 5 March 2011 14:09, Johannes Berg <johannes@sipsolutions.net> wrote:
> On Sat, 2011-03-05 at 09:45 +0000, Mathias Burén wrote:
>
>> I compiled my own kernel (downloaded 2.6.37-rc8 source, applied the
>> apparmor patch required for Ubuntu, copied over the config, make
>> oldconfig, enabled iwlwifi debug in menuconfig then compiled it),
>> booted it and loaded iwlagn with debug=0x43fff. Then I attempted the
>> same thing (Ubuntu Adhoc, no wireless security, trying to connect with
>> the phone).
>>
>> The entire dmesg can be found here:
>> http://www.privatepaste.com/download/49e6ead6c7
>
> So the warning is gone now?
>
> johannes
>
>

I got it again, with the newly compiled kernel. However, I've been
trying for 20 minutes now and when I load iwlagn with the debug
parameter I can't seem to get the warning. I was monitoring dmesg with
"watch --interval=1 "dmesg|tail -n40"" but I never saw the warning. As
soon as I removed the module, and inserted it again without the debug
option I could reproduce the warning. Here are some dmesg logs:

no debug, crash 1: http://www.privatepaste.com/download/06539404a8
no debug, crash 2: http://www.privatepaste.com/download/a6be5f5c81
debug, attempting to connect (network found but no IP received):
http://www.privatepaste.com/download/0dcea94fb0
debug, attempting to connect (network found but no IP received) 2:
http://www.privatepaste.com/download/f3bcc0a8ab
debug, attempting to connect (network found but no IP received) 3:
http://www.privatepaste.com/download/5ad33c21cd

So for whatever reason when debug is enabled I don't get the warning.
I'll try one last time with and without debug now just to confirm...

Hm, I've been trying for ages to reproduce the crash (with or without
debug enabled), however the "UbuntuAdhoc" network appears very rarely
on the phone (and I get a notification every other second on the
laptop "UbuntuAdhoc disconnected"). The few times the network appears
on the phone I've tried to connect, then I get this:

Attempting to connect:

[ 2273.874563] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[ 2273.874729] wlan0: No active IBSS STAs - trying to scan for other
IBSS networks with same SSID (merge)
[ 2275.716984] iwlagn 0000:03:00.0: Error sending
REPLY_TX_LINK_QUALITY_CMD: time out after 500ms.
[ 2275.725079] wlan0: Selected IBSS BSSID f6:98:ac:c4:66:25 based on
configured SSID
[ 2275.788313] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[ 2275.789196] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[ 2275.789324] wlan0: No active IBSS STAs - trying to scan for other
IBSS networks with same SSID (merge)
[ 2277.119589] wlan0: Selected IBSS BSSID f6:98:ac:c4:66:25 based on
configured SSID
[ 2277.170348] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[ 2277.171164] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[ 2277.171306] wlan0: No active IBSS STAs - trying to scan for other
IBSS networks with same SSID (merge)
[ 2278.488817] wlan0: Trigger new scan to find an IBSS to join
[ 2281.248817] wlan0: Selected IBSS BSSID f6:98:ac:c4:66:25 based on
configured SSID
[ 2281.250494] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[ 2281.251432] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[ 2282.751112] wlan0: Selected IBSS BSSID f6:98:ac:c4:66:25 based on
configured SSID
[ 2282.795959] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[ 2282.796729] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[ 2282.796896] wlan0: No active IBSS STAs - trying to scan for other
IBSS networks with same SSID (merge)
[ 2284.229258] wlan0: Selected IBSS BSSID f6:98:ac:c4:66:25 based on
configured SSID
[ 2284.263836] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[ 2284.264583] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[ 2284.264930] wlan0: No active IBSS STAs - trying to scan for other
IBSS networks with same SSID (merge)
[ 2285.666846] wlan0: Selected IBSS BSSID f6:98:ac:c4:66:25 based on
configured SSID
[ 2285.700889] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[ 2285.701671] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[ 2285.701813] wlan0: No active IBSS STAs - trying to scan for other
IBSS networks with same SSID (merge)

Obtaining IP address on phone:

[ 2423.981988] cfg80211: Found new beacon on frequency: 5785 MHz (Ch
157) on phy0
[ 2424.016521] cfg80211: Found new beacon on frequency: 5805 MHz (Ch
161) on phy0
[ 2426.182617] wlan0: Trigger new scan to find an IBSS to join
[ 2429.063958] wlan0: Creating new IBSS network, BSSID 12:e4:a7:81:4d:7c
[ 2429.074249] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[ 2429.075213] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[ 2429.531435] wlan0: no IPv6 routers present
[ 2430.418990] wlan0: Trigger new scan to find an IBSS to join
[ 2433.356034] wlan0: Selected IBSS BSSID 8a:e9:57:48:45:be based on
configured SSID
[ 2433.356515] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[ 2433.357397] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[ 2434.866178] wlan0: Selected IBSS BSSID 8a:e9:57:48:45:be based on
configured SSID
[ 2434.893583] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[ 2434.894347] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[ 2434.894484] wlan0: No active IBSS STAs - trying to scan for other
IBSS networks with same SSID (merge)
[ 2436.292923] wlan0: Selected IBSS BSSID 8a:e9:57:48:45:be based on
configured SSID
[ 2436.354619] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[ 2436.355601] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[ 2436.355770] wlan0: No active IBSS STAs - trying to scan for other
IBSS networks with same SSID (merge)
[ 2437.736175] wlan0: Selected IBSS BSSID 8a:e9:57:48:45:be based on
configured SSID
[ 2437.768543] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[ 2437.769386] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[ 2437.769559] wlan0: No active IBSS STAs - trying to scan for other
IBSS networks with same SSID (merge)
[ 2439.141544] wlan0: Selected IBSS BSSID 8a:e9:57:48:45:be based on
configured SSID
[ 2439.185032] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[ 2439.185926] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[ 2440.586132] wlan0: Selected IBSS BSSID 8a:e9:57:48:45:be based on
configured SSID
[ 2440.623583] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[ 2440.624288] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[ 2440.624393] wlan0: No active IBSS STAs - trying to scan for other
IBSS networks with same SSID (merge)
[ 2441.999051] wlan0: Selected IBSS BSSID 8a:e9:57:48:45:be based on
configured SSID
[ 2442.061302] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[ 2442.062066] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[ 2442.062208] wlan0: No active IBSS STAs - trying to scan for other
IBSS networks with same SSID (merge)

Here's a dmesg with debug enabled when the phone found the network and
is trying to get an IP:
http://www.privatepaste.com/download/7b32b9608d

I finally produced another warning, this is when the phone was
scanning for networks, unfortunately again without debug enabled:
http://www.privatepaste.com/download/d41f26f916

I'm not sure this helps... I also uploaded the kernel config here:
http://www.privatepaste.com/58e1d350cb

Kind regards,
// Mathias

Re: 2.6.38-rc7, iwlagn warning

[Johannes Berg]

FWIW, I'm changing the subject since "crash" bothers me, it's not even
close to a crash.

On Sat, 2011-03-05 at 23:45 +0000, Mathias Burén wrote:

> I got it again, with the newly compiled kernel. However, I've been
> trying for 20 minutes now and when I load iwlagn with the debug
> parameter I can't seem to get the warning. I was monitoring dmesg with
> "watch --interval=1 "dmesg|tail -n40"" but I never saw the warning. As
> soon as I removed the module, and inserted it again without the debug
> option I could reproduce the warning. Here are some dmesg logs:

Curious. 

> no debug, crash 1: http://www.privatepaste.com/download/06539404a8
> no debug, crash 2: http://www.privatepaste.com/download/a6be5f5c81

And I'd prefer if you also stopped using the word crash. Nothing
crashed. All you got was a stack trace because I put a warning there.
Really, not the end of the world, and in fact it probably has very
little or even no effect on functionality.


However ... actually looking at the log files I'm totally confused what
it is that you're doing. Something appears to be continually switching
between interface modes, even using wireless extensions, yet it really
wants to be IBSS all the time. What's causing all this pointless
switching? It'd be useful to figure that out, but I'm not sure how. What
applications are you running that manage wireless? Are you, by any
chance, running wpa_supplicant manually in addition to network-manager?

Irregardless of that though, there's clearly some kind of bug in the
driver since the TX power setting times out, and then as a result we get
the warning.

Would you be willing to enable tracing and capture a trace using
trace-cmd, by running 'trace-cmd record -e mac80211 -e iwlwifi'?

johannes

Re: 2.6.38-rc7, iwlagn warning

[Mathias Burén]

On 8 March 2011 15:17, Johannes Berg <johannes@sipsolutions.net> wrote:
> FWIW, I'm changing the subject since "crash" bothers me, it's not even
> close to a crash.

Of course, sorry.

> On Sat, 2011-03-05 at 23:45 +0000, Mathias Burén wrote:
>
>> I got it again, with the newly compiled kernel. However, I've been
>> trying for 20 minutes now and when I load iwlagn with the debug
>> parameter I can't seem to get the warning. I was monitoring dmesg with
>> "watch --interval=1 "dmesg|tail -n40"" but I never saw the warning. As
>> soon as I removed the module, and inserted it again without the debug
>> option I could reproduce the warning. Here are some dmesg logs:
>
> Curious.
>
>> no debug, crash 1: http://www.privatepaste.com/download/06539404a8
>> no debug, crash 2: http://www.privatepaste.com/download/a6be5f5c81
>
> And I'd prefer if you also stopped using the word crash. Nothing
> crashed. All you got was a stack trace because I put a warning there.
> Really, not the end of the world, and in fact it probably has very
> little or even no effect on functionality.
>

Got it.

> However ... actually looking at the log files I'm totally confused what
> it is that you're doing. Something appears to be continually switching
> between interface modes, even using wireless extensions, yet it really
> wants to be IBSS all the time. What's causing all this pointless
> switching? It'd be useful to figure that out, but I'm not sure how. What
> applications are you running that manage wireless? Are you, by any
> chance, running wpa_supplicant manually in addition to network-manager?

I'm using NetworkManager, I haven't started anything else manually. I
don't know why it switches modes like that, it happens on 2 laptops
(both Ubuntu 10.10) so it could very well be some NetworkManager
related issue.

> Irregardless of that though, there's clearly some kind of bug in the
> driver since the TX power setting times out, and then as a result we get
> the warning.
>
> Would you be willing to enable tracing and capture a trace using
> trace-cmd, by running 'trace-cmd record -e mac80211 -e iwlwifi'?
>
> johannes
>
>

I've since upgraded to 2.6.38-rc8 (same config). Looking around in the
config, is it CONFIG_FUNCTION_TRACER I need to enable, and is that it?
(kernel function tracer)

// Mathias

Re: 2.6.38-rc7, iwlagn warning

[Johannes Berg]

On Tue, 2011-03-08 at 16:22 +0000, Mathias Burén wrote:

> > Would you be willing to enable tracing and capture a trace using
> > trace-cmd, by running 'trace-cmd record -e mac80211 -e iwlwifi'?

> I've since upgraded to 2.6.38-rc8 (same config). Looking around in the
> config, is it CONFIG_FUNCTION_TRACER I need to enable, and is that it?
> (kernel function tracer)

You need CONFIG_MAC80211_DRIVER_API_TRACER and
CONFIG_IWLWIFI_DEVICE_TRACING (and their prerequisites, which you can
find in menuconfig by hitting the slash ("/") key and searching for
these config symbols, remove the CONFIG_ prefix)

johannes

Re: 2.6.38-rc7, iwlagn warning

[Johannes Berg]

On Tue, 2011-03-08 at 16:22 +0000, Mathias Burén wrote:

> I'm using NetworkManager, I haven't started anything else manually. I
> don't know why it switches modes like that, it happens on 2 laptops
> (both Ubuntu 10.10) so it could very well be some NetworkManager
> related issue.

Actually, before you do the tracing, can we get the supplicant logs? See
http://live.gnome.org/NetworkManager/Debugging under "Debugging WiFi
connections".

johannes

Re: 2.6.38-rc7, iwlagn warning

[Mathias Burén]

On 8 March 2011 16:45, Johannes Berg <johannes@sipsolutions.net> wrote:
> On Tue, 2011-03-08 at 16:22 +0000, Mathias Burén wrote:
>
>> I'm using NetworkManager, I haven't started anything else manually. I
>> don't know why it switches modes like that, it happens on 2 laptops
>> (both Ubuntu 10.10) so it could very well be some NetworkManager
>> related issue.
>
> Actually, before you do the tracing, can we get the supplicant logs? See
> http://live.gnome.org/NetworkManager/Debugging under "Debugging WiFi
> connections".
>
> johannes
>
>

I've a trace file and a dmesg (iwlagn loaded without debug though)
which caught the warning again, up here:
trace http://www.2shared.com/file/XIqwsRt0/trace.html
dmesg http://www.2shared.com/file/vShUfLjr/dmesg-warning-no-connection.html

Here's the NetworkManager stuff:

$ ps aux |grep wpa
root      5320  0.0  0.0  28404  2828 ?        S    17:01   0:00
/sbin/wpa_supplicant -u -s -dddt -f /var/log/wpa_supplicant.log

dmesg from trying to connect:


[  852.538122] wlan0: No active IBSS STAs - trying to scan for other
IBSS networks with same SSID (merge)
[  856.519009] wlan0: Selected IBSS BSSID 2e:d2:7e:91:0b:75 based on
configured SSID
[  856.525468] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[  856.526236] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[  860.518782] wlan0: Selected IBSS BSSID 2e:d2:7e:91:0b:75 based on
configured SSID
[  860.525444] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[  860.526172] iwlagn 0000:03:00.0: Unable to find TIM Element in beacon
[  860.615831] wlan0: No active IBSS STAs - trying to scan for other
IBSS networks with same SSID (merge)


$ cat /var/log/wpa_supplicant.log
1299603957.708982: WPS: UUID based on MAC address - hexdump(len=16):
cc fa a1 31 39 a7 5c 33 96 d8 eb 09 dd fe 7f 0f
1299603957.721046: ssid - hexdump_ascii(len=11):
     55 62 75 6e 74 75 41 64 68 6f 63                  UbuntuAdhoc
1299603965.996780: ssid - hexdump_ascii(len=11):
     55 62 75 6e 74 75 41 64 68 6f 63                  UbuntuAdhoc
1299603975.655187: ssid - hexdump_ascii(len=11):
     55 62 75 6e 74 75 41 64 68 6f 63                  UbuntuAdhoc
1299603985.161298: ssid - hexdump_ascii(len=11):
     55 62 75 6e 74 75 41 64 68 6f 63                  UbuntuAdhoc
1299603994.696625: ssid - hexdump_ascii(len=11):
     55 62 75 6e 74 75 41 64 68 6f 63                  UbuntuAdhoc

[snip]

1299604089.756872: WPS: UUID based on MAC address - hexdump(len=16):
cc fa a1 31 39 a7 5c 33 96 d8 eb 09 dd fe 7f 0f
1299604089.768927: ssid - hexdump_ascii(len=11):
     55 62 75 6e 74 75 41 64 68 6f 63                  UbuntuAdhoc
1299604094.005785: ssid - hexdump_ascii(len=11):
     55 62 75 6e 74 75 41 64 68 6f 63                  UbuntuAdhoc

Anything else I can try/provide?

Thanks,
// Mathias

Re: 2.6.38-rc7, iwlagn warning

[Johannes Berg]

On Tue, 2011-03-08 at 17:13 +0000, Mathias Burén wrote:

> 1299604089.756872: WPS: UUID based on MAC address - hexdump(len=16):
> cc fa a1 31 39 a7 5c 33 96 d8 eb 09 dd fe 7f 0f
> 1299604089.768927: ssid - hexdump_ascii(len=11):
>      55 62 75 6e 74 75 41 64 68 6f 63                  UbuntuAdhoc
> 1299604094.005785: ssid - hexdump_ascii(len=11):
>      55 62 75 6e 74 75 41 64 68 6f 63                  UbuntuAdhoc
> 
> Anything else I can try/provide?

Could you do the -dddt thing as explained on the link I had before?

Obviously, we're now looking for the cause -- while the warning still
shouldn't happen *even if userspace is misbehaving*. The trace will
hopefully help me figure out why we get the warning, I'll look at it
later.

johannes

Re: 2.6.38-rc7, iwlagn warning

[Mathias Burén]

On 8 March 2011 17:18, Johannes Berg <johannes@sipsolutions.net> wrote:
> On Tue, 2011-03-08 at 17:13 +0000, Mathias Burén wrote:
>
>> 1299604089.756872: WPS: UUID based on MAC address - hexdump(len=16):
>> cc fa a1 31 39 a7 5c 33 96 d8 eb 09 dd fe 7f 0f
>> 1299604089.768927: ssid - hexdump_ascii(len=11):
>>      55 62 75 6e 74 75 41 64 68 6f 63                  UbuntuAdhoc
>> 1299604094.005785: ssid - hexdump_ascii(len=11):
>>      55 62 75 6e 74 75 41 64 68 6f 63                  UbuntuAdhoc
>>
>> Anything else I can try/provide?
>
> Could you do the -dddt thing as explained on the link I had before?
>
> Obviously, we're now looking for the cause -- while the warning still
> shouldn't happen *even if userspace is misbehaving*. The trace will
> hopefully help me figure out why we get the warning, I'll look at it
> later.
>
> johannes
>
>

I think the wpa_supplicant log file is generated correctly now, see:
http://www.2shared.com/file/QTkhZ1VC/wpa_supplicant.html


Kind regards,
// Mathias

Re: 2.6.38-rc7, iwlagn warning

[Dan Williams]

On Tue, 2011-03-08 at 17:54 +0000, Mathias Burén wrote:
> On 8 March 2011 17:18, Johannes Berg <johannes@sipsolutions.net> wrote:
> > On Tue, 2011-03-08 at 17:13 +0000, Mathias Burén wrote:
> >
> >> 1299604089.756872: WPS: UUID based on MAC address - hexdump(len=16):
> >> cc fa a1 31 39 a7 5c 33 96 d8 eb 09 dd fe 7f 0f
> >> 1299604089.768927: ssid - hexdump_ascii(len=11):
> >>      55 62 75 6e 74 75 41 64 68 6f 63                  UbuntuAdhoc
> >> 1299604094.005785: ssid - hexdump_ascii(len=11):
> >>      55 62 75 6e 74 75 41 64 68 6f 63                  UbuntuAdhoc
> >>
> >> Anything else I can try/provide?
> >
> > Could you do the -dddt thing as explained on the link I had before?
> >
> > Obviously, we're now looking for the cause -- while the warning still
> > shouldn't happen *even if userspace is misbehaving*. The trace will
> > hopefully help me figure out why we get the warning, I'll look at it
> > later.
> >
> > johannes
> >
> >
> 
> I think the wpa_supplicant log file is generated correctly now, see:
> http://www.2shared.com/file/QTkhZ1VC/wpa_supplicant.html

Could you also grab /var/log/daemon.log or /var/log/NetworkManager.log,
whichever one exists?  And just to  make sure, when this problem
happens, there is only one wpa_supplicant running at the time, right?
Is something like wicd also running?

The logs there look like something external is telling the supplicant to
disassociate, which could be NM or some other tool, but NM should not be
exhibiting this behavior if NM itself was used to start the adhoc
network.

Dan

Re: 2.6.38-rc7, iwlagn warning

[Mathias Burén]

On 8 March 2011 18:16, Dan Williams <dcbw@redhat.com> wrote:
> On Tue, 2011-03-08 at 17:54 +0000, Mathias Burén wrote:
>> On 8 March 2011 17:18, Johannes Berg <johannes@sipsolutions.net> wrote:
>> > On Tue, 2011-03-08 at 17:13 +0000, Mathias Burén wrote:
>> >
>> >> 1299604089.756872: WPS: UUID based on MAC address - hexdump(len=16):
>> >> cc fa a1 31 39 a7 5c 33 96 d8 eb 09 dd fe 7f 0f
>> >> 1299604089.768927: ssid - hexdump_ascii(len=11):
>> >>      55 62 75 6e 74 75 41 64 68 6f 63                  UbuntuAdhoc
>> >> 1299604094.005785: ssid - hexdump_ascii(len=11):
>> >>      55 62 75 6e 74 75 41 64 68 6f 63                  UbuntuAdhoc
>> >>
>> >> Anything else I can try/provide?
>> >
>> > Could you do the -dddt thing as explained on the link I had before?
>> >
>> > Obviously, we're now looking for the cause -- while the warning still
>> > shouldn't happen *even if userspace is misbehaving*. The trace will
>> > hopefully help me figure out why we get the warning, I'll look at it
>> > later.
>> >
>> > johannes
>> >
>> >
>>
>> I think the wpa_supplicant log file is generated correctly now, see:
>> http://www.2shared.com/file/QTkhZ1VC/wpa_supplicant.html
>
> Could you also grab /var/log/daemon.log or /var/log/NetworkManager.log,
> whichever one exists?  And just to  make sure, when this problem
> happens, there is only one wpa_supplicant running at the time, right?
> Is something like wicd also running?
>
> The logs there look like something external is telling the supplicant to
> disassociate, which could be NM or some other tool, but NM should not be
> exhibiting this behavior if NM itself was used to start the adhoc
> network.
>
> Dan
>
>
>


dameon.log http://www.2shared.com/file/9ntZ37Q9/daemon.html

I think the problem is Ubuntu-related, I can see error messages about
dnsmasq (which NetworkManager uses for its DHCP purposes, right). I
set the phone to static IPs, then suddenly the whole thing started
working. No warning in dmesg...

// Mathias

Re: 2.6.38-rc7, iwlagn warning

[Johannes Berg]

On Tue, 2011-03-08 at 19:10 +0000, Mathias Burén wrote:

> > Could you also grab /var/log/daemon.log or /var/log/NetworkManager.log,
> > whichever one exists?  And just to  make sure, when this problem
> > happens, there is only one wpa_supplicant running at the time, right?
> > Is something like wicd also running?
> >
> > The logs there look like something external is telling the supplicant to
> > disassociate, which could be NM or some other tool, but NM should not be
> > exhibiting this behavior if NM itself was used to start the adhoc
> > network.

> dameon.log http://www.2shared.com/file/9ntZ37Q9/daemon.html
> 
> I think the problem is Ubuntu-related, I can see error messages about
> dnsmasq (which NetworkManager uses for its DHCP purposes, right). I
> set the phone to static IPs, then suddenly the whole thing started
> working. No warning in dmesg...

Yeah -- if you configure /etc/dnsmasq.conf to not listen on all
interfaces, or you just disable it, then it should all work.

In any case, I'll look more into the warning, but even if I fix the
warning it won't really work any better for you until you manage to fix
the dnsmasq thing -- maybe file a bug against Ubuntu.

johannes

Re: 2.6.38-rc7, iwlagn warning

[Johannes Berg]

On Tue, 2011-03-08 at 20:39 +0100, Johannes Berg wrote:

> In any case, I'll look more into the warning, but even if I fix the
> warning it won't really work any better for you until you manage to fix
> the dnsmasq thing -- maybe file a bug against Ubuntu.

Err, only if you use default config etc. of course.

johannes

Re: 2.6.38-rc7, iwlagn warning

[Dan Williams]

On Tue, 2011-03-08 at 20:39 +0100, Johannes Berg wrote:
> On Tue, 2011-03-08 at 19:10 +0000, Mathias Burén wrote:
> 
> > > Could you also grab /var/log/daemon.log or /var/log/NetworkManager.log,
> > > whichever one exists?  And just to  make sure, when this problem
> > > happens, there is only one wpa_supplicant running at the time, right?
> > > Is something like wicd also running?
> > >
> > > The logs there look like something external is telling the supplicant to
> > > disassociate, which could be NM or some other tool, but NM should not be
> > > exhibiting this behavior if NM itself was used to start the adhoc
> > > network.
> 
> > dameon.log http://www.2shared.com/file/9ntZ37Q9/daemon.html
> > 
> > I think the problem is Ubuntu-related, I can see error messages about
> > dnsmasq (which NetworkManager uses for its DHCP purposes, right). I
> > set the phone to static IPs, then suddenly the whole thing started
> > working. No warning in dmesg...
> 
> Yeah -- if you configure /etc/dnsmasq.conf to not listen on all
> interfaces, or you just disable it, then it should all work.

NM should also not just loop continuously trying to reactivate the adhoc
connection when it fails.  Maybe a few times, but certainly not forever.

Dan

Re: 2.6.38-rc7, iwlagn warning

[Johannes Berg]

On Tue, 2011-03-08 at 17:13 +0000, Mathias Burén wrote:

> trace http://www.2shared.com/file/XIqwsRt0/trace.html
> dmesg http://www.2shared.com/file/vShUfLjr/dmesg-warning-no-connection.html

Just to confirm -- these were taken at the same time?

johannes

Re: 2.6.38-rc7, iwlagn crash

[Johannes Berg]

On Sat, 2011-03-05 at 23:45 +0000, Mathias Burén wrote:

> however the "UbuntuAdhoc" network appears very rarely
> on the phone (and I get a notification every other second on the
> laptop "UbuntuAdhoc disconnected").

FWIW, this is definitely due to the continuous pointless mode switching
I pointed out in my other mail.

johannes