Re: VMM sh: time sleep 30 takes 56 seconds
On Mon, Oct 22, 2018 at 02:52:42AM -0200, Daniel Bolgheroni wrote: > On Fri, Oct 19, 2018 at 04:16:51AM +, Mike Larkin wrote: > > On Thu, Oct 18, 2018 at 10:34:20PM -0300, Daniel Bolgheroni wrote: > > > On Wed, Oct 17, 2018 at 08:42:46PM +, Mike Larkin wrote: > > > > A 1000Hz host helps here. I get 10.32s real time on sleep 10 with that > > > > setting. > > > > > > > > Note that qemu behaves the same way on OpenBSD. > > > > > > OK, the output is still slow when on serial, but things improved > > > > Is the console baudrate 9600 or 115200? > > It's running at 115200. > > $ vmctl start 1 -c > Connected to /dev/ttyp7 (speed 115200) ^^^ if this is what you are using to determine that, I'd ask you to ensure that you stty com0 115200 in /etc/boot.conf and that the /etc/ttys line has 115200 for the console also. The baudrate from the output of the 'cu' used by 'vmctl console' always prints 115200 in this case, even if vmd is only outputting at 9600. -ml > [ using 2145656 bytes of bsd ELF symbol table ] > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > Copyright (c) 1995-2018 OpenBSD. All rights reserved. https://www.OpenBSD.org > > OpenBSD 6.4 (GENERIC.MP) #364: Thu Oct 11 13:30:23 MDT 2018 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 520093696 (496MB) > avail mem = 495116288 (472MB) > > (...) > > Thank you. > > -- > db
Re: Bad sectors on boot disk
There is no point in taking such action. Replace the drive. Once this begins, more blocks will go bad soon. > I'm getting console messages like: > > wd0a: uncorrectable data error reading fsbn 530469 of ... > > I found this page: > > How to repair bad sectors on HDD in OpenBSD (Part I) > > at: > > > https://www.s-vp.com/blog/post/how-to-repair-bad-sectors-on-hdd-in-openbsd-part-i > > Question 1: > Is it possible to repair "wd0a"? > Do I need another boot disk to do the repair? > I'm in the process of building another boot disk with the identical OpenBSD > version. I'm assuming it will take less time this way since I can copy the > settings from a backup. > > Question 2: > Once I build the new boot disk mentioned in Question 1 I thought I'd clone > it and keep it up to date using rsync. Is the page: > > OpenBSD 5.5 and later | cloning a disk the easy way > > at: > > > https://bytesandbones.wordpress.com/2014/09/23/openbsd-5-5-and-later-cloning-a-disk-the-easy-way/ > > Is this set of instructions complete or is there a better set of > instructions? Will this disk be bootable after cloning or do I have to > install OpenBSD on the clone first to make the disk bootable? Is this a > suitable way to maintain a spare clone of my boot disk? My data is kept on > other hard disks in my system. > > Thanks, Joe. > PS. My email web page flashed so I resent the message. I hope this gets > through. Sorry if it's a duplicate. >
Bad sectors on boot disk
I'm getting console messages like: wd0a: uncorrectable data error reading fsbn 530469 of ... I found this page: How to repair bad sectors on HDD in OpenBSD (Part I) at: https://www.s-vp.com/blog/post/how-to-repair-bad-sectors-on-hdd-in-openbsd-part-i Question 1: Is it possible to repair "wd0a"? Do I need another boot disk to do the repair? I'm in the process of building another boot disk with the identical OpenBSD version. I'm assuming it will take less time this way since I can copy the settings from a backup. Question 2: Once I build the new boot disk mentioned in Question 1 I thought I'd clone it and keep it up to date using rsync. Is the page: OpenBSD 5.5 and later | cloning a disk the easy way at: https://bytesandbones.wordpress.com/2014/09/23/openbsd-5-5-and-later-cloning-a-disk-the-easy-way/ Is this set of instructions complete or is there a better set of instructions? Will this disk be bootable after cloning or do I have to install OpenBSD on the clone first to make the disk bootable? Is this a suitable way to maintain a spare clone of my boot disk? My data is kept on other hard disks in my system. Thanks, Joe. PS. My email web page flashed so I resent the message. I hope this gets through. Sorry if it's a duplicate.
Re: phonetic alphabet on OpenBSD
This is an openbsd mailing list. You are chatting about something entirely unrelated to openbsd. Please take it offline. Thank you. > On Mon, Oct 22, 2018 at 07:15:03PM +0200, Christian Weisgerber wrote: > > > I have to ask also, is the audio quality that comes out the speakers (in > > > general) good enough to learn the proper sounds? Every device I have > > > seems to have wildly varying qualities and characteristics. > > > For example, (OK, not OpenBSD but somewhat relevant) if I wanted to > > > listen to the speech coming out of Google Translate, would a native > > > speaker of say Spanish, German or Russian consider the sounds "proper"? > > > > What a bizarre question. Listen to English dialog from your speaker > > setup. Does it sound like "proper" English? Anything that plays > > music in reasonable quality--so *anything*, really--will more than > > do for human speech. > > Actually, despite seeming like a bizarre question, which seems to be > true, it is not. > One of the more difficult parts of learning to speak and hear a new > language consists of adding the new neural pathways to actually be able > to stop translating the new languages sounds into the closest English > sounds. As we originally learn a language, our brains develop the > ability to "only" be able to hear the native sounds of that language > only. Our brains, etc. conveniently move what we hear or speak to the > closest English sounds. This prevents us from hearing the new speech > sounds at first until we train our brain to hear and make the brand new > sounds. So asking only a native speaker if the sounds are proper or not > is the only way to really be sure. Although I can vouch for quality in > English, I simply do not, yet, have the ability to judge new sounds. > Only a native speaker of that language can do this task. > > IMHO, I do think this is a reasonable question to ask. There are some > languages with some very unusual sounds. > > As far as music, I can definitely hear that European played classical > music tends to sound better than American played (Same piece). > I have no idea what is different, but I can hear it. > > Chris Bennett > >
Re: phonetic alphabet on OpenBSD
On Mon, Oct 22, 2018 at 07:15:03PM +0200, Christian Weisgerber wrote: > > I have to ask also, is the audio quality that comes out the speakers (in > > general) good enough to learn the proper sounds? Every device I have > > seems to have wildly varying qualities and characteristics. > > For example, (OK, not OpenBSD but somewhat relevant) if I wanted to > > listen to the speech coming out of Google Translate, would a native > > speaker of say Spanish, German or Russian consider the sounds "proper"? > > What a bizarre question. Listen to English dialog from your speaker > setup. Does it sound like "proper" English? Anything that plays > music in reasonable quality--so *anything*, really--will more than > do for human speech. Actually, despite seeming like a bizarre question, which seems to be true, it is not. One of the more difficult parts of learning to speak and hear a new language consists of adding the new neural pathways to actually be able to stop translating the new languages sounds into the closest English sounds. As we originally learn a language, our brains develop the ability to "only" be able to hear the native sounds of that language only. Our brains, etc. conveniently move what we hear or speak to the closest English sounds. This prevents us from hearing the new speech sounds at first until we train our brain to hear and make the brand new sounds. So asking only a native speaker if the sounds are proper or not is the only way to really be sure. Although I can vouch for quality in English, I simply do not, yet, have the ability to judge new sounds. Only a native speaker of that language can do this task. IMHO, I do think this is a reasonable question to ask. There are some languages with some very unusual sounds. As far as music, I can definitely hear that European played classical music tends to sound better than American played (Same piece). I have no idea what is different, but I can hear it. Chris Bennett
Re: FAM Question
I proposed entr as a replacement for FAM. November idea how to start gamin. Markus Rosjat schrieb am Mo., 22. Okt. 2018 08:56: > Hi Julian, > > > Am 22.10.2018 um 01:26 schrieb Julian Suschlik: > > FAM/gamin execute programs when parts of the filesystem change AFAIK. > > > > My goto program for this is entr (http://entrproject.org/) available as > > port under sysutils/entr (http://ports.su/sysutils/entr) > > > > I still don't get what you trying to tell me. I simply need to know how > to start gamin as a background process since FAM package isnt arround > anymore. Usally there would be some kind of rc script in rc.d somewere > but there isnt. There isnt a man page to be found so I'm lost how to get > things running. > > regards > > -- > Markus Rosjatfon: +49 351 8107224mail: ros...@ghweb.de > > G+H Webservice GbR Gorzolla, Herrmann > Königsbrücker Str. 70, 01099 Dresden > > http://www.ghweb.de > fon: +49 351 8107220 fax: +49 351 8107227 > > Bitte prüfen Sie, ob diese Mail wirklich ausgedruckt werden muss! Before > you print it, think about your responsibility and commitment to the > ENVIRONMENT > >
Re: amd64.iso KVM guest kernel panic pc=ffffffff811c303c (Opteron_G3 to Opteron_G5)
On Mon, Oct 22, 2018 at 08:59:46PM +0300, snikolov wrote: > On Mon, 2018-10-22 at 10:27 -0700, Mike Larkin wrote: > > On Mon, Oct 22, 2018 at 10:13:14AM -0700, Mike Larkin wrote: > > > On Mon, Oct 22, 2018 at 08:01:13PM +0300, snikolov wrote: > > > > > This appears to be related to the LFENCE serializing MSR change > > > > > that > > > > > went in > > > > > during the last round of side channel analysis fixes: > > > > > > > > > > 811c3037: b9 29 10 01 > > > > > c0 mov$0xc0011029,%ecx > > > > > 811c303c: 0f 32 rdmsr > > > > > > > > > > According to the commit, "This MSR is available on all AMD > > > > > families > > > > > > = 10h...", > > > > > > > > > > and since yours is family 15h, it should work. Maybe that > > > > > assumption > > > > > was wrong? > > > > > > > > > > -ml > > > > > > > > > > > > > The Host's CPU is FX-8350 ,so you assumed right. Yet, I am new to > > > > openBSD so I have no clue what approach to be taken. > > > > > > > > Strahil > > > > > > Maybe a BIOS update is available? The date on yours is 2014. Maybe > > > they > > > added that MSR after? > > > > > > > As brynet@ pointed out in a later reply, BIOS update probably won't > > help. > > > > -ml > > > > BIOS update is unavailable, yet the microcode patch_level is > '0x06000852'. The kernel is: 3.10.0-862.3.3.el7.x86_64 > > Any kernel parameters to disable the mitigations and still leave the > CPU at Opteron_G5 ? > > Strahil > Not from the OpenBSD side. -ml
Re: amd64.iso KVM guest kernel panic pc=ffffffff811c303c (Opteron_G3 to Opteron_G5)
On Mon, 2018-10-22 at 10:27 -0700, Mike Larkin wrote: > On Mon, Oct 22, 2018 at 10:13:14AM -0700, Mike Larkin wrote: > > On Mon, Oct 22, 2018 at 08:01:13PM +0300, snikolov wrote: > > > > This appears to be related to the LFENCE serializing MSR change > > > > that > > > > went in > > > > during the last round of side channel analysis fixes: > > > > > > > > 811c3037: b9 29 10 01 > > > > c0 mov$0xc0011029,%ecx > > > > 811c303c: 0f 32 rdmsr > > > > > > > > According to the commit, "This MSR is available on all AMD > > > > families > > > > > = 10h...", > > > > > > > > and since yours is family 15h, it should work. Maybe that > > > > assumption > > > > was wrong? > > > > > > > > -ml > > > > > > > > > > The Host's CPU is FX-8350 ,so you assumed right. Yet, I am new to > > > openBSD so I have no clue what approach to be taken. > > > > > > Strahil > > > > Maybe a BIOS update is available? The date on yours is 2014. Maybe > > they > > added that MSR after? > > > > As brynet@ pointed out in a later reply, BIOS update probably won't > help. > > -ml > BIOS update is unavailable, yet the microcode patch_level is '0x06000852'. The kernel is: 3.10.0-862.3.3.el7.x86_64 Any kernel parameters to disable the mitigations and still leave the CPU at Opteron_G5 ? Strahil
Re: amd64.iso KVM guest kernel panic pc=ffffffff811c303c (Opteron_G3 to Opteron_G5)
On Mon, Oct 22, 2018 at 10:13:14AM -0700, Mike Larkin wrote: > On Mon, Oct 22, 2018 at 08:01:13PM +0300, snikolov wrote: > > > This appears to be related to the LFENCE serializing MSR change that > > > went in > > > during the last round of side channel analysis fixes: > > > > > > 811c3037: b9 29 10 01 > > > c0 mov$0xc0011029,%ecx > > > 811c303c: 0f 32 rdmsr > > > > > > According to the commit, "This MSR is available on all AMD families > > > >= 10h...", > > > and since yours is family 15h, it should work. Maybe that assumption > > > was wrong? > > > > > > -ml > > > > > The Host's CPU is FX-8350 ,so you assumed right. Yet, I am new to > > openBSD so I have no clue what approach to be taken. > > > > Strahil > > Maybe a BIOS update is available? The date on yours is 2014. Maybe they > added that MSR after? > As brynet@ pointed out in a later reply, BIOS update probably won't help. -ml
Re: phonetic alphabet on OpenBSD
Chris Bennett: > When I last looked, apparently IPA had two fonts, neither of which > worked for all the characters. Is this still true? You don't need extra fonts. IPA is covered both by Deja Vu that OpenBSD ships as the default TrueType font, as well as xterm's default bitmap font. > I have to ask also, is the audio quality that comes out the speakers (in > general) good enough to learn the proper sounds? Every device I have > seems to have wildly varying qualities and characteristics. > For example, (OK, not OpenBSD but somewhat relevant) if I wanted to > listen to the speech coming out of Google Translate, would a native > speaker of say Spanish, German or Russian consider the sounds "proper"? What a bizarre question. Listen to English dialog from your speaker setup. Does it sound like "proper" English? Anything that plays music in reasonable quality--so *anything*, really--will more than do for human speech. Google Translate's audio is machine-generated text-to-speech output. Again, check what it does for English. > Is there any software that makes proper sounds available (to port, I'm > too poor to buy non-free)? You might find this interactive IPA chart useful: http://www.ipachart.com/ > Haven't yet seen a class offering: > "How to correct your pronunciation years later to sound normal" That's the work of speech therapists and dialect coaches. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: amd64.iso KVM guest kernel panic pc=ffffffff811c303c (Opteron_G3 to Opteron_G5)
On Mon, Oct 22, 2018 at 08:01:13PM +0300, snikolov wrote: > > This appears to be related to the LFENCE serializing MSR change that > > went in > > during the last round of side channel analysis fixes: > > > > 811c3037: b9 29 10 01 > > c0 mov$0xc0011029,%ecx > > 811c303c: 0f 32 rdmsr > > > > According to the commit, "This MSR is available on all AMD families > > >= 10h...", > > and since yours is family 15h, it should work. Maybe that assumption > > was wrong? > > > > -ml > > > The Host's CPU is FX-8350 ,so you assumed right. Yet, I am new to > openBSD so I have no clue what approach to be taken. > > Strahil Maybe a BIOS update is available? The date on yours is 2014. Maybe they added that MSR after?
Re: amd64.iso KVM guest kernel panic pc=ffffffff811c303c (Opteron_G3 to Opteron_G5)
On Mon, Oct 22, 2018 at 09:49:54AM -0700, Mike Larkin wrote: > On Mon, Oct 22, 2018 at 07:09:21AM +0300, snikolov wrote: > > Dear All, > > > > I have managed to configure and get the output of the serial console on > > KVM and here is the output (with different CPU type only the name of > > the CPU changes) : > > ~~ > > >> OpenBSD/amd64 CDBOOT 3.40 > > boot> > > cannot open cd0a:/etc/random.seed: No such file or directory > > booting cd0a:/6.4/amd64/bsd.rd: 354+1500160+3892040+0+598016 > > [372715+111+441072+293323]=0xa208a0 > > entry point at 0x1000158 > > Copyright (c) 1982, 1986, 1989, 1991, 1993 > > The Regents of the University of California. All rights > > reserved. > > Copyright (c) 1995-2018 OpenBSD. All rights reserved. https://www.Open > > BSD.org > > > > OpenBSD 6.4 (RAMDISK_CD) #348: Thu Oct 11 13:36:16 MDT 2018 > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_C > > D > > real mem = 4278030336 (4079MB) > > avail mem = 4144590848 (3952MB) > > mainbus0 at root > > bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xf6110 (11 entries) > > bios0: vendor SeaBIOS version "1.11.0-2.el7" date 04/01/2014 > > bios0: Red Hat KVM > > acpi0 at bios0: rev 0 > > acpi0: tables DSDT FACP APIC > > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > > cpu0 at mainbus0: apid 0 (boot processor) > > cpu0: AMD Opteron 63xx class CPU, 3992.09 MHz, 15-02-00 > > cpu0: > > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36 > > ,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,PCLMUL,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,x2A > > PIC,POPCNT,AES,XSAVE,AVX,F16C,HV,NXE,PAGE1GB,LONG,LAHF,ABM,SSE4A,MASSE, > > 3DNOWP,XOP,FMA4,TBM > > cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB > > 64b/line 16-way L2 cache, 16MB 64b/line 16-way L3 cache > > cpu0: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped > > cpu0: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped > > fatal protection fault in supervisor mode > > trap type 4 code 0 rip 811c303c cs 8 rflags 10202 cr2 0 cpl e > > rsp 81a06a20 > > gsbase 0x81872ff0 kgsbase 0x0 > > panic: trap type 4, code=0, pc=811c303c > > > > The operating system has halted. > > Please press any key to reboot. > > ~~ > > > > Should I report this as a bug ? > > > > Best Regards, > > Strahil Nikolov > > > > > > On Sun, 2018-10-21 at 18:07 +0300, snikolov wrote: > > > Hello All, > > > > > > During install of install64.iso I experience a kernel panic during > > > boot of the CD (pc=811c303c). > > > install64.iso sha256sum is > > > 81833b79e23dc0f961ac5fb34484bca66386deb3181ddb8236870fa4f488cdd2 > > > which > > > matches https://cdn.openbsd.org/pub/OpenBSD/6.4/amd64/SHA256 > > > > > > I have tested with various CPUs on my RHEL 7.5 and it seems that > > > Opteron_G3/G4/G5 and FX-8350 (host-passthrough) causes the > > > panic,while > > > Opteron_G1/G2 is OK. Booting install63.iso on the same VM is OK and I > > > got the installer prompt. > > > > > > Does anyone observes the same behaviour or it is only me ? > > > > > > Best Regards, > > > Strahil Nikolov > > > > This appears to be related to the LFENCE serializing MSR change that went in > during the last round of side channel analysis fixes: > > 811c3037: b9 29 10 01 c0 mov$0xc0011029,%ecx > 811c303c: 0f 32 rdmsr > > According to the commit, "This MSR is available on all AMD families >= > 10h...", > and since yours is family 15h, it should work. Maybe that assumption was > wrong? > > -ml This appears to be another case of an outdated host kernel / KVM combination. If you tried to boot OpenBSD on the bare hardware, it wouldn't panic. We're following AMD's recommendation here, as far as can tell. https://marc.info/?l=openbsd-misc=153315801921789=2 -Bryan.
Re: amd64.iso KVM guest kernel panic pc=ffffffff811c303c (Opteron_G3 to Opteron_G5)
> This appears to be related to the LFENCE serializing MSR change that > went in > during the last round of side channel analysis fixes: > > 811c3037: b9 29 10 01 > c0 mov$0xc0011029,%ecx > 811c303c: 0f 32 rdmsr > > According to the commit, "This MSR is available on all AMD families > >= 10h...", > and since yours is family 15h, it should work. Maybe that assumption > was wrong? > > -ml > The Host's CPU is FX-8350 ,so you assumed right. Yet, I am new to openBSD so I have no clue what approach to be taken. Strahil
Re: amd64.iso KVM guest kernel panic pc=ffffffff811c303c (Opteron_G3 to Opteron_G5)
On Mon, Oct 22, 2018 at 07:09:21AM +0300, snikolov wrote: > Dear All, > > I have managed to configure and get the output of the serial console on > KVM and here is the output (with different CPU type only the name of > the CPU changes) : > ~~ > >> OpenBSD/amd64 CDBOOT 3.40 > boot> > cannot open cd0a:/etc/random.seed: No such file or directory > booting cd0a:/6.4/amd64/bsd.rd: 354+1500160+3892040+0+598016 > [372715+111+441072+293323]=0xa208a0 > entry point at 0x1000158 > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights > reserved. > Copyright (c) 1995-2018 OpenBSD. All rights reserved. https://www.Open > BSD.org > > OpenBSD 6.4 (RAMDISK_CD) #348: Thu Oct 11 13:36:16 MDT 2018 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_C > D > real mem = 4278030336 (4079MB) > avail mem = 4144590848 (3952MB) > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xf6110 (11 entries) > bios0: vendor SeaBIOS version "1.11.0-2.el7" date 04/01/2014 > bios0: Red Hat KVM > acpi0 at bios0: rev 0 > acpi0: tables DSDT FACP APIC > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: AMD Opteron 63xx class CPU, 3992.09 MHz, 15-02-00 > cpu0: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36 > ,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,PCLMUL,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,x2A > PIC,POPCNT,AES,XSAVE,AVX,F16C,HV,NXE,PAGE1GB,LONG,LAHF,ABM,SSE4A,MASSE, > 3DNOWP,XOP,FMA4,TBM > cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB > 64b/line 16-way L2 cache, 16MB 64b/line 16-way L3 cache > cpu0: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped > cpu0: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped > fatal protection fault in supervisor mode > trap type 4 code 0 rip 811c303c cs 8 rflags 10202 cr2 0 cpl e > rsp 81a06a20 > gsbase 0x81872ff0 kgsbase 0x0 > panic: trap type 4, code=0, pc=811c303c > > The operating system has halted. > Please press any key to reboot. > ~~ > > Should I report this as a bug ? > > Best Regards, > Strahil Nikolov > > > On Sun, 2018-10-21 at 18:07 +0300, snikolov wrote: > > Hello All, > > > > During install of install64.iso I experience a kernel panic during > > boot of the CD (pc=811c303c). > > install64.iso sha256sum is > > 81833b79e23dc0f961ac5fb34484bca66386deb3181ddb8236870fa4f488cdd2 > > which > > matches https://cdn.openbsd.org/pub/OpenBSD/6.4/amd64/SHA256 > > > > I have tested with various CPUs on my RHEL 7.5 and it seems that > > Opteron_G3/G4/G5 and FX-8350 (host-passthrough) causes the > > panic,while > > Opteron_G1/G2 is OK. Booting install63.iso on the same VM is OK and I > > got the installer prompt. > > > > Does anyone observes the same behaviour or it is only me ? > > > > Best Regards, > > Strahil Nikolov > This appears to be related to the LFENCE serializing MSR change that went in during the last round of side channel analysis fixes: 811c3037: b9 29 10 01 c0 mov$0xc0011029,%ecx 811c303c: 0f 32 rdmsr According to the commit, "This MSR is available on all AMD families >= 10h...", and since yours is family 15h, it should work. Maybe that assumption was wrong? -ml
Re: ospfd fib and kernel fib
On Mon, Oct 22, 2018 at 08:48:28AM +0200, open...@kene.nu wrote:
> Hello,
>
> I am having trouble with ospfd not updating the kernel fib as it
> should (I think). This is in my lab environment on vagrant.
>
> host# uname -a
> OpenBSD host 6.4 GENERIC.MP#329 amd64
> host# ospfctl sh rib | grep 172.29.21.2
> 172.29.21.2/32 172.29.2.10 Intra-Area Network 20 00:03:12
> host# ospfctl sh fib | grep 172.29.21.2
> *O 32 172.29.21.2/32 172.29.2.10
> host# netstat -rn | grep 172.29.21.2
> host# cat /etc/ospfd.conf
> router-id 172.29.23.2
>
> area 0.0.0.0 {
> auth-type crypt
> auth-md 1 "one"
> auth-md 2 "two"
> auth-md-keyid 1
> }
Is this the config that was active while you produced above outputs?
It does not contain any interface statements.
>
> So, what is going on? The route is in the ospfd fib but not in the
> kernel fib. I understand that the next hop must be reachable, and it
> is. Other than that I have no idea what qualifies a route to be
> propagated from ospf fib to kernel fib.
>
Re: pf keep sate
It is due to history. ipf didn't have stateful, at all. the first version of pf didn't have stateful, but it was incrementally added starting after 1 year over a period of 3 years. during development, it was not the default. other projects started adopting pf. (here is where it ges ugly) Along with many other advances, stateful was made the default. but other projects kept their old code, or performed partial updates of the code, or didn't change the defaults like we did therefore the lack of unification in the ecosystem can be directly blamed on those other projects who adopted our code, but soon abandoned efforts to keep things updated. but there is another piece of blame which can be apportioned i suppose -- a wise man does not assume that one system is the same as another, and reads the MODERN documentation rather than something dated off the web. Keeping things identical takes much effort, and one should not assume the work was done. > Thanks for your answer. > > The disturbing thing for me was that I work on several firewalls, and some > have the flags S/SA keep state options, and some not… so as I’m quite new to > pf I was really wondering. > > f.g. > > > Le 22 oct. 2018 à 17:09, Daniel Corbe a écrit : > > > > at 10:04 AM, Frédéric Goudal wrote: > > > >> - is there any reason to add keep state to a pass rule ? > > > > 1) UDP rules don’t keep state by default. > > > > 2) Even for TCP connections, it’s better to explicitly throw a keep state > > on there for clarity, so that people who come in behind you and actually > > bother reading the documentation don’t have to ask the same question. > > There’s also other available options for TCP connections that you might > > want to look into, such as flags S/SA (only allow initial handshake between > > endpoints that don’t have an established state) and modulate state, which > > generates strong, random ISNs for new connections. > > > > > > > > > > > > >
Re: pf keep sate
Thanks for your answer. The disturbing thing for me was that I work on several firewalls, and some have the flags S/SA keep state options, and some not… so as I’m quite new to pf I was really wondering. f.g. > Le 22 oct. 2018 à 17:09, Daniel Corbe a écrit : > > at 10:04 AM, Frédéric Goudal wrote: > >> - is there any reason to add keep state to a pass rule ? > > 1) UDP rules don’t keep state by default. > > 2) Even for TCP connections, it’s better to explicitly throw a keep state on > there for clarity, so that people who come in behind you and actually bother > reading the documentation don’t have to ask the same question. There’s also > other available options for TCP connections that you might want to look into, > such as flags S/SA (only allow initial handshake between endpoints that don’t > have an established state) and modulate state, which generates strong, random > ISNs for new connections. > > > > > >
Re: pf keep sate
Daniel Corbe(dco...@hammerfiber.com) on 2018.10.22 11:09:08 -0400: > at 10:04 AM, Fr??d??ric Goudal wrote: > > >- is there any reason to add keep state to a pass rule ? Only if you want to use one of the "Stateful Tracking Options" (see pf.conf(5)). For example, to add no-sync (dont send the state via pfsync(4)) you would add "keep state (no-sync)" to a rule: pass in proto tcp from any to any port www keep state (no-sync) (Of course you would only consider this if you actually have a pfsync(4) interface configured). > 1) UDP rules don???t keep state by default. Yes, they do. > 2) Even for TCP connections, it???s better to explicitly throw a keep state > on there for clarity, so that people who come in behind you and actually > bother reading the documentation don???t have to ask the same question. Thats a matter of taste, but i prefer not to read and write a useless "keep state" on every line. > There???s also other available options for TCP connections that you might > want to look into, such as flags S/SA (only allow initial handshake between > endpoints that don???t have an established state) which is the default too. > and modulate state, which generates strong, random ISNs for new connections. > > > > > --
Re: pf keep sate
at 10:04 AM, Frédéric Goudal wrote: - is there any reason to add keep state to a pass rule ? 1) UDP rules don’t keep state by default. 2) Even for TCP connections, it’s better to explicitly throw a keep state on there for clarity, so that people who come in behind you and actually bother reading the documentation don’t have to ask the same question. There’s also other available options for TCP connections that you might want to look into, such as flags S/SA (only allow initial handshake between endpoints that don’t have an established state) and modulate state, which generates strong, random ISNs for new connections.
pf keep sate
Hello, There is something that I don’t really understand about pf keep state : - documentation says : All pass rules automatically create a state entry when a packet matches the rule. This can be explicitly disabled by using the no state option. But… I find a lot of example on the web that add the keep state on tcp pass rules, and what is worse, I have to work on a production firewall that has such rules, so I can’t test. So my question is - is there any reason to add keep state to a pass rule ? Thanks. f.g.
dmesg for Edgeouter Lite
Upgraded my ERL to 6.4 release from 6.4-beta (snapshot was downloaded and installed 9/27/18) and only ran into a minor snag regarding unbound. I recently enabled DNS-over-TLS and DNSSEC on my unbound machines and while the upgrade to 6.4 release went without a problem on my apu2, the lack of a hardware clock on the ERL rendered unbound non-responsive due to DNSSEC requiring accurate time to verify the root key signature. This was an oversight on my part, as I didn't enable a secondary DNS server for the ERL to talk to beyond itself. So, if you are using DNSSEC, remember to have a secondary DNS server, or perhaps put IP addresses instead of server names for NTP, in order to not be bit by this. This machine acts as primary DNS server for management network, and secondary DNS server for home network. dmesg to follow. Thanks to the OpenBSD team! Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2018 OpenBSD. All rights reserved. https://www.OpenBSD.org OpenBSD 6.4 (GENERIC.MP) #0: Sat Oct 13 03:52:37 UTC 2018 visa@octeon:/usr/src/sys/arch/octeon/compile/GENERIC.MP real mem = 536870912 (512MB) avail mem = 523796480 (499MB) mainbus0 at root: board 20002 rev 2.18 cpu0 at mainbus0: CN50xx CPU rev 0.1 500 MHz, Software FP emulation cpu0: cache L1-I 32KB 4 way D 16KB 64 way, L2 128KB 8 way cpu1 at mainbus0: CN50xx CPU rev 0.1 500 MHz, Software FP emulation cpu1: cache L1-I 32KB 4 way D 16KB 64 way, L2 128KB 8 way clock0 at mainbus0: int 5 octcrypto0 at mainbus0 iobus0 at mainbus0 simplebus0 at iobus0: "soc" octciu0 at simplebus0 cn30xxsmi0 at simplebus0 com0 at simplebus0: ns16550a, 64 byte fifo com0: console dwctwo0 at iobus0 base 0x118006800 irq 56 usb0 at dwctwo0: USB revision 2.0 uhub0 at usb0 configuration 1 interface 0 "Octeon DWC2 root hub" rev 2.00/1.00 addr 1 octrng0 at iobus0 base 0x14000 irq 0 cn30xxgmx0 at iobus0 base 0x118000800 cnmac0 at cn30xxgmx0: RGMII, address 44:d9:e7:40:b5:c8 atphy0 at cnmac0 phy 7: AR8035 10/100/1000 PHY, rev. 2 cnmac1 at cn30xxgmx0: RGMII, address 44:d9:e7:40:b5:c9 atphy1 at cnmac1 phy 6: AR8035 10/100/1000 PHY, rev. 2 cnmac2 at cn30xxgmx0: RGMII, address 44:d9:e7:40:b5:ca atphy2 at cnmac2 phy 5: AR8035 10/100/1000 PHY, rev. 2 /dev/ksyms: Symbol table not valid. umass0 at uhub0 port 1 configuration 1 interface 0 "Lexar USB Flash Drive" rev 2.10/11.00 addr 2 umass0: using SCSI over Bulk-Only scsibus0 at umass0: 2 targets, initiator 0 sd0 at scsibus0 targ 1 lun 0: SCSI4 0/direct removable serial.05dca83aZB0L2W63LA4P sd0: 30526MB, 512 bytes/sector, 62517248 sectors vscsi0 at root scsibus1 at vscsi0: 256 targets softraid0 at root scsibus2 at softraid0: 256 targets boot device: sd0 root on sd0a (fb74a192b03ee90f.a) swap on sd0b dump on sd0b WARNING: No TOD clock, believing file system. WARNING: CHECK AND RESET THE DATE!
dmesg for apu2
Hello all. Upgraded my apu2 to 6.4 release from 6.4-beta (snapshot was from 9/27/18) and everything went flawlessly. This machine acts as DHCP server for two networks, primary DNS server for one, and is ready to be pressed into service as a gateway machine if necessary. dmesg to follow. Thanks to everyone on the OpenBSD team! OpenBSD 6.4 (GENERIC.MP) #364: Thu Oct 11 13:30:23 MDT 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 1996152832 (1903MB) avail mem = 1926451200 (1837MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0x77fb7020 (7 entries) bios0: vendor coreboot version "88a4f96" date 03/07/2016 bios0: PC Engines apu2 acpi0 at bios0: rev 2 acpi0: sleep states S0 S1 S2 S3 S4 S5 acpi0: tables DSDT FACP SSDT APIC HEST SSDT SSDT HPET acpi0: wakeup devices PWRB(S4) PBR4(S4) PBR5(S4) PBR6(S4) PBR7(S4) PBR8(S4) UOH1(S3) UOH3(S3) UOH5(S3) XHC0(S4) acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD GX-412TC SOC, 998.27 MHz, 16-30-01 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TOPEXT,DBKP,PERFTSC,PCTRL3,ITSC,BMI1,XSAVEOPT cpu0: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 2MB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: AMD GX-412TC SOC, 998.15 MHz, 16-30-01 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TOPEXT,DBKP,PERFTSC,PCTRL3,ITSC,BMI1,XSAVEOPT cpu1: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 2MB 64b/line 16-way L2 cache cpu1: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu1: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 2 (application processor) cpu2: AMD GX-412TC SOC, 998.15 MHz, 16-30-01 cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TOPEXT,DBKP,PERFTSC,PCTRL3,ITSC,BMI1,XSAVEOPT cpu2: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 2MB 64b/line 16-way L2 cache cpu2: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu2: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: AMD GX-412TC SOC, 998.16 MHz, 16-30-01 cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TOPEXT,DBKP,PERFTSC,PCTRL3,ITSC,BMI1,XSAVEOPT cpu3: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 2MB 64b/line 16-way L2 cache cpu3: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu3: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative cpu3: smt 0, core 3, package 0 ioapic0 at mainbus0: apid 4 pa 0xfec0, version 21, 24 pins ioapic1 at mainbus0: apid 5 pa 0xfec2, version 21, 32 pins, remapped acpihpet0 at acpi0: 14318180 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PBR4) acpiprt2 at acpi0: bus 1 (PBR5) acpiprt3 at acpi0: bus 2 (PBR6) acpiprt4 at acpi0: bus 3 (PBR7) acpiprt5 at acpi0: bus -1 (PBR8) acpicpu0 at acpi0: C2(0@400 io@0x1771), C1(@1 halt!), PSS acpicpu1 at acpi0: C2(0@400 io@0x1771), C1(@1 halt!), PSS acpicpu2 at acpi0: C2(0@400 io@0x1771), C1(@1 halt!), PSS acpicpu3 at acpi0: C2(0@400 io@0x1771), C1(@1 halt!), PSS acpibtn0 at acpi0: PWRB acpicmos0 at acpi0 cpu0: 998 MHz: speeds: 1000 800 600 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "AMD AMD64 16h Root Complex" rev 0x00 pchb1 at pci0 dev 2 function 0 "AMD AMD64 16h Host" rev 0x00 ppb0 at pci0 dev 2 function 2 "AMD AMD64 16h PCIE" rev 0x00: msi pci1 at ppb0 bus 1 em0 at pci1 dev 0 function 0 "Intel I211" rev 0x03: msi, address 00:0d:b9:43:19:88 ppb1 at
Re: relayd and radius
On 19/10/18 21:01, Shawn Southern wrote:
> So apparently this works... I was expecting relayd to listen on those ports,
> but I'm guessing that since it hooks through pf, that's not necessary.
>
> -Original Message-
> From: owner-m...@openbsd.org On Behalf Of Shawn
> Southern
> Sent: October 19, 2018 1:00 PM
> To: misc@openbsd.org
> Subject: relayd and radius
>
> We have a lot of devices that use RADIUS, but they do not allow us to specify
> a 2nd RADIUS server. Since we use OpenBSD w/ CARP as our router/firewall, we
> want to use relayd to provide some redundancy for the RADIUS servers.
>
> There are two internal subnets - 10.10.10.0/24, which has our servers, and
> 10.10.11.0/24 that has the devices using RADIUS to authenticate clients.
> 10.10.10.1 and 10.10.11.1 are both carp interfaces.
>
> When starting relayd, nothing appears to be listening on the RADIUS ports.
> Is this even possible with relayd? Is my configuration just horribly wrong?
>
> relayd.conf:
> radius1 = "10.10.10.5"
> radius2 = "10.10.10.6"
> radius_listen = "10.10.11.1"
>
> table { $radius1 }
> table { $radius2 }
>
> redirect radius {
> listen on $radius_listen udp port 1812:1813
> forward to check icmp
> forward to check icmp
> }
>
> Thanks in advance for any help!
>
Yes, relayd adds rdr-to rules in pf. No port listening.
You should check your configuration
I believe it should be
table { $radius1, $radius2 }
and then on redirect: forward to check icmp
G
Re: bgp match to $neighbor set nexthop $carp_ip on 6.4
On Mon, Oct 22, 2018 at 01:17:30PM +0200, Marko Cupa? wrote:
> Hi,
>
> I am struggling to announce nexthop to my bgp peers after default
> ruleset change in 6.4's bgpd.conf.
>
> On 6.3, I used to have:
>
> match to $ISP1 set nexthop $CARP_TO_ISP1
> match to $ISP2 set nexthop $CARP_TO_ISP2
> deny from ebgp
> deny to ebgp
> allow to { $ISP1 $ISP2 }
> allow from ibgp
> allow to ibgp
> (...defaults...)
>
>
> I like the idea of having my simple ruleset done with minimal override
> to defaults. Moreover, I see that slapping above ruleset to 6.4 does
> not work the same as on 6.3 (I think I'm sending garbage upstream).
You can check with 'bgpctl show rib out nei $ISP1 detail' what you are
sending. Also tcpdump is able to show you what you are sending.
> Any good soul out there to tell me what to put above:
>
> ### for simple BGP setups, no editing below this line is required ###
>
> ...in order to set nexthop per upstream neighbor, if possible?
The new ruleset has a few deny quick rules in it. Make sure you don't hit
one of those.
It would be helpful to see the full ruleset as shown with 'bgpd -nv'
--
:wq Claudio
bgp match to $neighbor set nexthop $carp_ip on 6.4
Hi,
I am struggling to announce nexthop to my bgp peers after default
ruleset change in 6.4's bgpd.conf.
On 6.3, I used to have:
match to $ISP1 set nexthop $CARP_TO_ISP1
match to $ISP2 set nexthop $CARP_TO_ISP2
deny from ebgp
deny to ebgp
allow to { $ISP1 $ISP2 }
allow from ibgp
allow to ibgp
(...defaults...)
I like the idea of having my simple ruleset done with minimal override
to defaults. Moreover, I see that slapping above ruleset to 6.4 does
not work the same as on 6.3 (I think I'm sending garbage upstream).
Any good soul out there to tell me what to put above:
### for simple BGP setups, no editing below this line is required ###
...in order to set nexthop per upstream neighbor, if possible?
Thank you in advance,
--
Before enlightenment - chop wood, draw water.
After enlightenment - chop wood, draw water.
Marko Cupać
https://www.mimar.rs/
Re: Libreoffice package missing in i386 tree
On Mon, Oct 22, 2018 at 10:03:44AM +0200, Peter Hessler wrote: > Packages for i386 are finalized and are uploaded to the mirrors. What > you see, is what was built. > > > On 2018 Oct 22 (Mon) at 08:15:18 +0300 (+0300), Kihaguru Gathura wrote: > :Hi, > : > :Is the LibreOffice package in the i386 tree expected for OpenBSD 6.4? > :not listed the mirrors so far. > : > :Kihaguru > : BROKEN-i386=undefined refs to operator new/delete in libuno_cppuhelpergcc3.so (since 27-aug-17) seems like nobody found/looked for a solution since then. Sorry. -- Marc
Re: Graphical debugger for C/C++ ?
On 10/21/18 4:49 PM, Edgar Pettijohn III wrote: I wanted to give cgdb a shot. How do I make sure its using egdb? cgdb --help cgdb -d egdb
Re: Problem with keyboard layout
Am 10/22/18 um 9:57 AM schrieb Stefan Wollny: [ ... ] > > $ cat /etc/wsconsctl.conf | grep encoding > keyboard.encoding=de# use different keyboard encoding > > Yet this setting seems not to be recognized: > $ doas wsconsctl | grep encoding > keyboard.encoding=unknown_0 > [ ... ] Additional information: This issue seems to be related to the X server. Initially I noticed this behaviour when starting with xenodm. Switching to a console outside of X gives me the expected German keyboard layout. The same if I disable xenodm in /etc/rc.conf.local and start OpenBSD into a console: Initially I have the German keyboard layout but once I start X via 'startx' I get the US layout. *At least I know now where to find the symbols blindly :/ * Thus here is the Xorg.0.log which has the line Option "XkbLayout" "us" close to the end. [ 536.726] (WW) checkDevMem: failed to open /dev/xf86 and /dev/mem (Operation not permitted) Check that you have set 'machdep.allowaperture=1' in /etc/sysctl.conf and reboot your machine refer to xf86(4) for details [ 536.726]linear framebuffer access unavailable [ 536.740] (--) Using wscons driver on /dev/ttyC4 [ 536.748] X.Org X Server 1.19.6 Release Date: 2017-12-20 [ 536.748] X Protocol Version 11, Revision 0 [ 536.748] Build Operating System: OpenBSD 6.4 amd64 [ 536.748] Current Operating System: OpenBSD asterix.heim.netz 6.4 GENERIC.MP#376 amd64 [ 536.748] Build Date: 21 October 2018 11:05:48PM [ 536.748] [ 536.748] Current version of pixman: 0.34.0 [ 536.749]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 536.749] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 536.749] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Oct 22 10:32:24 2018 [ 536.749] (==) Using system config directory "/usr/X11R6/share/X11/xorg.conf.d" [ 536.749] (==) No Layout section. Using the first Screen section. [ 536.749] (==) No screen section available. Using defaults. [ 536.749] (**) |-->Screen "Default Screen Section" (0) [ 536.749] (**) | |-->Monitor "" [ 536.749] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 536.749] (==) Automatically adding devices [ 536.749] (==) Automatically enabling devices [ 536.749] (==) Not automatically adding GPU devices [ 536.749] (==) Max clients allowed: 256, resource mask: 0x1f [ 536.749] (==) FontPath set to: /usr/X11R6/lib/X11/fonts/misc/, /usr/X11R6/lib/X11/fonts/TTF/, /usr/X11R6/lib/X11/fonts/OTF/, /usr/X11R6/lib/X11/fonts/Type1/, /usr/X11R6/lib/X11/fonts/100dpi/, /usr/X11R6/lib/X11/fonts/75dpi/ [ 536.749] (==) ModulePath set to "/usr/X11R6/lib/modules" [ 536.749] (II) The server relies on wscons to provide the list of input devices. If no devices become available, reconfigure wscons or disable AutoAddDevices. [ 536.749] (II) Loader magic: 0x1c454c971000 [ 536.749] (II) Module ABI versions: [ 536.749]X.Org ANSI C Emulation: 0.4 [ 536.749]X.Org Video Driver: 23.0 [ 536.749]X.Org XInput driver : 24.1 [ 536.749]X.Org Server Extension : 10.0 [ 536.749] (--) PCI:*(0:0:2:0) 8086:0416:1558:0655 rev 6, Mem @ 0xf780/4194304, 0xe000/268435456, I/O @ 0xf000/64 [ 536.749] (II) LoadModule: "glx" [ 536.750] (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so [ 536.752] (II) Module glx: vendor="X.Org Foundation" [ 536.752]compiled for 1.19.6, module version = 1.0.0 [ 536.752]ABI class: X.Org Server Extension, version 10.0 [ 536.752] (==) Matched modesetting as autoconfigured driver 0 [ 536.752] (==) Assigned the driver to the xf86ConfigLayout [ 536.752] (II) LoadModule: "modesetting" [ 536.752] (II) Loading /usr/X11R6/lib/modules/drivers/modesetting_drv.so [ 536.752] (II) Module modesetting: vendor="X.Org Foundation" [ 536.752]compiled for 1.19.6, module version = 1.19.6 [ 536.752]Module class: X.Org Video Driver [ 536.752]ABI class: X.Org Video Driver, version 23.0 [ 536.752] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [ 536.753] (**) modeset(0): claimed PCI slot 0@0:2:0 [ 536.753] (II) modeset(0): using default device [ 536.753] (II) modeset(0): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 24/32 [ 536.753] (==) modeset(0): Depth 24, (==) framebuffer bpp 32 [ 536.753] (==) modeset(0): RGB weight 888 [ 536.753] (==) modeset(0): Default visual is TrueColor [ 536.753] (II) Loading sub module "glamoregl" [ 536.753] (II) LoadModule: "glamoregl" [ 536.754] (II) Loading /usr/X11R6/lib/modules/libglamoregl.so [ 536.761] (II) Module glamoregl:
Re: Libreoffice package missing in i386 tree
Packages for i386 are finalized and are uploaded to the mirrors. What you see, is what was built. On 2018 Oct 22 (Mon) at 08:15:18 +0300 (+0300), Kihaguru Gathura wrote: :Hi, : :Is the LibreOffice package in the i386 tree expected for OpenBSD 6.4? :not listed the mirrors so far. : :Kihaguru : -- "His great aim was to escape from civilization, and, as soon as he had money, he went to Southern California."
Problem with keyboard layout
Hi there! I have reported this a few days ago on bugs but the issue seemed to be solved with amd64/current as of Sunday morning but reappeared on Sunday afternoons version (German time). System is OpenBSD 6.4-current (GENERIC.MP) #375: Sun Oct 21 09:29:13 MDT 2018 (full dmesg at the end) $ cat .profile | grep LC export LC_CTYPE="de_DE.UTF-8" ~ $ locale LANG=de_DE.UTF-8 LC_COLLATE="de_DE.UTF-8" LC_CTYPE=de_DE.UTF-8 LC_MONETARY="de_DE.UTF-8" LC_NUMERIC="de_DE.UTF-8" LC_TIME="de_DE.UTF-8" LC_MESSAGES="de_DE.UTF-8" LC_ALL= $ cat /etc/wsconsctl.conf | grep encoding keyboard.encoding=de# use different keyboard encoding Yet this setting seems not to be recognized: $ doas wsconsctl | grep encoding keyboard.encoding=unknown_0 Trying to do $ doas wsconsctl keyboard.encoding=de drops the system into ddb without access to the keyboard (thus it is not possible to type 'trace'... ) Is this s.th. known? How to proceed? Best, STEFAN OpenBSD 6.4-current (GENERIC.MP) #375: Sun Oct 21 09:29:13 MDT 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17079074816 (16287MB) avail mem = 16552185856 (15785MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb500 (35 entries) bios0: vendor American Megatrends Inc. version "1.03.06" date 06/25/2014 bios0: Notebook W65_67SZ acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT ASF! SSDT SSDT SSDT MCFG HPET SSDT SSDT SSDT DMAR acpi0: wakeup devices PXSX(S4) RP01(S4) PXSX(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) GLAN(S4) EHC1(S3) EHC2(S3) XHC_(S3) HDEF(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz, 3093.31 MHz, 06-3c-03 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz, 3092.84 MHz, 06-3c-03 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz, 3092.83 MHz, 06-3c-03 cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 1, core 0, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz, 3092.83 MHz, 06-3c-03 cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 acpimcfg0: addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (RP01) acpiprt2 at acpi0: bus 3 (RP03) acpiprt3 at acpi0: bus 4 (RP04) acpiprt4 at acpi0: bus 1 (P0P2) acpiprt5 at acpi0: bus -1 (P0PA) acpiprt6 at acpi0: bus -1 (P0PB) acpiprt7 at acpi0: bus 1 (PEG0) acpiec0 at acpi0 acpicpu0 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1
Re: FAM Question
Hi Julian, Am 22.10.2018 um 01:26 schrieb Julian Suschlik: FAM/gamin execute programs when parts of the filesystem change AFAIK. My goto program for this is entr (http://entrproject.org/) available as port under sysutils/entr (http://ports.su/sysutils/entr) I still don't get what you trying to tell me. I simply need to know how to start gamin as a background process since FAM package isnt arround anymore. Usally there would be some kind of rc script in rc.d somewere but there isnt. There isnt a man page to be found so I'm lost how to get things running. regards -- Markus Rosjatfon: +49 351 8107224mail: ros...@ghweb.de G+H Webservice GbR Gorzolla, Herrmann Königsbrücker Str. 70, 01099 Dresden http://www.ghweb.de fon: +49 351 8107220 fax: +49 351 8107227 Bitte prüfen Sie, ob diese Mail wirklich ausgedruckt werden muss! Before you print it, think about your responsibility and commitment to the ENVIRONMENT
ospfd fib and kernel fib
Hello,
I am having trouble with ospfd not updating the kernel fib as it
should (I think). This is in my lab environment on vagrant.
host# uname -a
OpenBSD host 6.4 GENERIC.MP#329 amd64
host# ospfctl sh rib | grep 172.29.21.2
172.29.21.2/32 172.29.2.10 Intra-Area Network 20 00:03:12
host# ospfctl sh fib | grep 172.29.21.2
*O 32 172.29.21.2/32 172.29.2.10
host# netstat -rn | grep 172.29.21.2
host# cat /etc/ospfd.conf
router-id 172.29.23.2
area 0.0.0.0 {
auth-type crypt
auth-md 1 "one"
auth-md 2 "two"
auth-md-keyid 1
}
So, what is going on? The route is in the ospfd fib but not in the
kernel fib. I understand that the next hop must be reachable, and it
is. Other than that I have no idea what qualifies a route to be
propagated from ospf fib to kernel fib.
