From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Christoph Anton Mitterer <calestyo@scientia.net>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
Greg Dietsche <Gregory.Dietsche@cuw.edu>,
linux-kernel@vger.kernel.org
Subject: Re: iwl4965: "MAC is in deep sleep!" freezes
Date: Thu, 8 Sep 2011 10:49:13 +0200 [thread overview]
Message-ID: <20110908084913.GB2195@redhat.com> (raw)
In-Reply-To: <265f56a4dc9f5d3edeca3d101e445353@imap.dd24.net>
On Mon, Sep 05, 2011 at 09:42:01AM +0000, Christoph Anton Mitterer wrote:
> On Mon, 5 Sep 2011 11:19:18 +0200, Stanislaw Gruszka <sgruszka@redhat.com>
> wrote:
> > this look like firmware hang. This happen just after module load, that's
> > good news, because it allow to log relative small amount debug messages
> > to see what possibly driver do wrong to crash firmware.
> Note, that the effects of - usually but not always - frozen system while
> the errors are printed (sometimes keyboard input seems still be possible
> during that) ... happen over and over again... say about every 10 minutes
> or so.
> Not just the first time the modules is loaded.
> Is the firmware loaded over and over again?
I think is not, but even if is, kernel should not crash. Can you grab
crash logs using photo camera, serial cable or netconsole, to allow to
see where exactly crash happen and fix it.
> > Please configure syslog to log kernel debug messages.
> Will mail it later.
Firmware hang seems to happen when REPLY_LEDS_CMD command is send.
No idea if attached patch could help or not, but is worth to try it.
It prevent to send LED command asynchronously, when possibly some
other commands are pending in firmware.
If it does not help, please provide the same way captured debug
messages from 2.6.38 kernel, where drivers works. I'll compare
it with broken driver logs to figure out what broken driver
do differently.
Thanks
Stanislaw
next prev parent reply other threads:[~2011-09-08 8:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bbdbd01d4965ae789384bc1f9d0a2426@imap.dd24.net>
2011-09-02 23:38 ` iwl4965: "MAC is in deep sleep!" freezes Jonathan Nieder
2011-09-03 12:45 ` Christoph Anton Mitterer
2011-09-05 9:24 ` Stanislaw Gruszka
2011-09-05 9:19 ` Stanislaw Gruszka
2011-09-05 9:42 ` Christoph Anton Mitterer
2011-09-08 8:49 ` Stanislaw Gruszka [this message]
2011-09-08 16:19 ` Stanislaw Gruszka
2011-09-24 16:50 ` Stanislaw Gruszka
2011-11-14 0:02 ` Christoph Anton Mitterer
2011-11-14 1:46 ` Jonathan Nieder
2011-11-16 18:08 ` Christoph Anton Mitterer
2011-11-18 7:45 ` Stanislaw Gruszka
2011-12-29 15:17 ` Christoph Anton Mitterer
2011-12-29 20:11 ` Jonathan Nieder
2012-01-03 10:51 ` Stanislaw Gruszka
2012-01-04 1:22 ` Christoph Anton Mitterer
2012-01-05 10:14 ` Stanislaw Gruszka
2012-01-16 22:08 ` Christoph Anton Mitterer
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=20110908084913.GB2195@redhat.com \
--to=sgruszka@redhat.com \
--cc=Gregory.Dietsche@cuw.edu \
--cc=calestyo@scientia.net \
--cc=jrnieder@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).