Description:
raid10 Call trace while entering S4 and rebuild is in progress
Hibernation is interrupted by Call Trace.
OS is installed on RAID volume, the volume is in rebuild state while entering S4.
When volume is in clean state, entering S4 is successful.
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Create RAID volume on SATA drives.
2. Install OS on previously created volume.
3. Degrade RAID volume by disconnecting member drive.
4. Add spare drive and start rebuild.
5. While rebuild is in progress, enter S4:
#echo 0 > /sys/power/pm_async
#echo disk > /sys/power/state
Expected results:
Platform can be hibernated.
Actual results:
Platform does not enter to hibernation.
After creation of image file following Call Trace appears:
Description:
raid10 Call trace while entering S4 and rebuild is in progress
Hibernation is interrupted by Call Trace.
OS is installed on RAID volume, the volume is in rebuild state while entering S4.
When volume is in clean state, entering S4 is successful.
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Create RAID volume on SATA drives.
2. Install OS on previously created volume.
3. Degrade RAID volume by disconnecting member drive.
4. Add spare drive and start rebuild.
5. While rebuild is in progress, enter S4:
#echo 0 > /sys/power/pm_async
#echo disk > /sys/power/state
Expected results:
Platform can be hibernated.
Actual results:
Platform does not enter to hibernation.
After creation of image file following Call Trace appears:
[ 721.889413] Call Trace: ea9>] schedule+0x29/0x70 c05>] blk_queue_ enter+0x125/ 0x240 a20>] ? wake_up_ atomic_ t+0x30/ 0x30 013>] generic_ make_request+ 0x43/0x380 87c>] ? __schedule+ 0x41c/0xa20 7ed>] raid10d+ 0xb3d/0x1650 [raid10] ea9>] ? schedule+0x29/0x70 7f1>] ? schedule_ timeout+ 0x221/0x2d0 16d>] md_thread+ 0x16d/0x1e0 a20>] ? wake_up_ atomic_ t+0x30/ 0x30 000>] ? find_pers+0x80/0x80 a31>] kthread+0xd1/0xe0 960>] ? insert_ kthread_ work+0x40/ 0x40 c1d>] ret_from_ fork_nospec_ begin+0x7/ 0x21 960>] ? insert_ kthread_ work+0x40/ 0x40 kernel/ hung_task_ timeout_ secs" disables this message.
[ 721.892833] [<ffffffff9115f
[ 721.899068] [<ffffffff90d41
[ 721.906172] [<ffffffff90ac1
[ 721.913382] [<ffffffff90d42
[ 721.920871] [<ffffffff9115f
[ 721.927709] [<ffffffffc015e
[ 721.935032] [<ffffffff9115f
[ 721.941506] [<ffffffff9115d
[ 721.948949] [<ffffffff90f87
[ 721.955543] [<ffffffff90ac1
[ 721.962824] [<ffffffff90f87
[ 721.969430] [<ffffffff90ac0
[ 721.975651] [<ffffffff90ac0
[ 721.983254] [<ffffffff9116c
[ 721.991259] [<ffffffff90ac0
[ 721.998894] INFO: task md126_resync:2164 blocked for more than 120 seconds.
[ 722.007498] "echo 0 > /proc/sys/
[ 722.017085] md126_resync D ffff9fa10b4b4100 0 2164 2 0x00000080
Target Kernel: TBD
Target Release:19.04