public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Caspar Zhang <caspar@casparzhang.com>
To: Romu <huruomu@gmail.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] proc01 failed on 2.6.39 kernel
Date: Tue, 27 Sep 2011 18:26:25 +0800	[thread overview]
Message-ID: <4E81A4D1.7030502@casparzhang.com> (raw)
In-Reply-To: <CANoG8sWBQBjVej__oW0HSWB3wiXBU0HrdFE=5DpUeFABtoF5wQ@mail.gmail.com>

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

      reply	other threads:[~2011-09-27 10:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-27  9:49 [LTP] proc01 failed on 2.6.39 kernel Romu
2011-09-27 10:26 ` Caspar Zhang [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E81A4D1.7030502@casparzhang.com \
    --to=caspar@casparzhang.com \
    --cc=huruomu@gmail.com \
    --cc=ltp-list@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox