linux-mips
[Top] [All Lists]

Re: movidis x16 hard lockup using 2.6.33

To: David Daney <ddaney@caviumnetworks.com>
Subject: Re: movidis x16 hard lockup using 2.6.33
From: Peter 'p2' De Schrijver <p2@debian.org>
Date: Fri, 26 Mar 2010 21:05:32 +0200
Cc: linux-mips@linux-mips.org
In-reply-to: <4BAD03A5.9070701@caviumnetworks.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20100326184132.GU2437@apfelkorn> <4BAD03A5.9070701@caviumnetworks.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.18 (2008-05-17)
Hi David,

> On 03/26/2010 11:41 AM, Peter 'p2' De Schrijver wrote:
>> Hi,
>>
>> Thanks to Jan Rovins and David Daney we linux 2.6.33 working fine with 1 
>> additional
>> patch for the ethernet NICs. We are using this machine as a buildd. 
>> Unfortunately
>> we found out that building gcc 4.5 using all available 16 cores causes the 
>> machine
>> to lock up after about 6 hours of building. There is no output on the serial
>> console indicating a kernel panic or some malfunction. The machine is hosted 
>> in
>> some data center so physical access is difficult.
>>
>> Any insight welcome !
>>
>> Thanks,
>>
>
> What is the output of:
>
> cat /proc/cpuinfo | grep 'system type'
>
>

p2@corelli:/home/buildd$ cat /proc/cpuinfo | grep 'system type'                 
                             
system type             : CUST_WSX16 (CN3860p3.X-500-EXP)


> Also you could try running with the attached patch.  It is not the best  
> watchdog, but it will print the register state for each core when things  
> get stuck.  Occasionally that is enough to see where the problem is.
>

Ok. I will try that.

Thanks,

Peter.

<Prev in Thread] Current Thread [Next in Thread>