On Thursday, August 19, 2010, Luis R. Rodriguez wrote: > On Wed, Aug 18, 2010 at 3:01 PM, Rafael J. Wysocki <rjw@xxxxxxx> wrote: > > Hi, > > > > While testing 2.6.36-rc1 (with a couple of fixes on top) > > Which couple of fixes? AMD bood fix, HID suspend fix and shmem fix (two of them have already been merged). > > I noticed that the ath9k > > driver didn't work after resume from suspend to RAM. > > To rule out if its an ath9k issue you can try > compat-wireless-2.6.36-rc1 from here: > > http://wireless.kernel.org/en/users/Download/stable/ > > and install it on an older kernel, you can use ./scripts/driver-select > to only enable ath9k to compile. Well, that sounds a bit complicated and even if I know it's not ath9k, that's not going to help me find the real source of the problem. > I've been using pm-suspend on this release for a few days now without > any issue but I am using an AR9003 chipset. What chipset are you > using? Can you provide the dmesg output upon module load? Sure. [ 9.680128] ath9k 0000:09:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 [ 9.689487] ath9k 0000:09:00.0: setting latency timer to 64 [ 9.706383] HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 9.805043] hda_codec: ALC272X: BIOS auto-probing. [ 9.819389] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:14.2/input/input8 [ 10.155052] ath: EEPROM regdomain: 0x65 [ 10.155058] ath: EEPROM indicates we should expect a direct regpair map [ 10.155066] ath: Country alpha2 being used: 00 [ 10.155070] ath: Regpair used: 0x65 [ 10.179762] phy0: Selected rate control algorithm 'ath9k_rate_control' [ 10.181657] Registered led device: ath9k-phy0::radio [ 10.181890] Registered led device: ath9k-phy0::assoc [ 10.182139] Registered led device: ath9k-phy0::tx [ 10.182339] Registered led device: ath9k-phy0::rx lspci says it's: 09:00.0 Network controller: Atheros Communications Inc. AR928X Wireless Network Adapter (PCI-Express) (rev 01) Thanks, Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
