From: Helmut Schaa <helmut.schaa@googlemail.com>
To: Tim Blechmann <tim@klingt.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: rt61pci issue
Date: Thu, 11 Nov 2010 16:13:25 +0100 [thread overview]
Message-ID: <AANLkTikqx43LwfyB4979Mazhch41cGaa7txP6zjCa99F@mail.gmail.com> (raw)
In-Reply-To: <201011111556.31601.tim@klingt.org>
On Thu, Nov 11, 2010 at 3:56 PM, Tim Blechmann <tim@klingt.org> wrote:
>> Mind to put a (maybe rate limited) printk into the interrupt thread
>> that prints out "reg"
>> and "reg_mcu" so that we can see which interrupts get triggered?
>
> log attached, generated with:
Thanks. Unfortunately nothing special in there. Mostly RX and TX interrupts. So
there must be something else ...
Helmut
next prev parent reply other threads:[~2010-11-11 15:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 13:02 rt61pci issue Tim Blechmann
2010-11-11 13:45 ` Helmut Schaa
[not found] ` <201011111556.31601.tim@klingt.org>
2010-11-11 15:13 ` Helmut Schaa [this message]
2010-11-12 6:47 ` Helmut Schaa
2010-11-12 7:03 ` Helmut Schaa
2010-11-25 17:19 ` Tim Blechmann
2010-11-28 19:14 ` Helmut Schaa
2011-02-17 10:07 ` Tim Blechmann
2010-11-12 13:49 ` Helmut Schaa
2010-11-12 16:03 ` Tim Blechmann
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=AANLkTikqx43LwfyB4979Mazhch41cGaa7txP6zjCa99F@mail.gmail.com \
--to=helmut.schaa@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=tim@klingt.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).