Bug 14460 - No wireless connection with Ralink RT2500 since update to kernel 2.6.31
No wireless connection with Ralink RT2500 since update to kernel 2.6.31
Status: CLOSED CODE_FIX
Product: Platform Specific/Hardware
Classification: Unclassified
Component: x86-64
All Linux
: P1 high
Assigned To: platform_x86_64@kernel-bugs.osdl.org
:
Depends on:
Blocks: 13615
  Show dependency treegraph
 
Reported: 2009-10-24 21:18 UTC by Filipp Andjelo
Modified: 2011-03-30 23:56 UTC (History)
8 users (show)

See Also:
Kernel Version: 2.6.31.5
Tree: Mainline
Regression: Yes


Attachments
reports and output (3.65 KB, text/plain)
2009-10-24 22:49 UTC, Filipp Andjelo
Details

Description Filipp Andjelo 2009-10-24 21:18:00 UTC
Description:
After the kernel update to 2.6.31 my wireless network is dead. Till now, I didn't find anything that could bring a solution or even s.t. about the root of the problem. Module seems to be initialized successfully, but no even a scan for networks can be done. The only error I could find is a repeating crap in the dmesg (see attachment).
Comment 1 Filipp Andjelo 2009-10-24 21:20:29 UTC
I had to fallback to kernel 2.6.30.6, I have no problems in that version, so s.t. was broken since that one.
Comment 2 Filipp Andjelo 2009-10-24 22:49:44 UTC
Created attachment 23515 [details]
reports and output
Comment 3 Ivo van Doorn 2009-10-27 17:44:15 UTC
Try disabling powersaving:
iwconfig wlan0 power off
Comment 4 Filipp Andjelo 2009-10-27 18:54:26 UTC
I've tried it already, but it didn't help.
Comment 5 Michal Kašpar 2009-11-04 19:14:04 UTC
I'm not sure if it is the same problem, but seems quite simillar. My Edimax EW-7128G wireless doesnt work with WEP since 2.6.31 kernel (Debian flavor). It associates with AP but no packets get through. There is nothing strange in logs, just no packets are comming back from the network. I've accidentaly tried WPA2 and it works fine, so it seems the problem appears with WEP only.
lspci identifies the card as:
07:01.0 Network controller [0280]: RaLink RT2561/RT61 802.11g PCI [1814:0301]
and it uses rt61pci driver.
Comment 6 Filipp Andjelo 2009-11-04 22:35:10 UTC
My problem appears using WPA2, I didn't try WEP. I wouldn't miss WEP although it is useless, if you know what I mean :)
Comment 7 Rafael J. Wysocki 2009-11-17 21:56:32 UTC
On Tuesday 17 November 2009, Filipp Andjelo wrote:
> Hi,
> 
> the Problem still exist, no solution or workaround was found yet.
Comment 8 Sin-young "Divinespear" Kang 2009-11-21 12:44:55 UTC
I can confirm this error.

I got spam of below same error message:
----
phy1 -> rt2500pci_set_device_state: Error - Device failed to enter state 3 (-16).
phy1 -> rt2500pci_set_device_state: Error - Device failed to enter state 4 (-5).
----

"iwconfig wlan0 power off" does not working for me too.


<more info>

uname -a
----
Linux divinelaptop 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:05:01 UTC 2009 x86_64 GNU/Linux
----

lspci -vvvv
----
05:09.0 Network controller: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01)
	Subsystem: Micro-Star International Co., Ltd. Device 6833
	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-
	Interrupt: pin A routed to IRQ 22
	Region 0: Memory at 7e000000 (32-bit, non-prefetchable) [size=8K]
	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 modules: rt2500pci
----
Comment 9 Gertjan van Wingerde 2009-11-24 22:33:54 UTC
Would it be possible to enable RT2X00_DEBUG and post a full dmesg of a run with debugging enabled?
Comment 10 Filipp Andjelo 2009-11-27 18:43:46 UTC
First, I don't have much experience with modules/kernel debugging. I've recompiled the modules with RT2X00_DEBUG and enabled DEBUG Logging with "echo 8 > /proc/sys/kernel/printk" but no additional information is shown in dmesg. What am I doing wrong? I think, I need some help :)
Comment 11 Sin-young "Divinespear" Kang 2009-11-29 20:49:27 UTC
there is no additional information with RT2X00_DEBUG....

so I inserted some info printing code, and this is result.

