On Thu, Nov 13, 2008 at 9:46 PM, Dan McGee <dpmcgee@xxxxxxxxx> wrote: > Also reported here a few times, I've been seeing this bug every time I > try to load up the ath5k module in my kernel: > http://www.kerneloops.org/search.php?search=ieee80211_register_hw&btnG=Function+Search > > If you guys have any suggestions, I'd love to hear them. I > disassembled the code in question but am not very good with these > things. It looks to be somewhere between lines 804-825 in > net/mac80211/main.c. > > -Dan > > ath5k_pci 0000:01:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 > ath5k_pci 0000:01:00.0: setting latency timer to 64 > ath5k_pci 0000:01:00.0: registered as '' > BUG: unable to handle kernel NULL pointer dereference at 00000000 > IP: [<b80c1252>] :mac80211:ieee80211_register_hw+0x10f/0x2d6 > *pde = 00000000 > Oops: 0000 [#1] PREEMPT > Modules linked in: ath5k(+) mac80211 > > Pid: 818, comm: modprobe Not tainted (2.6.27.6eee #3) > EIP: 0060:[<b80c1252>] EFLAGS: 00010286 CPU: 0 > EIP is at ieee80211_register_hw+0x10f/0x2d6 [mac80211] I don't know assembly but if you compile with debugging symbols you can pin point the line at which your EIP points to with gdb. Run gdb /lib/modules/`uname -r`/kernel/net/mac80211.ko Then l *(ieee80211_register_hw+0x10f) If our offsets are the same then its probably on line 791: (gdb) l *(ieee80211_register_hw+0x10f) 0x2df is in ieee80211_register_hw (net/mac80211/main.c:791). 786 mdev->type = ARPHRD_IEEE80211; 787 mdev->header_ops = &ieee80211_header_ops; 788 mdev->set_multicast_list = ieee80211_master_set_multicast_list; 789 790 name = wiphy_dev(local->hw.wiphy)->driver->name; 791 local->hw.workqueue = create_freezeable_workqueue(name); 792 if (!local->hw.workqueue) { 793 result = -ENOMEM; 794 goto fail_workqueue; 795 } I have run into this before but on a very rare occasion and it was with iwlagn, and I wasn't able to find the culprit. Do you run into this all the time? Luis -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
