Return-path: Received: from rv-out-0506.google.com ([209.85.198.231]:3502 "EHLO rv-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760260AbYENTJO (ORCPT ); Wed, 14 May 2008 15:09:14 -0400 Received: by rv-out-0506.google.com with SMTP id l9so36557rvb.1 for ; Wed, 14 May 2008 12:09:13 -0700 (PDT) Message-ID: (sfid-20080514_210918_106237_696B3246) Date: Wed, 14 May 2008 15:09:13 -0400 From: "Bob Copeland" To: "Zack Weinberg" Subject: Re: Getting ath5k driver working with Thinkpad T61 [168c:1014] Cc: linux-wireless@vger.kernel.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 References: Sender: linux-wireless-owner@vger.kernel.org List-ID: On Wed, May 14, 2008 at 2:45 PM, Zack Weinberg wrote: > On Wed, May 14, 2008 at 2:38 PM, Bob Copeland wrote: >> On Wed, May 14, 2008 at 1:24 PM, Zack Weinberg 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