mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Steven Noonan" <steven@uplinklabs.net>
To: "Justin P. Mattock" <justinmattock@gmail.com>
Cc: "Dave Jones" <davej@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: ath9k microwave anomaly
Date: Fri, 2 Jan 2009 19:49:39 -0800	[thread overview]
Message-ID: <f488382f0901021949y60b6d60fjeaeb6bb12a851f8@mail.gmail.com> (raw)
In-Reply-To: <495EDC10.20605@gmail.com>

On Fri, Jan 2, 2009 at 7:31 PM, Justin P. Mattock
<justinmattock@gmail.com> wrote:
> Dave Jones wrote:
>>
>> On Fri, Jan 02, 2009 at 06:47:32PM -0800, Justin P. Mattock wrote:
>>  > Now I'm not trying to be funny,
>>  > but I think I figured a problem
>>  > with running ath9k, and having the internet
>>  > timeout.(for me at least);
>>  > When streaming T.V.(cspan2), and
>>  > streaming music(somafm), at the same time,
>>  > then using the microwave, I'll experience a blackout
>>  > of internet(T.V. stops, then music stops streaming);
>>
>> not specific to ath9k.
>>
>> http://blogs.zdnet.com/Ou/?p=578 has some pretty graphics
>> to show just how much noise a microwave puts into the part
>> of the spectrum wifi uses.
>>
>>        Dave
>>
>>
>
> Damn that's allot,
> no wonder I was having these timeouts.
> i.g. system streams fine for 10 hours.
> then the next day a timeout after 2 hours due
> to microwave use.
> Thanks for pointing that blog out.
> that opened my eyes up to how powerful
> a microwave is. makes me wonder if that
> grade in the window actually does what is supposed to.
> (block gamma rays or whatever the dangerous wave is);
>
> regards;
>
> Justin P. Mattock
>
Yeah, I think it was Luis Rodriguez (from Atheros) who told me that a
microwave was the best way to make a signal "wet poop" for
interference testing.

  parent reply	other threads:[~2009-01-03  3:49 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-03  2:47 Justin P. Mattock
2009-01-03  3:21 ` Dave Jones
2009-01-03  3:31   ` Justin P. Mattock
2009-01-03  3:48     ` Dave Jones
2009-01-07 16:45       ` Pavel Machek
2009-01-03  3:49     ` Steven Noonan [this message]
2009-01-03  3:59       ` Justin P. Mattock
2009-01-03  4:48         ` Robert Hancock
2009-01-03  7:30           ` Willy Tarreau
2009-01-03  8:11             ` Justin P. Mattock
2009-01-03 19:51               ` Folkert van Heusden
2009-01-03 20:15                 ` Justin P. Mattock
2009-01-03 20:20                   ` Folkert van Heusden
2009-01-03 20:58                     ` Justin P. Mattock
2009-01-03 21:26                       ` Bastien ROUCARIES
2009-01-03 22:52                         ` Justin P. Mattock
2009-01-03 14:15             ` Bastien ROUCARIES
2009-01-03 16:52               ` Justin P. Mattock
2009-01-03 13:49     ` Alan Cox

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=f488382f0901021949y60b6d60fjeaeb6bb12a851f8@mail.gmail.com \
    --to=steven@uplinklabs.net \
    --cc=davej@redhat.com \
    --cc=justinmattock@gmail.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®