cpufreq.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 16436] ath5k (AR5001) does not work after resume and fails with "ath5k phy0: gain calibration timeout"
Date: Sat, 5 May 2012 10:36:30 GMT	[thread overview]
Message-ID: <201205051036.q45AaUob023382@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-16436-12968@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=16436


zxcasdqwe@mailinator.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |zxcasdqwe@mailinator.com




--- Comment #39 from zxcasdqwe@mailinator.com  2012-05-05 10:36:27 ---
I still have it on a vanilla 32bit SMP 3.3.3 with AR5414 .
I upgrade kernels very often and I first started noticing the problem with 3.3
series (3.3.2, to be precise).
I've had these kernels in 3.2/3.3 series:
3.2.2
3.2.3
3.2.4
3.2.5
3.2.6
3.2.7
3.2.8
3.2.9
3.2.11
3.3.2
3.3.3

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2012-05-05 10:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-16436-12968@https.bugzilla.kernel.org/>
2011-04-27 19:19 ` [Bug 16436] ath5k (AR5001) does not work after resume and fails with "ath5k phy0: gain calibration timeout" bugzilla-daemon
2011-06-23 18:41 ` bugzilla-daemon
2011-06-23 18:43 ` bugzilla-daemon
2012-01-18  2:13 ` bugzilla-daemon
2012-05-05 10:36 ` bugzilla-daemon [this message]
2012-05-05 10:39 ` bugzilla-daemon
2012-05-07 21:54 ` bugzilla-daemon
2012-05-07 22:11 ` bugzilla-daemon
2012-05-13 14:33 ` bugzilla-daemon
2012-05-14 22:46 ` bugzilla-daemon
2012-08-29 17:26 ` bugzilla-daemon
2012-11-05 14:20 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201205051036.q45AaUob023382@bugzilla.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=cpufreq@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).