| 2018-11-02 05:00:13 |
quanxian |
bug |
|
|
added bug |
| 2019-03-05 03:22:06 |
quanxian |
bug |
|
|
added subscriber Roman Sobanski |
| 2019-05-07 02:56:08 |
quanxian |
bug task added |
|
ubuntu |
|
| 2019-05-07 02:57:57 |
quanxian |
description |
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:
[ 721.892833] [<ffffffff9115fea9>] schedule+0x29/0x70
[ 721.899068] [<ffffffff90d41c05>] blk_queue_enter+0x125/0x240
[ 721.906172] [<ffffffff90ac1a20>] ? wake_up_atomic_t+0x30/0x30
[ 721.913382] [<ffffffff90d42013>] generic_make_request+0x43/0x380
[ 721.920871] [<ffffffff9115f87c>] ? __schedule+0x41c/0xa20
[ 721.927709] [<ffffffffc015e7ed>] raid10d+0xb3d/0x1650 [raid10]
[ 721.935032] [<ffffffff9115fea9>] ? schedule+0x29/0x70
[ 721.941506] [<ffffffff9115d7f1>] ? schedule_timeout+0x221/0x2d0
[ 721.948949] [<ffffffff90f8716d>] md_thread+0x16d/0x1e0
[ 721.955543] [<ffffffff90ac1a20>] ? wake_up_atomic_t+0x30/0x30
[ 721.962824] [<ffffffff90f87000>] ? find_pers+0x80/0x80
[ 721.969430] [<ffffffff90ac0a31>] kthread+0xd1/0xe0
[ 721.975651] [<ffffffff90ac0960>] ? insert_kthread_work+0x40/0x40
[ 721.983254] [<ffffffff9116cc1d>] ret_from_fork_nospec_begin+0x7/0x21
[ 721.991259] [<ffffffff90ac0960>] ? insert_kthread_work+0x40/0x40
[ 721.998894] INFO: task md126_resync:2164 blocked for more than 120 seconds.
[ 722.007498] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 722.017085] md126_resync D ffff9fa10b4b4100 0 2164 2 0x00000080
Target Kernel: TBD
Target Release:19.04 |
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:
[ 721.892833] [<ffffffff9115fea9>] schedule+0x29/0x70
[ 721.899068] [<ffffffff90d41c05>] blk_queue_enter+0x125/0x240
[ 721.906172] [<ffffffff90ac1a20>] ? wake_up_atomic_t+0x30/0x30
[ 721.913382] [<ffffffff90d42013>] generic_make_request+0x43/0x380
[ 721.920871] [<ffffffff9115f87c>] ? __schedule+0x41c/0xa20
[ 721.927709] [<ffffffffc015e7ed>] raid10d+0xb3d/0x1650 [raid10]
[ 721.935032] [<ffffffff9115fea9>] ? schedule+0x29/0x70
[ 721.941506] [<ffffffff9115d7f1>] ? schedule_timeout+0x221/0x2d0
[ 721.948949] [<ffffffff90f8716d>] md_thread+0x16d/0x1e0
[ 721.955543] [<ffffffff90ac1a20>] ? wake_up_atomic_t+0x30/0x30
[ 721.962824] [<ffffffff90f87000>] ? find_pers+0x80/0x80
[ 721.969430] [<ffffffff90ac0a31>] kthread+0xd1/0xe0
[ 721.975651] [<ffffffff90ac0960>] ? insert_kthread_work+0x40/0x40
[ 721.983254] [<ffffffff9116cc1d>] ret_from_fork_nospec_begin+0x7/0x21
[ 721.991259] [<ffffffff90ac0960>] ? insert_kthread_work+0x40/0x40
[ 721.998894] INFO: task md126_resync:2164 blocked for more than 120 seconds.
[ 722.007498] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 722.017085] md126_resync D ffff9fa10b4b4100 0 2164 2 0x00000080
Target Kernel: TBD
Target Release:19.10 |
|
| 2019-05-07 02:58:01 |
quanxian |
tags |
intel-kernel-19.04 |
intel-kernel-19.10 |
|
| 2019-10-25 05:37:35 |
quanxian |
description |
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:
[ 721.892833] [<ffffffff9115fea9>] schedule+0x29/0x70
[ 721.899068] [<ffffffff90d41c05>] blk_queue_enter+0x125/0x240
[ 721.906172] [<ffffffff90ac1a20>] ? wake_up_atomic_t+0x30/0x30
[ 721.913382] [<ffffffff90d42013>] generic_make_request+0x43/0x380
[ 721.920871] [<ffffffff9115f87c>] ? __schedule+0x41c/0xa20
[ 721.927709] [<ffffffffc015e7ed>] raid10d+0xb3d/0x1650 [raid10]
[ 721.935032] [<ffffffff9115fea9>] ? schedule+0x29/0x70
[ 721.941506] [<ffffffff9115d7f1>] ? schedule_timeout+0x221/0x2d0
[ 721.948949] [<ffffffff90f8716d>] md_thread+0x16d/0x1e0
[ 721.955543] [<ffffffff90ac1a20>] ? wake_up_atomic_t+0x30/0x30
[ 721.962824] [<ffffffff90f87000>] ? find_pers+0x80/0x80
[ 721.969430] [<ffffffff90ac0a31>] kthread+0xd1/0xe0
[ 721.975651] [<ffffffff90ac0960>] ? insert_kthread_work+0x40/0x40
[ 721.983254] [<ffffffff9116cc1d>] ret_from_fork_nospec_begin+0x7/0x21
[ 721.991259] [<ffffffff90ac0960>] ? insert_kthread_work+0x40/0x40
[ 721.998894] INFO: task md126_resync:2164 blocked for more than 120 seconds.
[ 722.007498] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 722.017085] md126_resync D ffff9fa10b4b4100 0 2164 2 0x00000080
Target Kernel: TBD
Target Release:19.10 |
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:
[ 721.892833] [<ffffffff9115fea9>] schedule+0x29/0x70
[ 721.899068] [<ffffffff90d41c05>] blk_queue_enter+0x125/0x240
[ 721.906172] [<ffffffff90ac1a20>] ? wake_up_atomic_t+0x30/0x30
[ 721.913382] [<ffffffff90d42013>] generic_make_request+0x43/0x380
[ 721.920871] [<ffffffff9115f87c>] ? __schedule+0x41c/0xa20
[ 721.927709] [<ffffffffc015e7ed>] raid10d+0xb3d/0x1650 [raid10]
[ 721.935032] [<ffffffff9115fea9>] ? schedule+0x29/0x70
[ 721.941506] [<ffffffff9115d7f1>] ? schedule_timeout+0x221/0x2d0
[ 721.948949] [<ffffffff90f8716d>] md_thread+0x16d/0x1e0
[ 721.955543] [<ffffffff90ac1a20>] ? wake_up_atomic_t+0x30/0x30
[ 721.962824] [<ffffffff90f87000>] ? find_pers+0x80/0x80
[ 721.969430] [<ffffffff90ac0a31>] kthread+0xd1/0xe0
[ 721.975651] [<ffffffff90ac0960>] ? insert_kthread_work+0x40/0x40
[ 721.983254] [<ffffffff9116cc1d>] ret_from_fork_nospec_begin+0x7/0x21
[ 721.991259] [<ffffffff90ac0960>] ? insert_kthread_work+0x40/0x40
[ 721.998894] INFO: task md126_resync:2164 blocked for more than 120 seconds.
[ 722.007498] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 722.017085] md126_resync D ffff9fa10b4b4100 0 2164 2 0x00000080
Target Kernel: TBD
Target Release:20.04 |
|
| 2019-10-25 05:37:41 |
quanxian |
tags |
intel-kernel-19.10 |
intel-kernel-20.04 |
|
| 2020-02-11 06:02:32 |
quanxian |
intel: status |
New |
Won't Fix |
|
