Guillermo Garc?a Rojas | 3 May 18:31 2016
Picon

Bug 209222 -r298793 automatic shutdown for "kernel: ACPI Error: No installed handler for fixed event - PM_Timer (0), disabling (20160422/evevent-323)" and more under virtual box

Hi,

I'm having the same issue with downloaded ISO from Monday May 2nd under VirtualBox same version.

It happens at 10 minutes after system is started.

Thanks.
_______________________________________________
freebsd-current <at> freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"

Mark Millard | 3 May 08:04 2016
Picon

Bug 209222 -r298793 automatic shutdown for "kernel: ACPI Error: No installed handler for fixed event - PM_Timer (0), disabling (20160422/evevent-323)" and more under virtual box

I just upgraded my amd64 11.0-CURRENT that runs under virtual box on Mac OS X to -r298793. This was via
buildworld buildkernel then installing them, like normal for me.

The result is about 10-11 minutes after starting to boot FreeBSD shuts down with (for example):
(the root login line is just to give an idea of the time frame after the login prompt)

> May  2 21:52:18 FreeBSDx64 login: ROOT LOGIN (root) ON ttyv0
> May  2 22:01:45 FreeBSDx64 kernel: ACPI Error: No installed handler for fixed event - PM_Timer (0),
disabling (20160422/evevent-323)
> May  2 22:01:45 FreeBSDx64 kernel: ACPI Error: No installed handler for fixed event - RealTimeClock (4),
disabling (20160422/evevent-323)
> May  2 22:01:45 FreeBSDx64 kernel: ACPI Error: No handler or method for GPE 01, disabling event (20160422/evgpe-834)
> May  2 22:01:45 FreeBSDx64 kernel: ACPI Error: No handler or method for GPE 03, disabling event (20160422/evgpe-834)
> May  2 22:01:45 FreeBSDx64 kernel: ACPI Error: No handler or method for GPE 04, disabling event (20160422/evgpe-834)
> May  2 22:01:45 FreeBSDx64 kernel: ACPI Error: No handler or method for GPE 05, disabling event (20160422/evgpe-834)
> May  2 22:01:45 FreeBSDx64 kernel: ACPI Error: No handler or method for GPE 06, disabling event (20160422/evgpe-834)
> May  2 22:01:45 FreeBSDx64 kernel: ACPI Error: No handler or method for GPE 07, disabling event (20160422/evgpe-834)
> May  2 22:01:45 FreeBSDx64 kernel: .
> May  2 22:01:45 FreeBSDx64 afpd[652]: AFP Server shutting down
> May  2 22:01:45 FreeBSDx64 cnid_metad[654]: shutting down on SIGTERM
> May  2 22:01:45 FreeBSDx64 netatalk[639]: Netatalk AFP server exiting
> May  2 22:01:46 FreeBSDx64 kernel: .
> May  2 22:01:47 FreeBSDx64 kernel: , 576.
> May  2 22:01:47 FreeBSDx64 syslogd: exiting on signal 15

===
Mark Millard
markmi at dsl-only.net

_______________________________________________
(Continue reading)

O. Hartmann | 2 May 22:10 2016
Picon
Picon

CURRENT (r298939): kernelbuild failure: _cpuset.h:50:1: error: use of undeclared identifier 'NBBY'

CURRENT (r298939) kernelbuild fails due to the error shown below:

[...]
In file included from /usr/src/lib/libdevctl/devctl.c:31:
In file included from /usr/obj/usr/src/tmp/usr/include/sys/bus.h:35:
/usr/obj/usr/src/tmp/usr/include/sys/_cpuset.h:50:1: error: use of undeclared identifier
'NBBY' /usr/obj/usr/src/tmp/usr/include/sys/_bitset.h:52:24: note: expanded from macro
'BITSET_DEFINE' long    __bits[__bitset_words((_s))];                           \
                       ^
/usr/obj/usr/src/tmp/usr/include/sys/_bitset.h:41:41: note: expanded from macro
'__bitset_words' #define __bitset_words(_s)      (howmany(_s, _BITSET_BITS))
jenkins-admin | 2 May 21:01 2016
Picon

Build failed in Jenkins: FreeBSD_HEAD #237

See <https://jenkins.FreeBSD.org/job/FreeBSD_HEAD/237/>

