You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(6) |
Jun
(12) |
Jul
(46) |
Aug
(8) |
Sep
(27) |
Oct
(73) |
Nov
(56) |
Dec
(34) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(36) |
Feb
(33) |
Mar
(50) |
Apr
(66) |
May
(76) |
Jun
(63) |
Jul
(63) |
Aug
(26) |
Sep
(35) |
Oct
(34) |
Nov
(82) |
Dec
(99) |
2003 |
Jan
(152) |
Feb
(76) |
Mar
(146) |
Apr
(156) |
May
(71) |
Jun
(46) |
Jul
(42) |
Aug
(34) |
Sep
(32) |
Oct
(49) |
Nov
(66) |
Dec
(78) |
2004 |
Jan
(76) |
Feb
(48) |
Mar
(25) |
Apr
(78) |
May
(76) |
Jun
(71) |
Jul
(39) |
Aug
(53) |
Sep
(27) |
Oct
(26) |
Nov
(23) |
Dec
(29) |
2005 |
Jan
(53) |
Feb
(41) |
Mar
(48) |
Apr
(36) |
May
(29) |
Jun
(71) |
Jul
(61) |
Aug
(77) |
Sep
(49) |
Oct
(32) |
Nov
(27) |
Dec
(40) |
2006 |
Jan
(23) |
Feb
(48) |
Mar
(24) |
Apr
(31) |
May
(50) |
Jun
(42) |
Jul
(24) |
Aug
(140) |
Sep
(55) |
Oct
(43) |
Nov
(11) |
Dec
(18) |
2007 |
Jan
(15) |
Feb
(20) |
Mar
(99) |
Apr
(110) |
May
(140) |
Jun
(98) |
Jul
(90) |
Aug
(58) |
Sep
(86) |
Oct
(79) |
Nov
(137) |
Dec
(129) |
2008 |
Jan
(277) |
Feb
(321) |
Mar
(285) |
Apr
(373) |
May
(415) |
Jun
(328) |
Jul
(288) |
Aug
(469) |
Sep
(334) |
Oct
(570) |
Nov
(368) |
Dec
(376) |
2009 |
Jan
(401) |
Feb
(317) |
Mar
(373) |
Apr
(309) |
May
(280) |
Jun
(371) |
Jul
(504) |
Aug
(465) |
Sep
(231) |
Oct
(295) |
Nov
(271) |
Dec
(222) |
2010 |
Jan
(313) |
Feb
(231) |
Mar
(251) |
Apr
(166) |
May
(124) |
Jun
(83) |
Jul
(141) |
Aug
(195) |
Sep
(160) |
Oct
(204) |
Nov
(295) |
Dec
(206) |
2011 |
Jan
(262) |
Feb
(176) |
Mar
(168) |
Apr
(217) |
May
(70) |
Jun
(65) |
Jul
(89) |
Aug
(169) |
Sep
(125) |
Oct
(64) |
Nov
(116) |
Dec
(148) |
2012 |
Jan
(343) |
Feb
(352) |
Mar
(205) |
Apr
(151) |
May
(140) |
Jun
(103) |
Jul
(156) |
Aug
(221) |
Sep
(55) |
Oct
(150) |
Nov
(79) |
Dec
(77) |
2013 |
Jan
(95) |
Feb
(78) |
Mar
(157) |
Apr
(213) |
May
(220) |
Jun
(227) |
Jul
(275) |
Aug
(224) |
Sep
(156) |
Oct
(248) |
Nov
(338) |
Dec
(181) |
2014 |
Jan
(165) |
Feb
(299) |
Mar
(338) |
Apr
(315) |
May
(277) |
Jun
(186) |
Jul
(204) |
Aug
(212) |
Sep
(231) |
Oct
(152) |
Nov
(107) |
Dec
(167) |
2015 |
Jan
(197) |
Feb
(182) |
Mar
(135) |
Apr
(167) |
May
(192) |
Jun
(326) |
Jul
(311) |
Aug
(198) |
Sep
(84) |
Oct
(11) |
Nov
(3) |
Dec
(4) |
2016 |
Jan
(1) |
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2017 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(5) |
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
From: SourceForge.net <no...@so...> - 2007-03-22 07:50:10
|
Bugs item #1630608, was opened at 2007-01-08 14:02 Message generated for change (Comment added) made by subrata_modak You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=103382&aid=1630608&group_id=3382 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Testcases Group: None >Status: Closed >Resolution: Works For Me Priority: 5 Private: No Submitted By: Alexander Leidinger (aleidinger) Assigned to: Nobody/Anonymous (nobody) Summary: creat08 PASSes even when it fails Initial Comment: Hi, I work with some people to improve the Linux compatibility layer in FreeBSD. We use the LTP to verify our emulation layer. We run the LTP linux binaries in a chroot with gentoo libs/binaries withhin our emulation layer. So the LTP is exerciesing the emulated linux syscalls. As part of the tests I noticed, that the creat08 reports PASS in the logfile in the results directory (option "-l <name>" to runltp), but the verbose output to stdout reports failures. In our case we see: test 2 testdir.A.23971/nosetgid: Incorrect group --- test 3 testdir.A.23971/setgid: Incorrect modes, setgid bit not set --- test 4 testdir.A.23971/setgid: Incorrect group --- test 5 Test failed in block1 --- test 6 testdir.B.23971/setgid: Incorrect modes, setgid bit should be set --- test 7 Test failed in block2 --- test 9 Test failed because of above failures Bye, Alexander. ---------------------------------------------------------------------- >Comment By: Subrata (subrata_modak) Date: 2007-03-22 07:50 Message: Logged In: YES user_id=1737361 Originator: NO Please provide a way to reproduce the problem. Kindly see the attached log/output files on the same test. These may be a problem setting with your environment as ther might be a problem in the emulation environment. Thanks-- Subrata File Added: logs-output-creat08.tar ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=103382&aid=1630608&group_id=3382 |
From: Mike F. <va...@ge...> - 2007-03-22 07:33:15
|
On Tuesday 20 March 2007, Bruce Dubbs wrote: > mincore01 3 FAIL : call succeeded unexpectedly > > Is this a problem with the kernel or the test or possibly the compiler? most likely the kernel, but anything is possible you can double check the correct call is being made to the kernel by runnin= g=20 the test through strace =2Dmike |
From: SourceForge.net <no...@so...> - 2007-03-22 07:26:37
|
Bugs item #1630613, was opened at 2007-01-08 14:06 Message generated for change (Comment added) made by subrata_modak You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=103382&aid=1630613&group_id=3382 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Testcases Group: None >Status: Closed >Resolution: Works For Me Priority: 5 Private: No Submitted By: Alexander Leidinger (aleidinger) Assigned to: Nobody/Anonymous (nobody) Summary: dup201 fails without a message Initial Comment: Hi, I work with some people to improve the Linux compatibility layer in FreeBSD. We use the LTP to verify our emulation layer. We run the LTP linux binaries in a chroot with gentoo libs/binaries withhin our emulation layer. So the LTP is exerciesing the emulated linux syscalls. As part of the tests I noticed that the dup201 test fails (FAIL in the logfile in the results directory), but it doesn't print anything to stdout when runltp is started with verbose output (-p -v). Bye, Alexander. ---------------------------------------------------------------------- >Comment By: Subrata (subrata_modak) Date: 2007-03-22 07:26 Message: Logged In: YES user_id=1737361 Originator: NO Please provide a way to reproduce the problem. Please see the attached log/output files on the same test. Thanks-- Subrata File Added: logs-output-dup201.tar ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=103382&aid=1630613&group_id=3382 |
From: SourceForge.net <no...@so...> - 2007-03-22 07:15:46
|
Bugs item #1630623, was opened at 2007-01-08 14:19 Message generated for change (Comment added) made by subrata_modak You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=103382&aid=1630623&group_id=3382 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Testcases Group: None >Status: Closed >Resolution: Works For Me Priority: 5 Private: No Submitted By: Alexander Leidinger (aleidinger) Assigned to: Nobody/Anonymous (nobody) Summary: fsync02 fails without a message Initial Comment: Hi, I work with some people to improve the Linux compatibility layer in FreeBSD. We use the LTP to verify our emulation layer. We run the LTP linux binaries in a chroot with gentoo libs/binaries withhin our emulation layer. So the LTP is exerciesing the emulated linux syscalls. As part of the tests I noticed that the fsync02 test fails (FAIL in the logfile in the results directory), but it doesn't print anything to stdout when runltp is started with verbose output (-p -v). Bye, Alexander. ---------------------------------------------------------------------- >Comment By: Subrata (subrata_modak) Date: 2007-03-22 07:15 Message: Logged In: YES user_id=1737361 Originator: NO Please provide a way to reproduce the problem. Please see the attached log/output files on the same test. Thanks-- Subrata File Added: logs-output-fsync02.tar ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=103382&aid=1630623&group_id=3382 |
From: Subrata M. <sub...@in...> - 2007-03-22 07:01:11
|
Hi Ashok, Please visit http://ltp.cvs.sourceforge.net/ltp/ltp/testcases/kernel/syscalls/sysfs/ to find the relevant testcases that you are looking for. More File System Testcases can be found at: http://ltp.cvs.sourceforge.net/ltp/ltp/testcases/kernel/fs/ and for other IO testcases at: http://ltp.cvs.sourceforge.net/ltp/ltp/testcases/kernel/io/ Regards & Thanks-- Subrata Modak, ==================================== ==================================== "Ashok kumar" <ashokmudalister@ gmail.com> To Sent by: ltp...@li... ltp-list-bounces@ cc lists.sourceforge .net Subject [LTP] sysfs test cases 03/22/07 11:29 AM Hi, Just for my understanding purpose, i want have look at sysfs filesystem testcases. if possible i want run those and also interested in ramfs,debugfs,romfs.. Ashok ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Ltp-list mailing list Ltp...@li... https://lists.sourceforge.net/lists/listinfo/ltp-list |
From: Mike F. <va...@ge...> - 2007-03-22 06:56:29
|
On Wednesday 21 March 2007, Subrata Modak1 wrote: > It would be great if you could submit all your Patches/New Test cases into > "http://sourceforge.net/tracker/?func=3Dadd&group_id=3D3382&atid=3D303382= " apart > from sending to the mailing list. eh, sourceforge sucks ... their tracker system probably hasnt seen any usef= ul=20 changes in years ... but that's my experience =2Dmike |
From: Mike F. <va...@ge...> - 2007-03-22 06:52:59
|
On Wednesday 21 March 2007, Carmelo AMOROSO wrote: > The problem is that the test passes the '&bad_addr' instead of bad_addr > to the sysfs > syscall. true, added to cvs ... thanks ! -mike |
From: Subrata M. <sub...@in...> - 2007-03-22 06:48:05
|
That's correct Mike. But it is for the Admins of LTP to keep track/documentation of the activities. The tracking system serves as a ready and handy reference for any issues as we might miss out some of the very important mails. So, it's great if the patch is also found on the track list in addition to being sent to the mailing lists. Regards & Thanks-- Subrata Modak, ==================================== ==================================== Mike Frysinger <vapier@gentoo.or g> To ltp...@li... 03/22/07 12:06 PM cc Subrata Modak1/India/IBM@IBMIN Subject Re: [LTP] Submit Patches/bugs on sourceforge.net On Wednesday 21 March 2007, Subrata Modak1 wrote: > It would be great if you could submit all your Patches/New Test cases into > "http://sourceforge.net/tracker/?func=add&group_id=3382&atid=303382" apart > from sending to the mailing list. eh, sourceforge sucks ... their tracker system probably hasnt seen any useful changes in years ... but that's my experience -mike (See attached file: attty9sn.dat) |
From: Ashok k. <ash...@gm...> - 2007-03-22 05:59:47
|
Hi, Just for my understanding purpose, i want have look at sysfs filesystem testcases. if possible i want run those and also interested in ramfs,debugfs,romfs.. Ashok |
From: Carmelo A. <car...@st...> - 2007-03-21 09:24:55
|
Hi All, running the LTP test suite on STLinux distro I suspect to have found a bug into sysfs06 test case. The problem is that the test passes the '&bad_addr' instead of bad_addr to the sysfs syscall. Please, find attached the simple patch. Any comments are welcome. Best regards, Carmelo |
From: Subrata M. <sub...@in...> - 2007-03-21 05:59:17
|
Dear All, It would be great if you could submit all your Patches/New Test cases into "http://sourceforge.net/tracker/?func=add&group_id=3382&atid=303382" apart from sending to the mailing list. It eases the Patch/Bug tracking process for the Admins. Also raise all your bugs on Sourceforge.net. This makes sure that even if some of us misses the mailing list(s), the same bug/patch/new test case is available on Sourceforge.net and can be very easily traced back. Regards & Thanks-- Subrata Modak, ==================================== ==================================== |
From: Bruce D. <bru...@gm...> - 2007-03-21 01:20:10
|
I am running 2.6.16.27 and ltp-full-20070228. I'm getting one funny failure (all other tests pass): $ ./mincore01 mincore01 1 PASS : expected failure: errno = 22 (Invalid argument) mincore01 2 PASS : expected failure: errno = 14 (Bad address) mincore01 3 FAIL : call succeeded unexpectedly mincore01 4 PASS : expected failure: errno = 12 (Cannot allocate memory) I tried to check it out and put in four printfs to see what values were being passed to mincore and I got: PAGESIZE=4096 global_len=8192 global_pointer=0xb7efe000 global_vec=0x8052008 mincore01 1 PASS : expected failure: errno = 22 (Invalid argument) mincore01 2 PASS : expected failure: errno = 14 (Bad address) mincore01 3 PASS : expected failure: errno = 12 (Cannot allocate memory) mincore01 4 PASS : expected failure: errno = 12 (Cannot allocate memory) Removing the printfs returns the failure indication. Is this a problem with the kernel or the test or possibly the compiler? The compiler is gcc-4.0.3. -- Bruce |
From: Mike F. <va...@ge...> - 2007-03-19 07:09:55
|
On Saturday 17 March 2007, Helge Deller wrote: > To be honest, I think this patch is wrong and should be reverted. agreed, done so > Another point: > The "if"-clause itself is wrong as well. > In my opinion it should be: indeed, added to cvs -mike |
From: Helge D. <de...@gm...> - 2007-03-17 11:44:17
|
Michael Reed wrote: > Patch Applied > > Thanks > Michael To be honest, I think this patch is wrong and should be reverted. On Yi's machine the second call of two consecutive calls to gettimeofday(), the second one returned a time which was lower than the first call. This is a kernel bug and adding a nanosleep() just hides the real bug in the kernel. gettimeofday() has to always return monotonic growing (or at least the same value if the resolution is too low) time values, and if it doesn't this has to be fixed in the Linux kernel. Just search the Linux kernel mailing archives for the keywords "TSC", "clocksource" or "TSC unstable" and you will find a lot of work which was done to keep the values correct. Many applications really depend on stable monotonic clock values by gettimeofday(). Another point: The "if"-clause itself is wrong as well. In my opinion it should be: Index: gettimeofday02.c =================================================================== RCS file: /cvsroot/ltp/ltp/testcases/kernel/syscalls/gettimeofday/gettimeofday02.c,v retrieving revision 1.5 diff -u -p -r1.5 gettimeofday02.c --- gettimeofday02.c 27 Feb 2007 23:43:21 -0000 1.5 +++ gettimeofday02.c 17 Mar 2007 11:40:09 -0000 @@ -109,9 +109,9 @@ int main(int ac, char **av) } gettimeofday(&tv2,NULL); - if ( (tv2.tv_usec < tv1.tv_usec) && - (tv2.tv_sec <= tv1.tv_sec) - ) { + if ( (tv2.tv_sec < tv1.tv_sec) || + (tv2.tv_sec == tv1.tv_sec) && (tv2.tv_usec < tv1.tv_usec) + ) { tst_resm(TFAIL, "Time is going backwards (old %d.%d vs new %d %d!",tv1.tv_sec,tv1.tv_usec,tv2.tv_sec,tv2.tv_usec); cleanup(); exit(1); |
From: Mike F. <va...@ge...> - 2007-03-17 02:50:08
|
On Friday 16 March 2007, Henry Yei wrote: > - Adds malloc check and frees memory during cleanup merged, cheers -mike |
From: Mike F. <va...@ge...> - 2007-03-16 21:36:42
|
On Friday 16 March 2007, Ram wrote: > Hi, > Im having an ARM target which is running Linux-2.6.20, The root > filesystem is mounted over NFS. > > Initial Tests work well, After sometime, I get lots of nfs: server not > responding, still trying > and Okay errors. you're probably using NFSv2 + UDP ... dont do that, it sucks force NFSv3 + TCP -mike |
From: Mike F. <va...@ge...> - 2007-03-16 21:29:43
|
On Wednesday 14 March 2007, Will Newton wrote: > "The sizeof() operator and the prefix and postfix "++" and "--" > operators are not required." i was hoping you wouldnt notice that ;) i'm on the fence here ... implementing ++ or -- is trivial, and ((i+=3D1)) = is=20 lamer than ((i++)) ... =2Dmike |
From: Mike F. <va...@ge...> - 2007-03-16 21:28:35
|
On Wednesday 14 March 2007, Riaz Rahaman wrote: > there was bug in my previous patch...for retval of -1 and errno!=0 it > wasn't printing PASS message.. ive already rewritten the test entirely, so you should check current CVS -mike |
From: Jeff B. <jb...@re...> - 2007-03-16 11:04:01
|
Ram wrote: > Hi, > Im trying to test my kernel (ARM). I have a linux-2.6.20 kernel > with NFS Mounted Filesystem. > > The target loses the NFS Link when i perform network tests and memory tests. > > Is there any command line option to disable running these tests. > > > If not, How do i disable the tests at a source code level. Is there > any flag or macro?. > > Regards, > sriram > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Ltp-list mailing list > Ltp...@li... > https://lists.sourceforge.net/lists/listinfo/ltp-list > Ram, runltp has two built in options that you can use. -f CMDFILE Execute user defined list of testcases. -s PATTERN Only run test cases which match PATTERN. You can also write your own test script, Look in the $LTPROOT/testscripts there are plenty of examples. I would recommend building your own CMDFILE and run only the tests you want. If it is a small number you can use the -s option and pass in several tests you want. Thanks, Jeff |
From: Will N. <wil...@gm...> - 2007-03-16 11:03:05
|
On 3/16/07, Ram <vsh...@gm...> wrote: > Hi, > Im having an ARM target which is running Linux-2.6.20, The root > filesystem is mounted over NFS. > > Initial Tests work well, After sometime, I get lots of nfs: server not > responding, still trying > and Okay errors. > > How does one avoid it?. Perhaps your NFS block size is too large. The 2.6 defaults can be quite large and cause a lot of fragmentation which in turn puts a lot of pressure on the kernel network buffers. You could try mounting our NFS volume with the option rsize=1024,wsize=1024 |
From: Subrata M. <sub...@in...> - 2007-03-16 11:02:31
|
Dear Ram, It would be great if could attach file(s) containing the test output and logs. Regards & Thanks-- Subrata Modak, ==================================== ==================================== Ram <vshrirama@gmail. com> To Sent by: ltp...@li... ltp-list-bounces@ cc lists.sourceforge .net Subject [LTP] running LTP - NFS issues 03/16/07 04:18 PM Hi, Im having an ARM target which is running Linux-2.6.20, The root filesystem is mounted over NFS. Initial Tests work well, After sometime, I get lots of nfs: server not responding, still trying and Okay errors. How does one avoid it?. After a point, I only get these messages. The network connectivity is fine. I just want to run my tests on a target whose rootfs is mounted via NFS. Regards, sriram statvfs01 0 INFO : file system free blocks = 1010703 statvfs01 0 INFO : file system total inodes = 0 statvfs01 0 INFO : file system free inodes = 0 statvfs01 0 INFO : file system id = 0 statvfs01 0 INFO : file system max filename length = 255 <<<execution_status>>> duration=1 termination_type=exited termination_id=0 corefile=no cutime=1 cstime=0 <<<test_end>>> <<<test_start>>> tag=string01 stime=1027 cmdline="string01" contacts="" analysis=exit initiation_status="ok" <<<test_output>>> string01 1 PASS : Test passed <<<execution_status>>> duration=0 termination_type=exited termination_id=0 corefile=no cutime=5 cstime=0 <<<test_end>>> <<<test_start>>> tag=swapoff01 stime=1027 cmdline="swapoff01" contacts="" analysis=exit initiation_status="ok" <<<test_output>>> <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK ---------------------------------------- <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK swapoff01 1 BROK : Failed to make swapfile <<<execution_status>>> duration=582 termination_type=exited termination_id=2 corefile=no cutime=17 cstime=191 <<<test_end>>> <<<test_start>>> tag=swapoff02 stime=1609 cmdline="swapoff02" contacts="" analysis=exit initiation_status="ok" <<<test_output>>> <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK swapoff02 1 BROK : Failed to make swapfile swapoff02 2 BROK : Remaining cases broken swapoff02 3 BROK : Remaining cases broken swapoff02 0 WARN : Failed to turn off swap file. System reboot after execution of LTP test suite is recommended. <<<execution_status>>> duration=519 termination_type=exited termination_id=6 corefile=no cutime=25 cstime=190 <<<test_end>>> <<<test_start>>> tag=swapon01 stime=2128 cmdline="swapon01" contacts="" analysis=exit initiation_status="ok" <<<test_output>>> <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK CTRL-A Z for help |115200 8N1 | NOR | Minicom 2.00.0 | VT102 | Offline ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Ltp-list mailing list Ltp...@li... https://lists.sourceforge.net/lists/listinfo/ltp-list |
From: Ram <vsh...@gm...> - 2007-03-16 10:49:00
|
Hi, Im having an ARM target which is running Linux-2.6.20, The root filesystem is mounted over NFS. Initial Tests work well, After sometime, I get lots of nfs: server not responding, still trying and Okay errors. How does one avoid it?. After a point, I only get these messages. The network connectivity is fine. I just want to run my tests on a target whose rootfs is mounted via NFS. Regards, sriram statvfs01 0 INFO : file system free blocks = 1010703 statvfs01 0 INFO : file system total inodes = 0 statvfs01 0 INFO : file system free inodes = 0 statvfs01 0 INFO : file system id = 0 statvfs01 0 INFO : file system max filename length = 255 <<<execution_status>>> duration=1 termination_type=exited termination_id=0 corefile=no cutime=1 cstime=0 <<<test_end>>> <<<test_start>>> tag=string01 stime=1027 cmdline="string01" contacts="" analysis=exit initiation_status="ok" <<<test_output>>> string01 1 PASS : Test passed <<<execution_status>>> duration=0 termination_type=exited termination_id=0 corefile=no cutime=5 cstime=0 <<<test_end>>> <<<test_start>>> tag=swapoff01 stime=1027 cmdline="swapoff01" contacts="" analysis=exit initiation_status="ok" <<<test_output>>> <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK ---------------------------------------- <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK swapoff01 1 BROK : Failed to make swapfile <<<execution_status>>> duration=582 termination_type=exited termination_id=2 corefile=no cutime=17 cstime=191 <<<test_end>>> <<<test_start>>> tag=swapoff02 stime=1609 cmdline="swapoff02" contacts="" analysis=exit initiation_status="ok" <<<test_output>>> <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK swapoff02 1 BROK : Failed to make swapfile swapoff02 2 BROK : Remaining cases broken swapoff02 3 BROK : Remaining cases broken swapoff02 0 WARN : Failed to turn off swap file. System reboot after execution of LTP test suite is recommended. <<<execution_status>>> duration=519 termination_type=exited termination_id=6 corefile=no cutime=25 cstime=190 <<<test_end>>> <<<test_start>>> tag=swapon01 stime=2128 cmdline="swapon01" contacts="" analysis=exit initiation_status="ok" <<<test_output>>> <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK <5>nfs: server 192.168.13.251 not responding, still trying nfs: server 192.168.13.251 not responding, still trying <5>nfs: server 192.168.13.251 OK nfs: server 192.168.13.251 OK CTRL-A Z for help |115200 8N1 | NOR | Minicom 2.00.0 | VT102 | Offline |
From: Ram <vsh...@gm...> - 2007-03-16 08:32:37
|
Hi, Im trying to test my kernel (ARM). I have a linux-2.6.20 kernel with NFS Mounted Filesystem. The target loses the NFS Link when i perform network tests and memory tests. Is there any command line option to disable running these tests. If not, How do i disable the tests at a source code level. Is there any flag or macro?. Regards, sriram |
From: Helge D. <de...@gm...> - 2007-03-15 20:47:20
|
Hi Mike, On Tuesday 13 March 2007, Mike Frysinger wrote: > can i assume your other e-mail included everything needed to resolve this ? yes, and thanks a lot for applying them ! I've updated to latest CVS version of LTP, and now the PARISC Linux port finally survives all tests beside one: getcontext01 1 FAIL : getcontext - Sanity test : Fail errno=251 : Function not implemented That's correct, since we don't have the getcontext() call in glibc yet.... Thanks again, Helge ------------------- Summary: /etc/issue: Debian GNU/Linux 4.0 \n \l Linux c3000 2.6.20 #341 Wed Mar 7 22:23:17 CET 2007 parisc GNU/Linux Gnu C gcc (GCC) 4.1.2 20061115 (prerelease) (Debian 4.1.1-21) Gnu make 3.81 util-linux 2.12r mount 2.12r modutils 3.3-pre2 e2fsprogs 1.40-WIP Linux C Library 2.3.6 Dynamic linker (ldd) 2.3.6 Linux C++ Library 5.. Procps 3.2.7 Net-tools 1.60 Console-tools 0.2.3 Sh-utils 5.97 Modules Loaded free reports: total used free shared buffers cached Mem: 2069792 108588 1961204 0 20292 46744 -/+ buffers/cache: 41552 2028240 Swap: 2216928 0 2216928 /proc/cpuinfo processor : 0 cpu family : PA-RISC 2.0 cpu : PA8700 (PCX-W2) cpu MHz : 750.000000 model : 9000/785/C3700 model name : Allegro W2 hversion : 0x00005dc0 sversion : 0x00000481 I-cache : 768 KB D-cache : 1536 KB (WB, direct mapped) ITLB entries : 240 DTLB entries : 240 - shared with ITLB BTLB : not supported bogomips : 1495.04 software id : 2004631172 |
From: Riaz R. <rah...@gm...> - 2007-03-15 10:11:53
|
ok ^I are tab characters....sorry about the silly question...i got a little confused there. On 3/15/07, Riaz Rahaman <rah...@gm...> wrote: > > > > ---------- Forwarded message ---------- > From: Riaz Rahaman <rah...@gm...> > Date: Mar 15, 2007 11:05 AM > Subject: Re: [LTP] [PATCH]syconf01 > To: jb...@re... > Cc: ltp...@li... > > Hi Jeff, > > Sorry for the inconsistencty...sending a cleaner patch.... > > BTW...can any one tell me what is ^I hidden character mean? > > Riaz > > On 3/14/07, Jeff Burke <jb...@re...> wrote: > > > > Riaz, > > For consistency I think you should make a new patch. > > Some areas you have a space after the } others you dont' > > > > + } else tst_resm(TPASS,"PASS"); > > others you have > > + }else tst_resm(TPASS,"PASS"); > > > > Jeff > > > > > -- Regards, Riaz Ur Rahaman |