From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: crash in wireless-next
Date: Fri, 04 Nov 2011 12:43:20 -0700 [thread overview]
Message-ID: <4EB44058.1040705@candelatech.com> (raw)
In-Reply-To: <1320435238.3969.126.camel@jlt3.sipsolutions.net>
On 11/04/2011 12:33 PM, Johannes Berg wrote:
> On Fri, 2011-11-04 at 20:32 +0100, Johannes Berg wrote:
>> On Fri, 2011-11-04 at 11:16 -0700, Ben Greear wrote:
>>> 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...
>>
>> The only crash in wext I ever saw was recently with compat but I don't
>> think that looked similar.
>
> I guess you don't have CONFIG_COMPAT, but in that case I think so much
> gets inlined into wext_handle_ioctl() that I have no idea what could
> possibly crash. Disassembly of the place that crashed (preferably with
> -S if you have it) would be useful.
It might have been some issue with just copying over modules. I installed
a full kernel and the crash went away..at least for a bit. System crashed
while I was driving home, but serial console is at work..so will check it
later to see if it was the same issue.
I'll build w/debug and dis-assemble it if the problem persists.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2011-11-04 19:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-04 18:16 crash in wireless-next Ben Greear
2011-11-04 19:32 ` Johannes Berg
2011-11-04 19:33 ` Johannes Berg
2011-11-04 19:43 ` Ben Greear [this message]
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=4EB44058.1040705@candelatech.com \
--to=greearb@candelatech.com \
--cc=johannes@sipsolutions.net \
--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 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).