Prev: Staging: cxt1e1: Fix build error
Next: [PATCH 2.6.34-rc6] mxc: gadget: Fix bitfield for calculating maximum packet size
From: Nils Radtke on 13 May 2010 07:40
Hi,

short feedback:

- recompiled kernel and config80211 as M
- debug symbols included. Yet to try.
- reboot
Linux mypole 2.6.33.3 #22 SMP PREEMPT Thu May 13 12:52:22 CEST 2010 i686 GNU/Linux
- renamed in-tree iwlagn and iwlcore, ran depmod -a, confirmed by looking into modules.dep
- compat wireless compiled ok, modprobe fails w/:

[ 23.665814] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
[ 23.665817] iwlagn: Copyright(c) 2003-2010 Intel Corporation
[ 23.665869] BUG: unable to handle kernel NULL pointer dereference at (null)
[ 23.665934] IP: [<f8931b40>] iwl_alloc_all+0x20/0x50 [iwlcore]
[ 23.665980] *pdpt = 0000000036448001 *pde = 0000000000000000
[ 23.666019] Oops: 0002 [#1] PREEMPT SMP
[ 23.666019] last sysfs file: /sys/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/type
[ 23.666019] Modules linked in: iwlagn(+) iwlcore mac80211 uhci_hcd e1000e cfg80211
[ 23.666019]
[ 23.666019] Pid: 356, comm: modprobe Not tainted 2.6.33.3 #22 7666B4G/7666B4G
[ 23.666019] EIP: 0060:[<f8931b40>] EFLAGS: 00010282 CPU: 0
[ 23.666019] EIP is at iwl_alloc_all+0x20/0x50 [iwlcore]
[ 23.666019] EAX: 00000000 EBX: f8998f20 ECX: f61d0280 EDX: f88e1870
[ 23.666019] ESI: f61d0280 EDI: f8998f20 EBP: 00000000 ESP: f64ede38
[ 23.666019] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
[ 23.666019] Process modprobe (pid: 356, ti=f64ec000 task=f64b2030 task.ti=f64ec000)
[ 23.666019] Stack:
[ 23.666019] c114241c f64ede58 f752bc00 f89987c0 f897eed5 00000000 a1ffde9c f65affe0
[ 23.666019] <0> 000033bf f606dbbc f7535b0c c16f06bd c16f03fc c134d180 f752bc00 f89987c0
[ 23.666019] <0> f897ee90 00000000 c134d02b c134d851 f89987c0 f752bc00 f8997e9c f752bc5c
[ 23.666019] Call Trace:
[ 23.666019] [<c114241c>] ? sysfs_add_one+0x1c/0x140
[ 23.666019] [<f897eed5>] ? iwl_pci_probe+0x45/0x9c0 [iwlagn]
[ 23.666019] [<c16f06bd>] ? _raw_spin_lock+0xd/0x30
[ 23.666019] [<c16f03fc>] ? _raw_spin_unlock+0xc/0x20
[ 23.666019] [<c134d180>] ? pci_match_device+0xa0/0xc0
[ 23.666019] [<f897ee90>] ? iwl_pci_probe+0x0/0x9c0 [iwlagn]
[ 23.666019] [<c134d02b>] ? local_pci_probe+0xb/0x10
[ 23.666019] [<c134d851>] ? pci_device_probe+0x61/0x80
[ 23.666019] [<c1415dbb>] ? driver_probe_device+0x7b/0x170
[ 23.666019] [<c134d180>] ? pci_match_device+0xa0/0xc0
[ 23.666019] [<c16f0689>] ? _raw_spin_lock_irqsave+0x19/0x40
[ 23.671155] [<c1415f29>] ? __driver_attach+0x79/0x80
[ 23.671155] [<c1415eb0>] ? __driver_attach+0x0/0x80
[ 23.671155] [<c1415622>] ? bus_for_each_dev+0x52/0x80
[ 23.671155] [<c1415c56>] ? driver_attach+0x16/0x20
[ 23.671155] [<c1415eb0>] ? __driver_attach+0x0/0x80
[ 23.671155] [<c1414f1c>] ? bus_add_driver+0xcc/0x2b0
[ 23.671155] [<c134d790>] ? pci_device_remove+0x0/0x40
[ 23.671155] [<c14161c3>] ? driver_register+0x63/0x120
[ 23.671155] [<f899e000>] ? iwl_init+0x0/0x6a [iwlagn]
[ 23.671155] [<f899e000>] ? iwl_init+0x0/0x6a [iwlagn]
[ 23.671155] [<c134da7d>] ? __pci_register_driver+0x3d/0xb0
[ 23.671155] [<f899e04d>] ? iwl_init+0x4d/0x6a [iwlagn]
[ 23.671155] [<c100112f>] ? do_one_initcall+0x2f/0x190
[ 23.671155] [<c107ad54>] ? sys_init_module+0xb4/0x220
[ 23.671155] [<c1002c8c>] ? sysenter_do_call+0x12/0x22
[ 23.671155] Code: b6 00 00 00 00 8d bf 00 00 00 00 83 ec 10 89 5c 24 08 89 c3 b8 24 63 00 00 89 74 24 0c e8 59 fa fa ff 85 c0 89 c6 74 13 8b 40 30 <89> 30 89 f0 8b 5c 24 08 8b 74 24 0c 83 c4 10 c3 8b 03 c7 04 24
[ 23.671155] EIP: [<f8931b40>] iwl_alloc_all+0x20/0x50 [iwlcore] SS:ESP 0068:f64ede38
[ 23.671155] CR2: 0000000000000000
[ 23.693150] ---[ end trace 2f287167f09b7fb3 ]---


So, suspending test w/ compat-wireless drivers, doing w/ those in-tree w/ dbg symbols included and activated.

Cheers,

Nils

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Nils Radtke on 13 May 2010 11:10
Hi Reinette,

Attached the output from the debug-enabled in-tree iwlwifi driver connects.

The order of trial is: site A first, then site B. The sites have thus been visited
in the same order as last time and the commands executed have been equally the
same. The failures evenly.. All the log entries that caught my eye last time
can be found in the attached one also. I'm sending it bz2 compressed. My uplink
is a poor man's volume limited UMTS one.

The timestamp that is the last entry for site A log is: 4174.659838
Everthing after that timestamp is log for site B, 10 minutes by bike from site A.

We've been lucky, I could just finish site B survey as heaven opened it's doors such
wide that the streets flooded within seconds. Before that mosquitos took the chance
and bit me a dozen of times (*scratch*). I hope it was worth it and there's something
to be found in the logs. ;)

