Re: ntpd setting date incorrectly
Patch works.
hw.sensors.vmt0.timedelta0=0.000109 secs, OK, Thu Dec 17 09:29:31.932
Dec 17 09:29:19 ianm-openbsd ntpd[882]: ntp engine ready
Dec 17 09:29:20 ianm-openbsd ntpd[5528]: set local clock to Thu Dec 17 09:29:20
AEDT 2015 (offset 0.937695s)
Dec 17 09:29:20 ianm-openbsd savecore: no core dump
Dec 17 09:29:21 ianm-openbsd apmd: battery status: absent. external power
status: connected. estimated battery life 0%
Dec 17 09:29:22 ianm-openbsd ntpd[882]: constraint reply from 216.58.220.132:
offset -0.635569
Dec 17 09:29:42 ianm-openbsd ntpd[882]: peer 129.250.35.251 now valid
Dec 17 09:29:43 ianm-openbsd ntpd[882]: peer 121.0.0.42 now valid
Dec 17 09:29:43 ianm-openbsd ntpd[882]: peer 121.0.0.41 now valid
Dec 17 09:29:48 ianm-openbsd ntpd[882]: peer 202.127.210.36 now valid
Dec 17 09:30:47 ianm-openbsd ntpd[12574]: adjusting local clock by 0.054113s
I'll keep an eye out for any further issues.
Thanks.
Ian McWilliam
From: Martin Pieuchot [m...@openbsd.org]
Sent: Thursday, 17 December 2015 1:31 AM
To: Mike Belopuhov
Cc: Ian Mcwilliam; tech@openbsd.org
Subject: Re: ntpd setting date incorrectly
On 16/12/15(Wed) 14:56, Mike Belopuhov wrote:
> On Wed, Dec 16, 2015 at 03:53 +, Ian Mcwilliam wrote:
> >
> > Disable sensors * in ntpd.conf and time is good again.
> >
> > I see this on boot up when things go strange.
> >
> > hw.sensors.vmt0.timedelta0=1450237689.498077 secs, OK, Tue Nov 29
> > 18:36:38.371
> >
> > I wonder if it's related to this change? Thoughts?
> >
>
> Bah, I've noticed that, but forgot to mention this to mpi@.
> Martin, what has prompted you to change the behaviour here?
> It's the only spot in that commit that has changed the
> mountroot to a startup hook.
Because this driver is using the same function for a hook and a timer,
both taking (void *) pointer.
I don't understand for which reason this driver is using a hook, but
tell me if this works.
Index: dev/pv/vmt.c
===
RCS file: /cvs/src/sys/dev/pv/vmt.c,v
retrieving revision 1.6
diff -u -p -r1.6 vmt.c
--- dev/pv/vmt.c11 Dec 2015 16:07:01 - 1.6
+++ dev/pv/vmt.c16 Dec 2015 14:29:54 -
@@ -208,6 +208,7 @@ void vmt_shutdown(void *);
voidvmt_update_guest_info(struct vmt_softc *);
voidvmt_update_guest_uptime(struct vmt_softc *);
+voidvmt_tick_hook(struct device *self);
voidvmt_tick(void *);
voidvmt_resume(void);
@@ -364,9 +365,7 @@ vmt_attach(struct device *parent, struct
sensor_attach(>sc_sensordev, >sc_sensor);
sensordev_install(>sc_sensordev);
- timeout_set(>sc_tick, vmt_tick, sc);
- if (startuphook_establish(vmt_tick, sc) == NULL)
- DPRINTF("%s: unable to establish tick\n", DEVNAME(sc));
+ config_mountroot(self, vmt_tick_hook);
timeout_set(>sc_tclo_tick, vmt_tclo_tick, sc);
timeout_add_sec(>sc_tclo_tick, 1);
@@ -467,6 +466,15 @@ vmt_update_guest_info(struct vmt_softc *
sc->sc_set_guest_os = 1;
}
+}
+
+void
+vmt_tick_hook(struct device *self)
+{
+ struct vmt_softc *sc = (struct vmt_softc *)self;
+
+ timeout_set(>sc_tick, vmt_tick, sc);
+ vmt_tick(sc);
}
void
Re: ntpd setting date incorrectly
On Wed, Dec 16, 2015 at 03:53 +, Ian Mcwilliam wrote:
>
> Disable sensors * in ntpd.conf and time is good again.
>
> I see this on boot up when things go strange.
>
> hw.sensors.vmt0.timedelta0=1450237689.498077 secs, OK, Tue Nov 29 18:36:38.371
>
> I wonder if it's related to this change? Thoughts?
>
Bah, I've noticed that, but forgot to mention this to mpi@.
Martin, what has prompted you to change the behaviour here?
It's the only spot in that commit that has changed the
mountroot to a startup hook.
> ===
> RCS file: /cvs/src/sys/dev/pv/vmt.c,v
> retrieving revision 1.5
> retrieving revision 1.6
> diff -u -r1.5 -r1.6
> --- src/sys/dev/pv/vmt.c 2015/08/27 19:51:36 1.5
> +++ src/sys/dev/pv/vmt.c 2015/12/11 16:07:01 1.6
> @@ -1,4 +1,4 @@
> -/* $OpenBSD: vmt.c,v 1.5 2015/08/27 19:51:36 deraadt Exp $ */
> +/* $OpenBSD: vmt.c,v 1.6 2015/12/11 16:07:01 mpi Exp $ */
>
> /*
> * Copyright (c) 2007 David Crawshaw <da...@zentus.com>
> @@ -365,7 +365,7 @@
> sensordev_install(>sc_sensordev);
>
> timeout_set(>sc_tick, vmt_tick, sc);
> - if (mountroothook_establish(vmt_tick, sc) == NULL)
> + if (startuphook_establish(vmt_tick, sc) == NULL)
> DPRINTF("%s: unable to establish tick\n", DEVNAME(sc));
>
> timeout_set(>sc_tclo_tick, vmt_tclo_tick, sc);
>
>
> Ian McWilliam
>
> ____________
> From: Ian Mcwilliam
> Sent: Tuesday, 15 December 2015 12:04 PM
> To: tech@openbsd.org
> Subject: ntpd setting date incorrectly
>
> Not sure what has changed in the last couple of days but apparently I need to
> get back from the future.
>
> This is an OpenBSD VM running under VMWare Fusion Professional Version 8.0.2
> (3164312) Mac OS X 10.11.2
>
>
> Dec 14 17:22:44 ianm-openbsd ntpd[13773]: peer 121.0.0.41 now valid
> Dec 14 17:22:46 ianm-openbsd ntpd[13773]: peer 192.189.54.17 now valid
> Dec 14 17:22:49 ianm-openbsd ntpd[13773]: peer 54.252.165.245 now valid
> Dec 14 17:22:49 ianm-openbsd ntpd[13773]: peer 54.252.129.186 now valid
> Dec 14 17:23:44 ianm-openbsd ntpd[19417]: adjusting local clock by 45.252476s
>
> Machine shutdown
>
> Machine rebooted next day
>
> Dec 15 09:26:00 ianm-openbsd ntpd[1991]: ntp engine ready
>
> time correct until
>
> Nov 27 07:52:36 ianm-openbsd ntpd[21778]: set local clock to Sun Nov 27
> 07:52:36 AEDT 2061 (offset 1450131996.187864s)
> Nov 27 07:52:36 ianm-openbsd savecore: no core dump
> Nov 27 07:52:37 ianm-openbsd apmd: battery status: absent. external power
> status: connected. estimated battery life 0%
> Nov 27 07:53:56 ianm-openbsd ntpd[11805]: adjusting local clock by
> -1450131950.806132s
> Nov 27 07:55:26 ianm-openbsd ntpd[11805]: adjusting local clock by
> -1450131950.410569s
> Nov 27 07:56:56 ianm-openbsd ntpd[11805]: adjusting local clock by
> -1450131949.960758s
> Nov 27 07:58:26 ianm-openbsd ntpd[11805]: adjusting local clock by
> -1450131949.511029s
> Nov 27 07:59:56 ianm-openbsd ntpd[11805]: adjusting local clock by
> -1450131949.061268s
> Nov 27 08:01:26 ianm-openbsd ntpd[11805]: adjusting local clock by
> -1450131948.611426s
> Nov 27 08:02:56 ianm-openbsd ntpd[11805]: adjusting local clock by
> -1450131948.161660s
> Nov 27 08:04:26 ianm-openbsd ntpd[11805]: adjusting local clock by
> -1450131947.711849s
> Nov 27 08:05:56 ianm-openbsd ntpd[11805]: adjusting local clock by
> -1450131947.262024s
> Nov 27 08:07:26 ianm-openbsd ntpd[11805]: adjusting local clock by
> -1450131946.812191s
> Nov 27 08:07:32 ianm-openbsd dhclient[21622]: DHCPDISCOVER on em0 - interval 1
> Nov 27 08:07:33 ianm-openbsd dhclient[21622]: DHCPDISCOVER on em0 - interval 1
> Nov 27 08:07:33 ianm-openbsd dhclient[21622]: DHCPOFFER from 172.16.28.254
> (00:50:56:f1:c4:f7)
> Nov 27 08:07:33 ianm-openbsd dhclient[21622]: DHCPREQUEST on em0 to
> 255.255.255.255
> Nov 27 08:07:33 ianm-openbsd dhclient[21622]: DHCPACK from 172.16.28.254
> (00:50:56:f1:c4:f7)
> Nov 27 08:07:33 ianm-openbsd dhclient[21622]: bound to 172.16.28.141 --
> renewal in 900 seconds.
> Nov 27 08:08:56 ianm-openbsd ntpd[11805]: adjusting local clock by
> -1450131946.362273s
>
> manually setting the date/time shows that things appear fine until next
> reboot.
>
> Nov 27 08:57:27 ianm-openbsd ntpd[11805]: adjusting local clock by
> -1450131932.766352s
> Nov 27 08:58:57 ianm-openbsd ntpd[11805]: adjusting local clock by
> -1450131932.316650s
> Dec 15 10:34:21 ianm-openbsd ntpd[11805]: adjusting local clock by 33.548572s
> Dec 15 10:34:21 ianm-openbsd ntpd[1991]: clock is now synced
> Dec 15 10:35:
Re: ntpd setting date incorrectly
On 16/12/15(Wed) 14:56, Mike Belopuhov wrote:
> On Wed, Dec 16, 2015 at 03:53 +, Ian Mcwilliam wrote:
> >
> > Disable sensors * in ntpd.conf and time is good again.
> >
> > I see this on boot up when things go strange.
> >
> > hw.sensors.vmt0.timedelta0=1450237689.498077 secs, OK, Tue Nov 29
> > 18:36:38.371
> >
> > I wonder if it's related to this change? Thoughts?
> >
>
> Bah, I've noticed that, but forgot to mention this to mpi@.
> Martin, what has prompted you to change the behaviour here?
> It's the only spot in that commit that has changed the
> mountroot to a startup hook.
Because this driver is using the same function for a hook and a timer,
both taking (void *) pointer.
I don't understand for which reason this driver is using a hook, but
tell me if this works.
Index: dev/pv/vmt.c
===
RCS file: /cvs/src/sys/dev/pv/vmt.c,v
retrieving revision 1.6
diff -u -p -r1.6 vmt.c
--- dev/pv/vmt.c11 Dec 2015 16:07:01 - 1.6
+++ dev/pv/vmt.c16 Dec 2015 14:29:54 -
@@ -208,6 +208,7 @@ void vmt_shutdown(void *);
voidvmt_update_guest_info(struct vmt_softc *);
voidvmt_update_guest_uptime(struct vmt_softc *);
+voidvmt_tick_hook(struct device *self);
voidvmt_tick(void *);
voidvmt_resume(void);
@@ -364,9 +365,7 @@ vmt_attach(struct device *parent, struct
sensor_attach(>sc_sensordev, >sc_sensor);
sensordev_install(>sc_sensordev);
- timeout_set(>sc_tick, vmt_tick, sc);
- if (startuphook_establish(vmt_tick, sc) == NULL)
- DPRINTF("%s: unable to establish tick\n", DEVNAME(sc));
+ config_mountroot(self, vmt_tick_hook);
timeout_set(>sc_tclo_tick, vmt_tclo_tick, sc);
timeout_add_sec(>sc_tclo_tick, 1);
@@ -467,6 +466,15 @@ vmt_update_guest_info(struct vmt_softc *
sc->sc_set_guest_os = 1;
}
+}
+
+void
+vmt_tick_hook(struct device *self)
+{
+ struct vmt_softc *sc = (struct vmt_softc *)self;
+
+ timeout_set(>sc_tick, vmt_tick, sc);
+ vmt_tick(sc);
}
void
Re: ntpd setting date incorrectly
Disable sensors * in ntpd.conf and time is good again.
I see this on boot up when things go strange.
hw.sensors.vmt0.timedelta0=1450237689.498077 secs, OK, Tue Nov 29 18:36:38.371
I wonder if it's related to this change? Thoughts?
===
RCS file: /cvs/src/sys/dev/pv/vmt.c,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- src/sys/dev/pv/vmt.c2015/08/27 19:51:36 1.5
+++ src/sys/dev/pv/vmt.c2015/12/11 16:07:01 1.6
@@ -1,4 +1,4 @@
-/* $OpenBSD: vmt.c,v 1.5 2015/08/27 19:51:36 deraadt Exp $ */
+/* $OpenBSD: vmt.c,v 1.6 2015/12/11 16:07:01 mpi Exp $ */
/*
* Copyright (c) 2007 David Crawshaw <da...@zentus.com>
@@ -365,7 +365,7 @@
sensordev_install(>sc_sensordev);
timeout_set(>sc_tick, vmt_tick, sc);
- if (mountroothook_establish(vmt_tick, sc) == NULL)
+ if (startuphook_establish(vmt_tick, sc) == NULL)
DPRINTF("%s: unable to establish tick\n", DEVNAME(sc));
timeout_set(>sc_tclo_tick, vmt_tclo_tick, sc);
Ian McWilliam
From: Ian Mcwilliam
Sent: Tuesday, 15 December 2015 12:04 PM
To: tech@openbsd.org
Subject: ntpd setting date incorrectly
Not sure what has changed in the last couple of days but apparently I need to
get back from the future.
This is an OpenBSD VM running under VMWare Fusion Professional Version 8.0.2
(3164312) Mac OS X 10.11.2
Dec 14 17:22:44 ianm-openbsd ntpd[13773]: peer 121.0.0.41 now valid
Dec 14 17:22:46 ianm-openbsd ntpd[13773]: peer 192.189.54.17 now valid
Dec 14 17:22:49 ianm-openbsd ntpd[13773]: peer 54.252.165.245 now valid
Dec 14 17:22:49 ianm-openbsd ntpd[13773]: peer 54.252.129.186 now valid
Dec 14 17:23:44 ianm-openbsd ntpd[19417]: adjusting local clock by 45.252476s
Machine shutdown
Machine rebooted next day
Dec 15 09:26:00 ianm-openbsd ntpd[1991]: ntp engine ready
time correct until
Nov 27 07:52:36 ianm-openbsd ntpd[21778]: set local clock to Sun Nov 27
07:52:36 AEDT 2061 (offset 1450131996.187864s)
Nov 27 07:52:36 ianm-openbsd savecore: no core dump
Nov 27 07:52:37 ianm-openbsd apmd: battery status: absent. external power
status: connected. estimated battery life 0%
Nov 27 07:53:56 ianm-openbsd ntpd[11805]: adjusting local clock by
-1450131950.806132s
Nov 27 07:55:26 ianm-openbsd ntpd[11805]: adjusting local clock by
-1450131950.410569s
Nov 27 07:56:56 ianm-openbsd ntpd[11805]: adjusting local clock by
-1450131949.960758s
Nov 27 07:58:26 ianm-openbsd ntpd[11805]: adjusting local clock by
-1450131949.511029s
Nov 27 07:59:56 ianm-openbsd ntpd[11805]: adjusting local clock by
-1450131949.061268s
Nov 27 08:01:26 ianm-openbsd ntpd[11805]: adjusting local clock by
-1450131948.611426s
Nov 27 08:02:56 ianm-openbsd ntpd[11805]: adjusting local clock by
-1450131948.161660s
Nov 27 08:04:26 ianm-openbsd ntpd[11805]: adjusting local clock by
-1450131947.711849s
Nov 27 08:05:56 ianm-openbsd ntpd[11805]: adjusting local clock by
-1450131947.262024s
Nov 27 08:07:26 ianm-openbsd ntpd[11805]: adjusting local clock by
-1450131946.812191s
Nov 27 08:07:32 ianm-openbsd dhclient[21622]: DHCPDISCOVER on em0 - interval 1
Nov 27 08:07:33 ianm-openbsd dhclient[21622]: DHCPDISCOVER on em0 - interval 1
Nov 27 08:07:33 ianm-openbsd dhclient[21622]: DHCPOFFER from 172.16.28.254
(00:50:56:f1:c4:f7)
Nov 27 08:07:33 ianm-openbsd dhclient[21622]: DHCPREQUEST on em0 to
255.255.255.255
Nov 27 08:07:33 ianm-openbsd dhclient[21622]: DHCPACK from 172.16.28.254
(00:50:56:f1:c4:f7)
Nov 27 08:07:33 ianm-openbsd dhclient[21622]: bound to 172.16.28.141 -- renewal
in 900 seconds.
Nov 27 08:08:56 ianm-openbsd ntpd[11805]: adjusting local clock by
-1450131946.362273s
manually setting the date/time shows that things appear fine until next reboot.
Nov 27 08:57:27 ianm-openbsd ntpd[11805]: adjusting local clock by
-1450131932.766352s
Nov 27 08:58:57 ianm-openbsd ntpd[11805]: adjusting local clock by
-1450131932.316650s
Dec 15 10:34:21 ianm-openbsd ntpd[11805]: adjusting local clock by 33.548572s
Dec 15 10:34:21 ianm-openbsd ntpd[1991]: clock is now synced
Dec 15 10:35:52 ianm-openbsd ntpd[11805]: adjusting local clock by 33.107247s
Dec 15 10:35:52 ianm-openbsd ntpd[1991]: clock is now unsynced
Dec 15 10:37:21 ianm-openbsd ntpd[11805]: adjusting local clock by 32.662256s
Dec 15 10:38:51 ianm-openbsd ntpd[11805]: adjusting local clock by 32.212314s
Dec 15 10:40:21 ianm-openbsd ntpd[11805]: adjusting local clock by 31.762446s
Dec 15 10:41:38 ianm-openbsd ntpd[1991]: constraint reply from 74.125.237.17:
offset 30.905949
Dec 15 10:41:38 ianm-openbsd ntpd[1991]: constraint reply from 74.125.237.20:
offset 30.905572
Dec 15 10:41:38 ianm-openbsd ntpd[1991]: constraint reply from 74.125.237.19:
offset 30.903128
Dec 15 10:41:38 ianm-openbsd ntpd[1991]: constraint reply from 74.125.237.18:
offset 30.900721
Dec 15 10:41:38 ianm-openbsd ntpd[1991]: constraint
ntpd setting date incorrectly
Not sure what has changed in the last couple of days but apparently I need to get back from the future. This is an OpenBSD VM running under VMWare Fusion Professional Version 8.0.2 (3164312) Mac OS X 10.11.2 Dec 14 17:22:44 ianm-openbsd ntpd[13773]: peer 121.0.0.41 now valid Dec 14 17:22:46 ianm-openbsd ntpd[13773]: peer 192.189.54.17 now valid Dec 14 17:22:49 ianm-openbsd ntpd[13773]: peer 54.252.165.245 now valid Dec 14 17:22:49 ianm-openbsd ntpd[13773]: peer 54.252.129.186 now valid Dec 14 17:23:44 ianm-openbsd ntpd[19417]: adjusting local clock by 45.252476s Machine shutdown Machine rebooted next day Dec 15 09:26:00 ianm-openbsd ntpd[1991]: ntp engine ready time correct until Nov 27 07:52:36 ianm-openbsd ntpd[21778]: set local clock to Sun Nov 27 07:52:36 AEDT 2061 (offset 1450131996.187864s) Nov 27 07:52:36 ianm-openbsd savecore: no core dump Nov 27 07:52:37 ianm-openbsd apmd: battery status: absent. external power status: connected. estimated battery life 0% Nov 27 07:53:56 ianm-openbsd ntpd[11805]: adjusting local clock by -1450131950.806132s Nov 27 07:55:26 ianm-openbsd ntpd[11805]: adjusting local clock by -1450131950.410569s Nov 27 07:56:56 ianm-openbsd ntpd[11805]: adjusting local clock by -1450131949.960758s Nov 27 07:58:26 ianm-openbsd ntpd[11805]: adjusting local clock by -1450131949.511029s Nov 27 07:59:56 ianm-openbsd ntpd[11805]: adjusting local clock by -1450131949.061268s Nov 27 08:01:26 ianm-openbsd ntpd[11805]: adjusting local clock by -1450131948.611426s Nov 27 08:02:56 ianm-openbsd ntpd[11805]: adjusting local clock by -1450131948.161660s Nov 27 08:04:26 ianm-openbsd ntpd[11805]: adjusting local clock by -1450131947.711849s Nov 27 08:05:56 ianm-openbsd ntpd[11805]: adjusting local clock by -1450131947.262024s Nov 27 08:07:26 ianm-openbsd ntpd[11805]: adjusting local clock by -1450131946.812191s Nov 27 08:07:32 ianm-openbsd dhclient[21622]: DHCPDISCOVER on em0 - interval 1 Nov 27 08:07:33 ianm-openbsd dhclient[21622]: DHCPDISCOVER on em0 - interval 1 Nov 27 08:07:33 ianm-openbsd dhclient[21622]: DHCPOFFER from 172.16.28.254 (00:50:56:f1:c4:f7) Nov 27 08:07:33 ianm-openbsd dhclient[21622]: DHCPREQUEST on em0 to 255.255.255.255 Nov 27 08:07:33 ianm-openbsd dhclient[21622]: DHCPACK from 172.16.28.254 (00:50:56:f1:c4:f7) Nov 27 08:07:33 ianm-openbsd dhclient[21622]: bound to 172.16.28.141 -- renewal in 900 seconds. Nov 27 08:08:56 ianm-openbsd ntpd[11805]: adjusting local clock by -1450131946.362273s manually setting the date/time shows that things appear fine until next reboot. Nov 27 08:57:27 ianm-openbsd ntpd[11805]: adjusting local clock by -1450131932.766352s Nov 27 08:58:57 ianm-openbsd ntpd[11805]: adjusting local clock by -1450131932.316650s Dec 15 10:34:21 ianm-openbsd ntpd[11805]: adjusting local clock by 33.548572s Dec 15 10:34:21 ianm-openbsd ntpd[1991]: clock is now synced Dec 15 10:35:52 ianm-openbsd ntpd[11805]: adjusting local clock by 33.107247s Dec 15 10:35:52 ianm-openbsd ntpd[1991]: clock is now unsynced Dec 15 10:37:21 ianm-openbsd ntpd[11805]: adjusting local clock by 32.662256s Dec 15 10:38:51 ianm-openbsd ntpd[11805]: adjusting local clock by 32.212314s Dec 15 10:40:21 ianm-openbsd ntpd[11805]: adjusting local clock by 31.762446s Dec 15 10:41:38 ianm-openbsd ntpd[1991]: constraint reply from 74.125.237.17: offset 30.905949 Dec 15 10:41:38 ianm-openbsd ntpd[1991]: constraint reply from 74.125.237.20: offset 30.905572 Dec 15 10:41:38 ianm-openbsd ntpd[1991]: constraint reply from 74.125.237.19: offset 30.903128 Dec 15 10:41:38 ianm-openbsd ntpd[1991]: constraint reply from 74.125.237.18: offset 30.900721 Dec 15 10:41:38 ianm-openbsd ntpd[1991]: constraint reply from 74.125.237.16: offset 30.823298 Dec 15 10:41:51 ianm-openbsd ntpd[11805]: adjusting local clock by 31.312487s Dec 15 10:41:55 ianm-openbsd ntpd[1991]: peer 121.0.0.42 now valid Dec 15 10:41:57 ianm-openbsd ntpd[1991]: peer 110.21.107.139 now valid Dec 15 10:41:58 ianm-openbsd ntpd[1991]: peer 202.60.94.11 now valid Dec 15 10:41:58 ianm-openbsd ntpd[1991]: peer 60.241.92.80 now valid Dec 15 10:42:54 ianm-openbsd ntpd[11805]: adjusting local clock by 30.997486s ntpd_flags="-s" ntpd.conf #servers pool.ntp.org #servers 0.au.pool.ntp.org servers au.pool.ntp.org sensor * constraints from "https://www.google.com; OpenBSD 5.8-current (GENERIC.MP) #0: Mon Dec 14 10:37:32 AEDT 2015 r...@ianm-openbsd..edu.au:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 3141468160 (2995MB) avail mem = 3042197504 (2901MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (242 entries) bios0: vendor Phoenix Technologies LTD version "6.00" date 07/02/2015 bios0: VMware, Inc. VMware Virtual Platform acpi0 at bios0: rev 2 acpi0: sleep states S0 S1 S4 S5 acpi0: tables DSDT FACP BOOT APIC MCFG SRAT HPET WAET acpi0: wakeup devices PCI0(S3) USB_(S1) P2P0(S3) S1F0(S3) S2F0(S3) S3F0(S3) S4F0(S3) S5F0(S3) S6F0(S3) S7F0(S3)
