------- Comment From [email protected] 2016-03-01 21:49 EDT-------
Hi ,

Inside grub file I  made xmon on, but it is not active even after
updating grub and reboot the guest.

linux   /boot/vmlinux-4.2.0-16-generic root=UUID=b7301650-03c4-44
983-a51b-ab0b061b50de ro  splash xmon=on quiet crashkernel=384M-:128M

root@abag3:~# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinux-4.2.0-16-generic 
root=UUID=b7301650-03c4-4983-a51b-ab0b061b50de ro splash quiet

I tried to cause kernel panic, which shows that xmon is disable.After 
performing kernel panic , the guest started rebooting itself after few mins.
Details are give below:

root@abag3:~# echo c > /proc/sysrq-trigger
[ 1079.297301] sysrq: SysRq : Trigger a crash
[ 1079.297556] Unable to handle kernel paging request for data at address 
0x00000000
[ 1079.297905] Faulting instruction address: 0xc00000000062f094
[ 1079.298482] Oops: Kernel access of bad area, sig: 11 [#1]
[ 1079.298719] SMP NR_CPUS=2048 NUMA pSeries
[ 1079.298993] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd 
grace fscache pseries_rng dm_multipath scsi_dh rtc_generic sunrpc autofs4 btrfs 
xor raid6_pq
[ 1079.300169] CPU: 25 PID: 2379 Comm: bash Not tainted 4.2.0-30-generic 
#36-Ubuntu
[ 1079.300589] task: c000000169825140 ti: c0000001698f0000 task.ti: 
c0000001698f0000
[ 1079.300957] NIP: c00000000062f094 LR: c000000000630148 CTR: c00000000062f060
[ 1079.301248] REGS: c0000001698f3990 TRAP: 0300   Not tainted  
(4.2.0-30-generic)
[ 1079.301537] MSR: 8000000000009033 <SF,EE,ME,IR,DR,RI,LE>  CR: 28242222  XER: 
20000000
[ 1079.302264] CFAR: c000000000009958 DAR: 0000000000000000 DSISR: 42000000 
SOFTE: 1
GPR00: c000000000630148 c0000001698f3c10 c00000000151af00 0000000000000063
GPR04: c00000017f848450 c00000017f859cd8 c00000017f180000 0000000000000165
GPR08: 0000000000000007 0000000000000001 0000000000000000 c00000017f1862a0
GPR12: c00000000062f060 c00000000fb4ed80 ffffffffffffffff 0000000022000000
GPR16: 0000000010170710 0000010010640278 00000000101406f0 00000000100c7100
GPR20: 0000000000000000 000000001017df98 0000000010140588 0000000000000000
GPR24: 0000000010153440 000000001017b848 c000000001464098 0000000000000004
GPR28: c000000001464458 0000000000000063 c000000001420cb4 0000000000000000
[ 1079.306339] NIP [c00000000062f094] sysrq_handle_crash+0x34/0x50
[ 1079.306598] LR [c000000000630148] __handle_sysrq+0xe8/0x270
[ 1079.306786] Call Trace:
[ 1079.306898] [c0000001698f3c10] [c000000000da0e50] 
_fw_tigon_tg3_bin_name+0x2cbb8/0x34c90 (unreliable)
[ 1079.307285] [c0000001698f3c30] [c000000000630148] __handle_sysrq+0xe8/0x270
[ 1079.307589] [c0000001698f3cd0] [c0000000006308e8] 
write_sysrq_trigger+0x78/0xa0
[ 1079.307926] [c0000001698f3d00] [c00000000035f710] proc_reg_write+0xb0/0x110
[ 1079.308219] [c0000001698f3d50] [c0000000002cb28c] __vfs_write+0x6c/0xe0
[ 1079.308514] [c0000001698f3d90] [c0000000002cbfc0] vfs_write+0xc0/0x230
[ 1079.308808] [c0000001698f3de0] [c0000000002ccffc] SyS_write+0x6c/0x110
[ 1079.309100] [c0000001698f3e30] [c000000000009204] system_call+0x38/0xb4
[ 1079.309383] Instruction dump:
[ 1079.309541] 3842bea0 7c0802a6 f8010010 f821ffe1 60000000 60000000 3d220019 
3949dfe4
[ 1079.310085] 39200001 912a0000 7c0004ac 39400000 <992a0000> 38210020 e8010010 
7c0803a6
[ 1079.310635] ---[ end trace 9d06f2b7e9e9d2b3 ]---
[ 1079.317763]
[ 1081.320510] Kernel panic - not syncing: Fatal exception
[ 1081.331107] ---[ end Kernel panic - not syncing: Fatal exception

The latest kernel build :
[root@abakvm ~]# uname -a
Linux abakvm 3.18.24-376.el7_1.pkvm3_1_0.5400.1.ppc64le #1 SMP Tue Feb 16 
11:42:11 CST 2016 ppc64le ppc64le ppc64le GNU/Linux

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1543480

Title:
  ISST-KVM:Ubuntu1510:abakvm: abag3 guest hung while running stress
  test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1543480/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to