Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 11 Jan 2013 14:19:38 -0800
From:      Adrian Chadd <adrian.chadd@gmail.com>
To:        Slawa Olhovchenkov <slw@zxy.spb.ru>
Cc:        "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org>
Subject:   Re: Atheros 9220 don't return from S3 state
Message-ID:  <CAJ-VmomBRDBk9oOaZo-6kvLWYvFxrH99XhyHH9FeyUta6pqzww@mail.gmail.com>
In-Reply-To: <20130111075136.GA67643@zxy.spb.ru>
References:  <20130109121613.GO1967@zxy.spb.ru> <50edf68e.ec05320a.6ea9.ffff8ee4@mx.google.com> <20130110080729.GQ1967@zxy.spb.ru> <CAJ-VmonkpnV=H0-pP-6Rv%2BvHoU4Sdi-7KzgLKz9%2BHjmXtuZGkA@mail.gmail.com> <20130111075136.GA67643@zxy.spb.ru>

next in thread | previous in thread | raw e-mail | index | archive | help
.. so there's no _specific_ code being run when it goes to sleep or
comes back from sleep for the 11n PCI NICs (AR5416, AR9160, AR9220,
AR9227..) .. there's some code to tinker with the internal reset
line(s) that force the hardware to re-initialise, but that's not
appropriate for you.

The problem here is:

* it probe/attches fine;
* you go to sleep;
* you come back from sleep;
* the PCI registers seem to be all 0xffffffff; which means the slot or
the card is entirely asleep.

So it's not something I can do when the NIC comes back - there's
likely something that needs to happen to the PCI interface inside the
AR9220 before you put the chip to sleep. And I don't (yet) have
anything like that in the driver(s) that I've seen internally.

But we need to first eliminate that it's the specific slot in
question.. does Linux work right?



adrian



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmomBRDBk9oOaZo-6kvLWYvFxrH99XhyHH9FeyUta6pqzww>