Re: AWS t2.medium GENERIC.MP with 010-intelfpu has floating point exceptions with commands like dhclient
On Thu, Jul 26, 2018 at 01:19:39PM +0200, Mike Belopuhov wrote: > Hi, > > Have you had a chance to test a current snapshot? > > Cheers, > Mike Thanks, Mike. I did test a current snapshot. It booted with no problems! Any chance this will be a 6.3 Errata? dmesg below. Note, it seems the CPU is different with this t2.medium (Intel(R) Xeon(R) CPU E5-2676 v3 @ 2.40GHz) vs. (Intel(R) Xeon(R) CPU E5-2686 v4 @ 2.30GHz) in my previous report. So I spun up another t2.medium with (Intel(R) Xeon(R) CPU E5-2676 v3 @ 2.40GHz) running 6.3, ran syspatch, and watched it fall all over itself again. So it seems that whatever's in -current fixed the problem. -ME OpenBSD 6.3-current (GENERIC.MP) #144: Thu Jul 26 08:20:44 MDT 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4278190080 (4080MB) avail mem = 4139360256 (3947MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb01f (12 entries) bios0: vendor Xen version "4.2.amazon" date 08/24/2006 bios0: Xen HVM domU acpi0 at bios0: rev 2 acpi0: sleep states S3 S4 S5 acpi0: tables DSDT FACP APIC HPET WAET SSDT SSDT acpi0: wakeup devices acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat ioapic0 at mainbus0: apid 1 pa 0xfec0, version 11, 48 pins , remapped to apid 1 cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Xeon(R) CPU E5-2676 v3 @ 2.40GHz, 2394.85 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,RDTSCP,LONG,LAHF,ABM,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,XSAVEOPT,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 100MHz cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Xeon(R) CPU E5-2676 v3 @ 2.40GHz, 2394.88 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,RDTSCP,LONG,LAHF,ABM,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,XSAVEOPT,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 0, package 1 acpihpet0 at acpi0: 6250 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpicpu0 at acpi0: C1(@1 halt!) acpicpu1 at acpi0: C1(@1 halt!) acpicmos0 at acpi0 "ACPI0007" at acpi0 not configured "ACPI0007" at acpi0 not configured pvbus0 at mainbus0: Xen 4.2 xen0 at pvbus0: features 0x705, 32 grant table frames, event channel 4 xbf0 at xen0 backend 0 channel 6: disk scsibus1 at xbf0: 2 targets sd0 at scsibus1 targ 0 lun 0: SCSI3 0/direct fixed sd0: 8192MB, 512 bytes/sector, 16777216 sectors xnf0 at xen0 backend 0 channel 7: address 02:de:66:59:18:8a "console" at xen0: device/console/0 not configured pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02 pcib0 at pci0 dev 1 function 0 "Intel 82371SB ISA" rev 0x00 pciide0 at pci0 dev 1 function 1 "Intel 82371SB IDE" rev 0x00: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility pciide0: channel 0 disabled (no drives) pciide0: channel 1 disabled (no drives) piixpm0 at pci0 dev 1 function 3 "Intel 82371AB Power" rev 0x01: SMBus disabled vga1 at pci0 dev 2 function 0 "Cirrus Logic CL-GD5446" rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) xspd0 at pci0 dev 3 function 0 "XenSource Platform Device" rev 0x01 isa0 at pcib0 isadma0 at isa0 fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo com0: console pckbc0 at isa0 port 0x60/5 irq 1 irq 12 pckbd0 at pckbc0 (kbd slot) wskbd0 at pckbd0: console keyboard, using wsdisplay0 pms0 at pckbc0 (aux slot) wsmouse0 at pms0 mux 0 pcppi0 at isa0 port 0x61 spkr0 at pcppi0 vscsi0 at root scsibus2 at vscsi0: 256 targets softraid0 at root scsibus3 at softraid0: 256 targets root on sd0a (408f5ba7d26a4b06.a) swap on sd0b dump on sd0b fd0 at fdc0 drive 0: density unknown fd1 at fdc0 drive 1: density unknown
Re: AWS t2.medium GENERIC.MP with 010-intelfpu has floating point exceptions with commands like dhclient
On 17 July 2018 at 18:21, Mike Erdely wrote: > > > In reply to a private reply I received, I sent the following update: > > > Does your single-CPU micro instance also provide the same Xen and CPU versions? i.e. > > Diff below. First machine: t2.small (1 cpu). Second machine: t2.medium (2 cpu) > t2.small: > - GENERIC that ships with 6.3: No problem > - GENERIC with 6.3 010_intelfpu: No problem > - GENERIC.MP that ships with 6.3: No problem > - GENERIC.MP with 6.3 010_intelfpu: No problem > t2.medium: > - GENERIC that ships with 6.3: No problem > - GENERIC with 6.3 010_intelfpu: No problem > - GENERIC.MP that ships with 6.3: No problem > - GENERIC.MP with 6.3 010_intelfpu: Boots but has floating point errors making it unusable as described > > > to me this looks quite fishy since the hardware looks to be supported well by OBSD so I would guess on bad iteraction between Xen and OBSD here... Hi, Have you had a chance to test a current snapshot? Cheers, Mike
Re: AWS t2.medium GENERIC.MP with 010-intelfpu has floating point exceptions with commands like dhclient
In reply to a private reply I received, I sent the following update: > Does your single-CPU micro instance also provide the same Xen and CPU > versions? i.e. Diff below. First machine: t2.small (1 cpu). Second machine: t2.medium (2 cpu) t2.small: - GENERIC that ships with 6.3: No problem - GENERIC with 6.3 010_intelfpu: No problem - GENERIC.MP that ships with 6.3: No problem - GENERIC.MP with 6.3 010_intelfpu: No problem t2.medium: - GENERIC that ships with 6.3: No problem - GENERIC with 6.3 010_intelfpu: No problem - GENERIC.MP that ships with 6.3: No problem - GENERIC.MP with 6.3 010_intelfpu: Boots but has floating point errors making it unusable as described > to me this looks quite fishy since the hardware looks to be supported well by > OBSD so I would guess on bad iteraction between Xen and OBSD here... --- dmesg.mwe-1cpu.GENERIC.MP.011 Tue Jul 17 12:20:07 2018 +++ dmesg.mwe-2cpu.GENERIC.MP.011 Tue Jul 17 12:20:07 2018 @@ -1,11 +1,11 @@ OpenBSD 6.3 (GENERIC.MP) #4: Sun Jun 17 11:22:20 CEST 2018 r...@syspatch-63-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP -real mem = 2130706432 (2032MB) -avail mem = 2059116544 (1963MB) +real mem = 4278190080 (4080MB) +avail mem = 4141465600 (3949MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root -bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb01f (11 entries) +bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb01f (12 entries) bios0: vendor Xen version "4.2.amazon" date 08/24/2006 bios0: Xen HVM domU acpi0 at bios0: rev 2 @@ -17,23 +17,30 @@ ioapic0 at mainbus0: apid 1 pa 0xfec0, version 11, 48 pins , remapped to apid 1 cpu0 at mainbus0: apid 0 (boot processor) -cpu0: Intel(R) Xeon(R) CPU E5-2676 v3 @ 2.40GHz, 2400.35 MHz +cpu0: Intel(R) Xeon(R) CPU E5-2686 v4 @ 2.30GHz, 2300.34 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,RDTSCP,LONG,LAHF,ABM,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,XSAVEOPT,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 100MHz +cpu1 at mainbus0: apid 2 (application processor) +cpu1: Intel(R) Xeon(R) CPU E5-2686 v4 @ 2.30GHz, 2300.28 MHz +cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,RDTSCP,LONG,LAHF,ABM,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,XSAVEOPT,MELTDOWN +cpu1: 256KB 64b/line 8-way L2 cache +cpu1: smt 0, core 0, package 1 acpihpet0 at acpi0: 6250 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpicpu0 at acpi0: C1(@1 halt!) +acpicpu1 at acpi0: C1(@1 halt!) "ACPI0007" at acpi0 not configured +"ACPI0007" at acpi0 not configured pvbus0 at mainbus0: Xen 4.2 -xen0 at pvbus0: features 0x705, 32 grant table frames, event channel 3 -xbf0 at xen0 backend 0 channel 5: disk +xen0 at pvbus0: features 0x705, 360 grant table frames, event channel 4 +xbf0 at xen0 backend 0 channel 6: disk scsibus1 at xbf0: 2 targets sd0 at scsibus1 targ 0 lun 0: SCSI3 0/direct fixed sd0: 8192MB, 512 bytes/sector, 16777216 sectors -xnf0 at xen0 backend 0 channel 6: address 02:38:a9:ed:ca:12 +xnf0 at xen0 backend 0 channel 7: address 02:30:a6:f3:e7:c2 "console" at xen0: device/console/0 not configured pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02 @@ -61,6 +68,6 @@ scsibus2 at vscsi0: 256 targets softraid0 at root scsibus3 at softraid0: 256 targets -root on sd0a (c7e9b171ef2a41ab.a) swap on sd0b dump on sd0b +root on sd0a (e0657587b973b5b4.a) swap on sd0b dump on sd0b fd0 at fdc0 drive 0: density unknown fd1 at fdc0 drive 1: density unknown
