All of lore.kernel.org
 help / color / mirror / Atom feed
From: Huang, Ying <ying.huang@intel.com>
To: lkp@lists.01.org
Subject: Re: [floppy] 09954bad44: kmsg.blk_update_request:I/O_error, dev_fd#, sector
Date: Mon, 15 Feb 2016 08:34:32 +0800	[thread overview]
Message-ID: <87egcehkvb.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1602150001150.22727@cbobk.fhfr.pm>

[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]

Jiri Kosina <jkosina@suse.cz> writes:

> On Sun, 14 Feb 2016, kernel test robot wrote:
>
>> FYI, we noticed the below changes on
>> 
>> https://git.kernel.org/pub/scm/linux/kernel/git/jikos/linux-block.git for-4.5/for-jens
>> commit 09954bad448791ef01202351d437abdd9497a804 ("floppy: refactor open() flags handling")
>> 
>> 
>> [    6.750917] blk_update_request: I/O error, dev fd0, sector 0
>> [    6.751922] floppy: error -5 while reading block 0
>> 
>> 
>> To reproduce:
>> 
>>         git clone git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
>>         cd lkp-tests
>>         bin/lkp install job.yaml  # job file is attached in this email
>>         bin/lkp run     job.yaml
>
> Seem like I am probably rather bad reading the job.yaml syntax. Do you 
> happen to have C source that reproduces this? It's very likely that it's 
> actually an intended change in bahavior.

Sorry, we use shell script to do the test so we have no C source to
reproduce.  Could you try the above steps?

Best Regards,
Huang, Ying


      reply	other threads:[~2016-02-15  0:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-14  3:03 [floppy] 09954bad44: kmsg.blk_update_request:I/O_error, dev_fd#, sector kernel test robot
2016-02-14 23:01 ` Jiri Kosina
2016-02-15  0:34   ` Huang, Ying [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=87egcehkvb.fsf@yhuang-dev.intel.com \
    --to=ying.huang@intel.com \
    --cc=lkp@lists.01.org \
    /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.