linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: 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 16:07:59 -0400	[thread overview]
Message-ID: <1248725279.7440.8.camel@mj> (raw)
In-Reply-To: <200907272035.41193.chris2553@googlemail.com>

On Mon, 2009-07-27 at 20:35 +0100, Chris Clayton wrote:
> On Monday 27 July 2009, Pavel Roskin wrote:
> >
> > 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.
> 
> I've taken some photos of the screen from the insertion of the card through to ejecting it, and 
> uploaded them to imageshack: They can be viewed at:
> 
> http://img145.imageshack.us/img145/8741/xdscn0647.jpg
> http://img170.imageshack.us/img170/1954/xdscn0648.jpg
> http://img195.imageshack.us/img195/807/xdscn0649.jpg
> http://img195.imageshack.us/img195/9625/xdscn0650.jpg
> http://img195.imageshack.us/img195/2717/xdscn0651.jpg
> http://img170.imageshack.us/img170/6103/xdscn0652.jpg
> http://img170.imageshack.us/img170/5844/xdscn0653.jpg
> 
> Between them they should show all the output to the console, although some do overlap a little.
> 
> I hope they are helpful in tracking down this problem.

Do you remove the card?  It's like the card is disconnected at some
point, either physically or logically.

It looks like a problem specific to the hardware, not anything in the
common wireless code.  I suggest that you post your question to
users@rt2x00.serialmonkey.com.  That's the mailing list for rt61pci and
other Ralink devices.

-- 
Regards,
Pavel Roskin

  reply	other threads:[~2009-07-27 20:08 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
2009-07-27 19:35                 ` Chris Clayton
2009-07-27 20:07                   ` Pavel Roskin [this message]
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=1248725279.7440.8.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).