From: Brendan Kirby <brendan.kirby@imgtec.com>
To: <pinskia@gmail.com>
Cc: "<gdb@sourceware.org>" <gdb@sourceware.org>,
"<sergiodj@redhat.com>" <sergiodj@redhat.com>,
"Maciej W. Rozycki" <maciej.rozycki@imgtec.com>
Subject: Re: MIPS GDB Buildbot slave running Debian Jessie
Date: Mon, 13 Jul 2015 23:01:00 -0000 [thread overview]
Message-ID: <55A4433F.2050704@imgtec.com> (raw)
In-Reply-To: <C81FD62A-77B3-4CB5-9004-4D7916C5FE59@gmail.com>
On 07/13/2015 02:55 PM, pinskia@gmail.com wrote:
>> On Jul 14, 2015, at 5:32 AM, Brendan Kirby <brendan.kirby@imgtec.com> wrote:
>>
>> I'm interested in setting up a GDB Buildbot slave on a MIPS board. The
>> board is an Edge Router Pro board running Debian Jessie. I've
>> configured, built and run the GDB test suite on it based on the steps
>> other builders are using in the GDB Buildbot master. Due to what looks
>> like I-cache coherency issues in the kernel the board needs to be run
>> with no SMP. Otherwise it builds and runs the test suite correctly.
>> We're passing over 23,000 of the GDB tests, but we still have 400 to 500
>> test failures. Would it be possible to get this board added to the GDB
>> Buildbot? If so, could you send me or point me at the config.json and
>> the master.cfg files so that I can send a patch?
> There is no I cache coherency issues I know with respect of the octeon inside the edge router pro. Maybe it is just kernel version issue. I would run 4.1 on it as that should have most if not all octeon support in it.
I'm actually running the 4.1.1 kernel from kernel.org on this board. I
can send the results from a big and little endian run if that will
help. Also, I can try it on 4.1.2 which I think just came out last week.
Brendan
next prev parent reply other threads:[~2015-07-13 23:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 21:32 Brendan Kirby
2015-07-13 21:55 ` pinskia
2015-07-13 23:01 ` Brendan Kirby [this message]
2015-07-13 23:13 ` Sergio Durigan Junior
2015-07-14 17:37 ` Sergio Durigan Junior
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=55A4433F.2050704@imgtec.com \
--to=brendan.kirby@imgtec.com \
--cc=gdb@sourceware.org \
--cc=maciej.rozycki@imgtec.com \
--cc=pinskia@gmail.com \
--cc=sergiodj@redhat.com \
/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