Re: an oops possibly due to an SMP related bug in netfilter

[Bill Davidsen <davidsen@tmr.com>]

Joshua N Pritikin wrote:
> On Mon, Aug 30, 2004 at 06:57:53PM +0200, KOVACS Krisztian wrote:
> 
>>On Mon, Aug 30, 2004 at 05:38:09PM +0530, Joshua N Pritikin wrote:
>>
>>>(Perhaps I am one of the few people crazy enough to run a firewall on
>>>an SMP machine.  ;-)
>>> 
>>>CPU:    0 
>>>EIP:    0060:[<c8895955>]    Not tainted 
>>>EFLAGS: 00010246   (2.6.7)  
>>>EIP is at __ip_conntrack_find+0x179/0x1a0 [ip_conntrack] 
>>>eax: 00000001   ebx: 00000000   ecx: c0353cc0   edx: 00000000 
>>>esi: 00000000   edi: 00000000   ebp: c0353c88   esp: c0353c6c 
>>>ds: 007b   es: 007b   ss: 0068 
>>>Process swapper (pid: 0, threadinfo=c0352000 task=c0300980)
>>
>>  I don't think you're the only one running iptables on SMP... This looks
>>like a conntrack hash table corruption, so the first thing you should
>>check is your memory, of course. Are you 100 percent sure that it is ok?
> 
> 
> Fair enough.
> 
> Memtest86 doesn't spot anything BUT it could be due to voltage
> fluctuation.  I guess I can't run this motherboard without a UPS.
> 
Bad to guess, there's a program called memburn which may also be used. 
It's doing testing in a different way and I just grabbed it because 
someone in comp.sys.intel reported finding problems which memtest didn't 
show.

I run firewall on a LOT of dual Xeon+HT and ran iptables firewall on 
dual P5-166 until it died. I don't think there are problems.

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me