From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Adrian von Bidder <avbidder@fortytwo.ch>
Cc: linux-wireless@vger.kernel.org
Subject: Re: ath5k connection loss (failed to wakeup the MAC Chip)
Date: Tue, 28 Jul 2009 22:52:30 +0300 [thread overview]
Message-ID: <1248810750.30488.8.camel@maxim-laptop> (raw)
In-Reply-To: <200907280838.42541@fortytwo.ch>
On Tue, 2009-07-28 at 08:38 +0200, Adrian von Bidder wrote:
> Heyho!
>
> (This is using kernel 2.6.31-rc3 as packaged by Debian)
>
> While taking a full backup of my laptop, I noticed that after a few 100M the
> ath5k can't connect to WLAN anymore.
Yep, same here, same hardware.
I must say that moving large files typically results in prolonged
periods in which no communication is gone, maybe even something like
that.
Best regards,
Maxim Levitsky
next prev parent reply other threads:[~2009-07-28 19:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 6:38 ath5k connection loss (failed to wakeup the MAC Chip) Adrian von Bidder
2009-07-28 19:52 ` Maxim Levitsky [this message]
2009-07-28 23:53 ` Nick Kossifidis
2009-07-29 10:11 ` Adrian von Bidder
2009-07-29 19:09 ` Ben Greear
2009-07-29 21:07 ` Nick Kossifidis
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=1248810750.30488.8.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=avbidder@fortytwo.ch \
--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