Re: frequent softlockups with 3.10rc6.

[Dave Jones]

On Sun, Jun 23, 2013 at 06:04:52PM +0200, Oleg Nesterov wrote:
 
 > Could you please do the following:
 > 
 > 	1. # cd /sys/kernel/debug/tracing
 > 	   # echo 0 >> options/function-trace
 > 	   # echo preemptirqsoff >> current_tracer

dammit.

WARNING: at include/linux/list.h:385 rb_head_page_deactivate.isra.39+0x61/0x80()
 check_list_nodes corruption. next->prev should be prev (ffff88023b8a1a08), but was 00ffff88023b8a1a. (next=ffff880243288001).
 Modules linked in: coretemp hwmon snd_hda_codec_realtek kvm_intel kvm snd_hda_codec_hdmi crc32c_intel ghash_clmulni_intel microcode snd_hda_intel snd_hda_codec pcspkr snd_hwdep snd_seq snd_seq_device snd_pcm e1000e snd_page_alloc ptp snd_timer snd pps_core soundcore xfs libcrc32c
 CPU: 1 PID: 474 Comm: bash Not tainted 3.10.0-rc7+ #33
  ffffffff81a1762e ffff88023c659ce0 ffffffff816e467d ffff88023c659d18
  ffffffff8104a0c1 ffff88023b8a1a08 ffff8802434b9040 ffff8802434b8fe8
  0000000000000282 ffff88023109a620 ffff88023c659d78 ffffffff8104a12c
 Call Trace:
  [<ffffffff816e467d>] dump_stack+0x19/0x1b
  [<ffffffff8104a0c1>] warn_slowpath_common+0x61/0x80
  [<ffffffff8104a12c>] warn_slowpath_fmt+0x4c/0x50
  [<ffffffff81112c61>] rb_head_page_deactivate.isra.39+0x61/0x80
  [<ffffffff81113353>] ring_buffer_reset_cpu+0xa3/0x250
  [<ffffffff81111f4a>] ? ring_buffer_time_stamp+0x1a/0x30
  [<ffffffff81119d1a>] tracing_reset_online_cpus+0x5a/0xb0
  [<ffffffff8111ee13>] tracing_set_tracer+0x223/0x310
  [<ffffffff8111f16d>] tracing_set_trace_write+0xad/0xf0
  [<ffffffff811ad6bb>] ? vfs_write+0x1bb/0x1f0
  [<ffffffff812b9ca1>] ? security_file_permission+0x21/0xa0
  [<ffffffff811ad5c0>] vfs_write+0xc0/0x1f0
  [<ffffffff811cc487>] ? fget_light+0x387/0x4f0
  [<ffffffff811adfcc>] SyS_write+0x4c/0xa0
  [<ffffffff816f5d94>] tracesys+0xdd/0xe2
 ---[ end trace d4694abee6ec3f10 ]---


hopefully despite that it'll actually function as intended.

	Dave

--
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/