From: Tim Blechmann <tim@klingt.org>
To: linux-wireless@vger.kernel.org
Subject: Re: rt61pci bug
Date: Sat, 05 Dec 2009 20:28:38 +0100 [thread overview]
Message-ID: <hfec9b$kdo$1@ger.gmane.org> (raw)
In-Reply-To: <69e28c910911290859mc1da58ree7b2d3fa8dc371d@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 6635 bytes --]
On 11/29/2009 05:59 PM, Gábor Stefanik wrote:
> On Sun, Nov 29, 2009 at 3:01 PM, Tim Blechmann <tim-xpEK/MU0Hawdnm+yROfE0A@public.gmane.org> wrote:
>> On 11/04/2009 07:00 PM, Tim Blechmann wrote:
>>>> running the rt61pci module on 2.6.31.5 works fine, but using the recent
>>>> linus/master (2.6.32-rc5) results in this:
>>>
>>> same issue with 2.6.32-rc5 ... new bootlog with more debugging info
>>> attached ...
>>
>> i was still able to reproduce this issue with 2.6.32-rc8 ... it would
>> be nice, if someone could have a look into this issue before 2.6.32 is
>> released ...
>>
>> dmesg from 2.6.32-rc8:
>> [ 10.249098] rt61pci 0000:06:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
>> [ 10.257182] phy0 -> rt61pci_validate_eeprom: EEPROM recovery - NIC: 0xff80
>> [ 10.257184] phy0 -> rt61pci_validate_eeprom: EEPROM recovery - Led: 0xe0ff
>> [ 10.257187] phy0 -> rt2x00_set_chip: Info - Chipset detected - rt: 0302, rf: 0003, rev: 0002561c.
>> [ 10.351794] Registered led device: rt61pci-phy0::radio
>> [ 10.351839] Registered led device: rt61pci-phy0::assoc
>> [ 14.342046] rt61pci 0000:06:00.0: firmware: requesting rt2561.bin
>> [ 14.395533] phy0 -> rt2x00lib_request_firmware: Info - Firmware detected - version: 0.8.
>> [ 14.421238] phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 0 - CWmin: 3, CWmax: 4, Aifs: 2, TXop: 102.
>> [ 14.421245] phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 1 - CWmin: 4, CWmax: 5, Aifs: 2, TXop: 188.
>> [ 14.421252] phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 2 - CWmin: 5, CWmax: 10, Aifs: 3, TXop: 0.
>> [ 14.421258] phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 3 - CWmin: 5, CWmax: 10, Aifs: 7, TXop: 0.
>> [ 273.404685] phy0 -> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 2.
>> [ 273.404687] Please file bug report to http://rt2x00.serialmonkey.com.
>> [ 282.143549] wlan0: no IPv6 routers present
>> [ 357.304908] phy0 -> rt61pci_txdone: Warning - TX status report missed for entry 2
>> [ 357.333806] phy0 -> rt61pci_txdone: Warning - TX status report missed for entry 9
>> [ 360.172776] phy0 -> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 2.
>> [ 360.172778] Please file bug report to http://rt2x00.serialmonkey.com.
>> [ 360.172782] phy0 -> rt2x00mac_tx_rts_cts: Warning - Failed to send RTS/CTS frame.
>> [ 383.880010] No probe response from AP 00:24:fe:09:94:18 after 500ms, disconnecting.
>> [ 383.880026] phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 0 - CWmin: 2, CWmax: 3, Aifs: 2, TXop: 47.
>> [ 383.880034] phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 1 - CWmin: 3, CWmax: 4, Aifs: 2, TXop: 94.
>> [ 383.880042] phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 2 - CWmin: 4, CWmax: 10, Aifs: 3, TXop: 0.
>> [ 383.880050] phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 3 - CWmin: 4, CWmax: 10, Aifs: 7, TXop: 0.
>> [ 385.220460] wlan0: direct probe to AP 00:24:fe:09:94:18 (try 1)
>> [ 385.421337] wlan0: direct probe to AP 00:24:fe:09:94:18 (try 2)
>> [ 385.621304] wlan0: direct probe to AP 00:24:fe:09:94:18 (try 3)
>> [ 385.821264] wlan0: direct probe to AP 00:24:fe:09:94:18 timed out
>>
>>
>> lspci -vvv:
>>
>> 06:00.0 Network controller: RaLink RT2561/RT61 rev B 802.11g
>> Subsystem: D-Link System Inc Device 3c09
>> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
>> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
>> Latency: 64, Cache Line Size: 64 bytes
>> Interrupt: pin A routed to IRQ 16
>> Region 0: Memory at fb6f8000 (32-bit, non-prefetchable) [size=32K]
>> Capabilities: [40] Power Management version 2
>> Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
>> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>> Kernel driver in use: rt61pci
>> Kernel modules: rt61pci
>>
>> thanks, tim
>
> Could you please try a bisect between 2.6.31 and 2.6.32-rc5? That
> should reveal the faulty commit.
>
>>
>> --
>> tim@klingt.org
>> http://tim.klingt.org
>>
>> Happiness is a byproduct of function, purpose, and conflict; those who
>> seek happiness for itself seek victory without war.
>> William S. Burroughs
btw, on v2.6.31.6-rt19, i get the following messages continuously:
[35097.254691] phy0 -> rt61pci_txdone: Warning - TX status report missed for entry 15
[35097.352620] phy0 -> rt61pci_txdone: Warning - TX status report missed for entry 21
[35097.400820] phy0 -> rt61pci_txdone: Warning - TX status report missed for entry 11
[35097.682924] phy0 -> rt61pci_txdone: Warning - TX status report missed for entry 17
[35098.050321] phy0 -> rt61pci_txdone: Warning - TX status report missed for entry 5
[35098.203187] phy0 -> rt61pci_txdone: Warning - TX status report missed for entry 23
[35098.390729] phy0 -> rt61pci_txdone: Warning - TX status report missed for entry 15
[35098.572894] phy0 -> rt61pci_txdone: Warning - TX status report missed for entry 15
[35098.735895] phy0 -> rt61pci_txdone: Warning - TX status report missed for entry 19
[35099.069564] phy0 -> rt61pci_txdone: Warning - TX status report missed for entry 7
[35099.407685] phy0 -> rt61pci_txdone: Warning - TX status report missed for entry 9
[35099.408726] phy0 -> rt61pci_txdone: Warning - TX status report missed for entry 13
[35099.417144] phy0 -> rt61pci_txdone: Warning - TX status report missed for entry 17
[35099.420996] phy0 -> rt61pci_txdone: Warning - TX status report missed for entry 21
[35099.518701] phy0 -> rt61pci_txdone: Warning - TX status report missed for entry 23
[35100.012178] phy0 -> rt61pci_txdone: Warning - TX status report missed for entry 11
[35101.354838] phy0 -> rt61pci_txdone: Warning - TX status report missed for entry 15
[35101.448263] phy0 -> rt61pci_txdone: Warning - TX status report missed for entry 7
[35101.498144] phy0 -> rt61pci_txdone: Warning - TX status report missed for entry 13
[35102.168253] phy0 -> rt61pci_txdone: Warning - TX status report missed for entry 9
[35102.548745] phy0 -> rt61pci_txdone: Warning - TX status report missed for entry 9
what does this tell me? i am not able to get any network connection
with any 2.6.32-rc build, with (and without) the previously posted
error messages
tim
--
tim@klingt.org
http://tim.klingt.org
Who need fossil fuel when the sun ain't goin' nowhere
Amiri Baraka
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-12-05 19:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-25 11:02 rt61pci bug Tim Blechmann
2009-11-04 18:00 ` Tim Blechmann
2009-11-04 18:52 ` John W. Linville
2009-11-04 19:27 ` [rt2x00-users] " Matthijs Kooijman
2009-11-04 20:39 ` Luis Correia
[not found] ` <880c1630911060803k32b3ee46g7cfdfec2485f311@mail.gmail.com>
2009-11-06 16:04 ` Luis Correia
2009-11-29 14:01 ` Tim Blechmann
2009-11-29 16:59 ` Gábor Stefanik
2009-11-29 17:28 ` Tim Blechmann
2009-11-30 16:46 ` Tim Blechmann
2009-12-05 19:28 ` Tim Blechmann [this message]
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='hfec9b$kdo$1@ger.gmane.org' \
--to=tim@klingt.org \
--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).