From: Stephen Rothwell <sfr@canb.auug.org.au>
To: kernel test robot <xiaolong.ye@intel.com>
Cc: Christoph Hellwig <hch@lst.de>, Tejun Heo <tj@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
lkp@01.org
Subject: Re: [lkp-robot] [libata] 818831c8b2: kmsg.ata#.#:failed_to_set_xfermode(err_mask=#)
Date: Thu, 22 Jun 2017 10:43:48 +1000 [thread overview]
Message-ID: <20170622104348.169aa800@canb.auug.org.au> (raw)
In-Reply-To: <20170615025854.GB14017@yexl-desktop>
Hi all,
On Thu, 15 Jun 2017 10:58:54 +0800 kernel test robot <xiaolong.ye@intel.com> wrote:
>
> FYI, we noticed the following commit:
>
> commit: 818831c8b22f75353f59a63a484e20736c0567c9 ("libata: implement SECURITY PROTOCOL IN/OUT")
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
>
> in testcase: unixbench
> with following parameters:
>
> runtime: 300s
> nr_task: 100%
> test: fsbuffer
>
> test-description: UnixBench is the original BYTE UNIX benchmark suite aims to test performance of Unix-like system.
> test-url: https://github.com/kdlucas/byte-unixbench
>
>
> on test machine: 8 threads Intel(R) Core(TM) i7 CPU 870 @ 2.93GHz with 4G memory
>
> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
>
>
> [ 16.104144] ata2.00: Security Log not supported
> [ 16.104411] ata2.01: ATAPI: HL-DT-ST DVD+/-RW GH50N, B102, max UDMA/100
> [ 16.104757] ata2.00: failed to set xfermode (err_mask=0x40)
Just wondering if this has been fixed.
--
Cheers,
Stephen Rothwell
prev parent reply other threads:[~2017-06-22 0:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 2:58 kernel test robot
2017-06-22 0:43 ` Stephen Rothwell [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=20170622104348.169aa800@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=tj@kernel.org \
--cc=xiaolong.ye@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®