linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Emmanuel Grumbach <egrumbach@gmail.com>
To: Petko Manolov <petkan@nucleusys.com>,
	"Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"ilw@linux.intel.com" <ilw@linux.intel.com>,
	"Berg, Johannes" <johannes.berg@intel.com>
Subject: Re: iwlwifi crash with 3.13
Date: Thu, 23 Jan 2014 22:07:52 +0200	[thread overview]
Message-ID: <52E17698.9070607@gmail.com> (raw)
In-Reply-To: <20140123200045.GA4064@localhost>



On 01/23/2014 10:00 PM, Petko Manolov wrote:
> On 14-01-23 12:45:30, Grumbach, Emmanuel wrote:
>>>
>>> Ok - thanks.
>>> Can I see the output of
>>>
>>> cat /sys/kernel/debug/iwlwifi/*/iwlmvm/nvm_sw | hexdump | head -5
>>>
> 
> I don't have iwlwifi entry in /sys/kernel/debug.  My kernel is probably missing some config switches.
> 
>> If it easier - you can also reload the module and add debug=0x1:
> 
> Well, it wasn't easier.  I got multiple "invalid module parameter" sort of error before i realized CONFIG_IWLWIFI_DEBUG should be on. ;)
> 
>> modprobe iwlwifi debug=0x1.
> 
> Attached is the dmesg output.  It is 'xz' compressed as it was 150KB hog.

Unfortunately, I can't see the loading of iwlwifi.

> 
>> Note that you first need to unload iwlmvm, then, unload iwlwifi. After that you can reload iwlwifi.
>> I prefer the debufgs line above though, I'll get a bit more information.
> 
> Mgh, no such entry.  If you can point me as to what else i need to enable in my kernel config...
> 

Doesn't matter any more - I found the issue.

  reply	other threads:[~2014-01-23 20:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-23  9:16 iwlwifi crash with 3.13 Petko Manolov
2014-01-23  9:22 ` Grumbach, Emmanuel
2014-01-23 12:31   ` Petko Manolov
2014-01-23 12:34     ` Grumbach, Emmanuel
2014-01-23 12:45     ` Grumbach, Emmanuel
2014-01-23 19:11       ` Emmanuel Grumbach
2014-01-23 20:19         ` Petko Manolov
2014-01-23 20:00       ` Petko Manolov
2014-01-23 20:07         ` Emmanuel Grumbach [this message]
2014-01-23 20:21           ` Petko Manolov
2014-02-07 21:40             ` Petko Manolov
2014-02-08 18:10               ` Emmanuel Grumbach
2014-02-09 13:26                 ` Petko Manolov
2014-02-09 13:31                   ` Grumbach, Emmanuel
2014-02-09 13:49                     ` Petko Manolov
2014-02-07 11:08           ` Niklas Claesson
2014-02-08 18:11             ` Emmanuel Grumbach

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=52E17698.9070607@gmail.com \
    --to=egrumbach@gmail.com \
    --cc=emmanuel.grumbach@intel.com \
    --cc=ilw@linux.intel.com \
    --cc=johannes.berg@intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=petkan@nucleusys.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).