From: Peter 'p2' De Schrijver <p2@debian.org>
To: David Daney <ddaney@caviumnetworks.com>
Cc: linux-mips@linux-mips.org
Subject: Re: movidis x16 hard lockup using 2.6.33
Date: Fri, 26 Mar 2010 21:05:32 +0200 [thread overview]
Message-ID: <20100326190532.GV2437@apfelkorn> (raw)
In-Reply-To: <4BAD03A5.9070701@caviumnetworks.com>
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.
next prev parent reply other threads:[~2010-03-26 19:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 18:41 movidis x16 hard lockup using 2.6.33 Peter 'p2' De Schrijver
2010-03-26 18:57 ` David Daney
2010-03-26 19:05 ` Peter 'p2' De Schrijver [this message]
2010-03-27 23:07 ` Andreas Barth
2010-03-29 16:54 ` David Daney
2010-03-29 22:02 ` Andreas Barth
2010-03-29 22:13 ` David Daney
2010-03-29 22:23 ` Andreas Barth
2010-04-02 13:32 ` Andreas Barth
2010-04-03 15:43 ` Peter 'p2' De Schrijver
2010-04-15 18:43 ` irqbalance on movidis crashes the machine (was: movidis x16 hard lockup using 2.6.33) Andreas Barth
2010-04-15 20:35 ` Andreas Barth
2010-04-25 13:54 ` Andreas Barth
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=20100326190532.GV2437@apfelkorn \
--to=p2@debian.org \
--cc=ddaney@caviumnetworks.com \
--cc=linux-mips@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox