From: Jouni Malinen <jouni.malinen@atheros.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] still same problem
Date: Wed, 21 Jan 2009 14:35:42 +0200 [thread overview]
Message-ID: <1232541342.6354.9.camel@jm-desktop> (raw)
In-Reply-To: <200901211111.53874.wvdakker@wilsoft.nl>
On Wed, 2009-01-21 at 02:11 -0800, W. van den Akker wrote:
> I have tested with 1 CPU disabled. Running now for about 2 hours without
> hangups (I have several connection drops, but it will reconnect).
>
> I have also tested with 2 CPU's and HT-disabled (noht parameter) but that
> had no effect.
>
> So SMP looks like the cause of the problem here.
Thanks for testing this! I'm running most of my tests with a dual core
system, so SMP is being used, but with two cores, not two separate
chips. I don't think there should be much difference there, but
certainly our hardware configuration is different.
Could you please describe your hardware with more details so that we can
see whether we could find a similar system to try to reproduce this? Is
this the IBM 206 eserver with WMP300N you mentioned in an earlier
message in the thread? That seems to be (by default) a uni-processor
setup, so I would like to make sure we understand what is the exact
hardware used here since I do not think we have been able to reproduce
this type of issue so far in any dual core systems.
- Jouni
next prev parent reply other threads:[~2009-01-21 12:35 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-04 1:26 [ath9k-devel] still same problem Dmitri Seletski
2009-01-04 1:53 ` Barry Green
2009-01-04 3:34 ` Luis R. Rodriguez
2009-01-04 9:58 ` Jens Ott - Opteamax
2009-01-05 16:09 ` Luis R. Rodriguez
2009-01-17 23:55 ` W. van den Akker
2009-01-18 1:41 ` Jens Ott - Opteamax
2009-01-18 9:14 ` W. van den Akker
2009-01-18 5:17 ` Dmitri Seletski
2009-01-18 9:34 ` W. van den Akker
2009-01-18 15:16 ` Luis R. Rodriguez
2009-01-19 8:35 ` W. van den Akker
2009-01-19 22:31 ` W. van den Akker
2009-01-20 17:48 ` Luis R. Rodriguez
2009-01-20 18:32 ` W. van den Akker
2009-01-20 22:22 ` W. van den Akker
2009-01-20 23:08 ` Chris Kennedy
2009-01-21 7:54 ` W. van den Akker
2009-01-21 10:11 ` W. van den Akker
2009-01-21 12:35 ` Jouni Malinen [this message]
2009-01-21 17:01 ` [ath9k-devel] [PATCH] " Chris Kennedy
2009-01-21 21:05 ` W. van den Akker
2009-01-27 9:30 ` W. van den Akker
2009-01-27 21:47 ` Chris Kennedy
2009-01-21 17:15 ` [ath9k-devel] " W. van den Akker
2009-01-21 10:17 ` W. van den Akker
2009-01-04 10:33 ` W. van den Akker
2009-01-04 10:47 ` W. van den Akker
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=1232541342.6354.9.camel@jm-desktop \
--to=jouni.malinen@atheros.com \
--cc=ath9k-devel@lists.ath9k.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 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.