----
Nov 30 03:43:51 divinelaptop kernel: [325910.182674] cfg80211: Calling CRDA to update world regulatory domain
Nov 30 03:43:52 divinelaptop kernel: [325910.593504] rt2500pci 0000:05:09.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
Nov 30 03:43:52 divinelaptop kernel: [325910.606878] phy0 -> rt2500pci_validate_eeprom: EEPROM recovery - MAC: 36:e3:d9:0b:38:e6
Nov 30 03:43:52 divinelaptop kernel: [325910.606889] phy0 -> rt2x00_set_chip: Info - Chipset detected - rt: 0201, rf: 0000, rev: 00303030.
Nov 30 03:43:52 divinelaptop kernel: [325910.609096] phy0: Selected rate control algorithm 'minstrel'
Nov 30 03:43:52 divinelaptop kernel: [325910.611757] Registered led device: rt2500pci-phy0::radio
Nov 30 03:43:52 divinelaptop kernel: [325910.611804] Registered led device: rt2500pci-phy0::quality
Nov 30 03:43:52 divinelaptop kernel: [325910.623041] cfg80211: World regulatory domain updated:
Nov 30 03:43:52 divinelaptop kernel: [325910.623053] 	(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Nov 30 03:43:52 divinelaptop kernel: [325910.623061] 	(2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 30 03:43:52 divinelaptop kernel: [325910.623069] 	(2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Nov 30 03:43:52 divinelaptop kernel: [325910.623076] 	(2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Nov 30 03:43:52 divinelaptop kernel: [325910.623083] 	(5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 30 03:43:52 divinelaptop kernel: [325910.623090] 	(5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 30 03:43:52 divinelaptop NetworkManager: <info>  Found radio killswitch rfkill6 (at /sys/devices/pci0000:00/0000:00:14.4/0000:05:09.0/ieee80211/phy0/rfkill6) (driver <unknown>)
Nov 30 03:43:52 divinelaptop NetworkManager:    SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:14.4/0000:05:09.0/net/wmaster0, iface: wmaster0)
Nov 30 03:43:52 divinelaptop NetworkManager:    SCPlugin-Ifupdown: device added (path: /sys/devices/pci0000:00/0000:00:14.4/0000:05:09.0/net/wmaster0, iface: wmaster0): no ifupdown configuration found.
Nov 30 03:43:52 divinelaptop NetworkManager:    SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:14.4/0000:05:09.0/net/wlan0, iface: wlan0)
Nov 30 03:43:52 divinelaptop NetworkManager:    SCPlugin-Ifupdown: device added (path: /sys/devices/pci0000:00/0000:00:14.4/0000:05:09.0/net/wlan0, iface: wlan0): no ifupdown configuration found.
Nov 30 03:43:52 divinelaptop NetworkManager: <info>  (wlan0): driver supports SSID scans (scan_capa 0x01).
Nov 30 03:43:52 divinelaptop NetworkManager: <info>  (wlan0): new 802.11 WiFi device (driver: 'rt2500pci')
Nov 30 03:43:52 divinelaptop NetworkManager: <info>  (wlan0): exported as /org/freedesktop/NetworkManager/Devices/3
Nov 30 03:43:52 divinelaptop NetworkManager: <info>  (wlan0): now managed
Nov 30 03:43:52 divinelaptop NetworkManager: <info>  (wlan0): device state change: 1 -> 2 (reason 2)
Nov 30 03:43:52 divinelaptop NetworkManager: <info>  (wlan0): bringing up device.
Nov 30 03:43:52 divinelaptop kernel: [325911.242703] phy0 -> rt2500pci_set_device_state: Info - STATE_RADIO_RX_OFF
Nov 30 03:43:52 divinelaptop kernel: [325911.242739] phy0 -> rt2500pci_set_device_state: Info - STATE_RADIO_ON
Nov 30 03:43:52 divinelaptop kernel: [325911.242754] phy0 -> rt2500pci_set_device_state: Info - STATE_AWAKE
Nov 30 03:43:52 divinelaptop kernel: [325911.242762] phy0 -> rt2500pci_set_state: Info - rt2x00pci_register_read(PWRCSR1) = 30303F
Nov 30 03:43:52 divinelaptop kernel: [325911.242771] phy0 -> rt2500pci_set_state: Info - PWRCSR1_SET_STATE = 1 (expected 1), 
Nov 30 03:43:52 divinelaptop kernel: [325911.242778] phy0 -> rt2500pci_set_state: Info - PWRCSR1_BBP_DESIRE_STATE = 3 (expected 3), 
Nov 30 03:43:52 divinelaptop kernel: [325911.242786] phy0 -> rt2500pci_set_state: Info - PWRCSR1_RF_DESIRE_STATE = 3 (expected 3), 
Nov 30 03:43:52 divinelaptop kernel: [325911.242793] phy0 -> rt2500pci_set_state: Info - PWRCSR1_PUT_TO_SLEEP = 0 (expected 0)
Nov 30 03:43:52 divinelaptop kernel: [325911.242800] phy0 -> rt2500pci_set_state: Info - rt2x00pci_register_write(PWRCSR1) = 30303F
Nov 30 03:43:52 divinelaptop kernel: [325911.242807] phy0 -> rt2500pci_set_state: Info - rt2x00pci_register_read(PWRCSR1) = 30303F
Nov 30 03:43:52 divinelaptop kernel: [325911.242815] phy0 -> rt2500pci_set_state: Info - state (expected) = 3, bbp_state = 1, rf_state = 0
Nov 30 03:43:52 divinelaptop kernel: [325911.352545] phy0 -> rt2500pci_set_state: Info - rt2x00pci_register_read(PWRCSR1) = 30303F
Nov 30 03:43:52 divinelaptop kernel: [325911.352558] phy0 -> rt2500pci_set_state: Info - state (expected) = 3, bbp_state = 1, rf_state = 0
Nov 30 03:43:53 divinelaptop kernel: [325911.462544] phy0 -> rt2500pci_set_state: Info - rt2x00pci_register_read(PWRCSR1) = 30303F
Nov 30 03:43:53 divinelaptop kernel: [325911.462556] phy0 -> rt2500pci_set_state: Info - state (expected) = 3, bbp_state = 1, rf_state = 0
Nov 30 03:43:53 divinelaptop kernel: [325911.572551] phy0 -> rt2500pci_set_state: Info - rt2x00pci_register_read(PWRCSR1) = 30303F
Nov 30 03:43:53 divinelaptop kernel: [325911.572563] phy0 -> rt2500pci_set_state: Info - state (expected) = 3, bbp_state = 1, rf_state = 0
Nov 30 03:43:53 divinelaptop kernel: [325911.682540] phy0 -> rt2500pci_set_state: Info - rt2x00pci_register_read(PWRCSR1) = 30303F
Nov 30 03:43:53 divinelaptop kernel: [325911.682551] phy0 -> rt2500pci_set_state: Info - state (expected) = 3, bbp_state = 1, rf_state = 0
Nov 30 03:43:53 divinelaptop kernel: [325911.792540] phy0 -> rt2500pci_set_state: Info - rt2x00pci_register_read(PWRCSR1) = 30303F
Nov 30 03:43:53 divinelaptop kernel: [325911.792551] phy0 -> rt2500pci_set_state: Info - state (expected) = 3, bbp_state = 1, rf_state = 0
Nov 30 03:43:53 divinelaptop kernel: [325911.906949] phy0 -> rt2500pci_set_state: Info - rt2x00pci_register_read(PWRCSR1) = 30303F
Nov 30 03:43:53 divinelaptop kernel: [325911.906963] phy0 -> rt2500pci_set_state: Info - state (expected) = 3, bbp_state = 1, rf_state = 0
Nov 30 03:43:53 divinelaptop kernel: [325912.012556] phy0 -> rt2500pci_set_state: Info - rt2x00pci_register_read(PWRCSR1) = 30303F
Nov 30 03:43:53 divinelaptop kernel: [325912.012569] phy0 -> rt2500pci_set_state: Info - state (expected) = 3, bbp_state = 1, rf_state = 0
Nov 30 03:43:53 divinelaptop kernel: [325912.122541] phy0 -> rt2500pci_set_state: Info - rt2x00pci_register_read(PWRCSR1) = 30303F
Nov 30 03:43:53 divinelaptop kernel: [325912.122554] phy0 -> rt2500pci_set_state: Info - state (expected) = 3, bbp_state = 1, rf_state = 0
Nov 30 03:43:53 divinelaptop kernel: [325912.232562] phy0 -> rt2500pci_set_state: Info - rt2x00pci_register_read(PWRCSR1) = 30303F
Nov 30 03:43:53 divinelaptop kernel: [325912.232575] phy0 -> rt2500pci_set_state: Info - state (expected) = 3, bbp_state = 1, rf_state = 0
Nov 30 03:43:53 divinelaptop NetworkManager: <info>  (wlan0): preparing device.
Nov 30 03:43:53 divinelaptop NetworkManager: <info>  (wlan0): deactivating device (reason: 2).
Nov 30 03:43:53 divinelaptop kernel: [325912.342558] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 3 (-16).
Nov 30 03:43:53 divinelaptop kernel: [325912.342572] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 4 (-5).
Nov 30 03:43:53 divinelaptop kernel: [325912.342588] phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 0 - CWmin: 3, CWmax: 4, Aifs: 2, TXop: 102.
Nov 30 03:43:53 divinelaptop kernel: [325912.342598] phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 1 - CWmin: 4, CWmax: 5, Aifs: 2, TXop: 188.
Nov 30 03:43:53 divinelaptop kernel: [325912.343505] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Nov 30 03:43:54 divinelaptop NetworkManager: <info>  (wlan0): supplicant interface state:  starting -> ready
Nov 30 03:43:54 divinelaptop NetworkManager: <info>  (wlan0): device state change: 2 -> 3 (reason 42)
Nov 30 03:43:54 divinelaptop kernel: [325912.581993] phy0 -> rt2500pci_set_device_state: Info - STATE_RADIO_RX_OFF
Nov 30 03:43:54 divinelaptop kernel: [325912.582025] phy0 -> rt2500pci_set_device_state: Info - STATE_RADIO_ON
Nov 30 03:43:54 divinelaptop kernel: [325912.582036] phy0 -> rt2500pci_set_device_state: Info - STATE_AWAKE
Nov 30 03:43:54 divinelaptop kernel: [325912.582044] phy0 -> rt2500pci_set_state: Info - rt2x00pci_register_read(PWRCSR1) = 30303F
Nov 30 03:43:54 divinelaptop kernel: [325912.582052] phy0 -> rt2500pci_set_state: Info - PWRCSR1_SET_STATE = 1 (expected 1), 
Nov 30 03:43:54 divinelaptop kernel: [325912.582060] phy0 -> rt2500pci_set_state: Info - PWRCSR1_BBP_DESIRE_STATE = 3 (expected 3), 
Nov 30 03:43:54 divinelaptop kernel: [325912.582067] phy0 -> rt2500pci_set_state: Info - PWRCSR1_RF_DESIRE_STATE = 3 (expected 3), 
Nov 30 03:43:54 divinelaptop kernel: [325912.582075] phy0 -> rt2500pci_set_state: Info - PWRCSR1_PUT_TO_SLEEP = 0 (expected 0)
Nov 30 03:43:54 divinelaptop kernel: [325912.582082] phy0 -> rt2500pci_set_state: Info - rt2x00pci_register_write(PWRCSR1) = 30303F
Nov 30 03:43:54 divinelaptop kernel: [325912.582089] phy0 -> rt2500pci_set_state: Info - rt2x00pci_register_read(PWRCSR1) = 30303F
Nov 30 03:43:54 divinelaptop kernel: [325912.582097] phy0 -> rt2500pci_set_state: Info - state (expected) = 3, bbp_state = 1, rf_state = 0
Nov 30 03:43:54 divinelaptop kernel: [325912.682548] phy0 -> rt2500pci_set_state: Info - rt2x00pci_register_read(PWRCSR1) = 30303F
Nov 30 03:43:54 divinelaptop kernel: [325912.682561] phy0 -> rt2500pci_set_state: Info - state (expected) = 3, bbp_state = 1, rf_state = 0
Nov 30 03:43:54 divinelaptop kernel: [325912.792567] phy0 -> rt2500pci_set_state: Info - rt2x00pci_register_read(PWRCSR1) = 30303F
Nov 30 03:43:54 divinelaptop kernel: [325912.792579] phy0 -> rt2500pci_set_state: Info - state (expected) = 3, bbp_state = 1, rf_state = 0
Nov 30 03:43:54 divinelaptop kernel: [325912.902543] phy0 -> rt2500pci_set_state: Info - rt2x00pci_register_read(PWRCSR1) = 30303F
Nov 30 03:43:54 divinelaptop kernel: [325912.902555] phy0 -> rt2500pci_set_state: Info - state (expected) = 3, bbp_state = 1, rf_state = 0
Nov 30 03:43:54 divinelaptop kernel: [325913.020055] phy0 -> rt2500pci_set_state: Info - rt2x00pci_register_read(PWRCSR1) = 30303F
Nov 30 03:43:54 divinelaptop kernel: [325913.020068] phy0 -> rt2500pci_set_state: Info - state (expected) = 3, bbp_state = 1, rf_state = 0
Nov 30 03:43:54 divinelaptop kernel: [325913.130040] phy0 -> rt2500pci_set_state: Info - rt2x00pci_register_read(PWRCSR1) = 30303F
Nov 30 03:43:54 divinelaptop kernel: [325913.130052] phy0 -> rt2500pci_set_state: Info - state (expected) = 3, bbp_state = 1, rf_state = 0
Nov 30 03:43:54 divinelaptop kernel: [325913.240039] phy0 -> rt2500pci_set_state: Info - rt2x00pci_register_read(PWRCSR1) = 30303F
Nov 30 03:43:54 divinelaptop kernel: [325913.240049] phy0 -> rt2500pci_set_state: Info - state (expected) = 3, bbp_state = 1, rf_state = 0
Nov 30 03:43:54 divinelaptop kernel: [325913.350035] phy0 -> rt2500pci_set_state: Info - rt2x00pci_register_read(PWRCSR1) = 30303F
Nov 30 03:43:54 divinelaptop kernel: [325913.350044] phy0 -> rt2500pci_set_state: Info - state (expected) = 3, bbp_state = 1, rf_state = 0
Nov 30 03:43:55 divinelaptop kernel: [325913.460037] phy0 -> rt2500pci_set_state: Info - rt2x00pci_register_read(PWRCSR1) = 30303F
Nov 30 03:43:55 divinelaptop kernel: [325913.460047] phy0 -> rt2500pci_set_state: Info - state (expected) = 3, bbp_state = 1, rf_state = 0
Nov 30 03:43:55 divinelaptop kernel: [325913.570032] phy0 -> rt2500pci_set_state: Info - rt2x00pci_register_read(PWRCSR1) = 30303F
Nov 30 03:43:55 divinelaptop kernel: [325913.570042] phy0 -> rt2500pci_set_state: Info - state (expected) = 3, bbp_state = 1, rf_state = 0
Nov 30 03:43:55 divinelaptop kernel: [325913.680035] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 3 (-16).
Nov 30 03:43:55 divinelaptop kernel: [325913.680048] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 4 (-5).
----

-16 at stage 3 means EBUSY. Is it hardware problem?
Comment 12 Carlos 2009-11-29 23:21:37 UTC
I think this is the same bug as: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/404596

I got an rt61pci. If i try to load the driver i get an error:

 rt61pci 0000:05:09.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
 phy0 -> rt61pci_init_eeprom: Error - Invalid RF chipset detected.
 phy0 -> rt2x00lib_probe_dev: Error - Failed to allocate device.
 rt61pci 0000:05:09.0: PCI INT A disabled

Please, please fix this bug!
Comment 13 Ivo van Doorn 2009-11-30 17:16:39 UTC
(In reply to comment #12)
> I think this is the same bug as:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/404596
> 
> I got an rt61pci. If i try to load the driver i get an error:
> 
>  rt61pci 0000:05:09.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
>  phy0 -> rt61pci_init_eeprom: Error - Invalid RF chipset detected.
>  phy0 -> rt2x00lib_probe_dev: Error - Failed to allocate device.
>  rt61pci 0000:05:09.0: PCI INT A disabled
> 
> Please, please fix this bug!


What makes you think it is the same bug?
The driver is different, the error message is different, the bug behavior is different...
The only thing the 2 issues have in common is that the chipset comes from Ralink, and that the driver uses the rt2x00 library.
Comment 14 Carlos 2009-11-30 19:04:02 UTC
(In reply to comment #13)

> 
> What makes you think it is the same bug?
> The driver is different, the error message is different, the bug behavior is
> different...
> The only thing the 2 issues have in common is that the chipset comes from
> Ralink, and that the driver uses the rt2x00 library.

Sorry, i was tiered. Maybe you are right.
But both driver stop working with .31 and .32.

Should i open a new bug report for the rt61pci Problem?
Comment 15 Gertjan van Wingerde 2009-11-30 19:12:05 UTC
(In reply to comment #14)
> (In reply to comment #13)
> 
> > 
> > What makes you think it is the same bug?
> > The driver is different, the error message is different, the bug behavior is
> > different...
> > The only thing the 2 issues have in common is that the chipset comes from
> > Ralink, and that the driver uses the rt2x00 library.
> 
> Sorry, i was tiered. Maybe you are right.
> But both driver stop working with .31 and .32.
> 
> Should i open a new bug report for the rt61pci Problem?

Well, it is good to track both bugs as separate reports, although they *may*
be related, as in both cases we are looking at a driver reading bogus information
from the EEPROM.
Note how the rt2500pci problem also reads a random MAC address from the EEPROM.

I don't have a clue to where the problem is yet, but maybe some EEPROM related
problem has been introduced in 2.6.31.
Comment 16 Carlos 2009-12-05 21:35:33 UTC
(In reply to comment #15)
> Well, it is good to track both bugs as separate reports, although they *may*
> be related, as in both cases we are looking at a driver reading bogus
> information
> from the EEPROM.
> I don't have a clue to where the problem is yet, but maybe some EEPROM related
> problem has been introduced in 2.6.31.

Lets assume they are related. I cloned the 2.6.31 git and did some git bisect.
git bisect bad v2.6.31
git bisect good v2.6.30
After compiling the kernel 16 times i got this:

"5d423ccd7ba4285f1084e91b26805e1d0ae978ed is the first bad commit"

That commit does some changes in /arch/x86/kernel/e820.c

After an git checkout v2.6.31.6 and git revert 5d423ccd7ba4285f1084e91b26805e1d0ae978ed i could do an modprobe rt61pci without getting an error.
But ifconfig wlan0 up gives me an error:
SIOCSIFFLAGS: Unknown Error 132

I hope this could help. If there is anything I could do feel free to ask.
Comment 17 Carlos 2009-12-05 23:27:42 UTC
Ah, when i press the Wifi button on my laptop (Never needed that before) the SIOCSIFFLAGS is gone and the card works. 
Maybe the git revert 5d423ccd7ba4285f1084e91b26805e1d0ae978ed also works for the RT2500.
Comment 18 Sin-young "Divinespear" Kang 2009-12-07 03:25:22 UTC
boot with "pci=use_crs" should be work.
I cannot test wireless connect cause I don't have spots around here, but error spamming is stopped.
(from https://bugs.launchpad.net/ubuntu/+source/linux/+bug/404596)
Comment 19 Filipp Andjelo 2009-12-07 19:01:33 UTC
Yes, that works for my rt2500pci but what is that option for? An is that solution clean one? Any explanation is appreciated :)
Comment 20 Gertjan van Wingerde 2009-12-07 22:29:17 UTC
(In reply to comment #19)
> Yes, that works for my rt2500pci but what is that option for? An is that
> solution clean one? Any explanation is appreciated :)

I have sent this case to the x86 maintainer and the creator of the patch that is identified as to be causing this problem.
My initial conclusion is that this may be something that lies outside of the rt2x00 driver.
Comment 21 Gertjan van Wingerde 2009-12-07 22:59:48 UTC
(In reply to comment #20)
> (In reply to comment #19)
> > Yes, that works for my rt2500pci but what is that option for? An is that
> > solution clean one? Any explanation is appreciated :)
> 
> I have sent this case to the x86 maintainer and the creator of the patch that
> is identified as to be causing this problem.
> My initial conclusion is that this may be something that lies outside of the
> rt2x00 driver.

Test patch has been provided on Linux-kernel mailing list, see:
http://marc.info/?l=linux-kernel&m=126022647325204&w=2

Please test with this patch
Comment 22 Sin-young "Divinespear" Kang 2009-12-09 00:02:46 UTC
(In reply to comment #21)
> Test patch has been provided on Linux-kernel mailing list, see:
> http://marc.info/?l=linux-kernel&m=126022647325204&w=2
> 
> Please test with this patch

It work! thanks.
Comment 23 Florian Mickler 2010-10-07 22:22:19 UTC
This should be 

commit 99935a7a59eaca0292c1a5880e10bae03f4a5e3d
Author: Yinghai Lu <yinghai@kernel.org>
Date:   Sun Oct 4 21:54:24 2009 -0700

    x86/PCI: read root resources from IOH on Intel


in current mainline. 

Is that patch needed in 2.6.32.y?

Note You need to log in before you can comment on or make changes to this bug.