------------------------------------------
[...truncated 87867 lines...]
sh /builds/workspace/FreeBSD_HEAD/src/tools/install.sh  -C -o root -g wheel -m 444   libgssapi_ntlm.a /builds/workspace/FreeBSD_HEAD/obj/builds/workspace/FreeBSD_HEAD/src/tmp/usr/lib/
sh /builds/workspace/FreeBSD_HEAD/src/tools/install.sh  -s -o root -g wheel -m 444    
libgssapi_ntlm.so.10 /builds/workspace/FreeBSD_HEAD/obj/builds/workspace/FreeBSD_HEAD/src/tmp/usr/lib/
sh /builds/workspace/FreeBSD_HEAD/src/tools/install.sh  -o root -g wheel -m 444   
libgssapi_ntlm.so.10.debug /builds/workspace/FreeBSD_HEAD/obj/builds/workspace/FreeBSD_HEAD/src/tmp/usr/lib/debug/usr/lib/
sh /builds/workspace/FreeBSD_HEAD/src/tools/install.sh -l rs  libgssapi_ntlm.so.10 /builds/workspace/FreeBSD_HEAD/obj/builds/workspace/FreeBSD_HEAD/src/tmp/usr/lib/libgssapi_ntlm.so
===> kerberos5/lib/libgssapi_spnego (install)
--- lib__L ---
--- bsm_socket_type.o ---
cc   -O2 -pipe -I/builds/workspace/FreeBSD_HEAD/src/lib/libbsm/../../contrib/openbsm
-I/builds/workspace/FreeBSD_HEAD/src/lib/libbsm/../../contrib/openbsm/libbsm   -MD 
-MF.depend.bsm_socket_type.o -MTbsm_socket_type.o -std=gnu99 -fstack-protector-strong
-Wsystem-headers -Werror -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int
-Wno-unused-const-variable -Wno-tautological-compare -Wno-unused-value
-Wno-parentheses-equality -Wno-unused-function -Wno-enum-conversion
-Wno-unused-local-typedef -Wno-switch -Wno-switch-enum -Wno-knr-promoted-parameter
-Wno-parentheses  -Qunused-arguments  -c
/builds/workspace/FreeBSD_HEAD/src/lib/libbsm/../../contrib/openbsm/libbsm/bsm_socket_type.c
-o bsm_socket_type.o
--- kerberos5/lib__L ---
--- _libinstall ---
sh /builds/workspace/FreeBSD_HEAD/src/tools/install.sh  -C -o root -g wheel -m 444  
libgssapi_spnego.a /builds/workspace/FreeBSD_HEAD/obj/builds/workspace/FreeBSD_HEAD/src/tmp/usr/lib/
sh /builds/workspace/FreeBSD_HEAD/src/tools/install.sh  -s -o root -g wheel -m 444    
libgssapi_spnego.so.10 /builds/workspace/FreeBSD_HEAD/obj/builds/workspace/FreeBSD_HEAD/src/tmp/usr/lib/
sh /builds/workspace/FreeBSD_HEAD/src/tools/install.sh  -o root -g wheel -m 444   
(Continue reading)

Bill O'Hanlon | 2 May 20:35 2016
Picon
Gravatar

Kernel panic from recent build

​
 IMG_20160502_130335.jpg
<https://drive.google.com/file/d/1dtJxTwWXfhXVUUtn1Vvpzh3laJt7AILyCg/view?usp=drive_web>
​
I'm getting the following panic from a recent (May 2, 2016) build.
panic: Duplicate local APIC ID 0

The system is a Dell Precision T5500 with generic factory BIOS settings.
It has run previous builds without event for several years.

I'm attaching a link to a photo of the screen for added details.
--

-- 
Bill O'Hanlon
612-205-9643
_______________________________________________
freebsd-current <at> freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"
jenkins-admin | 2 May 20:21 2016
Picon

FreeBSD_HEAD_i386 - Build #3028 - Failure

FreeBSD_HEAD_i386 - Build #3028 - Failure:

Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3028/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3028/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3028/console

Change summaries:

298931 by pfg:
etc: minor spelling fixes.

Mostly comments but also some user-visible strings.

MFC after:	2 weeks

298930 by royger:
xen/time: fix PV clock resolution

The current resolution of the Xen PV clock is too high, which causes an
adjustment of 5s to be applied to it. Reduce the resolution to be the same
as the RTC plus one, so it's always selected as the best source when
available on x86.

Also don't reset the clock on resume, it's pointless and discards any
previous adjustments.

Sponsoted by: Citrix Systems R&D

298929 by royger:
xen/time: allow Dom0 to set the host time
(Continue reading)

jenkins-admin | 2 May 20:14 2016
Picon

FreeBSD_HEAD_amd64_gcc - Build #1211 - Failure

FreeBSD_HEAD_amd64_gcc - Build #1211 - Failure:

Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc/1211/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc/1211/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc/1211/console

Change summaries:

298933 by jhb:
Add a new bus method to fetch device-specific CPU sets.

bus_get_cpus() returns a specified set of CPUs for a device.  It accepts
an enum for the second parameter that indicates the type of cpuset to
request.  Currently two valus are supported:

 - LOCAL_CPUS (on x86 this returns all the CPUs in the package closest to
   the device when DEVICE_NUMA is enabled)
 - INTR_CPUS (like LOCAL_CPUS but only returns 1 SMT thread for each core)

For systems that do not support NUMA (or if it is not enabled in the kernel
config), LOCAL_CPUS fails with EINVAL.  INTR_CPUS is mapped to 'all_cpus'
by default.  The idea is that INTR_CPUS should always return a valid set.

Device drivers which want to use per-CPU interrupts should start using
INTR_CPUS instead of simply assigning interrupts to all available CPUs.
In the future we may wish to add tunables to control the policy of
INTR_CPUS (e.g. should it be local-only or global, should it ignore
SMT threads or not).

