From mboxrd@z Thu Jan 1 00:00:00 1970 From: W. van den Akker Date: Wed, 21 Jan 2009 11:17:42 +0100 Subject: [ath9k-devel] still same problem In-Reply-To: <200901210854.19236.listsrv@wilsoft.nl> References: <49601028.9030201@gmail.com> <200901210854.19236.listsrv@wilsoft.nl> Message-ID: <200901211117.43079.listsrv@wilsoft.nl> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org 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.