On 11/09/2017 09:54 AM, Bart Van Assche wrote: > On Thu, 2017-11-09 at 07:16 +0100, Oleksandr Natalenko wrote: >> is this something known to you, or it is just my fault applying this series to >> v4.13? Except having this warning, suspend/resume works for me: >> >> [ 27.383846] sd 0:0:0:0: [sda] Starting disk >> [ 27.383976] sd 1:0:0:0: [sdb] Starting disk >> [ 27.451218] sdb: Attempt to allocate non-preempt request in preempt-only >> mode. >> [ 27.459640] ------------[ cut here ]------------ >> [ 27.464521] WARNING: CPU: 0 PID: 172 at block/blk-core.c:823 blk_queue_enter+0x222/0x280 > > Hello Oleksandr, > > Thanks for the testing. The warning that you reported is expected. Maybe it > should be left out to avoid that users get confused. If the warning is expected, then it should be removed. It'll just confuse users and cause useless bug reports. > Jens, this patch series still applies cleanly on top of your for-4.15/block > branch. Are you fine with this patch series or do you perhaps want me to > repost it with Oleksandr's Tested-by tag added to each patch? Since you need to kill the warning anyway, let's get it respun. -- Jens Axboe
