Re: [Crash-utility] Fw: [CentOS] Can't see register value in crash vmcore

Sent from my Verizon, Samsung Galaxy smartphone -------- Original message --------From: wuzhouhui <wuzhouhui14(a)mails.ucas.ac.cn&gt; Date: 12/29/17 2:34 AM (GMT-05:00) To: crash-utility(a)redhat.com Subject: [Crash-utility] Fw: [CentOS] Can't see register value in crash vmcore -----原始邮件----- 发件人: wuzhouhui <wuzhouhui14(a)mails.ucas.ac.cn&gt; 发送时间: 2017-12-28 10:10:57 (星期四) 收件人: centos(a)centos.org 抄送: 主题: [CentOS] Can't see register value in crash vmcore OS: CentOS 6.5 Crash: crash-7.1.0-6.el6.x86_64 Kdump: kexec-tools-2.0.0-273.el6.x86_64 GDB: gdb-7.2-60.el6_4.1.x86_64 /etc/kdump.conf: core_collector makedumpfile -c --message-level 1 -d 31 Kernel crashed by panic("string"), but I can't see any register in vmcore: crash> bt PID: 53331  TASK: ffff880c523ed540  CPU: 2   COMMAND: "bw_sd-ar-7-0_2" #0 [ffff880c4f12f978] machine_kexec at ffffffff81038ed9 #1 [ffff880c4f12f9d8] crash_kexec at ffffffff810c5a82 #2 [ffff880c4f12faa8] panic at ffffffff815113b2 #3 [ffff880c4f12fb28] sd_submit_bio at ffffffffa0747a02 [sd] #4 [ffff880c4f12fb68] submit_clone_bio at ffffffffa0747d2b [sd] #5 [ffff880c4f12fb78] split_and_submit_bio_for_cbd at ffffffffa0747ec9 [sd] #6 [ffff880c4f12fbf8] sd_make_request at ffffffffa074c812 [sd] #7 [ffff880c4f12fc68] sdu_make_request at ffffffffa074ca41 [sd] #8 [ffff880c4f12fc88] generic_make_request at ffffffff81264d70 #9 [ffff880c4f12fd68] submit_bio at ffffffff81265140 #10 [ffff880c4f12fdb8] submit_area_bio at ffffffffa04ade20 [scst_vdisk] #11 [ffff880c4f12fde8] bwraid_submit_bio at ffffffffa04b03b2 [scst_vdisk] #12 [ffff880c4f12fe38] worker_thread at ffffffff81094c50 #13 [ffff880c4f12fee8] kthread at ffffffff8109ae26 #14 [ffff880c4f12ff48] kernel_thread at ffffffff8100c20a crash> Is it normal? Thanks. ___________ Yes.  A register dump will be displayed if an exception occurred.  In the case above, sd_submit_bio() made a direct call to panic(), and so there is no exception register dump.  You can use "bt -f",  "bt -F" or "bt -FF" to see the stack contents, which may help. Dave ____________________________________ CentOS mailing list CentOS(a)centos.org https://lists.centos.org/mailman/listinfo/centos -- Crash-utility mailing list Crash-utility(a)redhat.com https://www.redhat.com/mailman/listinfo/crash-utility