It'll only go into that mode if that core is off for some reason. So sure, do that and try to turn the radio off/on :-) adrian On 13 September 2012 09:51, Simon Wunderlich <simon.wunderlich@xxxxxxxxxxxxxxxxxxxx> wrote: > ath9k fellows, > > as it seems no one could find the cause for this problem so far. I'd therefore > like to create a workaround by checking one/some registers for 0xdeadbeef and > reset the chip if this is found. > > Can anyone recommend a register which should never go 0xdeadbeef in a normal case? > > From what i've seen, AR_CFG (0x0014) might be a good choice. My regdumps say: > > bad regdump: 0x000014 0xdeadbeef > good regdump: 0x000014 0x0008010a > > Unfortunately I don't have documentation to find out if this register can ever > go deadbeef in a normal case. :) > > What do you think? (of course, a proper solution is still appreciated ...) > > Cheers, > Simon > > > On Wed, Sep 05, 2012 at 04:20:52PM +0200, Sven Eckelmann wrote: >> On Wednesday 05 September 2012 07:08:47 Adrian Chadd wrote: >> > I don't think it's a stuck beacon WAR issue here; 0xdeadbeef really >> > does read like the MAC has gone to sleep. >> > >> > Where's the complete register dump hiding? >> >> It was not sent to the public mailing lists due to the size. You will receive >> the dump mentioned in the first mail in some minutes. >> >> Kind regards, >> Sven > > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > > iEYEARECAAYFAlBSDwwACgkQrzg/fFk7axaCLQCg27g4pk6seTqcix0RFoeoglZm > +fkAoJnqhGv77388XjzRPdhSM/V3yNYl > =BYI7 > -----END PGP SIGNATURE----- > -- 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