If there's anything else, let me know.

Cheers,

Nils

From: reinette chatre on 13 May 2010 12:40
On Thu, 2010-05-13 at 04:32 -0700, Nils Radtke wrote:
> short feedback:
>
> - recompiled kernel and config80211 as M
> - debug symbols included. Yet to try.
> - reboot
> Linux mypole 2.6.33.3 #22 SMP PREEMPT Thu May 13 12:52:22 CEST 2010 i686 GNU/Linux
> - renamed in-tree iwlagn and iwlcore, ran depmod -a, confirmed by looking into modules.dep

Note that compat-wireless installs its modules in updates/ and thus does
not overwrite your default ones. After default modules are unloaded the
ones in updates/ should be picked up first. No renaming or overwriting
of system's default modules should be done.

Following the instructions that come with compat-wireless should be all
you need to do.

Reinette


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Nils Radtke on 14 May 2010 13:50
Hi Reinette,

Might be of interest:

[63099.789939] eth1: associated
[63166.919257] iwlagn 0000:03:00.0: expected_tpt should have been calculated by now
[63180.322024] Hangcheck: hangcheck value past margin!
[63190.664526] iwlagn 0000:03:00.0: expected_tpt should have been calculated by now
[63193.255873] iwlagn 0000:03:00.0: expected_tpt should have been calculated by now
[63194.941768] iwlagn 0000:03:00.0: expected_tpt should have been calculated by now
[63195.099286] iwlagn 0000:03:00.0: expected_tpt should have been calculated by now
[63196.524065] iwlagn 0000:03:00.0: expected_tpt should have been calculated by now
[63197.417740] iwlagn 0000:03:00.0: expected_tpt should have been calculated by now
[63199.767526] iwlagn 0000:03:00.0: iwl_tx_agg_start on ra = 00:1a:70:aa:aa:aa tid = 0
[63205.689184] iwlagn 0000:03:00.0: iwl_tx_agg_start on ra = 00:1a:70:aa:aa:aa tid = 0
[63210.821316] iwlagn 0000:03:00.0: iwl_tx_agg_start on ra = 00:1a:70:aa:aa:aa tid = 0
[63228.178530] iwlagn 0000:03:00.0: iwl_tx_agg_start on ra = 00:1a:70:aa:aa:aa tid = 0

Happened on site B, with high throughput (280-340k/s). So, it's happening w/ both, fast
and slow conn speed.

Yes, I noticed and had a look into the compat-wireless scripts but preferred to do
it manually. Thank you for your explanation.

Cheers,

Nils

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: reinette chatre on 17 May 2010 19:20
Hi Nils,

On Thu, 2010-05-13 at 08:05 -0700, Nils Radtke wrote:
> Attached the output from the debug-enabled in-tree iwlwifi driver connects.

To keep track, this is 2.6.33.3.

>
> The order of trial is: site A first, then site B. The sites have thus been visited
> in the same order as last time and the commands executed have been equally the
> same. The failures evenly.. All the log entries that caught my eye last time
> can be found in the attached one also. I'm sending it bz2 compressed. My uplink
> is a poor man's volume limited UMTS one.

Thank you very much.

So from what I can tell (to summarize your previous emails) there are
three issues:

1) Error messages like:
iwlagn 0000:03:00.0: expected_tpt should have been calculated by now

2) Frequent deaths with code like:
eth1: deauthenticated from 00:40:96:aa:aa:aa (Reason: 2)

3) Error as follows:
[ 4148.141064] iwlagn 0000:03:00.0: TX Power requested while scanning!
[ 4148.141070] iwlagn 0000:03:00.0: Error sending TX power (-11)


To address (1), could you please run with attached debug patch and also
enable rate scaling debugging. That will be "modprobe iwlagn
debug=0x143fff).

Regarding (2): This is a common issue in busy environments where AP
decides to deathenticate station after it does not receive an ack for
data sent after a few retries. Was this test done in busy environment?

Regarding (3): Seems like driver is getting a request to scan after a
request to remove interface. I am still inquiring about this.

Reinette

First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: Staging: cxt1e1: Fix build error
Next: [PATCH 2.6.34-rc6] mxc: gadget: Fix bitfield for calculating maximum packet size