From: Pavel Roskin <proski@gnu.org>
To: Chris Clayton <chris2553@googlemail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: 2.6.31-rc2: Possible regression in rt61pci driver
Date: Mon, 27 Jul 2009 10:27:40 -0400 [thread overview]
Message-ID: <1248704860.2834.6.camel@mj> (raw)
In-Reply-To: <c6b1100b0907270235l19e9c2d9kb33dae2d6a0f78@mail.gmail.com>
On Mon, 2009-07-27 at 10:35 +0100, Chris Clayton wrote:
> I've built and installed a kernel with all the various types of
> MAC80211 debugging turned on (in addition to the RT61 driver's) and
> with CONFIG_MAC80211_DEFAULT_PS enabled. The attached file is the
> output from dmesg just after a freeze occurs. (The pcmcia card eject
> represents me ejecting the wireless card, so that the freeze "thaws"
> and I can capture the output from dmesg).
>
> Let me know if any additional diagnostics are needed. I have enabled
> MAC80211 debugfs too.
I could not reproduce the freezing with CONFIG_MAC80211_DEFAULT_PS
enabled. That said, I'm using wireless-testing with a patch for the
scanning state machine (hopefully it will be committed today).
The output of dmesg doesn't show anything interesting. The stack dump
from the video card is unlikely to be related.
But I think you may be getting something when the freeze happen. But to
see it, you need to be on a text console. There are other ways to
capture the kernel messages, which are described in the file
Documentation/oops-tracing.txt in the Linux sources.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2009-07-27 14:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 8:27 2.6.31-rc2: Possible regression in rt61pci driver Chris Clayton
2009-07-14 11:04 ` Chris Clayton
2009-07-21 11:39 ` Chris Clayton
2009-07-26 19:15 ` Chris Clayton
2009-07-26 20:10 ` Pavel Roskin
2009-07-26 21:33 ` Chris Clayton
2009-07-27 0:06 ` Pavel Roskin
2009-07-27 9:35 ` Chris Clayton
2009-07-27 14:27 ` Pavel Roskin [this message]
2009-07-27 19:35 ` Chris Clayton
2009-07-27 20:07 ` Pavel Roskin
2009-07-27 20:22 ` Chris Clayton
2009-07-27 20:30 ` Pavel Roskin
2009-07-27 20:32 ` Johannes Berg
2009-07-28 11:03 ` Chris Clayton
2009-07-28 11:11 ` Luis Correia
2009-07-28 13:34 ` Chris Clayton
2009-07-28 13:38 ` Luis Correia
2009-07-28 14:15 ` Chris Clayton
2009-07-29 7:03 ` Chris Clayton
2009-07-29 7:21 ` Johannes Berg
2009-07-29 7:45 ` Kalle Valo
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=1248704860.2834.6.camel@mj \
--to=proski@gnu.org \
--cc=chris2553@googlemail.com \
--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).