From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cedric Sodhi Date: Thu, 24 Feb 2011 13:33:22 +0100 Subject: [ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout In-Reply-To: <20110224122759.7357.qmail@stuge.se> References: <20110224074209.11758.qmail@stuge.se> <20110224090010.GB19782@fly> <20110224091823.32641.qmail@stuge.se> <20110224095848.GD24543@fly> <1298545686.25101.36.camel@jm-desktop> <20110224112107.GA11720@fly> <1298546937.25101.54.camel@jm-desktop> <20110224115202.664.qmail@stuge.se> <20110224122433.GB11720@fly> <20110224122759.7357.qmail@stuge.se> Message-ID: <20110224123322.GC11720@fly> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org Wait a second, this can't possibly caused by calling rfkill. I only installed rfkill to examine why that happens in the first place! On Thu, Feb 24, 2011 at 01:27:59PM +0100, Peter Stuge wrote: > Cedric Sodhi wrote: > > I'm as clueless. I inserted the "rfkill list" command at different > > stages in the the init-script and it turns out the Lock occurs BEFORE > > start( ) is called - outside of /etc/init.d/net.lo. > > > > But where? > > strace -fFs 1024 -o /tmp/out /etc/init.d/net.eth1 restart; grep -B 512 rfkill /tmp/out | wgetpaste -X > > Another thing to try would be to see if simple ip l s dev eth1 down or > .. up triggers the lock? > > > //Peter > _______________________________________________ > ath9k-devel mailing list > ath9k-devel at lists.ath9k.org > https://lists.ath9k.org/mailman/listinfo/ath9k-devel