From: Xishi Qiu <qiuxishi@huawei.com>
To: <linux-mm@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>,
"guozhibin 00179312" <g00179312@notesmail.huawei.com.cn>,
Xishi Qiu <qiuxishi@huawei.com>, <linux.nics@intel.com>,
<e1000-devel@lists.sourceforge.net>
Subject: bad pages when up/down network cable
Date: Tue, 14 Jul 2015 16:31:45 +0800 [thread overview]
Message-ID: <55A4C8F1.4000104@huawei.com> (raw)
1、the host directly link to the storage device，by intel ixgbe NIC;
between them, no switch or router.
2、the nic of the storage device suddenly become unused and then OK
after a little time, this happened frequency.
3、the host printk a lot of message like these:
The kernel is SUSE 3.0.13, use slab, and the following log shows the
page still have PG_slab when free_pages(). Does anyone have seen the
problem?
Jul 9 11:31:36 root kernel: [1042291.977565] BUG: Bad page state in process swapper pfn:00bf2
Jul 9 11:31:36 root kernel: [1042291.977568] page:ffffea0000029cf0 count:0 mapcount:0 mapping: (null) index:0x7f6d4f500
Jul 9 11:31:36 root kernel: [1042291.977571] page flags: 0x40000000000100(slab) // here is the reason
Jul 9 11:31:36 root kernel: [1042291.977574] Pid: 0, comm: swapper Tainted: G B X 3.0.13-0.27-default #1
Jul 9 11:31:36 root kernel: [1042291.977577] Call Trace:
Jul 9 11:31:36 root kernel: [1042291.977583] [<ffffffff810048b5>] dump_trace+0x75/0x300
Jul 9 11:31:36 root kernel: [1042291.977639] [<ffffffff8143ea0f>] dump_stack+0x69/0x6f
Jul 9 11:31:36 root kernel: [1042291.977644] [<ffffffff810f53a1>] bad_page+0xb1/0x120
Jul 9 11:31:37 root kernel: [1042291.977649] [<ffffffff810f5926>] free_pages_prepare+0xe6/0x110
Jul 9 11:31:37 root kernel: [1042291.977654] [<ffffffff810f9259>] free_hot_cold_page+0x49/0x1f0
Jul 9 11:31:37 root kernel: [1042291.977660] [<ffffffff8137a3b4>] skb_release_data+0xb4/0xe0
Jul 9 11:31:37 root kernel: [1042291.977665] [<ffffffff81379e79>] __kfree_skb+0x9/0x90
Jul 9 11:31:37 root kernel: [1042291.977676] [<ffffffffa02784a9>] ixgbe_clean_tx_irq+0xa9/0x480 [ixgbe]
Jul 9 11:31:37 root kernel: [1042291.977693] [<ffffffffa02788cb>] ixgbe_poll+0x4b/0x1a0 [ixgbe]
Jul 9 11:31:37 root kernel: [1042291.977705] [<ffffffff81389c3a>] net_rx_action+0x10a/0x2c0
Jul 9 11:31:37 root kernel: [1042291.977711] [<ffffffff81060a1f>] __do_softirq+0xef/0x220
Jul 9 11:31:37 root kernel: [1042291.977716] [<ffffffff8144a8bc>] call_softirq+0x1c/0x30
Jul 9 11:31:37 root kernel: [1042291.978974] DWARF2 unwinder stuck at call_softirq+0x1c/0x30
Thanks,
Xishi Qiu
next reply other threads:[~2015-07-14 8:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 8:31 Xishi Qiu [this message]
[not found] ` <CAD=hENdLy_K6LFE3Cm2nfxxVOhWRZWiJmKX5-EKdoBtnWP3MJQ@mail.gmail.com>
2015-07-14 9:24 ` [E1000-devel] bad pages when up/down network cable Xishi Qiu
2015-07-14 9:36 ` Xishi Qiu
2015-07-14 14:40 ` [linux-nics] " Skidmore, Donald C
2015-07-15 1:30 ` Xishi Qiu
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=55A4C8F1.4000104@huawei.com \
--to=qiuxishi@huawei.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=g00179312@notesmail.huawei.com.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@vger.kernel.org \
--cc=linux.nics@intel.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