Asset ID: |
1-72-1922054.1 |
Update Date: | 2014-09-01 |
Keywords: | |
Solution Type
Problem Resolution Sure
Solution
1922054.1
:
Solaris 11.1 M10-4S or T4-1 guest domain can panic in numaio_constraint_add_core_cpu
Related Items |
- SPARC T4-1
- Fujitsu M10-4S
- Solaris Operating System
|
Related Categories |
- PLA-Support>Sun Systems>SAND>Kernel>SN-SND: Sun Kernel System Crash
|
In this Document
Created from <SR 3-8698038858>
Applies to:
Solaris SPARC Operating System - Version 11.1 to 11.1 [Release 11.0]
SPARC T4-1 - Version All Versions to All Versions [Release All Releases]
Fujitsu M10-4S - Version All Versions to All Versions [Release All Releases]
Oracle Solaris on SPARC (64-bit)
Symptoms
Solaris 11.1 M10-4S or T4-1 guest domain may panic with the following messages while or after control domain run ldm set-vcpu
panic[cpu31]/thread=2a103e99c60:
BAD TRAP: type=31 rp=2a103e98860 addr=84 mmu_fsr=0 occurred in module "genunix"due to a NULL pointer dereference
sched:
trap type = 0x31
addr=0x84
pid=0, pc=0x11a360c, sp=0x2a103e98101, tstate=0x4480001601, context=0x0
g1-g7: 1, 1, 0, 0, 0, 0, 2a103e99c60
000002a103e985b0 unix:die+7c (31, 2a103e98860, 84, 0, 0, 10c4000)
%l0-3: 0000000000000031 0000000001000000 0000000000002000 00000000010c4370
%l4-7: 00000000010c4000 0000000000000000 0000000000000005 000002a103e98670
000002a103e98690 unix:trap+a90 (2a103e98860, e005e084, 1fff, 0, 1c00, 0)
%l0-3: 0000000000000000 0000000000000031 00000000c1680000 0000000000000000
%l4-7: 0000000000000001 0000000000000005 0000000000000000 0000000000000001
000002a103e987b0 unix:ktl0+64 (0, 1, 2, 10, c400d5f1b498, c400d5f1b498)
%l0-3: 00000400402fe300 00000000000000f8 0000004480001601 000000000101e5e0
%l4-7: 00000000010090f8 0000000000000001 0000000000000000 000002a103e98860
000002a103e98900 genunix:numaio_constraint_add_core_cpu+74 (c400d5f1b2c0, c400d5f1b468, 40048caa200, 0, c400d5f1b488, c02)
%l0-3: 0000000000000001 0000000000000001 0000000000000000 0000c400d5f1b3d8
%l4-7: 0000000000000090 0000000000000012 0000000000000002 0000000000000000
000002a103e989b0 genunix:numaio_core_cpu_setup+104 (c400d5f1b2c0, 74, 1d, c02, 40048caa200, c402195ba000)
%l0-3: 000000000000001d 000000000000001c 0000c4019f0d9980 000000000000000e
%l4-7: 000000000000000d 000000000000000d 0000000000000034 000000000000000e
000002a103e98a60 genunix:numaio_populate_constraint+24 (c400d5f1b2c0, c402195ba000, 1d, 1c, 2a103e99c64, c400d5f1b3d8)
%l0-3: 0000c402195ba000 0000000000000021 000000000000000a 000000001069d258
%l4-7: 000000001069d258 000000001038f9c0 0000000000000000 00000000104841f0
000002a103e98b10 genunix:numaio_constraint_set_cpu_part+bc (c400d5f1b2c0, c400c785a328, 10484000, c402195ba000, c400c5ff8540, 800)
%l0-3: 000000000000001d 0000000010484000 0000000010660568 0000000000000002
%l4-7: 0000000010660400 000000000000001d 0000000000000001 0000c400c70eec28
000002a103e98bc0 genunix:numaio_constraint_set_pool_by_name+b4 (c400d5f1b2c0,c400d5f70638, 10660568, 104841f0, c400c785a328, 10660400)
%l0-3: 0000000000000084 000004005b7b0380 000004005b7b0380 0000000000000081
%l4-7: 0000c400d5f1b3f8 0000000000000016 000004001d123630 00000000106ac400
000002a103e98c70 mac:mac_cpu_apply_constraint+9c (c400d5f07700, c400d5f70638,7bfce588, c400dbfe1118, 1, 400)
%l0-3: 0000c400d5f1b2c0 00000300007921e0 0000030000792208 0000c400dbfe1118
%l4-7: 0000000000005400 0000c400dbfe1118 0000000000000000 0000c400d5f6e088
000002a103e98d20 mac:mac_cpu_setup+50 (c400d5f07700, 2a103e99c60,c400d5f6e088,1, 2105, 1)
%l0-3: 0000000000000001 000000001069d800 0000c400c785a328 0000c400d5f70638
%l4-7: 00000000000025b0 0000000000002400 0000000000000003 0000000000000003
000002a103e98dd0 mac:mac_cpu_pool_setup+5c (c400d5f07700, c400d5f70a70, 0,c400d5f6e088, c400d5f6e078, 29f8)
%l0-3: 0000000000000000 0000c400d5f07700 0000000000000000 000000000000000c
%l4-7: 0000000000000003 0000000000000000 0000000000000001 000000000133fc00
000002a103e98e90 mac:mac_pool_link_update+194 (c401437daec0, c401122fefc0,5400, 7bfcd610, 25b0, 29e8)
%l0-3: 0000c400d5f52500 0000c400d5f07700 00000000000029f8 0000c401437dd470
%l4-7: 0000000000005544 0000c400d5f70a70 0000000000000000 0000000000000001
000002a103e98f40 mac:mac_pool_update+50 (c401122fefc0, 0, c4027acee700, 1,2c, 70523b80)
%l0-3: 0000000000000020 0000000000000021 000000000000000a 000000000000000c
%l4-7: 0000000000000003 00000000011a61d0 0000c4027acee700 0000000000000000
000002a103e98ff0 mac:mac_pool_event_cb+98 (2, 1, 0, 30000ee0240, 107272c0,c401122fefc0)
%l0-3: 0000000000000031 000004005c58ce10 000004005c58ce00 0000000000000010
%l4-7: 0000000000000002 00000000feedf800 0000000000003006 0000000000003000
000002a103e990b0 genunix:pool_event_notify+38 (c4014f201500, 2, 1, 7bfaea10,10660a38, 107272b0)
%l0-3: 0000000000000bbb 000004005c3100c0 000004005c310000 00000000000000c0
%l4-7: 0000000000000018 0000000000000003 0000000000003006 0000c400c5e8e540
000002a103e99160 genunix:taskq_thread+3a8 (160213894fe1f6, c400c5e8e520,160213894fe6f6, c400c5e8e552, c400c5e8e554, c40111bcf448)
%l0-3: 0000000000080000 0000000000010000 0000c400c5e8e550 0000000000000001
%l4-7: 0000c400c5e8e540 0000c400c5e8e590 0000c400c5e8e548 00000000fffeffff
Changes
The problem can happen during or after running ldm set-vcpu in control domain.
Cause
Due to bug BUG 15756136, this issue can happen on M10-4S and T4-1 servers running Solaris 11.1
This is due to mismatch in cpu_coreid of cpu_physid_t versus cpu_core in machcpu.
The output of these 2 list should match each other.
> ::walk cpu |::print -at cpu_t cpu_m|::print struct machcpu cpu_core
cpu_core = 0xc0b
cpu_core = 0xc0b
cpu_core = 0xc0e
cpu_core = 0xc0e
cpu_core = 0xc11
cpu_core = 0xc11
cpu_core = 0xc14
cpu_core = 0xc14
cpu_core = 0xc17
cpu_core = 0xc17
cpu_core = 0xc1a
cpu_core = 0xc1a
cpu_core = 0xc1d
cpu_core = 0xc1d
cpu_core = 0xc20
cpu_core = 0xc20
cpu_core = 0xc23
cpu_core = 0xc23
cpu_core = 0xc26
cpu_core = 0xc26
cpu_core = 0xc29
cpu_core = 0xc29
cpu_core = 0xc2c
cpu_core = 0xc2c
cpu_core = 0xc2f
cpu_core = 0xc2f
cpu_core = 0xc32
cpu_core = 0xc32
cpu_core = 0xc35
cpu_core = 0xc35
cpu_core = 0xc02
cpu_core = 0xc02
cpu_core = 0xc05
cpu_core = 0xc05
cpu_core = 0xc08
cpu_core = 0xc08
cpu_core = 0xc38
cpu_core = 0xc38
> ::walk cpu |::print cpu_t cpu_physid |::print cpu_physid_t cpu_coreid
cpu_coreid = 0xc02
cpu_coreid = 0xc02
cpu_coreid = 0xc05
cpu_coreid = 0xc05
cpu_coreid = 0xc08
cpu_coreid = 0xc08
cpu_coreid = 0xc0b
cpu_coreid = 0xc0b
cpu_coreid = 0xc0e
cpu_coreid = 0xc0e
cpu_coreid = 0xc11
cpu_coreid = 0xc11
cpu_coreid = 0xc14
cpu_coreid = 0xc14
cpu_coreid = 0xc17
cpu_coreid = 0xc17
cpu_coreid = 0xc1a
cpu_coreid = 0xc1a
cpu_coreid = 0xc1d
cpu_coreid = 0xc1d
cpu_coreid = 0xc20
cpu_coreid = 0xc20
cpu_coreid = 0xc23
cpu_coreid = 0xc23
cpu_coreid = 0xc26
cpu_coreid = 0xc26
cpu_coreid = 0xc29
cpu_coreid = 0xc29
cpu_coreid = 0xc2c
cpu_coreid = 0xc2c
cpu_coreid = 0xc02
cpu_coreid = 0xc02
cpu_coreid = 0xc05
cpu_coreid = 0xc05
cpu_coreid = 0xc08
cpu_coreid = 0xc08
cpu_coreid = 0xc38
cpu_coreid = 0xc38
Solution
Please upgrade to Solaris 11.2 or later
References
<BUG:18918557> - BACKPORT 18918469 TO 11.3 - CPU_COREID DIFFERS FROM CPU_CORE CAUSING PANIC IN NU
<BUG:18415262> - S11U1 M10-4S PANIC IN NUMAIO_CONSTRAINT_ADD_CORE_CPU
<BUG:15756136> - SUNBT7113485 WRONG VALUE STORED IN CPU_COREID
Attachments
This solution has no attachment