From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: crash in wireless-next
Date: Fri, 04 Nov 2011 11:16:44 -0700 [thread overview]
Message-ID: <4EB42C0C.40101@candelatech.com> (raw)
Anyone seen a crash like this? I was restarting my user-space
tools, and had just unloaded the drivers that had,
around 135 virtual stations created. Just my disable-ht
patch series applied on top of yesterday's wireless-testing.
I'll dig into it more when I get a chance, but let me know
if someone is already working on this...
BUG: unable to handle kernel NULL pointer dereference at 00000006
IP: [<c076b7e7>] wext_handle_ioctl+0xd9/0x17e
*pde = 00000000
Oops: 0000 [#1] SMP
Modules linked in: ath5k arc4 ath9k mac80211 ath9k_common ath9k_hw ath cfg80211 xt_CT iptable_raw bridge ]
Pid: 1335, comm: hald Tainted: G W 3.1.0-wl+ #3 To Be Filled By O.E.M. To Be Filled By O.E.M./To.
EIP: 0060:[<c076b7e7>] EFLAGS: 00010297 CPU: 0
EIP is at wext_handle_ioctl+0xd9/0x17e
EAX: f06a5000 EBX: 00000001 ECX: 00008b01 EDX: 00000002
ESI: f40b1ed4 EDI: 000008d3 EBP: f40b1e8c ESP: f40b1e74
DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
Process hald (pid: 1335, ti=f40b0000 task=f48fb340 task.ti=f40b0000)
Stack:
00008b01 00000001 00008b01 00000000 00008b01 c0a9c140 f40b1f08 c06f9523
bfdc339c 0017a0b9 c06ecfaa 000000d0 f40b1eb0 c0556c1d f0477440 bfdc339c
c06ed007 f40b1ee4 c04ad561 f15a2180 1b96bccf c0a3d9e4 00000020 00000000
Call Trace:
[<c06f9523>] dev_ioctl+0x529/0x561
[<c06ecfaa>] ? sk_prot_alloc+0x23/0xd1
[<c0556c1d>] ? security_sk_alloc+0x10/0x13
[<c06ed007>] ? sk_prot_alloc+0x80/0xd1
[<c04ad561>] ? kmem_cache_alloc+0x24/0x9d
[<c06e8e25>] ? kernel_sendmsg+0x37/0x37
[<c06e9000>] sock_ioctl+0x1db/0x1e7
[<c06e8e25>] ? kernel_sendmsg+0x37/0x37
[<c04c5996>] do_vfs_ioctl+0x464/0x4a9
[<c07919ac>] ? _raw_spin_unlock+0x8/0xa
[<c04b86a4>] ? fd_install+0x44/0x4a
[<c06e9d75>] ? sock_map_fd+0x1f/0x25
[<c06ea637>] ? sys_socket+0x43/0x5a
[<c06ea6c5>] ? sys_socketcall+0x77/0x1b6
[<c04c5a1c>] sys_ioctl+0x41/0x61
[<c07962d8>] sysenter_do_call+0x12/0x28
Code: 75 06 85 db 74 51 89 da 0f b7 7a 04 8d 99 00 75 ff ff 39 fb 73 04 8b 12 eb 11 0f b7 7a 06 8d 99 20
EIP: [<c076b7e7>] wext_handle_ioctl+0xd9/0x17e SS:ESP 0068:f40b1e74
CR2: 0000000000000006
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2011-11-04 18:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-04 18:16 Ben Greear [this message]
2011-11-04 19:32 ` crash in wireless-next Johannes Berg
2011-11-04 19:33 ` Johannes Berg
2011-11-04 19:43 ` Ben Greear
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=4EB42C0C.40101@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.