* [LTP] proc01 failed on 2.6.39 kernel
@ 2011-09-27 9:49 Romu
2011-09-27 10:26 ` Caspar Zhang
0 siblings, 1 reply; 2+ messages in thread
From: Romu @ 2011-09-27 9:49 UTC (permalink / raw)
To: ltp-list
Hi,
proc01 in ltp-20110915 failed on 2.6.39 kernel:
<<<test_start>>>
tag=proc01 stime=1317119259
cmdline="proc01"
contacts=""
analysis=exit
<<<test_output>>>
incrementing stop
proc01 0 TINFO : /proc/sysrq-trigger: is write-only.
proc01 0 TINFO : /proc/kmsg: known issue: errno=EAGAIN(11):
Resource temporarily unavailable
proc01 0 TINFO : /proc/acpi/event: known issue:
errno=EBUSY(16): Device or resource busy
proc01 0 TINFO : /proc/sys/fs/binfmt_misc/register: is write-only.
proc01 1 TFAIL : read failed: /proc/self/task/6144/ns/net:
errno=EINVAL(22): Invalid argument
proc01 2 TFAIL : read failed: /proc/self/task/6144/ns/uts:
errno=EINVAL(22): Invalid argument
proc01 3 TFAIL : read failed: /proc/self/task/6144/ns/ipc:
errno=EINVAL(22): Invalid argument
proc01 0 TINFO : /proc/self/task/6144/mem: known issue:
errno=EIO(5): Input/output error
proc01 0 TINFO : /proc/self/task/6144/clear_refs: is write-only.
proc01 4 TFAIL : read failed: /proc/self/ns/net:
errno=EINVAL(22): Invalid argument
proc01 5 TFAIL : read failed: /proc/self/ns/uts:
errno=EINVAL(22): Invalid argument
proc01 6 TFAIL : read failed: /proc/self/ns/ipc:
errno=EINVAL(22): Invalid argument
proc01 0 TINFO : /proc/self/mem: known issue: errno=EIO(5):
Input/output error
proc01 0 TINFO : /proc/self/clear_refs: is write-only.
proc01 7 TFAIL : readproc() failed with 6 errors.
<<<execution_status>>>
initiation_status="ok"
duration=940 termination_type=exited termination_id=1 corefile=no
cutime=1652 cstime=92280
<<<test_end>>>
INFO: ltp-pan reported some tests FAIL
LTP Version: LTP-20110915
I have no clue about the failure. Any help would be great, thanks in advance.
Regards,
Romu
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [LTP] proc01 failed on 2.6.39 kernel
2011-09-27 9:49 [LTP] proc01 failed on 2.6.39 kernel Romu
@ 2011-09-27 10:26 ` Caspar Zhang
0 siblings, 0 replies; 2+ messages in thread
From: Caspar Zhang @ 2011-09-27 10:26 UTC (permalink / raw)
To: Romu; +Cc: ltp-list
On 09/27/2011 05:49 PM, Romu wrote:
> Hi,
>
> proc01 in ltp-20110915 failed on 2.6.39 kernel:
>
> <<<test_start>>>
> tag=proc01 stime=1317119259
> cmdline="proc01"
> contacts=""
> analysis=exit
> <<<test_output>>>
> incrementing stop
> proc01 0 TINFO : /proc/sysrq-trigger: is write-only.
> proc01 0 TINFO : /proc/kmsg: known issue: errno=EAGAIN(11):
> Resource temporarily unavailable
> proc01 0 TINFO : /proc/acpi/event: known issue:
> errno=EBUSY(16): Device or resource busy
> proc01 0 TINFO : /proc/sys/fs/binfmt_misc/register: is write-only.
> proc01 1 TFAIL : read failed: /proc/self/task/6144/ns/net:
> errno=EINVAL(22): Invalid argument
> proc01 2 TFAIL : read failed: /proc/self/task/6144/ns/uts:
> errno=EINVAL(22): Invalid argument
> proc01 3 TFAIL : read failed: /proc/self/task/6144/ns/ipc:
> errno=EINVAL(22): Invalid argument
> proc01 0 TINFO : /proc/self/task/6144/mem: known issue:
> errno=EIO(5): Input/output error
> proc01 0 TINFO : /proc/self/task/6144/clear_refs: is write-only.
> proc01 4 TFAIL : read failed: /proc/self/ns/net:
> errno=EINVAL(22): Invalid argument
> proc01 5 TFAIL : read failed: /proc/self/ns/uts:
> errno=EINVAL(22): Invalid argument
> proc01 6 TFAIL : read failed: /proc/self/ns/ipc:
> errno=EINVAL(22): Invalid argument
> proc01 0 TINFO : /proc/self/mem: known issue: errno=EIO(5):
> Input/output error
> proc01 0 TINFO : /proc/self/clear_refs: is write-only.
> proc01 7 TFAIL : readproc() failed with 6 errors.
> <<<execution_status>>>
> initiation_status="ok"
> duration=940 termination_type=exited termination_id=1 corefile=no
> cutime=1652 cstime=92280
> <<<test_end>>>
> INFO: ltp-pan reported some tests FAIL
> LTP Version: LTP-20110915
>
> I have no clue about the failure. Any help would be great, thanks in advance.
>
looks like it was caused by the namespace support in 2.6.39:
http://thread.gmane.org/gmane.linux.kernel/1039644
LTP proc test seems couldn't handle them yet.
Thanks,
Caspar
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2011-09-27 10:59 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-09-27 9:49 [LTP] proc01 failed on 2.6.39 kernel Romu
2011-09-27 10:26 ` Caspar Zhang
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox