Re: A lot of stuff gets printed before login such as 259 %pnpinfo R, 263 sim_time RW

2018-09-08 Thread Carsten Mattner 
On Fri, Sep 7, 2018 at 10:44 PM Matthew Dillon  Ah, you probably have a 'sysctl var=data' in /etc/sysctl.conf instead of
> just 'var=data'.  That is, you probably have the 'sysctl' keyword in your
> /etc/sysctl.conf when that file should only contain the var=data
> specifications.

Since this is interesting behavior, it piqued my curiosity. Does anyone
have a technical explanation what the existence of 'systctl.*' triggers
in the kernel?

Re: A lot of stuff gets printed before login such as 259 %pnpinfo R, 263 sim_time RW

2018-09-08 Thread Laurent Vivier 
Hello Siju, Matthew

Indeed, I had sysctl hw.acpi.cpu.cx_lowest=C3

Removing the sysctl part did the trick! 

Thanks for the heads-up !

 Original Message 
Subject: Re: A lot of stuff gets printed before login such as 259 %pnpinfo R, 
263 sim_time RW
From: Siju George 
To: Matthew Dillon 
CC: Laurent Vivier ,users@dragonflybsd.org



Yes, i had 

sysctl kern.ipc.shm_allow_removed=1 in /etc/sysctl.conf

changed it to just

kern.ipc.shm_allow_removed=1

and the problem is fixed.

Laurent, did you have the same problem?

thanks

Siju





On Fri, Sep 7, 2018 at 10:44 PM Matthew Dillon mailto:dil...@backplane.com> > wrote:
Ah, you probably have a 'sysctl var=data' in /etc/sysctl.conf instead of just 
'var=data'.  That is, you probably have the 'sysctl' keyword in your 
/etc/sysctl.conf when that file should only contain the var=data specifications.

-Matt

Re: A lot of stuff gets printed before login such as 259 %pnpinfo R, 263 sim_time RW

2018-09-08 Thread Siju George 
Yes, i had

sysctl kern.ipc.shm_allow_removed=1 in /etc/sysctl.conf

changed it to just

kern.ipc.shm_allow_removed=1

and the problem is fixed.

Laurent, did you have the same problem?

thanks

Siju





On Fri, Sep 7, 2018 at 10:44 PM Matthew Dillon  wrote:

> Ah, you probably have a 'sysctl var=data' in /etc/sysctl.conf instead of
> just 'var=data'.  That is, you probably have the 'sysctl' keyword in your
> /etc/sysctl.conf when that file should only contain the var=data
> specifications.
>
> -Matt
>

Re: A lot of stuff gets printed before login such as 259 %pnpinfo R, 263 sim_time RW

2018-09-07 Thread Matthew Dillon 
Ah, you probably have a 'sysctl var=data' in /etc/sysctl.conf instead of
just 'var=data'.  That is, you probably have the 'sysctl' keyword in your
/etc/sysctl.conf when that file should only contain the var=data
specifications.

-Matt

Re: A lot of stuff gets printed before login such as 259 %pnpinfo R, 263 sim_time RW

2018-09-07 Thread Laurent Vivier 
Hello Siju,

I have the very same behavior on 5.2.2, when I press any key, I can access the 
login prompt.

I am curious too about the root cause of this :)

Cheers,

Laurent

 Original Message 
Subject: A lot of stuff gets printed before login such as 259 %pnpinfo R, 263 
sim_time RW
From: Siju George 
To: users@dragonflybsd.org
CC: 



Hi,

Great to be back on dflybsd after a long time :-)

My system is

 5.3-DEVELOPMENT DragonFly v5.3.0.18519.gec3ac-DEVELOPMENT #0: Fri Sep  7 
11:15:50 IST 2018

The system prints a lot of stuff before login on the console that I have to 
press ^C to get the login prompt.

/var/log/messages has these recurring entries

Sep  7 12:28:59 dfly kernel: 256 %parent R  *Handler String
Sep  7 12:28:59 dfly kernel: 257 0 R  Node
Sep  7 12:28:59 dfly kernel: 256 %desc R  *Handler String
Sep  7 12:28:59 dfly kernel: 257 %driver R  *Handler String
Sep  7 12:28:59 dfly kernel: 258 %location R  *Handler String
Sep  7 12:28:59 dfly kernel: 259 %pnpinfo R  *Handler String
Sep  7 12:28:59 dfly kernel: 260 %parent R  *Handler String
Sep  7 12:28:59 dfly kernel: 281 isab R  Node
Sep  7 12:28:59 dfly kernel: 256 %parent R  *Handler String
Sep  7 12:28:59 dfly kernel: 257 0 R  Node
Sep  7 12:28:59 dfly kernel: 256 %desc R  *Handler String
Sep  7 12:28:59 dfly kernel: 257 %driver R  *Handler String
Sep  7 12:28:59 dfly kernel: 258 %location R  *Handler String
Sep  7 12:28:59 dfly kernel: 259 %pnpinfo R  *Handler String
Sep  7 12:28:59 dfly kernel: 260 %parent R  *Handler String
Sep  7 12:28:59 dfly kernel: 282 isa R  Node

