Check bios settings. I think this occurs if the c states are set to
hardware controlled and not set to software controlled. The setting names
and values may may vary depending on the manufacturer.
On Sat, Jan 14, 2017 at 1:40 PM, Slawa Olhovchenkov wrote:
> I am have stable/11 and E5v4.
> I am d
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Thanks to all who responded, makes perfect sense now.
Paul Mather wrote:
The only thing you need on the host is to have the linux kernel module
loaded.
(You don't need to have any Linux packages installed there.) The
default setting
in /usr/local/etc/poudriere.conf is to have NOLINUX=yes comme
On Sat, Jan 14, 2017 at 06:40:02PM +0700, Eugene Grosbein wrote:
>
> > I suspect that this is because we only stop the scheduler upon a panic
> > if SMP is configured. Can you retest with the patch below applied?
> >
> > Index: sys/kern/kern_shutdown.c
> >
On Sat, 14 Jan 2017 15:11:42 +0100 Tijl Coosemans wrote:
> On Sat, 14 Jan 2017 01:07:09 +0100 Mark Martinec
> wrote:
>> When building packages under poudriere on 11.0-RELEASE-p7 (from a
>> command line in a terminal window) I'm noticing occasional streams of
>> diagnostic:
>>
>>ELF binary
I am have stable/11 and E5v4.
I am don't see cpufreq support by sysctl:
# sysctl dev.cpu.0
dev.cpu.0.cx_method: C1/hlt
dev.cpu.0.cx_usage_counters: 61755
dev.cpu.0.cx_usage: 100.00% last 1us
dev.cpu.0.cx_lowest: C2
dev.cpu.0.cx_supported: C1/1/1
dev.cpu.0.%parent: acpi0
dev.cpu.0.%pnpinfo: _HID=AC
On Jan 14, 2017, at 9:11 AM, Tijl Coosemans wrote:
> On Sat, 14 Jan 2017 01:07:09 +0100 Mark Martinec
> wrote:
>> When building packages under poudriere on 11.0-RELEASE-p7 (from a
>> command line in a terminal window) I'm noticing occasional streams of
>> diagnostic:
>>
>> ELF binary type "
On Sat, 14 Jan 2017 01:07:09 +0100 Mark Martinec
wrote:
> When building packages under poudriere on 11.0-RELEASE-p7 (from a
> command line in a terminal window) I'm noticing occasional streams of
> diagnostic:
>
>ELF binary type "3" not known.
>
> which seem to be related to building some
_flags = 16842752, lo_data = 0,
lo_witness = 0x0}, mtx_lock = 4}, _rm_lock_sx = {lock_object = {lo_name
= 0xc0a802a2 "IPFW static rules", lo_flags = 16842752, lo_data = 0,
lo_witness = 0x0}, sx_lock = 4}}}
Full kgdb script here: http://www.grosbein.net/freebsd/crash/20170114
On Sat, Jan 14, 2017 at 9:38 AM, Konstantin Tokarev
wrote:
> 14.01.2017, 12:18, "René Ladan" :
> > Op 14 jan. 2017 01:07 schreef "Mark Martinec" <
> mark.martinec+free...@ijs.si
> >> :
> > When building packages under poudriere on 11.0-RELEASE-p7 (from a command
> > line in a terminal window) I'm
_flags = 16842752, lo_data = 0,
lo_witness = 0x0}, mtx_lock = 4}, _rm_lock_sx = {lock_object = {lo_name
= 0xc0a802a2 "IPFW static rules", lo_flags = 16842752, lo_data = 0,
lo_witness = 0x0}, sx_lock = 4}}}
Full kgdb script here: http://www.grosbein.net/freebsd/crash/20170114
> I suspect that this is because we only stop the scheduler upon a panic
> if SMP is configured. Can you retest with the patch below applied?
>
> Index: sys/kern/kern_shutdown.c
> ===
> --- sys/kern/kern_shutdown.c (revision 312082)
14.01.2017, 12:18, "René Ladan" :
> Op 14 jan. 2017 01:07 schreef "Mark Martinec" > :
>
> When building packages under poudriere on 11.0-RELEASE-p7 (from a command
> line in a terminal window) I'm noticing occasional streams of diagnostic:
>
> ELF binary type "3" not known.
>
> which seem to be
Op 14 jan. 2017 01:07 schreef "Mark Martinec" :
When building packages under poudriere on 11.0-RELEASE-p7 (from a command
line in a terminal window) I'm noticing occasional streams of diagnostic:
ELF binary type "3" not known.
which seem to be related to building some linux packages (example b
14 matches
Mail list logo
