From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel@vger.kernel.org
Cc: Steven Noonan <steven@uplinklabs.net>, Dave Jones <davej@redhat.com>
Subject: Re: ath9k microwave anomaly
Date: Fri, 02 Jan 2009 22:48:29 -0600 [thread overview]
Message-ID: <495EEE1D.8050500@shaw.ca> (raw)
In-Reply-To: <495EE2A0.2080703@gmail.com>
Justin P. Mattock wrote:
> Steven Noonan wrote:
>> 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.
>>
>>
> Well, this one here seems to be not
> that old, but it's enough to cause
> interference. Hopefully not too old
> to cause me to go sterile!!
> interesting thing is when
> the microwave is cold and then started
> I noticed more interference, as to when
> it's been running for a while.
I think the standards for microwaves allow a reasonable amount of
microwave leakage - still way below the levels that can harm you, but
compared to the power levels that a WiFi device puts out, it's pretty
significant..
next prev parent reply other threads:[~2009-01-03 4:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-03 2:47 ath9k microwave anomaly 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
2009-01-03 3:59 ` Justin P. Mattock
2009-01-03 4:48 ` Robert Hancock [this message]
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=495EEE1D.8050500@shaw.ca \
--to=hancockr@shaw.ca \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=steven@uplinklabs.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.