From: Nils Radtke <lkml@Think-Future.de>
To: reinette.chatre@intel.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel BUG in iwl-agn-rs.c:2076, WAS: iwlagn + some accesspoint == hardlock
Date: Thu, 13 May 2010 13:32:57 +0200 [thread overview]
Message-ID: <20100513113257.GA7535@localhost> (raw)
In-Reply-To: <1273706072.2295.67.camel@rchatre-DESK>
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
next prev parent reply other threads:[~2010-05-13 11:33 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 19:17 kernel BUG in iwl-agn-rs.c:2076, WAS: iwlagn + some accesspoint == hardlock NilsRadtkelkml
2010-05-03 19:22 ` John W. Linville
2010-05-06 9:14 ` Christian Borntraeger
2010-05-06 16:28 ` reinette chatre
2010-05-11 15:50 ` Christian Borntraeger
2010-05-11 17:21 ` reinette chatre
2010-05-12 15:18 ` Christian Borntraeger
2010-05-10 18:36 ` Nils Radtke
2010-05-10 23:32 ` reinette chatre
2010-05-12 14:39 ` Nils Radtke
2010-05-12 23:14 ` reinette chatre
2010-05-13 10:34 ` Nils Radtke
2010-05-13 11:32 ` Nils Radtke [this message]
2010-05-13 16:31 ` reinette chatre
2010-05-14 17:45 ` Nils Radtke
2010-05-13 15:05 ` Nils Radtke
2010-05-17 23:19 ` reinette chatre
2010-05-20 12:15 ` Nils Radtke
2010-05-20 18:33 ` reinette chatre
2010-05-31 20:12 ` Nils Radtke
2010-06-02 17:51 ` reinette chatre
2010-06-04 16:57 ` Nils Radtke
2010-06-08 17:46 ` reinette chatre
2010-06-10 14:22 ` Nils Radtke
2010-06-10 16:19 ` reinette chatre
2010-05-20 12:31 ` Nils Radtke
2010-05-20 18:26 ` reinette chatre
2010-05-20 22:30 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2010-05-11 9:41 Nils Radtke
2010-04-29 18:26 kernel BUG in iwl-agn-rs.c:2076,was: iwlagn + some accesspoint = hardlock lkml
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100513113257.GA7535@localhost \
--to=lkml@think-future.de \
--cc=linux-kernel@vger.kernel.org \
--cc=reinette.chatre@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).