Date:	Wed, 30 Sep 2009 09:52:27 +0200
From:	Frans Pop <elendil@...net.nl>
To:	linux-wireless@...r.kernel.org
Cc:	linux-kernel@...r.kernel.org, Bob Copeland <me@...copeland.com>
Subject: [.32-rc1/2] ath5k: has become unreliable with .32-rc1

This is on a laptop I don't use much, but with .31 wireless has always
been (and still is) reliable (.31-rc5 is the last kernel I built for it).
On my other laptop wireless (iwlagn) works fine with .32-rc1.


The first time I booted .32-rc1 (reboot from .31-rc5), wireless came up
without problems, but failed to come back after suspend to RAM. I could
only get wireless back by ejecting and re-inserting the PCMCIA card.

The second and third time I booted .32-rc1 (to write this report; a cold
boot and a ".32 to .32" reboot), wireless did not come up at all.
See attached dmesg. The last part is after 'ifup ath0'. It seems to
associate, but then for some reason immediately deauthenticates again.
Ejecting/reinserting the PCMCIA card or unloading/reloading the driver
does not help.

After that I tried .31-rc5 again and wireless came up fine. And when I
then rebooted into .32, wireless came up OK as well, same as the first
boot.

So the difference looks to be how I boot: if I do a *cold* boot directly
into .32, wireless fails; if I *reboot* from .31 into .32, wireless
comes up correctly. Reboot from .32 to .32 fails too.

I think the "wireless after boot" problem and the "resume" problem could
very well be separate issues. The resume problem looks similar to
http://bugzilla.kernel.org/show_bug.cgi?id=13948.


System: Toshiba Satellite A40; i386, Pentium 4, Debian stable ("Lenny")

01:0b.0 CardBus bridge [0607]: Toshiba America Info Systems ToPIC100
     PCI to Cardbus Bridge with ZV Support [1179:0617] (rev 33)
02:00.0 Ethernet controller [0200]: Atheros Communications Inc.
     AR5212/AR5213 Multiprotocol MAC/baseband processor [168c:0013] (rev 01)

From ath_info:
 -==Device Information==-
MAC Version:  5212  (0x50)
MAC Revision: 5213A (0x59)
Device type:  1


dmesg diff showing resume with .31-rc5 and .32-rc1. Note that the "late"
config restore seems to have disappeared.

--- ../strider/2.6.31-rc5+resume        2009-09-30 03:42:21.000000000 +0200
+++ ../strider/2.6.32-rc1+resume        2009-09-30 03:38:54.000000000 +0200
 Back to C!
 CPU0: Thermal LVT vector (0xfa) already installed
 ACPI: Waking up from system sleep state S3
 pci 0000:00:02.1: restoring config space at offset 0x5 (was 0x0, writing 0x2c000000)
 pci 0000:00:02.1: restoring config space at offset 0x4 (was 0x8, writing 0x20000008)
 uhci_hcd 0000:00:1d.1: restoring config space at offset 0xf (was 0x2ff, writing 0x20b)