The x86 nexus driver exposes the internal set of interrupt CPUs from the
(Continue reading)

Warren Block | 2 May 02:49 2016

FreeBSD Quarterly Status Report - First Quarter 2016 (fwd)

Introduction

    The first quarter of 2016 showed that FreeBSD retains a strong sense of
    ipseity. Improvements were pervasive, lending credence to the concept
    of meliorism.

    Panegyrics are relatively scarce, but not for lack of need. Perhaps
    this missive might serve that function in some infinitesimal way.

    There was propagation, reformation, randomization, accumulation,
    emulation, transmogrification, debuggenation, and metaphrasal during
    this quarter.

    In the financioartistic arena, pork snout futures narrowly edged out
    pointilism, while parietal art remained fixed.

    In all, a discomfiture of abundance. View the rubrics below, and marvel
    at their profusion and magnitude! Marvel!

    --Warren Block
      __________________________________________________________________

    Please submit status reports for the second quarter of 2016 by July 7.
    A thesaurus will be provided for submitters who do not have one of
    their own. We will need them back afterwards, preferably with no new
    teeth marks on the covers. Thank you!
      __________________________________________________________________

FreeBSD Team Reports

(Continue reading)

Graham Menhennitt | 1 May 22:43 2016
Picon

Re: boot fails "Can't stat /dev/da0a: No such file or directory"

On 30/04/2016 06:53 PM, Graham Menhennitt wrote:
> Hi all,
>
> I have a USB disk that I use for backup. Up till now, it's mounted
> without any problems at boot time. After updating to -current as of
> yesterday, it doesn't mount and causes the boot to fail.
>
> My /etc/fstab looks like:
>
>     # Device    Mountpoint    FStype    Options    Dump    Pass#
>
>     /dev/ada0s1a    /        ufs    rw    1    1
>     /dev/ada0s1b    none        swap    sw    0    0
>     /dev/da0a    /backup        ufs    rw,late    1    1
>
>
> I tried adding the "late" to fix the problem, but it doesn't help.
>
> The error message is:
>
>     /dev/ada0s1a: clean...
>     Can't stat /dev/da0a: No such file or directory
>     Unknown error; help!
>     ERROR: ABORTING BOOT (sending SIGTERM to parent)!
>
>
> (hand transcribed - maybe typos)
>
> Can anybody help, please.
>
(Continue reading)

RayCherng Yu | 1 May 15:48 2016
Picon

Cannot install the r298793 snapshot image

I installed the r299793 memstick.img and got this error message:

http://imgur.com/HktHn6b

Then I installed the mini-memstick.img instead. I got another error message:

http://imgur.com/dOPO83t

--

-- 
"Life is like a snowball. The important thing is finding wet snow and a
really long hill."

"Price is what you pay. Value is what you get."

"The first rule of Investing is don't lose money; the second rule is don't
forget rule #1..."

"Wall Street is the only place that people ride to work in a Rolls-Royce to
get advice from those who take the subway..."

— Warren Buffett.
_______________________________________________
freebsd-current <at> freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"
Shawn Webb | 1 May 14:35 2016

MCA unrecoverable machine check exception on APU2

Hey All,

I'm getting this panic. I'm not sure if it's a problem with the OS or
the hardware as this is a bit too low-level for me. Here's the dmesg
output along with the stack trace:

MCA: Bank 0, Status 0xb400000000000135
MCA: Global Cap 0x0000000000000106, Status 0x0000000000000004
MCA: Vendor "AuthenticAMD", ID 0x730f01, APIC ID 3
MCA: CPU 3 UNCOR DCACHE L1 DRD error
MCA: Address 0x44e9830
panic: Unrecoverable machine check exception
cpuid = 3
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00f53cb390
vpanic() at vpanic+0x182/frame 0xfffffe00f53cb410
panic() at panic+0x43/frame 0xfffffe00f53cb470
mca_intr() at mca_intr+0x6b/frame 0xfffffe00f53cb490
trap() at trap+0xa8/frame 0xfffffe00f53cb6a0
calltrap() at calltrap+0x8/frame 0xfffffe00f53cb6a0
--- trap 0x1c, rip = 0xffffffff80b6ffe1, rsp = 0xfffffe00f53cb770, rbp = 0xfffffe00f53cb7f0 ---
callout_process() at callout_process+0x131/frame 0xfffffe00f53cb7f0
handleevents() at handleevents+0x16d/frame 0xfffffe00f53cb830
timercb() at timercb+0x227/frame 0xfffffe00f53cb880
lapic_handle_timer() at lapic_handle_timer+0x9f/frame 0xfffffe00f53cb8c0
Xtimerint() at Xtimerint+0x8c/frame 0xfffffe00f53cb8c0
--- interrupt, rip = 0xffffffff80b85a39, rsp = 0xfffffe00f53cb990, rbp = 0xfffffe00f53cba70 ---
sched_idletd() at sched_idletd+0x439/frame 0xfffffe00f53cba70
fork_exit() at fork_exit+0x84/frame 0xfffffe00f53cbab0
fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe00f53cbab0
(Continue reading)


Gmane