what is the problem?

thanks :-)

Siju

My dmesg is

Copyright (c) 2003-2018 The DragonFly Project.
Copyright (c) 1992-2003 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.
DragonFly v5.3.0.18519.gec3ac-DEVELOPMENT #0: Fri Sep  7 11:15:50 IST 2018
    r...@dfly.loco.00:/usr/obj/usr/src/sys/X86_64_GENERIC
acpi_hpet: frequency 14318180
Using cputimer HPET for TSC calibration
Timer latency (in TSC ticks): 2825 min=2730 max=2850
TSC invariant clock: 2994371265 Hz
CPU: AMD Ryzen 7 1700 Eight-Core Processor           (2994.37-MHz K8-class CPU)
  Origin = "AuthenticAMD"  Id = 0x800f11  Stepping = 1
  
Features=0x178bfbff
  
Features2=0x76d8320b
  AMD Features=0x2e500800
  AMD 
Features2=0x35c233ff
  Structured Extended 
Features=0x209c01a9
  Thermal and PM Features=0x4
  MONITOR/MWAIT Features=0x2
real memory  = 17127142400 (16333 MB)
avail memory = 16021626880 (15279 MB)
   LAPIC AMD elvt0: 0x0001
   LAPIC AMD elvt1: 0x0001
   LAPIC AMD elvt2: 0x0001
   LAPIC AMD elvt3: 0x0001
LAPIC latency (in TSC ticks): 314 min: 300 max: 330
lapic: divisor index 0, frequency 49906190 Hz
core_bits 4 logical_CPU_bits 0
2-way htt, 1 Nodes, 8 cores/node
CPU Topology: cores_per_chip: 8; threads_per_core: 2; chips_per_package: 1;
Compute unit iDS:
0-0; 
SMI Frequency (worst case): 79 Hz (12580 us)
Initialize MI interrupts
TSC testing MP synchronization ...
TSC MPSYNC TEST 3540 16 -> 221 (10uS=29943)
TSC is MP synchronized
TSC: cputimer freq 93574102, shift 5
Spectre: support=( none ) req= operating=( none )
wdog: In-kernel automatic watchdog reset enabled
kbd0 at kbdmux0
md0: Malloc disk
interrupt uses mplock: swi_taskq
ACPI: RSDP 0x000F05B0 24 (v02 ALASKA)
ACPI: XSDT 0xDC092098 AC (v01 ALASKA A M I    01072009 AMI  
00010013)
ACPI: FACP 0xDC097AC8 000114 (v06 ALASKA A M I    01072009 AMI  
00010013)
Firmware Warning (ACPI): Optional FADT field Pm2ControlBlock has valid Length 
but zero Address: 0x/0x1 (20180810/tbfadt-801)
ACPI: DSDT 0xDC0921D8 0058E9 (v02 ALASKA A M I    01072009 INTL 
20120913)
ACPI: FACS 0xDC46EC80 40
ACPI: APIC 0xDC097BE0 DE (v03 ALASKA A M I    01072009 AMI  
00010013)
ACPI: FPDT 0xDC097CC0 44 (v01 ALASKA A M I    01072009 AMI  
00010013)
ACPI: SSDT 0xDC097D08 008C4C (v02                 0002 MSFT 
0400)
ACPI: FIDT 0xDC0A0958 9C (v01 ALASKA A M I    01072009 AMI  
00010013)
ACPI: SSDT 0xDC0A09F8 0020E4 (v01 AMD    AmdTable 0001 AMD  
0001)
ACPI: SRAT 0xDC0A2AE0 000130 (v03 AMD    AmdTable 0001 AMD  
0001)
ACPI: CRAT 0xDC0A2C10 000F50 (v01 AMD    AmdTable 0001 AMD  
0001)
ACPI: CDIT 0xDC0A3B60 29 (v01 AMD    AmdTable 0001 AMD  
0001)
ACPI: SSDT 0xDC0A3B90 0017E1 (v01 AMD    AOD      0001 INTL 
20120913)
ACPI: MCFG 0xDC0A5378 3C (v01 ALASKA A M I    01072009 MSFT 
00010013)
ACPI: HPET 0xDC0A53B8 38 (v01 ALASKA A M I    01072009 AMI  
0005)
ACPI: SSDT 0xDC0A53F0 24 (v01 AMDFCH FCHZP    1000 INTL 
20120913)
ACPI: UEFI 0xDC0A5418 42 (v01                       
)
ACPI: IVRS 0xDC0A5460 D0 (v02                 0001 AMD  
)
ACPI: SSDT