Date: Fri, 25 May 2012 09:48:22 -0600 From: Warner Losh <imp@bsdimp.com> To: Adrian Chadd <adrian@FreeBSD.org> Cc: freebsd-current@FreeBSD.org, freebsd-mobile@FreeBSD.org Subject: Re: 9-stable regression: 'cbb0: Warning: Bus reset timeout' Message-ID: <E658CA99-7A6F-45AF-A3AA-A1129915C3E9@bsdimp.com> In-Reply-To: <CAJ-Vmo=pKPHqB1uJJzqgonA5xHs0cvCX-B1vKmcCdRbmsHatWA@mail.gmail.com> References: <CAJ-VmomWf_%2Bo%2B5vQkr7-2HqBuYjk0K-y_EEyqQvpp_GVN3W_8Q@mail.gmail.com> <CAJ-Vmo=pKPHqB1uJJzqgonA5xHs0cvCX-B1vKmcCdRbmsHatWA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On May 25, 2012, at 1:53 AM, Adrian Chadd wrote: > To respond to my own email: >=20 > * if I unload cbb/pccard/cardbus and reload them, suddenly the slot = works. > * I've been toying with S3 suspend to RAM, so I wondered if it were = that. >=20 > Yes, it seems to be suspend related. I'll do some more thorough > testing tomorrow, but once I suspend, the ath(4) NIC gets detached > from the cardbus slot, then upon resume the NIC isn't found (bus > timeout) and won't be until I unload/reload the modules. >=20 > Should pccard/cbb/cardbus 'properly' handle S3 suspend/resume? Does it > work for anyone else? Once upon a time, it worked just fine. But that was before the long, = dark winter of my laptops not suspending, so maybe something got broken = along the way. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E658CA99-7A6F-45AF-A3AA-A1129915C3E9>