Linux wireless drivers development
 help / color / mirror / Atom feed
From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	ath5k-devel@lists.ath5k.org
Subject: Re: [ath5k-devel] deadlock triggered by buggy hardware (EEE PC) in wireless-testing+rfkill-rewrite v11
Date: Sun, 24 May 2009 20:55:50 +0300	[thread overview]
Message-ID: <1243187750.5450.1.camel@maxim-laptop> (raw)
In-Reply-To: <4A196ABE.4080806@tuffmail.co.uk>

On Sun, 2009-05-24 at 16:41 +0100, Alan Jenkins wrote:
> ath5k phy5: failed to wakeup the MAC Chip

I hate this bug....
I have it on my aspire one.
It happens seldom after a resume from ram.


Best regards,
	Maxim Levitsky


      reply	other threads:[~2009-05-24 17:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-24 10:23 deadlock triggered by buggy hardware (EEE PC) in wireless-testing+rfkill-rewrite v11 Alan Jenkins
2009-05-24 15:41 ` Alan Jenkins
2009-05-24 17:55   ` Maxim Levitsky [this message]

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=1243187750.5450.1.camel@maxim-laptop \
    --to=maximlevitsky@gmail.com \
    --cc=alan-jenkins@tuffmail.co.uk \
    --cc=ath5k-devel@lists.ath5k.org \
    --cc=linux-wireless@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