From: greg at kroah.com (Greg KH)
Subject: [Linux-kselftest-mirror] selftests: x86_64: kselftest mpx-mini-test_64 - no MPX support - failed - 3869 Aborted (core dumped)
Date: Fri, 24 Nov 2017 12:46:35 +0100 [thread overview]
Message-ID: <20171124114635.GB1916@kroah.com> (raw)
In-Reply-To: <CA+G9fYuco-vArAVrNhzPZiOza7LNboM7c6qrZJ_q=_fMsGHidQ@mail.gmail.com>
On Fri, Nov 24, 2017 at 04:52:22PM +0530, Naresh Kamboju wrote:
> On 24 November 2017 at 16:42, Greg KH <greg at kroah.com> wrote:
> > On Fri, Nov 24, 2017 at 12:11:41PM +0100, Greg KH wrote:
> >> On Fri, Nov 24, 2017 at 04:32:42PM +0530, Naresh Kamboju wrote:
> >> > Hi,
> >> >
> >> > We have found "no MPX support" bug while running kselftests on
> >> > SuperServer 5019S-ML - x86_64 device.
> >> > Please provide your comments to fix this bug.
> >> >
> >> > LKFT: 4.4-rc 4.9-rc 4.13-rc 4.14-rc: x86: kselftest mpx-mini-test_64 -
> >> > no MPX support - failed - 3869 Aborted (core dumped) (edit)
> >> > https://bugs.linaro.org/show_bug.cgi?id=3497
> >> >
> >> > NOTE:
> >> > Please add your self to Bugzilla to add comments.
> >>
> >> Ugh, what? Why not discuss it here, and provide the full log of what is
> >> happening and what you think should be done to fix it. Don't bury stuff
> >> in some random bugzilla...
> >>
> >> Perhaps a simple abort once you determine that MPX is not supported?
> >
> > Wait, that is what the test is doing, so it's working properly. Why is
> > this an issue?
>
> seems to be that the hardware change in LAB brought up this failures
> Here you could notice difference in test out on old and new machines.
>
> old machine:
> ------------
> processor lacks XSAVE, can not run MPX tests
> selftests: mpx-mini-test_64 [PASS]
>
> New machine:
> -------------
> XSAVE is supported by HW & OS
> XSAVE processor supported state mask: 0x1f
> XSAVE OS supported state mask: 0x1f
> BNDREGS: size: 64 user: 1 supervisor: 0 aligned: 0
> BNDCSR: size: 64 user: 1 supervisor: 0 aligned: 0
> no MPX support
> ./run_kselftest.sh: line 214: 3869 Aborted (core dumped) ./mpx-mini-test_64
> selftests: mpx-mini-test_64 [FAIL]
Yes, the tests runs differently on different hardware.
So abort() should not happen if there is no MPX support, care to make up
a patch and test it on your system?
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: greg@kroah.com (Greg KH)
Subject: [Linux-kselftest-mirror] selftests: x86_64: kselftest mpx-mini-test_64 - no MPX support - failed - 3869 Aborted (core dumped)
Date: Fri, 24 Nov 2017 12:46:35 +0100 [thread overview]
Message-ID: <20171124114635.GB1916@kroah.com> (raw)
Message-ID: <20171124114635.8qXWAe9t934drV6pJaXCBwSUQao4pxZ0A-VqAjkC-w4@z> (raw)
In-Reply-To: <CA+G9fYuco-vArAVrNhzPZiOza7LNboM7c6qrZJ_q=_fMsGHidQ@mail.gmail.com>
On Fri, Nov 24, 2017@04:52:22PM +0530, Naresh Kamboju wrote:
> On 24 November 2017@16:42, Greg KH <greg@kroah.com> wrote:
> > On Fri, Nov 24, 2017@12:11:41PM +0100, Greg KH wrote:
> >> On Fri, Nov 24, 2017@04:32:42PM +0530, Naresh Kamboju wrote:
> >> > Hi,
> >> >
> >> > We have found "no MPX support" bug while running kselftests on
> >> > SuperServer 5019S-ML - x86_64 device.
> >> > Please provide your comments to fix this bug.
> >> >
> >> > LKFT: 4.4-rc 4.9-rc 4.13-rc 4.14-rc: x86: kselftest mpx-mini-test_64 -
> >> > no MPX support - failed - 3869 Aborted (core dumped) (edit)
> >> > https://bugs.linaro.org/show_bug.cgi?id=3497
> >> >
> >> > NOTE:
> >> > Please add your self to Bugzilla to add comments.
> >>
> >> Ugh, what? Why not discuss it here, and provide the full log of what is
> >> happening and what you think should be done to fix it. Don't bury stuff
> >> in some random bugzilla...
> >>
> >> Perhaps a simple abort once you determine that MPX is not supported?
> >
> > Wait, that is what the test is doing, so it's working properly. Why is
> > this an issue?
>
> seems to be that the hardware change in LAB brought up this failures
> Here you could notice difference in test out on old and new machines.
>
> old machine:
> ------------
> processor lacks XSAVE, can not run MPX tests
> selftests: mpx-mini-test_64 [PASS]
>
> New machine:
> -------------
> XSAVE is supported by HW & OS
> XSAVE processor supported state mask: 0x1f
> XSAVE OS supported state mask: 0x1f
> BNDREGS: size: 64 user: 1 supervisor: 0 aligned: 0
> BNDCSR: size: 64 user: 1 supervisor: 0 aligned: 0
> no MPX support
> ./run_kselftest.sh: line 214: 3869 Aborted (core dumped) ./mpx-mini-test_64
> selftests: mpx-mini-test_64 [FAIL]
Yes, the tests runs differently on different hardware.
So abort() should not happen if there is no MPX support, care to make up
a patch and test it on your system?
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-11-24 11:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-24 11:02 [Linux-kselftest-mirror] selftests: x86_64: kselftest mpx-mini-test_64 - no MPX support - failed - 3869 Aborted (core dumped) naresh.kamboju
2017-11-24 11:02 ` Naresh Kamboju
2017-11-24 11:11 ` greg
2017-11-24 11:11 ` Greg KH
2017-11-24 11:12 ` greg
2017-11-24 11:12 ` Greg KH
2017-11-24 11:22 ` naresh.kamboju
2017-11-24 11:22 ` Naresh Kamboju
2017-11-24 11:46 ` greg [this message]
2017-11-24 11:46 ` Greg KH
2017-11-30 5:18 ` naresh.kamboju
2017-11-30 5:18 ` Naresh Kamboju
2017-11-30 15:15 ` dave.hansen
2017-11-30 15:15 ` Dave Hansen
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=20171124114635.GB1916@kroah.com \
--to=unknown@example.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.