From: Stefan Priebe <s.priebe@profihost.ag>
To: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Cc: linux-fsdevel@vger.kernel.org,
"xfs-masters@oss.sgi.com" <xfs-masters@oss.sgi.com>
Subject: xfs trace in 4.4.2
Date: Sat, 20 Feb 2016 09:02:28 +0100 [thread overview]
Message-ID: <56C81D94.7090603@profihost.ag> (raw)
Hi,
got this one today. Not sure if this is a bug.
[67674.907736] ------------[ cut here ]------------
[67674.955858] WARNING: CPU: 5 PID: 197 at fs/xfs/xfs_aops.c:1232
xfs_vm_releasepage+0xa9/0xe0()
[67675.005345] Modules linked in: dm_mod netconsole ipt_REJECT
nf_reject_ipv4 mpt3sas raid_class xt_multiport iptable_filter ip_tabl
es x_tables 8021q garp bonding coretemp loop usbhid ehci_pci ehci_hcd
sb_edac ipmi_si usbcore i2c_i801 edac_core usb_common ipmi_msg
handler button btrfs xor raid6_pq raid1 md_mod sg igb sd_mod
i2c_algo_bit ixgbe ahci i2c_core mdio isci libahci libsas ptp megaraid_
sas scsi_transport_sas pps_core
[67675.221939] CPU: 5 PID: 197 Comm: kswapd0 Not tainted 4.4.2+1-ph #1
[67675.277120] Hardware name: Supermicro
X9DRi-LN4+/X9DR3-LN4+/X9DRi-LN4+/X9DR3-LN4+, BIOS 3.2 03/04/2015
[67675.335176] ffffffffa3a5065d ffff88007950fa98 ffffffffa33bd4e1
0000000000000001
[67675.392983] 0000000000000000 ffff88007950fad8 ffffffffa3083587
ffff88007950fae8
[67675.449743] 0000000000000001 ffffea0020883480 ffff880cf4b9cdd0
ffffea00208834a0
[67675.506112] Call Trace:
[67675.561285] [<ffffffffa33bd4e1>] dump_stack+0x45/0x64
[67675.619364] [<ffffffffa3083587>] warn_slowpath_common+0x97/0xe0
[67675.675719] [<ffffffffa30835ea>] warn_slowpath_null+0x1a/0x20
[67675.731113] [<ffffffffa3320a89>] xfs_vm_releasepage+0xa9/0xe0
[67675.786116] [<ffffffffa318a4b0>] ? page_mkclean_one+0xd0/0xd0
[67675.844216] [<ffffffffa318b1d0>] ? anon_vma_prepare+0x150/0x150
[67675.903862] [<ffffffffa31506c2>] try_to_release_page+0x32/0x50
[67675.957625] [<ffffffffa3164d3e>] shrink_active_list+0x3ce/0x3e0
[67676.011497] [<ffffffffa31653d7>] shrink_lruvec+0x687/0x7d0
[67676.064980] [<ffffffffa31655fc>] shrink_zone+0xdc/0x2c0
[67676.118828] [<ffffffffa3166659>] kswapd+0x4f9/0x930
[67676.172075] [<ffffffffa3166160>] ?
mem_cgroup_shrink_node_zone+0x150/0x150
[67676.225139] [<ffffffffa30a08c9>] kthread+0xc9/0xe0
[67676.277539] [<ffffffffa30a0800>] ? kthread_stop+0xe0/0xe0
[67676.330124] [<ffffffffa36a8c8f>] ret_from_fork+0x3f/0x70
[67676.381816] [<ffffffffa30a0800>] ? kthread_stop+0xe0/0xe0
[67676.433499] ---[ end trace cb1827fe308f7f6b ]---
Greets Stefan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2016-02-20 8:20 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-20 8:02 Stefan Priebe [this message]
2016-02-20 14:45 ` xfs trace in 4.4.2 Brian Foster
2016-02-20 18:02 ` Stefan Priebe - Profihost AG
2016-03-04 18:47 ` xfs trace in 4.4.2 / also in 4.3.3 WARNING fs/xfs/xfs_aops.c:1232 xfs_vm_releasepage Stefan Priebe
2016-03-04 19:13 ` Brian Foster
2016-03-04 20:02 ` Stefan Priebe
2016-03-04 21:03 ` Brian Foster
2016-03-04 21:15 ` Stefan Priebe
2016-03-05 22:48 ` Dave Chinner
2016-03-05 22:58 ` Stefan Priebe
2016-03-23 13:26 ` Stefan Priebe - Profihost AG
2016-03-23 13:28 ` Stefan Priebe - Profihost AG
2016-03-23 14:07 ` Brian Foster
2016-03-24 8:10 ` Stefan Priebe - Profihost AG
2016-03-24 8:15 ` Stefan Priebe - Profihost AG
2016-03-24 11:17 ` Brian Foster
2016-03-24 12:17 ` Stefan Priebe - Profihost AG
2016-03-24 12:24 ` Brian Foster
2016-04-04 6:12 ` Stefan Priebe - Profihost AG
2016-05-11 12:26 ` Stefan Priebe - Profihost AG
2016-05-11 13:34 ` Brian Foster
2016-05-11 14:03 ` Stefan Priebe - Profihost AG
2016-05-11 15:59 ` Brian Foster
2016-05-11 19:20 ` Stefan Priebe
2016-05-15 11:03 ` Stefan Priebe
2016-05-15 11:50 ` Brian Foster
2016-05-15 12:41 ` Stefan Priebe
2016-05-16 1:06 ` Brian Foster
2016-05-22 19:36 ` Stefan Priebe - Profihost AG
2016-05-22 21:38 ` Dave Chinner
2016-05-30 7:23 ` Stefan Priebe - Profihost AG
2016-05-30 22:36 ` shrink_active_list/try_to_release_page bug? (was Re: xfs trace in 4.4.2 / also in 4.3.3 WARNING fs/xfs/xfs_aops.c:1232 xfs_vm_releasepage) Dave Chinner
2016-05-31 1:07 ` Minchan Kim
2016-05-31 2:55 ` Dave Chinner
2016-05-31 3:59 ` Minchan Kim
2016-05-31 6:07 ` Dave Chinner
2016-05-31 6:11 ` Stefan Priebe - Profihost AG
2016-05-31 7:31 ` Dave Chinner
2016-05-31 8:03 ` Stefan Priebe - Profihost AG
2016-06-02 12:13 ` Stefan Priebe - Profihost AG
2016-06-02 12:44 ` Holger Hoffstätte
2016-06-02 23:08 ` Dave Chinner
2016-05-31 9:50 ` Jan Kara
2016-06-01 1:38 ` Minchan Kim
2016-08-17 15:37 ` Andreas Grünbacher
2016-06-03 17:56 ` xfs trace in 4.4.2 / also in 4.3.3 WARNING fs/xfs/xfs_aops.c:1232 xfs_vm_releasepage Stefan Priebe - Profihost AG
2016-06-03 19:35 ` Holger Hoffstätte
2016-06-04 0:04 ` Dave Chinner
2016-06-26 5:45 ` Stefan Priebe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56C81D94.7090603@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=linux-fsdevel@vger.kernel.org \
--cc=xfs-masters@oss.sgi.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox