Thread: RE: [Fault-injection-developer] FITH test ABAT has updated.
Status: Alpha
Brought to you by:
rustyl
Menu
▾
▴
fault-injection-developer
|
From: Gao, K. <kev...@in...> - 2003-02-17 05:58:56
|
I have update the test script again, for how to using it is as following process. 1. mount sysfs 2. insert modules "fi_core, fi_dbp, fi_pf, fi_test" Then use command ./TEST_SUITE. I hope everything is OK :) -Kevin -----Original Message----- From: Louis Zhuang [mailto:lou...@li...] Sent: 2003?2?17? 9:07 To: Mark Haverkamp Cc: FITHML Subject: Re: [Fault-injection-developer] FITH test ABAT has updated. Thank you for your breave try ;-) Did you mount sysfs? On Sat, 2003-02-15 at 01:29, Mark Haverkamp wrote: > On Wed, 2003-02-12 at 18:49, Gao, Kevin wrote: > > Test suite has been updated, > > It includes most function test cases and boundary test cases. > > You can download at: > > > > bk://fau...@fa.../fith-tool. > > > > The ABAT's directory is in directory "fith-tool/fith_test" > > > > The function test cases are in directory > > "fith-tool/fith_test/fault_set/fun_test > > The boundary test cases are in directory > > "fith-tool/fith_test/fault_set/boundary_test. > > > > -Kevin > > > > Hi, > > I downloaded these and tried them out. I ran the ./TEST_SUITE script > and I had problems. I have included a lsmod and the test log output. > > Is there something obvious that I am doing wrong? If not, what is a good > way to go about debugging this? > > Thanks, > Mark. > > lsmod output: > > Module Size Used by > fi_test 6472 0 - Live 0xd891b000 > fi_mock_cs 2432 0 - Live 0xd890d000 > fi_mock_interceptor 3360 0 - Live 0xd8915000 > fi_irq 5728 0 - Live 0xd8912000 > fi_pf 8160 0 - Live 0xd890f000 > fi_sample_cs 3076 0 - Live 0xd88ff000 > fi_dbp 8736 0 - Live 0xd8907000 > fi_core 14816 6 fi_mock_cs,fi_mock_interceptor,fi_irq,fi_pf,fi_sample_cs,fi_dbp, Live 0xd8902000 > > > ************Start FITH test at 13:04:39 13-02-03 Thursday!************ > ------------------------------------------------------------------- > Original PPIO readb function works abnormally! > Test abandoned! > Original PPIO readw function works abnormally! > Test abandoned! > Original PPIO readl function works abnormally! > Test abandoned! > Original PPIO writeb function works abnormally! > Test abandoned! > Original PPIO writew function works abnormally! > Test abandoned! > Original PPIO writel function works abnormally! > Test abandoned! > ------------------------------------------------------------------- > Original MMIO readb function works abnormally! > Test abandoned! > Original MMIO readw function works abnormally! > Test abandoned! > Original MMIO readl function works abnormally! > Test abandoned! > Original MMIO writeb function works abnormally! > Test abandoned! > Original MMIO writew function works abnormally! > Test abandoned! > Original MMIO writel function works abnormally! > Test abandoned! > ------------------------------------------------------------------- > Precondition function test failed! > Test abandoned! > Skip function test failed! > Test abandoned! > Stop function test failed! > Test abandoned! > Protection_mask function test failed! > Test abandoned! > No corrupt action function test failed! > Test abandoned! > ------------------------------------------------------------------- > IO_address_zero test failed > IO_address_overrange test failed > MMIO_address_zero test failed > MMIO_address_overrange test failed > Corrupt 8 bit to 16 bit test failed > Corrupt 16 bit to 32 bit test failed > Same trigger in one faultset test failed > Invalid trigger mode (HZ) test failed > Invalid trigger mode (skip) test failed > Invalid trigger mode (stop) test failed > ------------------------------------------------------------------- > **********FITH FUNCTIONALITY TEST RESULT********** > > Original I/O read function works abnormally! > Original I/O write function works abnormally! > Original MMI/O read function works abnormally! > Original MMI/O write function works abnormally! > Faultset preconditon test failed! > Faultset trigger skip test failed! > Faultset stop pattern test failed! > Faultset hardware protect test failed! > Trigger without action test failed! > The whole boundary test failed! > > ************************************************** > > **********Complete FITH test at 13:04:54 13-02-03 Thursday!********** -- Yours truly, Louis Zhuang --------------- Fault Injection Test Harness Project BK tree: http://fault-injection.bkbits.net/linux-2.5 Home Page: http://sf.net/projects/fault-injection ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Fault-injection-developer mailing list Fau...@li... https://lists.sourceforge.net/lists/listinfo/fault-injection-developer |
|
From: Gao, K. <kev...@in...> - 2003-02-18 00:41:31
|
I want to know which directory that you mount the "sysfs". In our test case, the directory of "sysfs" should be /sys. Have you mounted the "sysfs" to directory "/sys"? -Kevin -----Original Message----- From: Mark Haverkamp [mailto:ma...@os...] Sent: 2003?2?18? 2:50 To: Gao, Kevin Cc: 'Louis Zhuang'; FITHML Subject: RE: [Fault-injection-developer] FITH test ABAT has updated. On Mon, 2003-02-17 at 08:09, Mark Haverkamp wrote: > On Sun, 2003-02-16 at 21:56, Gao, Kevin wrote: > > I have update the test script again, for how to using it is as following > > process. > > > > 1. mount sysfs > > 2. insert modules "fi_core, fi_dbp, fi_pf, fi_test" > > Then use command ./TEST_SUITE. > > > > I hope everything is OK :) > > > > -Kevin > > That is pretty much what I had done. I tried again with the new test > script and just loaded the modules in your list. Results following. > They look similar as before. > > Mark. > I found one of my problems. I had installed ficl in /usr/local/bin and the scripts assume that it is in /usr/local/sbin. I got a couple of cases to pass, but most still fail. Mark. ************Start FITH test at 10:42:24 17-02-03 Monday!************ ------------------------------------------------------------------- Original PPIO readb function works abnormally! Test abandoned! Original PPIO readw function works abnormally! Test abandoned! Original PPIO readl function works abnormally! Test abandoned! Original PPIO writeb function works abnormally! Test abandoned! Original PPIO writew function works abnormally! Test abandoned! Original PPIO writel function works abnormally! Test abandoned! ------------------------------------------------------------------- Original MMIO readb function works abnormally! Test abandoned! Original MMIO readw function works abnormally! Test abandoned! Original MMIO readl function works abnormally! Test abandoned! Original MMIO writeb function works abnormally! Test abandoned! Original MMIO writew function works abnormally! Test abandoned! Original MMIO writel function works abnormally! Test abandoned! ------------------------------------------------------------------- Precondition function test failed! Test abandoned! Skip function test failed! Test abandoned! Stop function test failed! Test abandoned! Protection_mask function test failed! Test abandoned! No corrupt action function test failed! Test abandoned! ------------------------------------------------------------------- IO_address_zero test passed IO_address_overrange test passed MMIO_address_zero test passed MMIO_address_overrange test passed Corrupt 8 bit to 16 bit test failed Corrupt 16 bit to 32 bit test failed Same trigger in one faultset test passed Invalid trigger mode (HZ) test failed Invalid trigger mode (skip) test failed Invalid trigger mode (stop) test failed ------------------------------------------------------------------- **********FITH FUNCTIONALITY TEST RESULT********** Original I/O read function works abnormally! Original I/O write function works abnormally! Original MMI/O read function works abnormally! Original MMI/O write function works abnormally! Faultset preconditon test failed! Faultset trigger skip test failed! Faultset stop pattern test failed! Faultset hardware protect test failed! Trigger without action test failed! The whole boundary test failed! ************************************************** **********Complete FITH test at 10:42:40 17-02-03 Monday!********** -- Mark Haverkamp <ma...@os...> |
|
From: Mark H. <ma...@os...> - 2003-02-18 15:25:52
|
On Mon, 2003-02-17 at 16:39, Gao, Kevin wrote: > I want to know which directory that you mount the "sysfs". > In our test case, the directory of "sysfs" should be /sys. > Have you mounted the "sysfs" to directory "/sys"? > > > -Kevin Yes, I saw in the code that it was looking in /sys. Mark. > > > -----Original Message----- > From: Mark Haverkamp [mailto:ma...@os...] > Sent: 2003?2?18? 2:50 > To: Gao, Kevin > Cc: 'Louis Zhuang'; FITHML > Subject: RE: [Fault-injection-developer] FITH test ABAT has updated. > > > On Mon, 2003-02-17 at 08:09, Mark Haverkamp wrote: > > On Sun, 2003-02-16 at 21:56, Gao, Kevin wrote: > > > I have update the test script again, for how to using it is as following > > > process. > > > > > > 1. mount sysfs > > > 2. insert modules "fi_core, fi_dbp, fi_pf, fi_test" > > > Then use command ./TEST_SUITE. > > > > > > I hope everything is OK :) > > > > > > -Kevin > > > > That is pretty much what I had done. I tried again with the new test > > script and just loaded the modules in your list. Results following. > > They look similar as before. > > > > Mark. > > > > I found one of my problems. I had installed ficl in /usr/local/bin and > the scripts assume that it is in /usr/local/sbin. I got a couple of > cases to pass, but most still fail. > > > Mark. > > > > ************Start FITH test at 10:42:24 17-02-03 Monday!************ > ------------------------------------------------------------------- > Original PPIO readb function works abnormally! > Test abandoned! > Original PPIO readw function works abnormally! > Test abandoned! > Original PPIO readl function works abnormally! > Test abandoned! > Original PPIO writeb function works abnormally! > Test abandoned! > Original PPIO writew function works abnormally! > Test abandoned! > Original PPIO writel function works abnormally! > Test abandoned! > ------------------------------------------------------------------- > Original MMIO readb function works abnormally! > Test abandoned! > Original MMIO readw function works abnormally! > Test abandoned! > Original MMIO readl function works abnormally! > Test abandoned! > Original MMIO writeb function works abnormally! > Test abandoned! > Original MMIO writew function works abnormally! > Test abandoned! > Original MMIO writel function works abnormally! > Test abandoned! > ------------------------------------------------------------------- > Precondition function test failed! > Test abandoned! > Skip function test failed! > Test abandoned! > Stop function test failed! > Test abandoned! > Protection_mask function test failed! > Test abandoned! > No corrupt action function test failed! > Test abandoned! > ------------------------------------------------------------------- > IO_address_zero test passed > IO_address_overrange test passed > MMIO_address_zero test passed > MMIO_address_overrange test passed > Corrupt 8 bit to 16 bit test failed > Corrupt 16 bit to 32 bit test failed > Same trigger in one faultset test passed > Invalid trigger mode (HZ) test failed > Invalid trigger mode (skip) test failed > Invalid trigger mode (stop) test failed > ------------------------------------------------------------------- > **********FITH FUNCTIONALITY TEST RESULT********** > > Original I/O read function works abnormally! > Original I/O write function works abnormally! > Original MMI/O read function works abnormally! > Original MMI/O write function works abnormally! > Faultset preconditon test failed! > Faultset trigger skip test failed! > Faultset stop pattern test failed! > Faultset hardware protect test failed! > Trigger without action test failed! > The whole boundary test failed! > > ************************************************** > > **********Complete FITH test at 10:42:40 17-02-03 Monday!********** -- Mark Haverkamp <ma...@os...> |
|
From: Gao, K. <kev...@in...> - 2003-02-18 15:43:09
|
In test script, I do not know the user's sysfs directory. But I need echo command to sysfs file. So I use /sys as default directory. Is everything is OK. I will update code soon and make the test code clean. -Kevin -----Original Message----- From: Mark Haverkamp [mailto:ma...@os...] Sent: 2003?2?18? 23:25 To: Gao, Kevin Cc: 'Louis Zhuang'; FITHML Subject: RE: [Fault-injection-developer] FITH test ABAT has updated. On Mon, 2003-02-17 at 16:39, Gao, Kevin wrote: > I want to know which directory that you mount the "sysfs". > In our test case, the directory of "sysfs" should be /sys. > Have you mounted the "sysfs" to directory "/sys"? > > > -Kevin Yes, I saw in the code that it was looking in /sys. Mark. > > > -----Original Message----- > From: Mark Haverkamp [mailto:ma...@os...] > Sent: 2003?2?18? 2:50 > To: Gao, Kevin > Cc: 'Louis Zhuang'; FITHML > Subject: RE: [Fault-injection-developer] FITH test ABAT has updated. > > > On Mon, 2003-02-17 at 08:09, Mark Haverkamp wrote: > > On Sun, 2003-02-16 at 21:56, Gao, Kevin wrote: > > > I have update the test script again, for how to using it is as following > > > process. > > > > > > 1. mount sysfs > > > 2. insert modules "fi_core, fi_dbp, fi_pf, fi_test" > > > Then use command ./TEST_SUITE. > > > > > > I hope everything is OK :) > > > > > > -Kevin > > > > That is pretty much what I had done. I tried again with the new test > > script and just loaded the modules in your list. Results following. > > They look similar as before. > > > > Mark. > > > > I found one of my problems. I had installed ficl in /usr/local/bin and > the scripts assume that it is in /usr/local/sbin. I got a couple of > cases to pass, but most still fail. > > > Mark. > > > > ************Start FITH test at 10:42:24 17-02-03 Monday!************ > ------------------------------------------------------------------- > Original PPIO readb function works abnormally! > Test abandoned! > Original PPIO readw function works abnormally! > Test abandoned! > Original PPIO readl function works abnormally! > Test abandoned! > Original PPIO writeb function works abnormally! > Test abandoned! > Original PPIO writew function works abnormally! > Test abandoned! > Original PPIO writel function works abnormally! > Test abandoned! > ------------------------------------------------------------------- > Original MMIO readb function works abnormally! > Test abandoned! > Original MMIO readw function works abnormally! > Test abandoned! > Original MMIO readl function works abnormally! > Test abandoned! > Original MMIO writeb function works abnormally! > Test abandoned! > Original MMIO writew function works abnormally! > Test abandoned! > Original MMIO writel function works abnormally! > Test abandoned! > ------------------------------------------------------------------- > Precondition function test failed! > Test abandoned! > Skip function test failed! > Test abandoned! > Stop function test failed! > Test abandoned! > Protection_mask function test failed! > Test abandoned! > No corrupt action function test failed! > Test abandoned! > ------------------------------------------------------------------- > IO_address_zero test passed > IO_address_overrange test passed > MMIO_address_zero test passed > MMIO_address_overrange test passed > Corrupt 8 bit to 16 bit test failed > Corrupt 16 bit to 32 bit test failed > Same trigger in one faultset test passed > Invalid trigger mode (HZ) test failed > Invalid trigger mode (skip) test failed > Invalid trigger mode (stop) test failed > ------------------------------------------------------------------- > **********FITH FUNCTIONALITY TEST RESULT********** > > Original I/O read function works abnormally! > Original I/O write function works abnormally! > Original MMI/O read function works abnormally! > Original MMI/O write function works abnormally! > Faultset preconditon test failed! > Faultset trigger skip test failed! > Faultset stop pattern test failed! > Faultset hardware protect test failed! > Trigger without action test failed! > The whole boundary test failed! > > ************************************************** > > **********Complete FITH test at 10:42:40 17-02-03 Monday!********** -- Mark Haverkamp <ma...@os...> |
|
From: Mark H. <ma...@os...> - 2003-02-18 16:01:51
|
On Tue, 2003-02-18 at 07:40, Gao, Kevin wrote: > In test script, I do not know the user's sysfs directory. > But I need echo command to sysfs file. So I use /sys > as default directory. > > Is everything is OK. > I will update code soon and make the test code clean. > > -Kevin I'm not sure what you mean. I have been mounting the sysfs directory as /sys and got the test failures. Also, in your test script you could use the mount command to see where the sysfs filesystem was mounted and use that path. For instance: # mount ... sysfs on /sys type sysfs (rw) Mark. > > -----Original Message----- > From: Mark Haverkamp [mailto:ma...@os...] > Sent: 2003?2?18? 23:25 > To: Gao, Kevin > Cc: 'Louis Zhuang'; FITHML > Subject: RE: [Fault-injection-developer] FITH test ABAT has updated. > > > On Mon, 2003-02-17 at 16:39, Gao, Kevin wrote: > > I want to know which directory that you mount the "sysfs". > > In our test case, the directory of "sysfs" should be /sys. > > Have you mounted the "sysfs" to directory "/sys"? > > > > > > -Kevin > > Yes, I saw in the code that it was looking in /sys. > > > Mark. -- Mark Haverkamp <ma...@os...> |
|
From: Gao, K. <kev...@in...> - 2003-02-18 16:41:35
|
Thank you for your comment, I will try to use mount command to catch the sysfs. But most important is that why test is failure. After you insert the modules fi_test, use command: # echo "read byte" > /sys/fith_test/io, Is there any information in ringbuffer? Could you give me the information? -----Original Message----- From: Mark Haverkamp [mailto:ma...@os...] Sent: 2003?2?19? 0:01 To: Gao, Kevin Cc: 'Louis Zhuang'; FITHML Subject: RE: [Fault-injection-developer] FITH test ABAT has updated. On Tue, 2003-02-18 at 07:40, Gao, Kevin wrote: > In test script, I do not know the user's sysfs directory. > But I need echo command to sysfs file. So I use /sys > as default directory. > > Is everything is OK. > I will update code soon and make the test code clean. > > -Kevin I'm not sure what you mean. I have been mounting the sysfs directory as /sys and got the test failures. Also, in your test script you could use the mount command to see where the sysfs filesystem was mounted and use that path. For instance: # mount ... sysfs on /sys type sysfs (rw) Mark. > > -----Original Message----- > From: Mark Haverkamp [mailto:ma...@os...] > Sent: 2003?2?18? 23:25 > To: Gao, Kevin > Cc: 'Louis Zhuang'; FITHML > Subject: RE: [Fault-injection-developer] FITH test ABAT has updated. > > > On Mon, 2003-02-17 at 16:39, Gao, Kevin wrote: > > I want to know which directory that you mount the "sysfs". > > In our test case, the directory of "sysfs" should be /sys. > > Have you mounted the "sysfs" to directory "/sys"? > > > > > > -Kevin > > Yes, I saw in the code that it was looking in /sys. > > > Mark. -- Mark Haverkamp <ma...@os...> |
|
From: Mark H. <ma...@os...> - 2003-02-18 16:50:17
|
On Tue, 2003-02-18 at 08:39, Gao, Kevin wrote: > Thank you for your comment, I will try to use mount command to > catch the sysfs. > But most important is that why test is failure. > After you insert the modules fi_test, > use command: > # echo "read byte" > /sys/fith_test/io, > Is there any information in ringbuffer? > Could you give me the information? OK, I assume that what you want showed up in dmesg. If this isn't the right data let me know where to look. FI_TEST: 309 jiffies = 90033991 #310 fi_test : COMMAND_IO_READ #311 fi_test : Expect read 0X5A* from parellel port register! #312 fi_test : 0XFF was read from parellel port register! -- Mark Haverkamp <ma...@os...> |
|
From: Louis Z. <lou...@li...> - 2003-02-19 00:37:03
|
On Wed, 2003-02-19 at 00:49, Mark Haverkamp wrote: > OK, I assume that what you want showed up in dmesg. If this isn't the > right data let me know where to look. > > > > FI_TEST: 309 jiffies = 90033991 > #310 fi_test : COMMAND_IO_READ > #311 fi_test : Expect read 0X5A* from parellel port register! > > #312 fi_test : 0XFF was read from parellel port register! Oh... it is the evil. fi_test assume your parellel is on 0x378. your can change the port address in fi_test.c:36 - Louis |
|
From: Mark H. <ma...@os...> - 2003-02-19 16:17:55
|
On Tue, 2003-02-18 at 16:33, Louis Zhuang wrote: > On Wed, 2003-02-19 at 00:49, Mark Haverkamp wrote: > > OK, I assume that what you want showed up in dmesg. If this isn't the > > right data let me know where to look. > > > > > > > > FI_TEST: 309 jiffies = 90033991 > > #310 fi_test : COMMAND_IO_READ > > #311 fi_test : Expect read 0X5A* from parellel port register! > > > > #312 fi_test : 0XFF was read from parellel port register! > Oh... it is the evil. fi_test assume your parellel is on 0x378. your can > change the port address in fi_test.c:36 > > - Louis Thanks. I checked my BIOS setup and the parallel port was disabled. I enabled it and tried the echo command and this time it looks like it worked. Feb 19 08:21:02 markh2 kernel: FI_TEST: 77 jiffies = 2189976 Feb 19 08:21:02 markh2 kernel: #78 fi_test : COMMAND_IO_READ Feb 19 08:21:02 markh2 kernel: #79 fi_test : Expect read 0X5A* from parellel port register! Feb 19 08:21:02 markh2 kernel: Feb 19 08:21:02 markh2 kernel: #80 fi_test : 0X5A was read from parellel port register! Unfortunately, the test run still has lots of failures. ************Start FITH test at 07:47:50 19-02-03 Wednesday!************ ------------------------------------------------------------------- Original PPIO readb function works abnormally! Test abandoned! Original PPIO readw function works abnormally! Test abandoned! Original PPIO readl function works abnormally! Test abandoned! Original PPIO writeb function works abnormally! Test abandoned! Original PPIO writew function works abnormally! Test abandoned! Original PPIO writel function works abnormally! Test abandoned! ------------------------------------------------------------------- Original MMIO readb function works abnormally! Test abandoned! Original MMIO readw function works abnormally! Test abandoned! Original MMIO readl function works abnormally! Test abandoned! Original MMIO writeb function works abnormally! Test abandoned! Original MMIO writew function works abnormally! Test abandoned! Original MMIO writel function works abnormally! Test abandoned! ------------------------------------------------------------------- Precondition function test failed! Test abandoned! Skip function test failed! Test abandoned! Stop function test failed! Test abandoned! Protection_mask function test failed! Test abandoned! No corrupt action function test failed! Test abandoned! ------------------------------------------------------------------- IO_address_zero test passed IO_address_overrange test passed MMIO_address_zero test passed MMIO_address_overrange test passed Corrupt 8 bit to 16 bit test failed Corrupt 16 bit to 32 bit test failed Same trigger in one faultset test passed Invalid trigger mode (HZ) test failed Invalid trigger mode (skip) test failed Invalid trigger mode (stop) test failed ------------------------------------------------------------------- **********FITH FUNCTIONALITY TEST RESULT********** Original I/O read function works abnormally! Original I/O write function works abnormally! Original MMI/O read function works abnormally! Original MMI/O write function works abnormally! Faultset preconditon test failed! Faultset trigger skip test failed! Faultset stop pattern test failed! Faultset hardware protect test failed! Trigger without action test failed! The whole boundary test failed! ************************************************** **********Complete FITH test at 07:48:06 19-02-03 Wednesday!********** Here is my /var/log/messages output if it helps. Feb 19 07:47:45 markh2 kernel: #0 fi_test : mmio_address = d88fc000 Feb 19 07:47:50 markh2 kernel: FI_TEST: 1 jiffies = 197742 Feb 19 07:47:50 markh2 kernel: #2 fi_test : COMMAND_IO_READ Feb 19 07:47:50 markh2 kernel: #3 fi_test : Expect read 0X5A* from parellel port register! Feb 19 07:47:50 markh2 kernel: Feb 19 07:47:50 markh2 kernel: #4 fi_test : 0X5A was read from parellel port register! Feb 19 07:47:50 markh2 kernel: Feb 19 07:47:50 markh2 kernel: FI_TEST: 5 jiffies = 197825 Feb 19 07:47:50 markh2 kernel: #6 fi_test : COMMAND_IO_READW Feb 19 07:47:50 markh2 kernel: #7 fi_test : Expect read 0X5A* from parellel port register! Feb 19 07:47:50 markh2 kernel: Feb 19 07:47:50 markh2 kernel: #8 fi_test : 0X5A was read from parellel port register! Feb 19 07:47:50 markh2 kernel: Feb 19 07:47:50 markh2 kernel: FI_TEST: 9 jiffies = 197909 Feb 19 07:47:50 markh2 kernel: #10 fi_test : COMMAND_IO_READL Feb 19 07:47:50 markh2 kernel: #11 fi_test : Expect read 0X5A* from parellel port register! Feb 19 07:47:50 markh2 kernel: Feb 19 07:47:50 markh2 kernel: #12 fi_test : 0X5A was read from parellel port register! Feb 19 07:47:50 markh2 kernel: Feb 19 07:47:51 markh2 kernel: FI_TEST: 13 jiffies = 197993 Feb 19 07:47:51 markh2 kernel: #14 fi_test : COMMAND_IO_WRITE Feb 19 07:47:51 markh2 kernel: #15 fi_test : Write 0X5A* to parellel port register! Feb 19 07:47:51 markh2 kernel: Feb 19 07:47:51 markh2 kernel: #16 fi_test : 0X5A was write to parellel port register! Feb 19 07:47:51 markh2 kernel: Feb 19 07:47:51 markh2 kernel: FI_TEST: 17 jiffies = 198076 Feb 19 07:47:51 markh2 kernel: #18 fi_test : COMMAND_IO_WRITEW Feb 19 07:47:51 markh2 kernel: #19 fi_test : Write 0X5A* to parellel port register! Feb 19 07:47:51 markh2 kernel: Feb 19 07:47:51 markh2 kernel: #20 fi_test : 0X5A was write to parellel port register! Feb 19 07:47:51 markh2 kernel: Feb 19 07:47:51 markh2 kernel: FI_TEST: 21 jiffies = 198161 Feb 19 07:47:51 markh2 kernel: #22 fi_test : COMMAND_IO_WRITEL Feb 19 07:47:51 markh2 kernel: #23 fi_test : Write 0X5A* to parellel port register! Feb 19 07:47:51 markh2 kernel: Feb 19 07:47:51 markh2 kernel: #24 fi_test : 0X5A was write to parellel port register! Feb 19 07:47:51 markh2 kernel: Feb 19 07:47:51 markh2 kernel: FI_TEST: 25 jiffies = 198252 Feb 19 07:47:51 markh2 kernel: #26 fi_test : COMMAND_MMIO_READ Feb 19 07:47:51 markh2 kernel: #27 fi_test : Expect read 0X5A* from MMI/O address Feb 19 07:47:51 markh2 kernel: #28 fi_test : 0X5A was read from MMI/O address Feb 19 07:47:51 markh2 kernel: FI_TEST: 29 jiffies = 198336 Feb 19 07:47:51 markh2 kernel: #30 fi_test : COMMAND_MMIO_READW Feb 19 07:47:51 markh2 kernel: #31 fi_test : Expect read 0X5A* from MMI/O address Feb 19 07:47:51 markh2 kernel: #32 fi_test : 0X5A5A was read from MMI/O address Feb 19 07:47:51 markh2 kernel: FI_TEST: 33 jiffies = 198420 Feb 19 07:47:51 markh2 kernel: #34 fi_test : COMMAND_MMIO_READL Feb 19 07:47:51 markh2 kernel: #35 fi_test : Expect read 0X5A* from MMI/O address Feb 19 07:47:51 markh2 kernel: #36 fi_test : 0X5A5A5A5A was read from MMI/O address Feb 19 07:47:51 markh2 kernel: FI_TEST: 37 jiffies = 198504 Feb 19 07:47:51 markh2 kernel: #38 fi_test : COMMAND_MMIO_WRITE Feb 19 07:47:51 markh2 kernel: #39 fi_test : Write 0X5A* to MMI/O address Feb 19 07:47:51 markh2 kernel: #40 fi_test : 0X5A was write to MMI/O address Feb 19 07:47:51 markh2 kernel: FI_TEST: 41 jiffies = 198589 Feb 19 07:47:51 markh2 kernel: #42 fi_test : COMMAND_MMIO_WRITEW Feb 19 07:47:51 markh2 kernel: #43 fi_test : Write 0X5A* to MMI/O address Feb 19 07:47:51 markh2 kernel: #44 fi_test : 0X5A5A was write to MMI/O address Feb 19 07:47:51 markh2 kernel: FI_TEST: 45 jiffies = 198673 Feb 19 07:47:51 markh2 kernel: #46 fi_test : COMMAND_MMIO_WRITEL Feb 19 07:47:51 markh2 kernel: #47 fi_test : Write 0X5A* to MMI/O address Feb 19 07:47:51 markh2 kernel: #48 fi_test : 0X5A5A5A5A was write to MMI/O address Feb 19 07:47:51 markh2 kernel: trigger_ctl_store: Invalid command format: add, 8 tokens found Feb 19 07:47:51 markh2 kernel: FI_TEST: 49 jiffies = 198788 Feb 19 07:47:51 markh2 kernel: #50 fi_test : COMMAND_IO_READ Feb 19 07:47:51 markh2 kernel: #51 fi_test : Expect read 0X5A* from parellel port register! Feb 19 07:47:51 markh2 kernel: Feb 19 07:47:51 markh2 kernel: #52 fi_test : 0X5A was read from parellel port register! Feb 19 07:47:51 markh2 kernel: Feb 19 07:47:51 markh2 kernel: del_trigger_by_name: trigger precondition does not exist Feb 19 07:47:51 markh2 kernel: add_trigger: Unable to arm the trigger, unregister skip_pattern Feb 19 07:47:51 markh2 kernel: FI_TEST: 53 jiffies = 198904 Feb 19 07:47:51 markh2 kernel: #54 fi_test : COMMAND_IO_READ Feb 19 07:47:51 markh2 kernel: #55 fi_test : Expect read 0X5A* from parellel port register! Feb 19 07:47:51 markh2 kernel: Feb 19 07:47:51 markh2 kernel: #56 fi_test : 0X5A was read from parellel port register! Feb 19 07:47:51 markh2 kernel: Feb 19 07:47:52 markh2 kernel: del_trigger_by_name: trigger skip_pattern does not exist Feb 19 07:47:52 markh2 kernel: add_trigger: Unable to arm the trigger, unregister stop_pattern Feb 19 07:47:52 markh2 kernel: FI_TEST: 57 jiffies = 199047 Feb 19 07:47:52 markh2 kernel: #58 fi_test : COMMAND_IO_READ Feb 19 07:47:52 markh2 kernel: #59 fi_test : Expect read 0X5A* from parellel port register! Feb 19 07:47:52 markh2 kernel: Feb 19 07:47:52 markh2 kernel: #60 fi_test : 0X5A was read from parellel port register! Feb 19 07:47:52 markh2 kernel: Feb 19 07:47:52 markh2 kernel: del_trigger_by_name: trigger stop_pattern does not exist Feb 19 07:47:52 markh2 kernel: trigger_ctl_store: Invalid command format: add, 11 tokens found Feb 19 07:47:52 markh2 kernel: FI_TEST: 61 jiffies = 199161 Feb 19 07:47:52 markh2 kernel: #62 fi_test : COMMAND_IO_READ Feb 19 07:47:52 markh2 kernel: #63 fi_test : Expect read 0X5A* from parellel port register! Feb 19 07:47:52 markh2 kernel: Feb 19 07:47:52 markh2 kernel: #64 fi_test : 0X5A was read from parellel port register! Feb 19 07:47:52 markh2 kernel: Feb 19 07:47:52 markh2 kernel: del_trigger_by_name: trigger hw_protected does not exist Feb 19 07:47:52 markh2 kernel: add_trigger: Unable to arm the trigger, unregister no_action Feb 19 07:47:52 markh2 kernel: FI_TEST: 65 jiffies = 199275 Feb 19 07:47:52 markh2 kernel: #66 fi_test : COMMAND_IO_READ Feb 19 07:47:52 markh2 kernel: #67 fi_test : Expect read 0X5A* from parellel port register! Feb 19 07:47:52 markh2 kernel: Feb 19 07:47:52 markh2 kernel: #68 fi_test : 0X5A was read from parellel port register! Feb 19 07:47:52 markh2 kernel: Feb 19 07:47:52 markh2 kernel: del_trigger_by_name: trigger no_action does not exist Feb 19 07:47:53 markh2 kernel: add_trigger: Unable to arm the trigger, unregister io_overrange Feb 19 07:47:56 markh2 kernel: add_trigger: Unable to arm the trigger, unregister 8_16 Feb 19 07:47:56 markh2 kernel: FI_TEST: 69 jiffies = 203528 Feb 19 07:47:56 markh2 kernel: #70 fi_test : COMMAND_IO_READW Feb 19 07:47:56 markh2 kernel: #71 fi_test : Expect read 0X5A* from parellel port register! Feb 19 07:47:56 markh2 kernel: Feb 19 07:47:56 markh2 kernel: #72 fi_test : 0X5A was read from parellel port register! Feb 19 07:47:56 markh2 kernel: Feb 19 07:47:56 markh2 kernel: del_trigger_by_name: trigger 8_16 does not exist Feb 19 07:47:57 markh2 kernel: FI_TEST: 73 jiffies = 204636 Feb 19 07:47:57 markh2 kernel: #74 fi_test : COMMAND_MMIO_READL Feb 19 07:47:57 markh2 kernel: #75 fi_test : Expect read 0X5A* from MMI/O address Feb 19 07:47:57 markh2 kernel: Feb 19 07:47:57 markh2 last message repeated 5 times Feb 19 07:47:57 markh2 kernel: #76 fi_test : 0X5A5AEF23 was read from MMI/O address Feb 19 07:47:58 markh2 kernel: add_trigger: Unable to arm the trigger, unregister two_in_one1 Feb 19 07:47:58 markh2 kernel: add_trigger: Unable to arm the trigger, unregister two_in_one2 Feb 19 07:47:59 markh2 kernel: add_trigger: Unable to arm the trigger, unregister invalid1 Feb 19 07:48:00 markh2 kernel: add_trigger: Unable to arm the trigger, unregister invalid2 Feb 19 07:48:01 markh2 kernel: add_trigger: Unable to arm the trigger, unregister invalid3 -- Mark Haverkamp <ma...@os...> |
|
From: Gao, K. <kev...@in...> - 2003-02-20 00:41:26
|
Based on your message, I think that is because the code of FITH is outdated. Please download the newest version of FITH. Thanks -Kevin -----Original Message----- From: Mark Haverkamp [mailto:ma...@os...] Sent: 2003?2?20? 0:16 To: Louis Zhuang Cc: Kevin Gao; FITHML Subject: RE: [Fault-injection-developer] FITH test ABAT has updated. On Tue, 2003-02-18 at 16:33, Louis Zhuang wrote: > On Wed, 2003-02-19 at 00:49, Mark Haverkamp wrote: > > OK, I assume that what you want showed up in dmesg. If this isn't the > > right data let me know where to look. > > > > > > > > FI_TEST: 309 jiffies = 90033991 > > #310 fi_test : COMMAND_IO_READ > > #311 fi_test : Expect read 0X5A* from parellel port register! > > > > #312 fi_test : 0XFF was read from parellel port register! > Oh... it is the evil. fi_test assume your parellel is on 0x378. your can > change the port address in fi_test.c:36 > > - Louis Thanks. I checked my BIOS setup and the parallel port was disabled. I enabled it and tried the echo command and this time it looks like it worked. Feb 19 08:21:02 markh2 kernel: FI_TEST: 77 jiffies = 2189976 Feb 19 08:21:02 markh2 kernel: #78 fi_test : COMMAND_IO_READ Feb 19 08:21:02 markh2 kernel: #79 fi_test : Expect read 0X5A* from parellel port register! Feb 19 08:21:02 markh2 kernel: Feb 19 08:21:02 markh2 kernel: #80 fi_test : 0X5A was read from parellel port register! Unfortunately, the test run still has lots of failures. ************Start FITH test at 07:47:50 19-02-03 Wednesday!************ ------------------------------------------------------------------- Original PPIO readb function works abnormally! Test abandoned! Original PPIO readw function works abnormally! Test abandoned! Original PPIO readl function works abnormally! Test abandoned! Original PPIO writeb function works abnormally! Test abandoned! Original PPIO writew function works abnormally! Test abandoned! Original PPIO writel function works abnormally! Test abandoned! ------------------------------------------------------------------- Original MMIO readb function works abnormally! Test abandoned! Original MMIO readw function works abnormally! Test abandoned! Original MMIO readl function works abnormally! Test abandoned! Original MMIO writeb function works abnormally! Test abandoned! Original MMIO writew function works abnormally! Test abandoned! Original MMIO writel function works abnormally! Test abandoned! ------------------------------------------------------------------- Precondition function test failed! Test abandoned! Skip function test failed! Test abandoned! Stop function test failed! Test abandoned! Protection_mask function test failed! Test abandoned! No corrupt action function test failed! Test abandoned! ------------------------------------------------------------------- IO_address_zero test passed IO_address_overrange test passed MMIO_address_zero test passed MMIO_address_overrange test passed Corrupt 8 bit to 16 bit test failed Corrupt 16 bit to 32 bit test failed Same trigger in one faultset test passed Invalid trigger mode (HZ) test failed Invalid trigger mode (skip) test failed Invalid trigger mode (stop) test failed ------------------------------------------------------------------- **********FITH FUNCTIONALITY TEST RESULT********** Original I/O read function works abnormally! Original I/O write function works abnormally! Original MMI/O read function works abnormally! Original MMI/O write function works abnormally! Faultset preconditon test failed! Faultset trigger skip test failed! Faultset stop pattern test failed! Faultset hardware protect test failed! Trigger without action test failed! The whole boundary test failed! ************************************************** **********Complete FITH test at 07:48:06 19-02-03 Wednesday!********** Here is my /var/log/messages output if it helps. Feb 19 07:47:45 markh2 kernel: #0 fi_test : mmio_address = d88fc000 Feb 19 07:47:50 markh2 kernel: FI_TEST: 1 jiffies = 197742 Feb 19 07:47:50 markh2 kernel: #2 fi_test : COMMAND_IO_READ Feb 19 07:47:50 markh2 kernel: #3 fi_test : Expect read 0X5A* from parellel port register! Feb 19 07:47:50 markh2 kernel: Feb 19 07:47:50 markh2 kernel: #4 fi_test : 0X5A was read from parellel port register! Feb 19 07:47:50 markh2 kernel: Feb 19 07:47:50 markh2 kernel: FI_TEST: 5 jiffies = 197825 Feb 19 07:47:50 markh2 kernel: #6 fi_test : COMMAND_IO_READW Feb 19 07:47:50 markh2 kernel: #7 fi_test : Expect read 0X5A* from parellel port register! Feb 19 07:47:50 markh2 kernel: Feb 19 07:47:50 markh2 kernel: #8 fi_test : 0X5A was read from parellel port register! Feb 19 07:47:50 markh2 kernel: Feb 19 07:47:50 markh2 kernel: FI_TEST: 9 jiffies = 197909 Feb 19 07:47:50 markh2 kernel: #10 fi_test : COMMAND_IO_READL Feb 19 07:47:50 markh2 kernel: #11 fi_test : Expect read 0X5A* from parellel port register! Feb 19 07:47:50 markh2 kernel: Feb 19 07:47:50 markh2 kernel: #12 fi_test : 0X5A was read from parellel port register! Feb 19 07:47:50 markh2 kernel: Feb 19 07:47:51 markh2 kernel: FI_TEST: 13 jiffies = 197993 Feb 19 07:47:51 markh2 kernel: #14 fi_test : COMMAND_IO_WRITE Feb 19 07:47:51 markh2 kernel: #15 fi_test : Write 0X5A* to parellel port register! Feb 19 07:47:51 markh2 kernel: Feb 19 07:47:51 markh2 kernel: #16 fi_test : 0X5A was write to parellel port register! Feb 19 07:47:51 markh2 kernel: Feb 19 07:47:51 markh2 kernel: FI_TEST: 17 jiffies = 198076 Feb 19 07:47:51 markh2 kernel: #18 fi_test : COMMAND_IO_WRITEW Feb 19 07:47:51 markh2 kernel: #19 fi_test : Write 0X5A* to parellel port register! Feb 19 07:47:51 markh2 kernel: Feb 19 07:47:51 markh2 kernel: #20 fi_test : 0X5A was write to parellel port register! Feb 19 07:47:51 markh2 kernel: Feb 19 07:47:51 markh2 kernel: FI_TEST: 21 jiffies = 198161 Feb 19 07:47:51 markh2 kernel: #22 fi_test : COMMAND_IO_WRITEL Feb 19 07:47:51 markh2 kernel: #23 fi_test : Write 0X5A* to parellel port register! Feb 19 07:47:51 markh2 kernel: Feb 19 07:47:51 markh2 kernel: #24 fi_test : 0X5A was write to parellel port register! Feb 19 07:47:51 markh2 kernel: Feb 19 07:47:51 markh2 kernel: FI_TEST: 25 jiffies = 198252 Feb 19 07:47:51 markh2 kernel: #26 fi_test : COMMAND_MMIO_READ Feb 19 07:47:51 markh2 kernel: #27 fi_test : Expect read 0X5A* from MMI/O address Feb 19 07:47:51 markh2 kernel: #28 fi_test : 0X5A was read from MMI/O address Feb 19 07:47:51 markh2 kernel: FI_TEST: 29 jiffies = 198336 Feb 19 07:47:51 markh2 kernel: #30 fi_test : COMMAND_MMIO_READW Feb 19 07:47:51 markh2 kernel: #31 fi_test : Expect read 0X5A* from MMI/O address Feb 19 07:47:51 markh2 kernel: #32 fi_test : 0X5A5A was read from MMI/O address Feb 19 07:47:51 markh2 kernel: FI_TEST: 33 jiffies = 198420 Feb 19 07:47:51 markh2 kernel: #34 fi_test : COMMAND_MMIO_READL Feb 19 07:47:51 markh2 kernel: #35 fi_test : Expect read 0X5A* from MMI/O address Feb 19 07:47:51 markh2 kernel: #36 fi_test : 0X5A5A5A5A was read from MMI/O address Feb 19 07:47:51 markh2 kernel: FI_TEST: 37 jiffies = 198504 Feb 19 07:47:51 markh2 kernel: #38 fi_test : COMMAND_MMIO_WRITE Feb 19 07:47:51 markh2 kernel: #39 fi_test : Write 0X5A* to MMI/O address Feb 19 07:47:51 markh2 kernel: #40 fi_test : 0X5A was write to MMI/O address Feb 19 07:47:51 markh2 kernel: FI_TEST: 41 jiffies = 198589 Feb 19 07:47:51 markh2 kernel: #42 fi_test : COMMAND_MMIO_WRITEW Feb 19 07:47:51 markh2 kernel: #43 fi_test : Write 0X5A* to MMI/O address Feb 19 07:47:51 markh2 kernel: #44 fi_test : 0X5A5A was write to MMI/O address Feb 19 07:47:51 markh2 kernel: FI_TEST: 45 jiffies = 198673 Feb 19 07:47:51 markh2 kernel: #46 fi_test : COMMAND_MMIO_WRITEL Feb 19 07:47:51 markh2 kernel: #47 fi_test : Write 0X5A* to MMI/O address Feb 19 07:47:51 markh2 kernel: #48 fi_test : 0X5A5A5A5A was write to MMI/O address Feb 19 07:47:51 markh2 kernel: trigger_ctl_store: Invalid command format: add, 8 tokens found Feb 19 07:47:51 markh2 kernel: FI_TEST: 49 jiffies = 198788 Feb 19 07:47:51 markh2 kernel: #50 fi_test : COMMAND_IO_READ Feb 19 07:47:51 markh2 kernel: #51 fi_test : Expect read 0X5A* from parellel port register! Feb 19 07:47:51 markh2 kernel: Feb 19 07:47:51 markh2 kernel: #52 fi_test : 0X5A was read from parellel port register! Feb 19 07:47:51 markh2 kernel: Feb 19 07:47:51 markh2 kernel: del_trigger_by_name: trigger precondition does not exist Feb 19 07:47:51 markh2 kernel: add_trigger: Unable to arm the trigger, unregister skip_pattern Feb 19 07:47:51 markh2 kernel: FI_TEST: 53 jiffies = 198904 Feb 19 07:47:51 markh2 kernel: #54 fi_test : COMMAND_IO_READ Feb 19 07:47:51 markh2 kernel: #55 fi_test : Expect read 0X5A* from parellel port register! Feb 19 07:47:51 markh2 kernel: Feb 19 07:47:51 markh2 kernel: #56 fi_test : 0X5A was read from parellel port register! Feb 19 07:47:51 markh2 kernel: Feb 19 07:47:52 markh2 kernel: del_trigger_by_name: trigger skip_pattern does not exist Feb 19 07:47:52 markh2 kernel: add_trigger: Unable to arm the trigger, unregister stop_pattern Feb 19 07:47:52 markh2 kernel: FI_TEST: 57 jiffies = 199047 Feb 19 07:47:52 markh2 kernel: #58 fi_test : COMMAND_IO_READ Feb 19 07:47:52 markh2 kernel: #59 fi_test : Expect read 0X5A* from parellel port register! Feb 19 07:47:52 markh2 kernel: Feb 19 07:47:52 markh2 kernel: #60 fi_test : 0X5A was read from parellel port register! Feb 19 07:47:52 markh2 kernel: Feb 19 07:47:52 markh2 kernel: del_trigger_by_name: trigger stop_pattern does not exist Feb 19 07:47:52 markh2 kernel: trigger_ctl_store: Invalid command format: add, 11 tokens found Feb 19 07:47:52 markh2 kernel: FI_TEST: 61 jiffies = 199161 Feb 19 07:47:52 markh2 kernel: #62 fi_test : COMMAND_IO_READ Feb 19 07:47:52 markh2 kernel: #63 fi_test : Expect read 0X5A* from parellel port register! Feb 19 07:47:52 markh2 kernel: Feb 19 07:47:52 markh2 kernel: #64 fi_test : 0X5A was read from parellel port register! Feb 19 07:47:52 markh2 kernel: Feb 19 07:47:52 markh2 kernel: del_trigger_by_name: trigger hw_protected does not exist Feb 19 07:47:52 markh2 kernel: add_trigger: Unable to arm the trigger, unregister no_action Feb 19 07:47:52 markh2 kernel: FI_TEST: 65 jiffies = 199275 Feb 19 07:47:52 markh2 kernel: #66 fi_test : COMMAND_IO_READ Feb 19 07:47:52 markh2 kernel: #67 fi_test : Expect read 0X5A* from parellel port register! Feb 19 07:47:52 markh2 kernel: Feb 19 07:47:52 markh2 kernel: #68 fi_test : 0X5A was read from parellel port register! Feb 19 07:47:52 markh2 kernel: Feb 19 07:47:52 markh2 kernel: del_trigger_by_name: trigger no_action does not exist Feb 19 07:47:53 markh2 kernel: add_trigger: Unable to arm the trigger, unregister io_overrange Feb 19 07:47:56 markh2 kernel: add_trigger: Unable to arm the trigger, unregister 8_16 Feb 19 07:47:56 markh2 kernel: FI_TEST: 69 jiffies = 203528 Feb 19 07:47:56 markh2 kernel: #70 fi_test : COMMAND_IO_READW Feb 19 07:47:56 markh2 kernel: #71 fi_test : Expect read 0X5A* from parellel port register! Feb 19 07:47:56 markh2 kernel: Feb 19 07:47:56 markh2 kernel: #72 fi_test : 0X5A was read from parellel port register! Feb 19 07:47:56 markh2 kernel: Feb 19 07:47:56 markh2 kernel: del_trigger_by_name: trigger 8_16 does not exist Feb 19 07:47:57 markh2 kernel: FI_TEST: 73 jiffies = 204636 Feb 19 07:47:57 markh2 kernel: #74 fi_test : COMMAND_MMIO_READL Feb 19 07:47:57 markh2 kernel: #75 fi_test : Expect read 0X5A* from MMI/O address Feb 19 07:47:57 markh2 kernel: Feb 19 07:47:57 markh2 last message repeated 5 times Feb 19 07:47:57 markh2 kernel: #76 fi_test : 0X5A5AEF23 was read from MMI/O address Feb 19 07:47:58 markh2 kernel: add_trigger: Unable to arm the trigger, unregister two_in_one1 Feb 19 07:47:58 markh2 kernel: add_trigger: Unable to arm the trigger, unregister two_in_one2 Feb 19 07:47:59 markh2 kernel: add_trigger: Unable to arm the trigger, unregister invalid1 Feb 19 07:48:00 markh2 kernel: add_trigger: Unable to arm the trigger, unregister invalid2 Feb 19 07:48:01 markh2 kernel: add_trigger: Unable to arm the trigger, unregister invalid3 -- Mark Haverkamp <ma...@os...> |
|
From: Mark H. <ma...@os...> - 2003-02-20 15:56:06
|
On Wed, 2003-02-19 at 16:38, Gao, Kevin wrote: > Based on your message, I think that is because > the code of FITH is outdated. > Please download the newest version of FITH. > Thanks > > -Kevin This helped. It looks like everything passed. Thanks, Mark. ************Start FITH test at 08:02:23 20-02-03 Thursday!************ ------------------------------------------------------------------- Original PPIO readb function works normally! Injecting faults into PPIO readb successful! Original PPIO readw function works normally! Injecting faults into PPIO readw successful! Original PPIO readl function works normally! Injecting faults into PPIO readl successful! Original PPIO writeb function works normally! Injecting faults into PPIO writeb successful! Original PPIO writew function works normally! Injecting faults into PPIO writew successful! Original PPIO writel function works normally! Injecting faults into PPIO writel successful! ------------------------------------------------------------------- Original MMIO readb function works normally! Injecting faults into MMIO readb successful! Original MMIO readw function works normally! Injecting faults into MMIO readw successful! Original MMIO readl function works normally! Injecting faults into MMIO readl successful! Original MMIO writeb function works normally! Injecting faults into MMIO writeb successful! Original MMIO writew function works normally! Injecting faults into MMIO writew successful! Original MMIO writel function works normally! Injecting faults into MMIO writel successful! ------------------------------------------------------------------- Precondition function test successful! Skip function test successful! Stop function test successful! Protection_mask function test successful! No corrupt action function test successful! ------------------------------------------------------------------- IO_address_zero test passed IO_address_overrange test passed MMIO_address_zero test passed MMIO_address_overrange test passed Corrupt 8 bit to 16 bit test passed Corrupt 16 bit to 32 bit test passed Same trigger in one faultset test passed Invalid trigger mode (HZ) test passed Invalid trigger mode (skip) test passed Invalid trigger mode (stop) test passed ------------------------------------------------------------------- **********FITH FUNCTIONALITY TEST RESULT********** Inject faults into I/O read passed! Inject faults into I/O write passed! Inject faults into MMI/O read passed! Inject faults into MMI/O write passed! Faultset preconditon test passed! Faultset skip pattern test passed! Faultset stop pattern test passed! Faultset hardware protect test passed! Trigger without action test passed! The whole boundary test passed! ************************************************** **********Complete FITH test at 08:02:52 20-02-03 Thursday!********** -- Mark Haverkamp <ma...@os...> |
|
From: Mark H. <ma...@os...> - 2003-02-17 16:09:59
|
On Sun, 2003-02-16 at 21:56, Gao, Kevin wrote: > I have update the test script again, for how to using it is as following > process. > > 1. mount sysfs > 2. insert modules "fi_core, fi_dbp, fi_pf, fi_test" > Then use command ./TEST_SUITE. > > I hope everything is OK :) > > -Kevin That is pretty much what I had done. I tried again with the new test script and just loaded the modules in your list. Results following. They look similar as before. Mark. [root@markh2 fi]# lsmod Module Size Used by fi_test 6472 0 - Live 0xd890e000 fi_pf 8160 0 - Live 0xd890b000 fi_dbp 8736 0 - Live 0xd8907000 fi_core 14816 2 fi_pf,fi_dbp, Live 0xd8902000 ************Start FITH test at 08:12:37 17-02-03 Monday!************ ------------------------------------------------------------------- Original PPIO readb function works abnormally! Test abandoned! Original PPIO readw function works abnormally! Test abandoned! Original PPIO readl function works abnormally! Test abandoned! Original PPIO writeb function works abnormally! Test abandoned! Original PPIO writew function works abnormally! Test abandoned! Original PPIO writel function works abnormally! Test abandoned! ------------------------------------------------------------------- Original MMIO readb function works abnormally! Test abandoned! Original MMIO readw function works abnormally! Test abandoned! Original MMIO readl function works abnormally! Test abandoned! Original MMIO writeb function works abnormally! Test abandoned! Original MMIO writew function works abnormally! Test abandoned! Original MMIO writel function works abnormally! Test abandoned! ------------------------------------------------------------------- Precondition function test failed! Test abandoned! Skip function test failed! Test abandoned! Stop function test failed! Test abandoned! Protection_mask function test failed! Test abandoned! No corrupt action function test failed! Test abandoned! ------------------------------------------------------------------- IO_address_zero test failed IO_address_overrange test failed MMIO_address_zero test failed MMIO_address_overrange test failed Corrupt 8 bit to 16 bit test failed Corrupt 16 bit to 32 bit test failed Same trigger in one faultset test failed Invalid trigger mode (HZ) test failed Invalid trigger mode (skip) test failed Invalid trigger mode (stop) test failed ------------------------------------------------------------------- **********FITH FUNCTIONALITY TEST RESULT********** Original I/O read function works abnormally! Original I/O write function works abnormally! Original MMI/O read function works abnormally! Original MMI/O write function works abnormally! Faultset preconditon test failed! Faultset trigger skip test failed! Faultset stop pattern test failed! Faultset hardware protect test failed! Trigger without action test failed! The whole boundary test failed! ************************************************** **********Complete FITH test at 08:12:52 17-02-03 Monday!********** -- Mark Haverkamp <ma...@os...> |
|
From: Mark H. <ma...@os...> - 2003-02-17 18:51:19
|
On Mon, 2003-02-17 at 08:09, Mark Haverkamp wrote: > On Sun, 2003-02-16 at 21:56, Gao, Kevin wrote: > > I have update the test script again, for how to using it is as following > > process. > > > > 1. mount sysfs > > 2. insert modules "fi_core, fi_dbp, fi_pf, fi_test" > > Then use command ./TEST_SUITE. > > > > I hope everything is OK :) > > > > -Kevin > > That is pretty much what I had done. I tried again with the new test > script and just loaded the modules in your list. Results following. > They look similar as before. > > Mark. > I found one of my problems. I had installed ficl in /usr/local/bin and the scripts assume that it is in /usr/local/sbin. I got a couple of cases to pass, but most still fail. Mark. ************Start FITH test at 10:42:24 17-02-03 Monday!************ ------------------------------------------------------------------- Original PPIO readb function works abnormally! Test abandoned! Original PPIO readw function works abnormally! Test abandoned! Original PPIO readl function works abnormally! Test abandoned! Original PPIO writeb function works abnormally! Test abandoned! Original PPIO writew function works abnormally! Test abandoned! Original PPIO writel function works abnormally! Test abandoned! ------------------------------------------------------------------- Original MMIO readb function works abnormally! Test abandoned! Original MMIO readw function works abnormally! Test abandoned! Original MMIO readl function works abnormally! Test abandoned! Original MMIO writeb function works abnormally! Test abandoned! Original MMIO writew function works abnormally! Test abandoned! Original MMIO writel function works abnormally! Test abandoned! ------------------------------------------------------------------- Precondition function test failed! Test abandoned! Skip function test failed! Test abandoned! Stop function test failed! Test abandoned! Protection_mask function test failed! Test abandoned! No corrupt action function test failed! Test abandoned! ------------------------------------------------------------------- IO_address_zero test passed IO_address_overrange test passed MMIO_address_zero test passed MMIO_address_overrange test passed Corrupt 8 bit to 16 bit test failed Corrupt 16 bit to 32 bit test failed Same trigger in one faultset test passed Invalid trigger mode (HZ) test failed Invalid trigger mode (skip) test failed Invalid trigger mode (stop) test failed ------------------------------------------------------------------- **********FITH FUNCTIONALITY TEST RESULT********** Original I/O read function works abnormally! Original I/O write function works abnormally! Original MMI/O read function works abnormally! Original MMI/O write function works abnormally! Faultset preconditon test failed! Faultset trigger skip test failed! Faultset stop pattern test failed! Faultset hardware protect test failed! Trigger without action test failed! The whole boundary test failed! ************************************************** **********Complete FITH test at 10:42:40 17-02-03 Monday!********** -- Mark Haverkamp <ma...@os...> |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X