From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brian Walker Date: Wed, 27 Jan 2010 19:36:26 -0500 Subject: [ath9k-devel] trouble with DWA-552 and ath9k In-Reply-To: <1264634005.19648.59.camel@mj> References: <4B2A5FA8.8060905@charter.net> <19242.62265.487757.695747@gargle.gargle.HOWL> <4B2AFC5D.1060001@charter.net> <19243.2224.974537.876295@gargle.gargle.HOWL> <4B39058A.6080108@charter.net> <1262033354.3002.11.camel@mj> <4B391DCB.6010500@charter.net> <1262035725.3002.23.camel@mj> <4B393739.9000601@charter.net> <20091229100250.xle1s7oai8ow08k8-cebfxv@webmail.spamcop.net> <4B3A8F7B.2050106@charter.net> <20091230011624.zygif55zaco8000s-cebfxv@webmail.spamcop.net> <4B436D94.4050304@charter.net> <19270.46529.788691.185819@gargle.gargle.HOWL> <4B489D63.9030305@charter.net> <19273.25018.877385.529083@gargle.gargle.HOWL> <4B4D1F4F.7090106@charter.net> <19277.32410.462158.258222@gargle.gargle.HOWL> <4B51E8FC.9030304@charter.net> <1264028629.10023.26.camel@mj> <4B5DE724.7000002@charter.net> <1264448097.10841.1.camel@mj> <4B5F8E37.4070901@charter.net> <1264634005.19648.59.camel@mj> Message-ID: <4B60DC0A.1080602@charter.net> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org On 01/27/2010 06:13 PM, Pavel Roskin wrote: > On Tue, 2010-01-26 at 19:52 -0500, Brian Walker wrote: > > >> ath: Marking phy0 as idle >> ath: timeout (100000 us) on reg 0x7000: 0xffffffff& 0x00000003 != >> 0x00000000 >> ath: RTC stuck in MAC reset >> ath: Chip reset failed >> > It looks like a completely different problem. There is no 0xdeadbeef > involved and the failure is in a different place. > > >> ath: Unable to reset channel 4198050593 (2412Mhz)<7>ath: not-idle: >> enabling radio >> > Apparently the statements to print "Unable to reset channel" are > incorrect in two places out of three in main.c. ath_print() should be > annotated so that gcc would warn about invalid format. > > Yes, the errors I am seeing appear to be the same ones I sent on January 12. The ones on January 12 were from the 2009-12-11 codebase and the ones I sent yesterday are from the 2010-01-24 codebase. It would appear that whatever is wrong with my DWA-552 and the ath9k driver has not been addressed yet. Any idea when it might be? I would be glad to provide additional logs, etc. if it would help. Brian