-ehci_hcd 0000:00:1d.7: PME# disabled
 PIIX_IDE 0000:00:1f.1: restoring config space at offset 0xf (was 0x1ff, writing 0x10b)
 PIIX_IDE 0000:00:1f.1: restoring config space at offset 0x1 (was 0x2800003, writing 0x2800007)
 e100 0000:01:08.0: restoring config space at offset 0xf (was 0x380801ff, writing 0x3808010b)
 e100 0000:01:08.0: restoring config space at offset 0x1 (was 0x2900003, writing 0x2900007)
 ath5k 0000:02:00.0: restoring config space at offset 0xf (was 0xffffffff, writing 0x1c0a0112)
 ath5k 0000:02:00.0: restoring config space at offset 0xe (was 0xffffffff, writing 0x0)
 ath5k 0000:02:00.0: restoring config space at offset 0xd (was 0xffffffff, writing 0x44)
 ath5k 0000:02:00.0: restoring config space at offset 0xc (was 0xffffffff, writing 0x0)
 ath5k 0000:02:00.0: restoring config space at offset 0xb (was 0xffffffff, writing 0x710316ab)
 ath5k 0000:02:00.0: restoring config space at offset 0xa (was 0xffffffff, writing 0x5001)
 ath5k 0000:02:00.0: restoring config space at offset 0x9 (was 0xffffffff, writing 0x0)
 ath5k 0000:02:00.0: restoring config space at offset 0x8 (was 0xffffffff, writing 0x0)
 ath5k 0000:02:00.0: restoring config space at offset 0x7 (was 0xffffffff, writing 0x0)
 ath5k 0000:02:00.0: restoring config space at offset 0x6 (was 0xffffffff, writing 0x0)
 ath5k 0000:02:00.0: restoring config space at offset 0x5 (was 0xffffffff, writing 0x0)
 ath5k 0000:02:00.0: restoring config space at offset 0x4 (was 0xffffffff, writing 0x30000000)
 ath5k 0000:02:00.0: restoring config space at offset 0x3 (was 0xffffffff, writing 0xa808)
 ath5k 0000:02:00.0: restoring config space at offset 0x2 (was 0xffffffff, writing 0x2000001)
 ath5k 0000:02:00.0: restoring config space at offset 0x1 (was 0xffffffff, writing 0x2900006)
 ath5k 0000:02:00.0: restoring config space at offset 0x0 (was 0xffffffff, writing 0x13168c)
-pci 0000:00:02.0: PME# disabled
-pci 0000:00:02.1: PME# disabled
 uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
 uhci_hcd 0000:00:1d.0: setting latency timer to 64
 uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
 uhci_hcd 0000:00:1d.1: setting latency timer to 64
-ehci_hcd 0000:00:1d.7: PME# disabled
 ehci_hcd 0000:00:1d.7: PCI INT D -> GSI 23 (level, low) -> IRQ 23
 ehci_hcd 0000:00:1d.7: setting latency timer to 64
 pci 0000:00:1e.0: setting latency timer to 64
 PIIX_IDE 0000:00:1f.1: PCI INT A -> GSI 18 (level, low) -> IRQ 18
 PIIX_IDE 0000:00:1f.1: setting latency timer to 64
 Intel ICH 0000:00:1f.5: PCI INT B -> GSI 17 (level, low) -> IRQ 17
 Intel ICH 0000:00:1f.5: setting latency timer to 64
 Intel ICH Modem 0000:00:1f.6: PCI INT B -> GSI 17 (level, low) -> IRQ 17
 Intel ICH Modem 0000:00:1f.6: setting latency timer to 64
-e100 0000:01:08.0: PME# disabled
 parport_pc 00:09: activated
 hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4
 hda: UDMA/100 mode selected
 hdc: host max PIO4 wanted PIO255(auto-tune) selected PIO4
 hdc: UDMA/33 mode selected
-ath5k 0000:02:00.0: restoring config space at offset 0xf (was 0x1c0a0100, writing 0x1c0a0112)
-ath5k 0000:02:00.0: restoring config space at offset 0x4 (was 0x0, writing 0x30000000)
-ath5k 0000:02:00.0: restoring config space at offset 0x3 (was 0x0, writing 0xa808)
-ath5k 0000:02:00.0: restoring config space at offset 0x1 (was 0x2900000, writing 0x2900006)
+ath5k 0000:02:00.0: enabling device (0000 -> 0002)
 ath5k 0000:02:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
+ath5k phy0: failed to wakeup the MAC Chip
+ath5k phy0: can't reset hardware (-5)
+ath5k phy0: failed to wakeup the MAC Chip
+ath5k phy0: can't reset hardware (-5)
 Restarting tasks ... done.


View attachment "dmesg.32-rc1" of type "text/plain" (28465 bytes)

Powered by blists - more mailing lists