linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stanislaw Gruszka <sgruszka@redhat.com>
To: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Intel Linux Wireless <ilw@linux.intel.com>
Subject: Re: Lots of trans->state != IWL_TRANS_FW_ALIVE warnings
Date: Mon, 15 Oct 2012 17:37:53 +0200	[thread overview]
Message-ID: <20121015153752.GE12560@redhat.com> (raw)
In-Reply-To: <20121015152336.GC12560@redhat.com>

On Mon, Oct 15, 2012 at 05:23:36PM +0200, Stanislaw Gruszka wrote:
> On Mon, Oct 15, 2012 at 03:14:51PM +0000, Grumbach, Emmanuel wrote:
> > > I glanced at the bugs and I can only see the trace dump. I am pretty sure
> > > there is an issue before the dump - fw assert of something like that. Can it be
> > > possible to get the full log?
> > > 
> > 
> > Can you ask people to try the attached patch?
> > This will let us know where the fw is brought down.
> 
> Yes, I'll build kernel with that patch and request for test and dmesg.

debug=0x400 is enough or do you want also some other flags?

Stanislaw

  reply	other threads:[~2012-10-15 15:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-15 14:47 Lots of trans->state != IWL_TRANS_FW_ALIVE warnings Stanislaw Gruszka
2012-10-15 14:56 ` Grumbach, Emmanuel
2012-10-15 15:14 ` Grumbach, Emmanuel
2012-10-15 15:23   ` Stanislaw Gruszka
2012-10-15 15:37     ` Stanislaw Gruszka [this message]
2012-10-15 18:53       ` Grumbach, Emmanuel
2012-10-17  6:58         ` Stanislaw Gruszka
2012-10-17  7:48           ` Grumbach, Emmanuel

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=20121015153752.GE12560@redhat.com \
    --to=sgruszka@redhat.com \
    --cc=emmanuel.grumbach@intel.com \
    --cc=ilw@linux.intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    /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).