Hi Aaron, Looks like you have a core file there, raise a TAC case and they’ll be able to determine the root cause for you.
Also see if there is anything readable in /dev/mapper/jvg_P-jlvmrootrw/var/crash/override_reboot_reason that may point you to the root cause. HTH, Graham On Thu, 5 Apr 2018 at 01:13, Aaron Gould <[email protected]> wrote: > Still in the process of turning up this new 5-node mx960 100 gig ring, and > I > went to the backup re console and went to login and saw this happen. > > > > Any idea why this happened and how do I tshoot cause ? > > > > > > > > FreeBSD/amd64 (mx960) (ttyu0) > > > > login: root > > Password:SysRq : Trigger a crash > > dmar: DRHD: handling fault status reg 2 > > dmar: DMAR:[DMA Write] Request device [02:10.1] fault addr 151d9000 > > DMAR:[fault reason 01] Present bit in root entry is clear > > dmar: DRHD: handling fault status reg 102 > > dmar: DMAR:[DMA Write] Request device [02:10.1] fault addr 1540c000 > > DMAR:[fault reason 01] Present bit in root entry is clear > > dmar: DRHD: handling fault status reg 202 > > dmar: DMAR:[DMA Write] Request device [02:10.1] fault addr 152fc000 > > DMAR:[fault reason 01] Present bit in root entry is clear > > dmar: DRHD: handling fault status reg 302 > > dmar: DMAR:[DMA Write] Request device [06:0a.0] fault addr 1ed10d000 > > DMAR:[fault reason 01] Present bit in root entry is clear > > dmar: DRHD: handling fault status reg 402 > > dmar: DMAR:[DMA Read] Request device [06:0a.0] fault addr ad4a000 > > DMAR:[fault reason 01] Present bit in root entry is clear > > dmar: INTR-REMAP: Request device [[05:00.1] fault index 40 > > INTR-REMAP:[fault reason 34] Present field in the IRTE entry is clear > > dmar: DRHD: handling fault status reg 602 > > dmar: DMAR:[DMA Read] Request device [06:0a.0] fault addr ad4a000 > > DMAR:[fault reason 01] Present bit in root entry is clear > > dmar: DRHD: handling fault status reg 702 > > dmar: DMAR:[DMA Read] Request device [06:0a.0] fault addr ad4a000 > > DMAR:[fault reason 01] Present bit in root entry is clear > > 4 logical volume(s) in volume group "jvg_S" now active > > 4 logical volume(s) in volume group "jvg_P" now active > > Override SW Exception reboot reason saved to > /dev/mapper/jvg_P-jlvmrootrw/var/crash/override_reboot_reason > > Compressed level 31 vmhost kernel core will be dumped to jvg_P-jlvmrootrw. > > Please use crash utility to analyze the core > > Copying data : [ 13 %] > > . > > . > > . > > Copying data : [100 %] > > > > The dumpfile is saved to vmcore-0-compressed-201804041305. > > > > makedumpfile Completed. > > > > > > (many more boot messages seen) > > > > > > -Aaron > > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > -- -sent from my iPhone; please excuse spelling, grammar and brevity- _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
