From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Zhouping Liu <zliu@redhat.com>
Cc: linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>,
caiqian <caiqian@redhat.com>, Caspar Zhang <czhang@redhat.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: [BUG][s390x] mm: system crashed
Date: Mon, 15 Apr 2013 07:56:27 +0200 [thread overview]
Message-ID: <20130415055627.GB4207@osiris> (raw)
In-Reply-To: <2068164110.268217.1365996520440.JavaMail.root@redhat.com>
On Sun, Apr 14, 2013 at 11:28:40PM -0400, Zhouping Liu wrote:
> Hi All,
>
> I hit the below crashed when doing memory related tests[1] on s390x:
>
> --------------- snip ---------------------
> i? 1/2 15929.351639A? i? 1/2 <000000000021c0a6>A? shrink_inactive_list+0x1c6/0x56c
> i? 1/2 15929.351647A? i? 1/2 <000000000021c69e>A? shrink_lruvec+0x252/0x56c
> i? 1/2 15929.351654A? i? 1/2 <000000000021ca44>A? shrink_zone+0x8c/0x1bc
> i? 1/2 15929.351662A? i? 1/2 <000000000021d080>A? balance_pgdat+0x50c/0x658
> i? 1/2 15929.351671A? i? 1/2 <000000000021d318>A? kswapd+0x14c/0x470
> i? 1/2 15929.351680A? i? 1/2 <0000000000158292>A? kthread+0xda/0xe4
> i? 1/2 15929.351690A? i? 1/2 <000000000062a5de>A? kernel_thread_starter+0x6/0xc
> i? 1/2 15929.351700A? i? 1/2 <000000000062a5d8>A? kernel_thread_starter+0x0/0xc
> i? 1/2 16109.346061A? INFO: rcu_sched self-detected stall on CPU { 0} (t=24006 jiffies
> g=89766 c=89765 q=10544)
> i? 1/2 16109.346101A? CPU: 0 Tainted: G D 3.9.0-rc6+ #1
> i? 1/2 16109.346106A? Process kswapd0 (pid: 28, task: 000000003b2a0000, ksp: 000000003b
> 2ab8c0)
> i? 1/2 16109.346110A? 000000000001bb60 000000000001bb70 0000000000000002 0000000
> 000000000
> 000000000001bc00 000000000001bb78 000000000001bb78 00000000001009ca
> 0000000000000000 0000000000002930 000000000000000a 000000000000000a
> 000000000001bbc0 000000000001bb60 0000000000000000 0000000000000000
> 000000000063bb18 00000000001009ca 000000000001bb60 000000000001bbb0
> i? 1/2 16109.346170A? Call Trace:
> i? 1/2 16109.346179A? (i? 1/2 <0000000000100920>A? show_trace+0x128/0x12c)
> i? 1/2 16109.346195A? i? 1/2 <00000000001cd320>A? rcu_check_callbacks+0x458/0xccc
> i? 1/2 16109.346209A? i? 1/2 <0000000000140f2e>A? update_process_times+0x4a/0x74
> i? 1/2 16109.346222A? i? 1/2 <0000000000199452>A? tick_sched_handle.isra.12+0x5e/0x70
> i? 1/2 16109.346235A? i? 1/2 <00000000001995aa>A? tick_sched_timer+0x6a/0x98
> i? 1/2 16109.346247A? i? 1/2 <000000000015c1ea>A? __run_hrtimer+0x8e/0x200
> i? 1/2 16109.346381A? i? 1/2 <000000000015d1b2>A? hrtimer_interrupt+0x212/0x2b0
> i? 1/2 16109.346385A? i? 1/2 <00000000001040f6>A? clock_comparator_work+0x4a/0x54
> i? 1/2 16109.346390A? i? 1/2 <000000000010d658>A? do_extint+0x158/0x15c
> i? 1/2 16109.346396A? i? 1/2 <000000000062aa24>A? ext_skip+0x38/0x3c
> i? 1/2 16109.346404A? i? 1/2 <00000000001153c8>A? smp_yield_cpu+0x44/0x48
> i? 1/2 16109.346412A? (i? 1/2 <000003d10051aec0>A? 0x3d10051aec0)
> i? 1/2 16109.346457A? i? 1/2 <000000000024206a>A? __page_check_address+0x16a/0x170
> i? 1/2 16109.346466A? i? 1/2 <00000000002423a2>A? page_referenced_one+0x3e/0xa0
> i? 1/2 16109.346501A? i? 1/2 <000000000024427c>A? page_referenced+0x32c/0x41c
> i? 1/2 16109.346510A? i? 1/2 <000000000021b1dc>A? shrink_page_list+0x380/0xb9c
> i? 1/2 16109.346521A? i? 1/2 <000000000021c0a6>A? shrink_inactive_list+0x1c6/0x56c
> i? 1/2 16109.346532A? i? 1/2 <000000000021c69e>A? shrink_lruvec+0x252/0x56c
> i? 1/2 16109.346542A? i? 1/2 <000000000021ca44>A? shrink_zone+0x8c/0x1bc
> i? 1/2 16109.346553A? i? 1/2 <000000000021d080>A? balance_pgdat+0x50c/0x658
> i? 1/2 16109.346564A? i? 1/2 <000000000021d318>A? kswapd+0x14c/0x470
> i? 1/2 16109.346576A? i? 1/2 <0000000000158292>A? kthread+0xda/0xe4
> i? 1/2 16109.346656A? i? 1/2 <000000000062a5de>A? kernel_thread_starter+0x6/0xc
> i? 1/2 16109.346682A? i? 1/2 <000000000062a5d8>A? kernel_thread_starter+0x0/0xc
> [-- MARK -- Fri Apr 12 06:15:00 2013]
> i? 1/2 16289.386061A? INFO: rcu_sched self-detected stall on CPU { 0} (t=42010 jiffies
> g=89766 c=89765 q=10627)
Did the system really crash or did you just see the rcu related warning(s)?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Zhouping Liu <zliu@redhat.com>
Cc: linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>,
caiqian <caiqian@redhat.com>, Caspar Zhang <czhang@redhat.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: [BUG][s390x] mm: system crashed
Date: Mon, 15 Apr 2013 07:56:27 +0200 [thread overview]
Message-ID: <20130415055627.GB4207@osiris> (raw)
In-Reply-To: <2068164110.268217.1365996520440.JavaMail.root@redhat.com>
On Sun, Apr 14, 2013 at 11:28:40PM -0400, Zhouping Liu wrote:
> Hi All,
>
> I hit the below crashed when doing memory related tests[1] on s390x:
>
> --------------- snip ---------------------
> � 15929.351639¨ � <000000000021c0a6>¨ shrink_inactive_list+0x1c6/0x56c
> � 15929.351647¨ � <000000000021c69e>¨ shrink_lruvec+0x252/0x56c
> � 15929.351654¨ � <000000000021ca44>¨ shrink_zone+0x8c/0x1bc
> � 15929.351662¨ � <000000000021d080>¨ balance_pgdat+0x50c/0x658
> � 15929.351671¨ � <000000000021d318>¨ kswapd+0x14c/0x470
> � 15929.351680¨ � <0000000000158292>¨ kthread+0xda/0xe4
> � 15929.351690¨ � <000000000062a5de>¨ kernel_thread_starter+0x6/0xc
> � 15929.351700¨ � <000000000062a5d8>¨ kernel_thread_starter+0x0/0xc
> � 16109.346061¨ INFO: rcu_sched self-detected stall on CPU { 0} (t=24006 jiffies
> g=89766 c=89765 q=10544)
> � 16109.346101¨ CPU: 0 Tainted: G D 3.9.0-rc6+ #1
> � 16109.346106¨ Process kswapd0 (pid: 28, task: 000000003b2a0000, ksp: 000000003b
> 2ab8c0)
> � 16109.346110¨ 000000000001bb60 000000000001bb70 0000000000000002 0000000
> 000000000
> 000000000001bc00 000000000001bb78 000000000001bb78 00000000001009ca
> 0000000000000000 0000000000002930 000000000000000a 000000000000000a
> 000000000001bbc0 000000000001bb60 0000000000000000 0000000000000000
> 000000000063bb18 00000000001009ca 000000000001bb60 000000000001bbb0
> � 16109.346170¨ Call Trace:
> � 16109.346179¨ (� <0000000000100920>¨ show_trace+0x128/0x12c)
> � 16109.346195¨ � <00000000001cd320>¨ rcu_check_callbacks+0x458/0xccc
> � 16109.346209¨ � <0000000000140f2e>¨ update_process_times+0x4a/0x74
> � 16109.346222¨ � <0000000000199452>¨ tick_sched_handle.isra.12+0x5e/0x70
> � 16109.346235¨ � <00000000001995aa>¨ tick_sched_timer+0x6a/0x98
> � 16109.346247¨ � <000000000015c1ea>¨ __run_hrtimer+0x8e/0x200
> � 16109.346381¨ � <000000000015d1b2>¨ hrtimer_interrupt+0x212/0x2b0
> � 16109.346385¨ � <00000000001040f6>¨ clock_comparator_work+0x4a/0x54
> � 16109.346390¨ � <000000000010d658>¨ do_extint+0x158/0x15c
> � 16109.346396¨ � <000000000062aa24>¨ ext_skip+0x38/0x3c
> � 16109.346404¨ � <00000000001153c8>¨ smp_yield_cpu+0x44/0x48
> � 16109.346412¨ (� <000003d10051aec0>¨ 0x3d10051aec0)
> � 16109.346457¨ � <000000000024206a>¨ __page_check_address+0x16a/0x170
> � 16109.346466¨ � <00000000002423a2>¨ page_referenced_one+0x3e/0xa0
> � 16109.346501¨ � <000000000024427c>¨ page_referenced+0x32c/0x41c
> � 16109.346510¨ � <000000000021b1dc>¨ shrink_page_list+0x380/0xb9c
> � 16109.346521¨ � <000000000021c0a6>¨ shrink_inactive_list+0x1c6/0x56c
> � 16109.346532¨ � <000000000021c69e>¨ shrink_lruvec+0x252/0x56c
> � 16109.346542¨ � <000000000021ca44>¨ shrink_zone+0x8c/0x1bc
> � 16109.346553¨ � <000000000021d080>¨ balance_pgdat+0x50c/0x658
> � 16109.346564¨ � <000000000021d318>¨ kswapd+0x14c/0x470
> � 16109.346576¨ � <0000000000158292>¨ kthread+0xda/0xe4
> � 16109.346656¨ � <000000000062a5de>¨ kernel_thread_starter+0x6/0xc
> � 16109.346682¨ � <000000000062a5d8>¨ kernel_thread_starter+0x0/0xc
> [-- MARK -- Fri Apr 12 06:15:00 2013]
> � 16289.386061¨ INFO: rcu_sched self-detected stall on CPU { 0} (t=42010 jiffies
> g=89766 c=89765 q=10627)
Did the system really crash or did you just see the rcu related warning(s)?
next prev parent reply other threads:[~2013-04-15 5:56 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <156480624.266924.1365995933797.JavaMail.root@redhat.com>
2013-04-15 3:28 ` [BUG][s390x] mm: system crashed Zhouping Liu
2013-04-15 3:28 ` Zhouping Liu
2013-04-15 5:56 ` Heiko Carstens [this message]
2013-04-15 5:56 ` Heiko Carstens
2013-04-15 6:16 ` Zhouping Liu
2013-04-15 6:16 ` Zhouping Liu
2013-04-16 7:50 ` Heiko Carstens
2013-04-16 7:50 ` Heiko Carstens
2013-04-16 7:56 ` Simon Jeons
2013-04-16 7:56 ` Simon Jeons
2013-04-16 8:03 ` Heiko Carstens
2013-04-16 8:03 ` Heiko Carstens
2013-04-16 8:26 ` Zhouping Liu
2013-04-16 8:26 ` Zhouping Liu
2013-04-18 6:27 ` Zhouping Liu
2013-04-18 6:27 ` Zhouping Liu
2013-04-18 7:13 ` Heiko Carstens
2013-04-18 7:13 ` Heiko Carstens
2013-04-24 10:42 ` [v3.9-rc8]: kernel BUG at mm/memcontrol.c:3994! (was: Re: [BUG][s390x] mm: system crashed) Heiko Carstens
2013-04-24 10:42 ` Heiko Carstens
2013-04-24 13:18 ` Michal Hocko
2013-04-24 13:18 ` Michal Hocko
2013-04-24 15:20 ` Johannes Weiner
2013-04-24 15:20 ` Johannes Weiner
2013-04-25 3:50 ` Hugh Dickins
2013-04-25 3:50 ` Hugh Dickins
2013-04-30 17:27 ` Johannes Weiner
2013-04-30 17:27 ` Johannes Weiner
2013-05-01 15:28 ` Hugh Dickins
2013-05-01 15:28 ` Hugh Dickins
2013-05-01 19:10 ` Johannes Weiner
2013-05-01 19:10 ` Johannes Weiner
2013-05-02 4:57 ` Hugh Dickins
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=20130415055627.GB4207@osiris \
--to=heiko.carstens@de.ibm.com \
--cc=caiqian@redhat.com \
--cc=czhang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=schwidefsky@de.ibm.com \
--cc=zliu@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.