10.2 Release seems to be crashing on Azure with "Standard DS" VM sizes

Scott Otis scott.otis at tandemcal.com
Sat Feb 6 05:16:33 UTC 2016


3.5 GB of RAM.

Here is the list from dmseg if that helps:

Copyright (c) 1992-2015 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
        The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 10.2-RELEASE #0 r286666: Wed Aug 12 15:26:37 UTC 2015
    root at releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
CPU: Intel(R) Xeon(R) CPU E5-2660 0 @ 2.20GHz (1109.74-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x206d7  Family=0x6  Model=0x2d  Stepping=7
  AMD Features=0x20100800<SYSCALL,NX,LM>
  AMD Features2=0x1<LAHF>
  XSAVE Features=0x1<XSAVEOPT>
Hypervisor: Origin = "Microsoft Hv"
real memory  = 3758096384 (3584 MB)
avail memory = 3515142144 (3352 MB)
Event timer "LAPIC" quality 400
ioapic0: Changing APIC ID to 0
ioapic0 <Version 1.1> irqs 0-23 on motherboard
random: <Software, Yarrow> initialized
kbd1 at kbdmux0
vmbus0: <Vmbus Devices> on motherboard
acpi0: <VRTUAL MICROSFT> on motherboard
acpi0: Power Button (fixed)
cpu0: <ACPI CPU> on acpi0
attimer0: <AT timer> port 0x40-0x43 irq 0 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
atrtc0: <AT realtime clock> port 0x70-0x71 irq 8 on acpi0
Event timer "RTC" frequency 32768 Hz quality 0
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <32-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
isab0: <PCI-ISA bridge> at device 7.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel PIIX4 UDMA33 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 7.1 on pci0
ata0: <Hyper-V ATA storage disengage driver> at channel 0 on atapci0
ata1: <ATA channel> at channel 1 on atapci0
pci0: <bridge> at device 7.3 (no driver attached)
vgapci0: <VGA-compatible display> mem 0xf8000000-0xfbffffff irq 11 at device 8.0 on pci0
vgapci0: Boot video device
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: model IntelliMouse Explorer, device ID 4
uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
uart0: console (115200,n,8,1)
uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
fdc0: <floppy drive controller (FDE)> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
orm0: <ISA Option ROM> at iomem 0xc0000-0xcbfff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
ppc0: cannot reserve I/O port range
Timecounters tick every 1.000 msec
random: unblocking device.
Timecounter "TSC" frequency 1109744806 Hz quality 800
Timecounter "Hyper-V" frequency 10000000 Hz quality 10000000
storvsc0 on vmbus0
storvsc1 on vmbus0
hyperv-utils0 on vmbus0
hyperv-utils0: Hyper-V Service attaching: Hyper-V Heartbeat Service

hyperv-utils1 on vmbus0
hyperv-utils1: Hyper-V Service attaching: Hyper-V KVP Service

hyperv-utils2 on vmbus0
hyperv-utils2: Hyper-V Service attaching: Hyper-V Shutdown Service

hyperv-utils3 on vmbus0
hyperv-utils3: Hyper-V Service attaching: Hyper-V Time Synch Service

da0 at blkvsc0 bus 0 scbus1 target 0 lun 0
hn0: <Synthetic Network Interface> on vmbus0
da0: <Msft Virtual Disk 1.0> Fixed Direct Access SPC-2 SCSI device
da0: 300.000MB/s transfers
da0: Command Queueing enabled
da0: 21505MB (44042240 512 byte sectors: 255H 63S/T 2741C)
hn0: unknown status 1073872902 received
hn0: unknown status 1073872902 received
hn0: hv send offload request succeeded
hn0: Using defaults for TSO: 65518/35/2048
hn0: Ethernet address: 00:0d:3a:31:7e:9e
storvsc2 on vmbus0
da1 at blkvsc1 bus 0 scbus2 target 1 lun 0
da1: <Msft Virtual Disk 1.0> Fixed Direct Access SPC-2 SCSI device
storvsc3 on vmbus0
da1: 300.000MB/s transfers
da1: Command Queueing enabled
da1: 7168MB (14680064 512 byte sectors: 255H 63S/T 913C)
Trying to mount root from ufs:/dev/gpt/rootfs [rw]...
WARNING: / was not properly dismounted
calcru: runtime went backwards from 3737 usec to 1889 usec for pid 272 (dhclient)
calcru: runtime went backwards from 97244 usec to 49171 usec for pid 272 (dhclient)
calcru: runtime went backwards from 47052 usec to 44339 usec for pid 16 (sh)
calcru: runtime went backwards from 595 usec to 410 usec for pid 5 (pagedaemon)
calcru: runtime went backwards from 18 usec to 9 usec for pid 4 (sctp_iterator)
calcru: runtime went backwards from 8932 usec to 4569 usec for pid 3 (fdc0)
calcru: runtime went backwards from 702786 usec to 368788 usec for pid 2 (cam)
calcru: runtime went backwards from 7662 usec to 6957 usec for pid 14 (rand_harvestq)
calcru: runtime went backwards from 8949 usec to 4525 usec for pid 13 (geom)
calcru: runtime went backwards from 38401460 usec to 32753458 usec for pid 11 (idle)
calcru: runtime went backwards from 189139 usec to 95666 usec for pid 1 (init)
calcru: runtime went backwards from 1078465 usec to 545696 usec for pid 0 (kernel)


-----Original Message-----
From: Adrian Chadd [mailto:adrian.chadd at gmail.com] 
Sent: Friday, February 5, 2016 4:46 PM
To: Scott Otis <scott.otis at tandemcal.com>
Cc: freebsd-stable at freebsd.org
Subject: Re: 10.2 Release seems to be crashing on Azure with "Standard DS" VM sizes


how much RAM does the VM have?

Yes, you need to either run dumpon or reboot once you update /etc/rc.conf .


On 5 February 2016 at 13:55, Scott Otis <scott.otis at tandemcal.com> wrote:
> Been trying to get a FreeBSD VM server running on Azure on a "Standard DS" size VM (so I have access to SSD storage for PostgreSQL).  The "Standard DS" series of VMs also have faster/newer CPUs than the original "Standard A" series of VMs.  I am using the image of FreeBSD from here: https://vmdepot.msopentech.com/Vhd/Show?vhdId=56718&version=61117 .  After setting up the VM it started rebooting every hour or so.  Initially I thought this was an Azure issue and Azure was forcibly rebooting the VM because it wasn't getting health reports back.  But I don't' believe this is the case anymore and I think FreeBSD is crashing.  (Note: I have setup a FreeBSD VM with a "Standard A" series VM and that seems to be running fine - though it looks like it might have crashed after about 38 hours which is much better than crashing after 1 hour).
> Here is the "last" log from the last two days:
> [--redacted--]   pts/2    [--redacted--] Fri Feb  5 21:10   still logged in
> [--redacted--]   pts/1    [--redacted--] Fri Feb  5 21:10   still logged in
> [--redacted--]   pts/0    [--redacted--] Fri Feb  5 20:58 - 21:10  (00:12)
> boot time                                  Fri Feb  5 20:53
> [--redacted--]   pts/1    [--redacted--] Fri Feb  5 04:59 - crash  (15:54)
> [--redacted--]   pts/0    [--redacted--] Fri Feb  5 04:59 - 04:59  (00:00)
> boot time                                  Fri Feb  5 04:41
> boot time                                  Fri Feb  5 02:16
> [--redacted--]   pts/1    [--redacted--] Fri Feb  5 00:36 - crash  (01:40)
> [--redacted--]   pts/0    [--redacted--] Fri Feb  5 00:36 - 00:36  (00:00)
> boot time                                  Fri Feb  5 00:29
> shutdown time                              Thu Feb  4 09:33
> boot time                                  Thu Feb  4 08:47
> [--redacted--]   pts/0    [--redacted--] Thu Feb  4 07:25 - crash  (01:21)
> boot time                                  Thu Feb  4 07:00
> boot time                                  Thu Feb  4 05:03
> boot time                                  Thu Feb  4 02:45
> [--redacted--]   pts/0    [--redacted--] Thu Feb  4 01:08 - crash  (01:36)
> boot time                                  Thu Feb  4 00:58
> There are boot times without previous shutdown times - and there is that "crash" text (which is why I'm thinking it is a crash).
> It looks by default the OS is setup to NOT save crash dumps
> sudo dumpon -v -l
> kernel dumps on /dev/null
> If that is the case - do I add this to /etc/rc.conf?
> dumpdev="AUTO"
> dumpdir="/var/crash"
> Is there anything I need to adjust there?
> Does that only take affect after a reboot?
> Do I need to set anything with dumpon(8)?
> Here is the info on the swapfile:
> sudo swapinfo -h
> Device          512-blocks     Used    Avail Capacity
> /dev/gpt/swapfs    2097152       0B     1.0G     0%
> Is that enough space for a kernel crash dump?
> Thanks for all your help with this.
> Regards,
> Scott Otis
> CTO & Co-Founder
> Tandem
> www.tandemcal.com<http://www.tandemcal.com/>
> _______________________________________________
> freebsd-stable at freebsd.org mailing list 
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"

More information about the freebsd-stable mailing list