From: chrubis@suse.cz
To: Bhushan Kumar <Bhushan.Kumar@mphasis.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] LTP] [PATCH ]: network stress interfaces part of the LTP stress fails
Date: Tue, 12 Feb 2013 16:33:47 +0100 [thread overview]
Message-ID: <20130212153347.GA24578@rei> (raw)
In-Reply-To: <E351E450E8B9F54684A699D42DC5ADF224468DBA@MPBAGVEX02.corp.mphasis.com>
Hi!
> Actually i relized below mentioned suggetion given by you.Currently i am trying to find out exact root cause for this issue :
>
> The Network stress interfaces part of the LTP stress fails.
>
> network_stress.interface:if4-mtu-change FAIL 2
>
> Below are the cause for failing above mentioned testcase:
>
> if4-mtu-change01 0 TINFO : Verify the IPv4 connectivity is not broken when ifconfig command changes MTU 128 times every 5 seconds
>
> if4-mtu-change01 1 TFAIL : eth1 is broken.
>
> if4-mtu-change02 0 TINFO : Verify the IPv4 connectivity is not broken when ip command changes MTU 128 times every 5 seconds
>
> if4-mtu-change02 2 TBROK : Test Link 0 is somthing wrong.
>
> Could u Please provide me any pointer/suggstion.
Sorry, you have to debug this on your own.
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2013-02-12 15:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 14:04 [LTP] LTP] [PATCH ]: network stress interfaces part of the LTP stress fails Bhushan Kumar
2013-02-12 14:41 ` chrubis
[not found] ` <E351E450E8B9F54684A699D42DC5ADF224468DBA@MPBAGVEX02.corp.mphasis.com>
2013-02-12 15:33 ` chrubis [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-02-01 13:32 KUMAR, BHUSHAN
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=20130212153347.GA24578@rei \
--to=chrubis@suse.cz \
--cc=Bhushan.Kumar@mphasis.com \
--cc=ltp-list@lists.sourceforge.net \
/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