Bug 17489 - trace in xfs_trans_ail_cursor_first
Summary: trace in xfs_trans_ail_cursor_first
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-13 16:14 CET by Chris Denice
Modified: 2016-02-25 14:18 CET (History)
0 users

See Also:
Source RPM: kernel-4.4.0-1.mga6.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Chris Denice 2016-01-13 16:14:27 CET 
Description of problem:

Attempting to suspend the system fails with a kernel trace in xfsaild. This only concerns kernel >= 4.4.0, works fine with any other older kernels:


here the trace:
-------------------------


[ 1854.056943] Freezing of tasks failed after 20.008 seconds (2 tasks refusing to freeze, wq_busy=0):
[ 1854.057096] xfsaild/sdc1    S ffff8807fa643e08     0   662      2 0x00000000
[ 1854.057213]  ffff8807fa643e08 ffff8807fbb46400 ffff8807f89ba300 ffff8807fa644000
[ 1854.057338]  0000000000000000 ffffffffc04d7580 ffff8807f8b22e40 0000000000000000
[ 1854.057463]  ffff8807fa643e20 ffffffff816ce0c5 ffff8807f8b22e80 ffff8807fa643ec8
[ 1854.057586] Call Trace:
[ 1854.057720]  [<ffffffffc04d7580>] ? xfs_trans_ail_cursor_first+0x90/0x90 [xfs]
[ 1854.057830]  [<ffffffff816ce0c5>] schedule+0x35/0x80
[ 1854.057964]  [<ffffffffc04d7aa4>] xfsaild+0x524/0x5d0 [xfs]
[ 1854.058105]  [<ffffffffc04d7580>] ? xfs_trans_ail_cursor_first+0x90/0x90 [xfs]
[ 1854.058266]  [<ffffffffc04d7580>] ? xfs_trans_ail_cursor_first+0x90/0x90 [xfs]
[ 1854.058374]  [<ffffffff81090409>] kthread+0xc9/0xe0
[ 1854.058449]  [<ffffffff81090340>] ? kthread_worker_fn+0x160/0x160
[ 1854.058540]  [<ffffffff816d218f>] ret_from_fork+0x3f/0x70
[ 1854.058621]  [<ffffffff81090340>] ? kthread_worker_fn+0x160/0x160
[ 1854.058710] xfsaild/sdb1    S ffff8807f8843e08     0   672      2 0x00000000
[ 1854.058823]  ffff8807f8843e08 ffff8807fbb26300 ffff8807faa962c0 ffff8807f8844000
[ 1854.058946]  0000000000000000 ffffffffc04d7580 ffff8800dba6bbc0 0000000000000000
[ 1854.059069]  ffff8807f8843e20 ffffffff816ce0c5 ffff8800dba6bc00 ffff8807f8843ec8
[ 1854.059192] Call Trace:
[ 1854.059289]  [<ffffffffc04d7580>] ? xfs_trans_ail_cursor_first+0x90/0x90 [xfs]
[ 1854.059395]  [<ffffffff816ce0c5>] schedule+0x35/0x80
[ 1854.059525]  [<ffffffffc04d7aa4>] xfsaild+0x524/0x5d0 [xfs]
[ 1854.059665]  [<ffffffffc04d7580>] ? xfs_trans_ail_cursor_first+0x90/0x90 [xfs]
[ 1854.059826]  [<ffffffffc04d7580>] ? xfs_trans_ail_cursor_first+0x90/0x90 [xfs]
[ 1854.059932]  [<ffffffff81090409>] kthread+0xc9/0xe0
[ 1854.060006]  [<ffffffff81090340>] ? kthread_worker_fn+0x160/0x160
[ 1854.060096]  [<ffffffff816d218f>] ret_from_fork+0x3f/0x70
[ 1854.060177]  [<ffffffff81090340>] ? kthread_worker_fn+0x160/0x160



Reproducible: 

Steps to Reproduce:
Comment 1 Chris Denice 2016-01-13 16:18:30 CET 
and the fix:

http://oss.sgi.com/archives/xfs/2015-10/msg00639.html
Comment 2 Samuel Verschelde 2016-01-18 10:42:38 CET 
Assigning to tmb

Assignee: bugsquad => tmb

Comment 3 Chris Denice 2016-02-01 18:33:13 CET 
My mistake, that patch is actually already in the kernel as tmb told me; and is the actual CAUSE of the bug :)

The follow-up discussion is there

http://oss.sgi.com/archives/xfs/2016-01/msg00467.html

reverting it fixes it apparently!

cheers.
Comment 4 Thomas Backlund 2016-02-13 21:54:07 CET 
Revert merged upstream and added in kernel-4.4.1-2.mga6 currently building

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 5 Chris Denice 2016-02-25 14:18:36 CET 
Thanks a lot, works nicely again!
Note You need to log in before you can comment on or make changes to this bug.