From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752581AbbFHKG5 (ORCPT ); Mon, 8 Jun 2015 06:06:57 -0400 Received: from s3.sipsolutions.net ([5.9.151.49]:46135 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751841AbbFHKGt (ORCPT ); Mon, 8 Jun 2015 06:06:49 -0400 Message-ID: <1433758004.2106.7.camel@sipsolutions.net> Subject: Re: kmalloc panic From: Johannes Berg To: Toan Pham Cc: Cong Wang , pavani , LKML , linux-wireless@vger.kernel.org, Linux Kernel Network Developers Date: Mon, 08 Jun 2015 12:06:44 +0200 In-Reply-To: (sfid-20150607_011021_446015_1BD068E9) References: <5565CAA1.9070409@redpinesignals.com> <1432803793.2459.2.camel@sipsolutions.net> (sfid-20150607_011021_446015_1BD068E9) Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.9-1+b1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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