[Bug 95166] [KBL] Suspend to disk does work after several iterations

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Apr 27 11:31:13 UTC 2016


https://bugs.freedesktop.org/show_bug.cgi?id=95166

Imre Deak <imre.deak at intel.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO

--- Comment #2 from Imre Deak <imre.deak at intel.com> ---
(In reply to cprigent from comment #1)
> Created attachment 123303 [details]
> logs.jpg
> 
> I launched 50 loops of each test modes of hibernation:
> 
> Freezer mode:
> It returned 3 times "write error: Device or resource busy"
> Apr 27 10:10:42 KBLU1 kernel: [  693.773538] Freezing user space processes
> ...
> Apr 27 10:10:42 KBLU1 kernel: [  713.776165] Freezing of tasks failed after
> 20.001 seconds (1 tasks refusing to freeze, wq_busy=0):
> Apr 27 10:10:42 KBLU1 kernel: [  713.776323] fstrim          D
> ffff8801ded4faa8     0  3757   3756 0x00080004
> Apr 27 10:10:42 KBLU1 kernel: [  713.776334]  ffff8801ded4faa8
> 00000000fffffffb ffff8801e6373c80 ffff8801dfda1e40
> Apr 27 10:10:42 KBLU1 kernel: [  713.776341]  ffff8801ded50000
> ffff8801edcd6d00 7fffffffffffffff ffff8801dfda1e40
> Apr 27 10:10:42 KBLU1 kernel: [  713.776347]  0000000016200000
> ffff8801ded4fac0 ffffffff81795b25 0000000000000000
> Apr 27 10:10:42 KBLU1 kernel: [  713.776353] Call Trace:
> Apr 27 10:10:42 KBLU1 kernel: [  713.776367]  [<ffffffff81795b25>]
> schedule+0x35/0x80
> Apr 27 10:10:42 KBLU1 kernel: [  713.776375]  [<ffffffff8179895f>]
> schedule_timeout+0x1af/0x260
> Apr 27 10:10:42 KBLU1 kernel: [  713.776385]  [<ffffffff810ebffc>] ?
> ktime_get+0x3c/0xb0
> Apr 27 10:10:42 KBLU1 kernel: [  713.776390]  [<ffffffff817950a4>]
> io_schedule_timeout+0xa4/0x110
> Apr 27 10:10:42 KBLU1 kernel: [  713.776397]  [<ffffffff81796eb4>]
> wait_for_completion_io+0xa4/0x110
> Apr 27 10:10:42 KBLU1 kernel: [  713.776403]  [<ffffffff810a27e0>] ?
> wake_up_q+0x70/0x70
> Apr 27 10:10:42 KBLU1 kernel: [  713.776412]  [<ffffffff81389d10>]
> blkdev_issue_discard+0x1e0/0x230
> Apr 27 10:10:42 KBLU1 kernel: [  713.776419]  [<ffffffff812bd169>]
> ext4_trim_fs+0x489/0x9e0
> Apr 27 10:10:42 KBLU1 kernel: [  713.776427]  [<ffffffff8128a329>]
> ext4_ioctl+0xc59/0x1300
> Apr 27 10:10:42 KBLU1 kernel: [  713.776436]  [<ffffffff8120ea92>]
> do_vfs_ioctl+0x92/0x580
> Apr 27 10:10:42 KBLU1 kernel: [  713.776444]  [<ffffffff812009f5>] ?
> SYSC_newfstat+0x25/0x30
> Apr 27 10:10:42 KBLU1 kernel: [  713.776451]  [<ffffffff8120eff9>]
> SyS_ioctl+0x79/0x90
> Apr 27 10:10:42 KBLU1 kernel: [  713.776458]  [<ffffffff81003cc9>]
> do_syscall_64+0x69/0x110
> Apr 27 10:10:42 KBLU1 kernel: [  713.776466]  [<ffffffff81799ba5>]
> entry_SYSCALL64_slow_path+0x25/0x25
> Apr 27 10:10:42 KBLU1 kernel: [  713.776472]
> 
> Devices, Platform, Processors, Core modes: 50 with success and without error.
> 
> Then the 1rst normal suspend to disk caused a crashed.
> I attach "test-mode-of-hibernation_kern.log.tar.gz" and logs.jpg (we see
> more logs in the screen than in kern.log)

The above looks like a filesystem or block device, fstrim problem. Please make
sure your filesystems, block devices are ok by running fsck and fstrim on them
manually as necessary.

On the screen capture log OTOH, there is a crash from the network device, so
you may need to avoid using network, or switch to another device/driver for the
test.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20160427/087c9ae9/attachment-0001.html>


More information about the intel-gfx-bugs mailing list