Return-path: Received: from mail-ie0-f169.google.com ([209.85.223.169]:41141 "EHLO mail-ie0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752009AbaDMItE (ORCPT ); Sun, 13 Apr 2014 04:49:04 -0400 Received: by mail-ie0-f169.google.com with SMTP id to1so7089931ieb.14 for ; Sun, 13 Apr 2014 01:49:02 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: Date: Sun, 13 Apr 2014 12:49:02 +0400 Message-ID: (sfid-20140413_104947_466441_BAFBDB02) Subject: Re: iwlwifi null pointer dereference From: Alexander Monakov To: Emmanuel Grumbach Cc: linux-wireless Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Sun, Apr 13, 2014 at 11:23 AM, Emmanuel Grumbach wrote: > On Sat, Apr 12, 2014 at 6:11 PM, Alexander Monakov wrote: >> Hello, >> >> On a laptop with Wireless-N 135 card and 3.14.0 kernel I'm getting a >> kernel oops on cold boot ans wireless seems unusable, but suprisingly >> everything works fine after a reboot: > > Wow - interesting - you are getting an interrupt before we even enable them. > > Does this help you? Yes, it did help. Thanks. (regarding interrupts, after installing an mSATA SSD that goes into the mini-PCIe slot next to the wireless card, I've noticed that "events" (mostly interrupts I guess) shown by PowerTop for the wireless card and the SATA controller seem correlated, even though the disk should be idle; I wonder what that means) Alexander