From: Jonathan Nieder <jrnieder@gmail.com>
To: Christoph Anton Mitterer <calestyo@scientia.net>
Cc: Stanislaw Gruszka <sgruszka@redhat.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, 29 Dec 2011 14:11:49 -0600 [thread overview]
Message-ID: <20111229201149.GB1674@elie.Belkin> (raw)
In-Reply-To: <1325171851.3907.33.camel@fermat.scientia.net>
Christoph Anton Mitterer wrote:
> The logging is basically identical to what I've send before.
>
> So either there is some weird hardware damage,.. or (as I suggested
> before) it might be just some different revision or so of the chipset,
> behaving different?!
>
> Guess it's pointless to send you the same logging output again, but if
> you'd like to I can do so.
Yes, please do, or provide a link and summary so we don't have to hunt
it down.
Hope that helps,
Jonathan
next prev parent reply other threads:[~2011-12-29 20:11 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
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 [this message]
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=20111229201149.GB1674@elie.Belkin \
--to=jrnieder@gmail.com \
--cc=Gregory.Dietsche@cuw.edu \
--cc=calestyo@scientia.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=sgruszka@redhat.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