Re: [BUG][s390x] mm: system crashed

From: Zhouping Liu
Date: Mon Apr 15 2013 - 02:19:17 EST

On 04/15/2013 01:56 PM, Heiko Carstens wrote:
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)?

I just check it again, actually at first the system didn't really crash, but the system is very slow in response.
and the reproducer process can't be killed, after I did some common actions such as 'ls' 'vim' etc, the system
seemed to be really crashed, no any response.

also in the previous testing, I can remember that the system would be no any response for a long time, just only
repeatedly print out the such above 'Call Trace' into console.

Thanks,
Zhouping
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/