From patchwork Sat Oct 11 07:31:11 2014 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Oleksij Rempel X-Patchwork-Id: 5068551 Return-Path: X-Original-To: patchwork-linux-wireless@patchwork.kernel.org Delivered-To: patchwork-parsemail@patchwork2.web.kernel.org Received: from mail.kernel.org (mail.kernel.org [198.145.19.201]) by patchwork2.web.kernel.org (Postfix) with ESMTP id D48ADC11AC for ; Sat, 11 Oct 2014 07:31:24 +0000 (UTC) Received: from mail.kernel.org (localhost [127.0.0.1]) by mail.kernel.org (Postfix) with ESMTP id 464D8201DD for ; Sat, 11 Oct 2014 07:31:24 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 45A7A201D3 for ; Sat, 11 Oct 2014 07:31:23 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752340AbaJKHbT (ORCPT ); Sat, 11 Oct 2014 03:31:19 -0400 Received: from mout.gmx.net ([212.227.15.18]:56327 "EHLO mout.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752333AbaJKHbQ (ORCPT ); Sat, 11 Oct 2014 03:31:16 -0400 Received: from [192.168.1.221] ([80.136.215.246]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0Lmr1w-1Y6O0j3EZ2-00hARQ; Sat, 11 Oct 2014 09:31:13 +0200 Message-ID: <5438DCBF.5090404@rempel-privat.de> Date: Sat, 11 Oct 2014 09:31:11 +0200 From: Oleksij Rempel User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: "Schroer, Jens Peter" CC: linux-wireless@vger.kernel.org Subject: Re: Kernel Oops with ath9k_htc during AES decrypt on ARM / BeagleBone Black References: <51054a8c690db75aa1efacb98e4379c9@scypho.com> <54368960.4040109@rempel-privat.de> <828b549f60c81155be705f5173fe0e11@scypho.com> <54369F07.9080705@rempel-privat.de> <1772bbe6a9db0760b4712cf8fad81fbc@scypho.com> In-Reply-To: <1772bbe6a9db0760b4712cf8fad81fbc@scypho.com> X-Provags-ID: V03:K0:u0hAZiKPlhxjmu+hTOYdUJzzoMjKsfVVVfbcRrPYFVaG177m2pU t8PWSSS7rRvqkDOwZmOta62SV45AWnCY8KDHPUi8T/eJupO+LW4Km9Ca9BnUt3hUNHDMGUd l9JrNOoJcGf+yLzapkFGSJGIUbgFIPTQAvcWN2tLriF3GNtMGrMka1OmPjcPObLVq2G0WGL JEz405F1kacSE1jWTjeMg== X-UI-Out-Filterresults: notjunk:1; Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org X-Spam-Status: No, score=-6.9 required=5.0 tests=BAYES_00, RCVD_IN_DNSWL_HI, T_RP_MATCHES_RCVD, T_TVD_MIME_EPI, UNPARSEABLE_RELAY autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP Am 10.10.2014 um 14:42 schrieb Schroer, Jens Peter: > Hi Oleksij, > > I have tried to recover the full dmesg, but it seems to be lost. > I am not sure if it disappeared with during the last reboot or was not > synced back to the flash due to the kernel panic. > I tried to reproduce the kernel oops, but get stuck with the problem I > mentioned in my other email. > Is there a way of printing / tracing bad packages, so that when this > crash occures the next time, I have hopefully more information available? > Also, just for completeness, the issue that stops me from trying to > reproduce the kernel oops: I don't think this two reports are separate issues. In both cases it is triggered by processing of broken RX packages. In one case, wrong rate, in other case wrong length. Lets start with rate, since it seems to be easier to reproduce. Theoretically packets with brocken rate should be just filtered out by ath9k_cmn_process_rate. Lets try this patch: diff --git a/drivers/net/wireless/ath/ath9k/common.c b/drivers/net/wireless/ath/ index c6dd7f1..f7c4db0 100644 --- a/drivers/net/wireless/ath/ath9k/common.c +++ b/drivers/net/wireless/ath/ath9k/common.c @@ -205,6 +205,7 @@ int ath9k_cmn_process_rate(struct ath_common *common, } } + printk("Warning! Unsuported rate.\n"); return -EINVAL; } EXPORT_SYMBOL(ath9k_cmn_process_rate);