linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Alejandro Riveira Fernández" <alejandro.riveira@gmail.com>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linville@tuxdriver.com, Greg KH <greg@kroah.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [2.6.27-rc7 vs 2.6.29 Regresion] Wifi Network Slownes rt2500pci
Date: Tue, 26 May 2009 14:43:11 +0200	[thread overview]
Message-ID: <1243341791.7607.4.camel@varda> (raw)
In-Reply-To: <200905261235.36658.IvDoorn@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]

El mar, 26-05-2009 a las 12:35 +0200, Ivo van Doorn escribió:

> > What causes the regression then?
> 
> No idea. Apparently the invalid bitmask is accepted by the device under
> certain conditions. Which would be very odd.... But since dozens
> of people reported this problem for 2.6.27 as well, it probably depends
> heavily on the actual chipset revision or configuration.
> 
> > Anyway For the script to work what config options do I need? debugfs?
> > Anything else ?
> 
> CONFIG_DEBUGFS
> CONFIG_MAC80211_DEBUGFS
> CONFIG_RT2X00_LIB_DEBUGFS
> 
> And thats it, make sure debugfs is mounted and just run the script.
> The script will detect mount location and rt2x00 interface.


That's what I get[1] with the good kernel but I think the script failed
because I got a very short output

$ sudo bash rt2x00_regdump.sh | xclip

kernel: 2.6.29.4-00258-ga2c0a36
driver: rt2500pci
version: 2.2.3
compiled: May 26 2009 13:05:03
dev_flags: 0x00000a2f
rt chip: 0201
rf chip: 0003
revision:00000004

csr length: 93
eeprom length: 256
bbp length: 64
rf length: 5


And nothing more...

> 
> Ivo

Alejandro

[1] Had to install gawk mawk does not have --posix. 

[-- Attachment #2: Esto es una parte de mensaje firmado digitalmente --]
[-- Type: application/pgp-signature, Size: 835 bytes --]

  reply	other threads:[~2009-05-26 12:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-25 10:34 [2.6.27-rc7 vs 2.6.29 Regresion] Wifi Network Slownes rt2500pci Alejandro Riveira Fernández
2009-05-25 11:23 ` Ivo van Doorn
2009-05-25 12:42   ` Alejandro Riveira Fernández
2009-05-26  8:58     ` Ivo van Doorn
2009-05-26 10:17       ` Alejandro Riveira Fernández
2009-05-26 10:35         ` Ivo van Doorn
2009-05-26 12:43           ` Alejandro Riveira Fernández [this message]
2009-05-26 12:45             ` Ivo van Doorn
2009-05-26 15:23               ` Alejandro Riveira Fernández
2009-06-02 14:01                 ` Alejandro Riveira Fernández
2009-06-02 16:34                   ` Ivo van Doorn
2009-06-02 16:51                     ` Alejandro Riveira Fernández
2009-06-02 21:53                       ` Ivo van Doorn
2009-06-02 22:22                         ` Alejandro Riveira Fernández
2009-06-03  5:45                           ` Ivo van Doorn

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=1243341791.7607.4.camel@varda \
    --to=alejandro.riveira@gmail.com \
    --cc=greg@kroah.com \
    --cc=ivdoorn@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=rjw@sisk.pl \
    /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).