From: Evgeniy Didin <Evgeniy.Didin@synopsys.com>
To: "adrian.hunter@intel.com" <adrian.hunter@intel.com>,
"Evgeniy.Didin@synopsys.com" <Evgeniy.Didin@synopsys.com>
Cc: "ulf.hansson@linaro.org" <ulf.hansson@linaro.org>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
"tytso@mit.edu" <tytso@mit.edu>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
"Alexey.Brodkin@synopsys.com" <Alexey.Brodkin@synopsys.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"jh80.chung@samsung.com" <jh80.chung@samsung.com>,
"adilger.kernel@dilger.ca" <adilger.kernel@dilger.ca>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>,
"Eugeniy.Paltsev@synopsys.com" <Eugeniy.Paltsev@synopsys.com>
Subject: Re: mmc: block: bonnie++ runs with errors on arc/hsdk board
Date: Tue, 13 Mar 2018 15:56:42 +0000 [thread overview]
Message-ID: <1520956602.10285.10.camel@synopsys.com> (raw)
In-Reply-To: <486fe92e-9b53-53a4-f98d-129a97032470@intel.com>
On Tue, 2018-03-13 at 16:05 +0200, Adrian Hunter wrote:
> On 13/03/18 14:04, Evgeniy Didin wrote:
> > Hello Adrian,
> >
> > I have discovered, that beggining with 4.16-rc1 bonnie++ benchmark
> > runs with errors on arc/hsdk board. After bisecting between 4.15 and 4.16-rc1,
> > I have found that errors started after
> > commit 81196976ed94 (mmc: block: Add blk-mq support).
> >
> > Error message is like:
> >
> > > # bonnie++ -u root -r 256 -s 512 -x 1 -d /mnt
> > > Using uid:0, gid:0.
> > > Writing with putc()...random: crng init done
> > > done
> > > Writing intelligently...INFO: task kworker/u8:0:5 blocked for more than 10 seconds.
> > > Not tainted 4.15.0-rc3-00012-g81196976ed94-dirty #1
> > > "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> > > kworker/u8:0 D 0 5 2 0x00000000
> > > Workqueue: writeback wb_workfn (flush-179:0)
> > >
> > > Stack Trace:
> > > __switch_to+0x0/0xac
> > > __schedule+0x1b8/0x738
> > > io_schedule+0x5c/0xc0
> > > bit_wait_io+0xc/0x48
> > > out_of_line_wait_on_bit+0x78/0xc0
> > > do_get_write_access+0x1aa/0x4cc
> > > jbd2_journal_get_write_access+0x32/0x74
> > > __ext4_journal_get_write_access+0x3a/0xac
> > > ext4_mb_mark_diskspace_used+0x66/0x5b0
> > > ext4_mb_new_blocks+0x1ee/0x830
> > > ext4_ext_map_blocks+0x504/0xcac
> > > ext4_map_blocks+0x262/0x5e8
> > > mpage_map_and_submit_extent+0xb8/0x648
> > > ext4_writepages+0x5ce/0x6b4
> > > do_writepages+0x20/0x84
> > > __writeback_single_inode+0x2a/0x154
> > > wb_writeback+0x538/0xae0
> > > wb_workfn+0x17c/0x334
> > > process_one_work+0x1a6/0x350
> > > worker_thread+0xf2/0x478
> > > kthread+0x120/0x13c
> > > ret_from_fork+0x18/0x1c
> >
> > There are some details of hsdk_defconfig presented bellow:
> >
> > SOFTLOCKUP_DETECTOR=y
> > DETECT_HUNG_TASK=y
> > DEFAULT_HUNG_TASK_TIMEOUT=10
> > MMC_DW=y
> > MMC_DW_PLTFM=y
> >
> > I have also tested bonnie++ on Wandboard on v4.16-rc5 with the same
> > DEFAULT_HUNG_TASK_TIMEOUT=10, but there were no errors.
> >
> > Even though it is not critical error and we see bonnie++ test proceeds to the end,
> > still it is strange, that some process is running in kernel space for a long time (at least 10sec).
> > What is strange, before metioned commit I can't reproduce this behaviour.
> >
> > I am wondering is this expected behaviour?
>
> Was the performance affected? i.e. the results from bonnie++
I have run bonnie++ several times before and after mentioned commit. Here is output:
--------------------------------------------------<8-------------------------------------------------------------------------
Before commit:
ARCLinux,512M,6442,50,7211,0,5333,0,12954,99,345638,100,+++++,+++,16,22322,100,+++++,+++,32735,99,22921,100,+++++,+++,32211,100
ARCLinux,512M,6611,51,7248,0,5162,0,12951,99,344763,99,+++++,+++,16,22649,99,+++++,+++,32723,99,22572,100,+++++,+++,31697,100
ARCLinux,512M,6597,52,7307,0,5368,0,12934,99,343987,99,+++++,+++,16,22775,100,+++++,+++,32713,99,22832,100,+++++,+++,31899,99
After commit:
ARCLinux,512M,4453,36,6474,1,5852,0,12940,99,344329,100,+++++,+++,16,22168,98,+++++,+++,32760,99,22755,100,+++++,+++,32205,100
ARCLinux,512M,5159,42,6944,1,5658,0,12945,99,344290,100,+++++,+++,16,22295,100,+++++,+++,32715,99,22888,99,+++++,+++,32007,99
ARCLinux,512M,5170,42,6840,2,5315,0,12946,99,343889,100,+++++,+++,16,22445,100,+++++,+++,32681,99,22967,100,+++++,+++,32117,99
--------------------------------------------------<8------------------------------------------------------------------------
^^^^
If i understand correctly, in third column is shown "sequential output" per character speed (K/sec), which decreased.
> What mount options did you use?
I didn't use any options. Simply:
# mount /dev/mmcblk0p1 /mnt
Best regards,
Evgeniy Didin
_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc
WARNING: multiple messages have this Message-ID (diff)
From: Evgeniy.Didin@synopsys.com (Evgeniy Didin)
To: linux-snps-arc@lists.infradead.org
Subject: mmc: block: bonnie++ runs with errors on arc/hsdk board
Date: Tue, 13 Mar 2018 15:56:42 +0000 [thread overview]
Message-ID: <1520956602.10285.10.camel@synopsys.com> (raw)
In-Reply-To: <486fe92e-9b53-53a4-f98d-129a97032470@intel.com>
On Tue, 2018-03-13@16:05 +0200, Adrian Hunter wrote:
> On 13/03/18 14:04, Evgeniy Didin wrote:
> > Hello Adrian,
> >
> > I have discovered, that beggining with 4.16-rc1 bonnie++ benchmark
> > runs with errors on arc/hsdk board. After bisecting between 4.15 and 4.16-rc1,
> > I have found that errors started after?
> > commit 81196976ed94 (mmc: block: Add blk-mq support).
> >
> > Error message is like:
> >
> > > # bonnie++ -u root -r 256 -s 512 -x 1 -d??/mnt?
> > > Using uid:0, gid:0.
> > > Writing with putc()...random: crng init done
> > > done
> > > Writing intelligently...INFO: task kworker/u8:0:5 blocked for more than 10 seconds.
> > > ??????Not tainted 4.15.0-rc3-00012-g81196976ed94-dirty #1
> > > "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> > > kworker/u8:0????D????0?????5??????2 0x00000000
> > > Workqueue: writeback wb_workfn (flush-179:0)
> > >
> > > Stack Trace:
> > > ??__switch_to+0x0/0xac
> > > ??__schedule+0x1b8/0x738
> > > ??io_schedule+0x5c/0xc0
> > > ??bit_wait_io+0xc/0x48
> > > ??out_of_line_wait_on_bit+0x78/0xc0
> > > ??do_get_write_access+0x1aa/0x4cc
> > > ??jbd2_journal_get_write_access+0x32/0x74
> > > ??__ext4_journal_get_write_access+0x3a/0xac
> > > ??ext4_mb_mark_diskspace_used+0x66/0x5b0
> > > ??ext4_mb_new_blocks+0x1ee/0x830
> > > ??ext4_ext_map_blocks+0x504/0xcac
> > > ??ext4_map_blocks+0x262/0x5e8
> > > ??mpage_map_and_submit_extent+0xb8/0x648
> > > ??ext4_writepages+0x5ce/0x6b4
> > > ??do_writepages+0x20/0x84
> > > ??__writeback_single_inode+0x2a/0x154
> > > ??wb_writeback+0x538/0xae0
> > > ??wb_workfn+0x17c/0x334
> > > ??process_one_work+0x1a6/0x350
> > > ??worker_thread+0xf2/0x478
> > > ??kthread+0x120/0x13c
> > > ??ret_from_fork+0x18/0x1c
> >
> > There are some details of hsdk_defconfig presented bellow:
> >
> > SOFTLOCKUP_DETECTOR=y
> > DETECT_HUNG_TASK=y
> > DEFAULT_HUNG_TASK_TIMEOUT=10
> > MMC_DW=y
> > MMC_DW_PLTFM=y
> >
> > I have also tested bonnie++ on Wandboard on v4.16-rc5 with the same
> > DEFAULT_HUNG_TASK_TIMEOUT=10, but there were no errors.
> >
> > Even though it is not critical error and we see bonnie++ test proceeds to the end,
> > still it is strange, that some process is running in kernel space for a long time (at least 10sec).
> > What is strange, before metioned commit I can't reproduce this behaviour.
> >
> > I am wondering is this expected behaviour??
>
> Was the performance affected? i.e. the results from bonnie++
I have run bonnie++ several times before and after mentioned commit. Here is output:
--------------------------------------------------<8-------------------------------------------------------------------------
Before commit:
ARCLinux,512M,6442,50,7211,0,5333,0,12954,99,345638,100,+++++,+++,16,22322,100,+++++,+++,32735,99,22921,100,+++++,+++,32211,100
ARCLinux,512M,6611,51,7248,0,5162,0,12951,99,344763,99,+++++,+++,16,22649,99,+++++,+++,32723,99,22572,100,+++++,+++,31697,100
ARCLinux,512M,6597,52,7307,0,5368,0,12934,99,343987,99,+++++,+++,16,22775,100,+++++,+++,32713,99,22832,100,+++++,+++,31899,99
After commit:
ARCLinux,512M,4453,36,6474,1,5852,0,12940,99,344329,100,+++++,+++,16,22168,98,+++++,+++,32760,99,22755,100,+++++,+++,32205,100
ARCLinux,512M,5159,42,6944,1,5658,0,12945,99,344290,100,+++++,+++,16,22295,100,+++++,+++,32715,99,22888,99,+++++,+++,32007,99
ARCLinux,512M,5170,42,6840,2,5315,0,12946,99,343889,100,+++++,+++,16,22445,100,+++++,+++,32681,99,22967,100,+++++,+++,32117,99
--------------------------------------------------<8------------------------------------------------------------------------
^^^^?
If i understand correctly, in third column is shown "sequential output" per character speed (K/sec), which decreased.
> What mount options did you use?
I didn't use any options. Simply:
# mount /dev/mmcblk0p1 /mnt
Best regards,
Evgeniy Didin
next prev parent reply other threads:[~2018-03-13 15:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 12:04 mmc: block: bonnie++ runs with errors on arc/hsdk board Evgeniy Didin
2018-03-13 12:04 ` Evgeniy Didin
2018-03-13 14:05 ` Adrian Hunter
2018-03-13 14:05 ` Adrian Hunter
2018-03-13 15:56 ` Evgeniy Didin [this message]
2018-03-13 15:56 ` Evgeniy Didin
2018-03-14 12:32 ` Evgeniy Didin
2018-03-14 12:32 ` Evgeniy Didin
2018-03-15 9:27 ` Adrian Hunter
2018-03-15 9:27 ` Adrian Hunter
2018-03-15 15:08 ` Evgeniy Didin
2018-03-15 15:08 ` Evgeniy Didin
2018-03-16 12:12 ` Adrian Hunter
2018-03-16 12:12 ` Adrian Hunter
2018-03-16 17:10 ` Evgeniy Didin
2018-03-16 17:10 ` Evgeniy Didin
2018-03-20 8:29 ` Adrian Hunter
2018-03-20 8:29 ` Adrian Hunter
2018-03-15 16:38 ` Vineet Gupta
2018-03-15 16:38 ` Vineet Gupta
2018-03-15 17:21 ` Alexey Brodkin
2018-03-15 17:21 ` Alexey Brodkin
2018-03-16 7:20 ` Adrian Hunter
2018-03-16 7:20 ` Adrian Hunter
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=1520956602.10285.10.camel@synopsys.com \
--to=evgeniy.didin@synopsys.com \
--cc=Alexey.Brodkin@synopsys.com \
--cc=Eugeniy.Paltsev@synopsys.com \
--cc=adilger.kernel@dilger.ca \
--cc=adrian.hunter@intel.com \
--cc=jh80.chung@samsung.com \
--cc=linus.walleij@linaro.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=tytso@mit.edu \
--cc=ulf.hansson@linaro.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.