All of lore.kernel.org
 help / color / mirror / Atom feed
From: W. van den Akker <listsrv@wilsoft.nl>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] still same problem
Date: Wed, 21 Jan 2009 11:17:42 +0100	[thread overview]
Message-ID: <200901211117.43079.listsrv@wilsoft.nl> (raw)
In-Reply-To: <200901210854.19236.listsrv@wilsoft.nl>

On Wednesday 21 January 2009, W. van den Akker wrote:
> > So my theory is that I was triggering the same problem using SMP/
> > Hyperthreading, I suspect your system is not a smaller single
> > processor system?  That would at least support that theory.  I think
> > the problem could be a spinlock locking problem in the interrupt
> > handler, or something like that.  I've programmed drivers, wrote a
> > good part of the IVTV driver, and this behavior reminds me of what I
> > saw there at times during development  (it would be stable on UP
> > systems, lock like this on SMP systems).  I have been peeking around
> > in the code some to get familiar with it, but of course may take some
> > time for me to start grasping what is going on to be able to
> > contribute any help myself.  So this is just what I'm thinking, since
> > freezes like this often seem to be something wrong in the interrupt
> > handler for SMP/preemption configured systems.  If you are using SMP,
> > maybe trying it with just one processor enabled would be a good test
> > to see if this is really true there too.
>
> Hil Chris,
>
> This is correct. Its a SMP system with HT. So I think your assumption is
> right. It must be in that direction.
>
> I will try to test it with one CPU disabled.
> I will report back.
>

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.

I will be happy to do further testing.

gr,
Willem

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

  parent reply	other threads:[~2009-01-21 10:17 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
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 [this message]
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=200901211117.43079.listsrv@wilsoft.nl \
    --to=listsrv@wilsoft.nl \
    --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.