Bug 168393

Summary:	[ath] [suspend/resume] suspend/resume sometimes fails
Product:	Base System	Reporter:	Rui Paulo <rpaulo>
Component:	wireless	Assignee:	freebsd-wireless (Nobody) <wireless>
Status:	Open ---
Severity:	Affects Only Me
Priority:	Normal
Version:	10.0-CURRENT
Hardware:	Any
OS:	Any

Description Rui Paulo freebsd_committer

2012-05-27 21:50:06 UTC

AR9285 suspend/resume sometimes fails:

ath0: ath_reset: unable to reset hardware; hal status 14
ath0: device timeout
ath0: ath_reset: unable to reset hardware; hal status 14
ath0: ath_reset: unable to reset hardware; hal status 14
ath0: device timeout
ath0: ath_reset: unable to reset hardware; hal status 14
ath0: ath_reset: unable to reset hardware; hal status 14
ath0: device timeout
ath0: ath_reset: unable to reset hardware; hal status 14
ath0: ath_reset: unable to reset hardware; hal status 14
ath0: device timeout
ath0: ath_reset: unable to reset hardware; hal status 14
ath0: ath_reset: unable to reset hardware; hal status 14
ath0: device timeout
ath0: ath_reset: unable to reset hardware; hal status 14
ath0: ath_reset: unable to reset hardware; hal status 14
ath0: device timeout
ath0: ath_reset: unable to reset hardware; hal status 14
ath0: ath_reset: unable to reset hardware; hal status 14

Fix: 

Suspend/resume again and the problem usually goes away.
How-To-Repeat: EeePC 1005HA suspend/resume (only happened once).

Comment 1 Rui Paulo freebsd_committer

2012-05-27 21:50:25 UTC

Responsible Changed
From-To: freebsd-bugs->adrian

To Adrian.

Comment 2 Rui Paulo freebsd_committer

2012-05-27 21:55:36 UTC

Class Changed
From-To: doc-bug->sw-bug

Fix the class.

Comment 3 Rui Paulo freebsd_committer

2012-05-27 21:55:36 UTC

Responsible Changed
From-To: adrian->freebsd-wireless

To wireless.

Comment 4 Eitan Adler freebsd_committer

2018-05-28 19:41:17 UTC

batch change:

For bugs that match the following
-  Status Is In progress 
AND
- Untouched since 2018-01-01.
AND
- Affects Base System OR Documentation

DO:

Reset to open status.


Note:
I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.