From: Johannes Berg <johannes@sipsolutions.net>
To: Toan Pham <tpham3783@gmail.com>
Cc: Cong Wang <xiyou.wangcong@gmail.com>,
pavani <pavani.muthyala@redpinesignals.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-wireless@vger.kernel.org,
Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: kmalloc panic
Date: Mon, 08 Jun 2015 12:06:44 +0200 [thread overview]
Message-ID: <1433758004.2106.7.camel@sipsolutions.net> (raw)
In-Reply-To: <CAGNmLEP0o9bnGEh-P=AVxUp-_rh9pO-zOiwUq_HboptRQ60dTA@mail.gmail.com> (sfid-20150607_011021_446015_1BD068E9)
On Sat, 2015-06-06 at 19:10 -0400, Toan Pham wrote:
> I am experiencing a similar issue on another system (at91sam9n12) that
> uses Redpine Signal Wireless Driver 1.1.0. I do not know the root
> cause yet, but it may be related to the Redpine Signals driver. Will
> update this mailing list if the problem is with the redpine driver.
> thanks
Please don't top-post.
It's almost certainly related to the redpine driver, but apparently not
using the upstream "rsi" driver ... you're in the wrong place here.
I'll note that the driver should probably be converted to cfg80211
instead of having its own wext handling (which I'd think is causing this
issue)
johannes
prev parent reply other threads:[~2015-06-08 10:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5565CAA1.9070409@redpinesignals.com>
2015-05-28 5:15 ` kmalloc panic Cong Wang
2015-05-28 7:21 ` pavani
2015-05-28 7:35 ` Richard Weinberger
2015-05-28 9:03 ` Johannes Berg
2015-06-06 23:10 ` Toan Pham
2015-06-08 10:06 ` Johannes Berg [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=1433758004.2106.7.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pavani.muthyala@redpinesignals.com \
--cc=tpham3783@gmail.com \
--cc=xiyou.wangcong@gmail.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).