From: srikanth krishnakar <skrishnakar@gmail.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Linuxppc-dev@ozlabs.org, Ltp-list@lists.sourceforge.net
Subject: Re: [LTP] msgctl10 fails on Powerpc Linux-2.6.29.6
Date: Fri, 24 Jul 2009 02:01:40 +0530 [thread overview]
Message-ID: <6213bc560907231331p188a7b32q7287e9fe777eaf18@mail.gmail.com> (raw)
In-Reply-To: <13B0CDE8-B974-4CFA-A4B9-8AC4374B4694@kernel.crashing.org>
[-- Attachment #1: Type: text/plain, Size: 2308 bytes --]
On Thu, Jul 23, 2009 at 6:33 AM, Kumar Gala <galak@kernel.crashing.org>wrote:
>
> On Jul 22, 2009, at 11:32 AM, srikanth krishnakar wrote:
>
>
>>
>> On Wed, Jul 22, 2009 at 9:14 PM, Kumar Gala <galak@kernel.crashing.org>
>> wrote:
>>
>> On Jul 22, 2009, at 10:38 AM, srikanth krishnakar wrote:
>>
>>
>>
>> On Wed, Jul 22, 2009 at 8:52 PM, Kumar Gala <galak@kernel.crashing.org>
>> wrote:
>> I'm not seeing any BUG* in traps.c @ line 904.
>>
>>
>> On Jul 21, 2009, at 4:33 AM, srikanth krishnakar wrote:
>>
>> The LTP test case msgctl10.c fails on linux-2.6.29.6 for PowerPC
>> architecture (ppc440)
>>
>>
>> msgctl10 1 B------------[ cut here ]------------
>> kernel BUG at arch/powerpc/kernel/traps.c:904!
>> Oops: Exception in kernel mode, sig: 5 [#9]
>>
>> I'm not seeing any BUG* in traps.c @ line 904. Do you have some other
>> patches on top of 2.6.29.6?
>>
>> - k
>>
>>
>> I have LTTng patches on top of linux-2.6.29.6.
>>
>> Does it modify traps.c? Can you see what the code around line 904 looks
>> like and post that.
>>
>> - k
>> 896
>> 897 #if defined(CONFIG_XILINX_VIRTEX_5_FXT) && defined(CONFIG_PPC_FPU)
>> 898 if (reason & REASON_ILLEGAL) {
>> 899 if (excep_state < 1) {
>> 900 excep_state++;
>> 901 return;
>> 902 }
>> 903 /* should never get here */
>> 904 BUG();
>> 905 }
>> 906 #endif
>> 907
>> 908 /* Try to emulate it if we should. */
>>
>>
> Are you sure this is coming from the LTTng patches? Which actual patch
> makes this change?
>
> - k
>
Thanks kumar,
I've got the patch out which fixes the issues. But now.. seems there is some
generic issue in PPC440 targets, I am observing that
*remap_file_pages01* and *remap_file_pages02 *test cases from LTP are
failing since *Linux-2.6.24* kernel to *Linux-2.6.30*. If you can give some
pointers that would be greatly appreciated ! Or if you have results for this
on any PPC44x would be helpful.
Arch : PowerPC
Target : Xilinx PowerPC440 virtex5
I've tried to test the cause for this but found that kernel throws error
message of "segmentation fault".
Thanks in Advance.
-Srikant
--
"The Good You Do, The Best You GET"
Regards
Srikanth Krishnakar
**********************
[-- Attachment #2: Type: text/html, Size: 4558 bytes --]
prev parent reply other threads:[~2009-07-23 20:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 9:33 msgctl10 fails on Powerpc Linux-2.6.29.6 srikanth krishnakar
2009-07-22 15:22 ` [LTP] " Kumar Gala
2009-07-22 15:38 ` srikanth krishnakar
2009-07-22 15:44 ` Kumar Gala
2009-07-22 16:32 ` srikanth krishnakar
2009-07-23 1:03 ` Kumar Gala
2009-07-23 20:31 ` srikanth krishnakar [this message]
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=6213bc560907231331p188a7b32q7287e9fe777eaf18@mail.gmail.com \
--to=skrishnakar@gmail.com \
--cc=Linuxppc-dev@ozlabs.org \
--cc=Ltp-list@lists.sourceforge.net \
--cc=galak@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).