On Wed, May 14, 2008 at 2:45 PM, Zack Weinberg <zackw@xxxxxxxxx> wrote: > On Wed, May 14, 2008 at 2:38 PM, Bob Copeland <me@xxxxxxxxxxxxxxx> wrote: >> On Wed, May 14, 2008 at 1:24 PM, Zack Weinberg <zackw@xxxxxxxxx> wrote: >>> [15498.709195] ACPI: PCI interrupt for device 0000:03:00.0 disabled >>> [15498.709205] ath5k_pci: probe of 0000:03:00.0 failed with error -5 >> >> Did you try power-cycling your machine? Looks like chip is hung. > > exactly the same thing happens immediately after cold boot with > nothing else having touched the chip. Interesting... can you confirm that madwifi also will not start from a cold boot? I only ask because I had a similar issue with my pci-e card that was fixed a while ago. Madwifi would work from a cold boot, though, if ath5k had never been loaded. Here's someone else with the same PCI ID, same symptom: http://kerneltrap.org/mailarchive/linux-ath5k-devel/2007/12/12/496961 Perhaps the best thing to do is add printks to ath5k_hw_nic_wakeup and see where it hangs? -- Bob Copeland %% www.bobcopeland.com -- 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
