Re: node: Cannot allocate memory
So just to eliminate the off variable I updated my snapshot. Updated packages, etc, etc And now node works fine... Ken On Wed, Jun 06, 2018 at 09:28:39PM -0400, Ken M wrote: > On Wed, Jun 06, 2018 at 09:10:59PM -0400, Thomas Frohwein wrote: > > > > I run ksh. Doubt that bash is the cause though... > > Might wanna check if you have the same problem with ksh. > > > > I tried in sh before submitting and got the same problem, I just tried ksh and > the same. Sorry for omitting that I tried to eliminate bash from the equation > first. > > > > > ... still, you provided rather little information to understand what might > > be > > particular about your system. In most cases, including a dmesg is MVP to > > understand this better. > > > > Sorry, I wasn't thinking a dmesg would be useful in this case. I will put at > the > end of this as well as the kdump from a ktrace on this. > > > > > Yes? what about your ulimit? > > I put myself in the staff user group so... > > $ ulimit -a > core file size (blocks, -c) unlimited > data seg size (kbytes, -d) 2097152 > file size (blocks, -f) unlimited > max locked memory (kbytes, -l) 1244372 > max memory size (kbytes, -m) 3710004 > open files (-n) 512 > pipe size(512 bytes, -p) 1 > stack size (kbytes, -s) 4096 > cpu time (seconds, -t) unlimited > max user processes (-u) 256 > virtual memory (kbytes, -v) 2101248 > > I also tried setting ulimit -d to my total memory size and no luck there. > > kdump of ktrace: > > $ kdump -f kt-node.out > 7097 ktrace RET ktrace 0 > 7097 ktrace CALL execve(0x7f7eb5d0,0x7f7ebb60,0x7f7ebb78) > 7097 ktrace NAMI "/bin/node" > 7097 ktrace RET execve -1 errno 2 No such file or directory > 7097 ktrace CALL execve(0x7f7eb5d0,0x7f7ebb60,0x7f7ebb78) > 7097 ktrace NAMI "/usr/bin/node" > 7097 ktrace RET execve -1 errno 2 No such file or directory > 7097 ktrace CALL execve(0x7f7eb5d0,0x7f7ebb60,0x7f7ebb78) > 7097 ktrace NAMI "/sbin/node" > 7097 ktrace RET execve -1 errno 2 No such file or directory > 7097 ktrace CALL execve(0x7f7eb5d0,0x7f7ebb60,0x7f7ebb78) > 7097 ktrace NAMI "/usr/sbin/node" > 7097 ktrace RET execve -1 errno 2 No such file or directory > 7097 ktrace CALL execve(0x7f7eb5d0,0x7f7ebb60,0x7f7ebb78) > 7097 ktrace NAMI "/usr/X11R6/bin/node" > 7097 ktrace RET execve -1 errno 2 No such file or directory > 7097 ktrace CALL execve(0x7f7eb5d0,0x7f7ebb60,0x7f7ebb78) > 7097 ktrace NAMI "/usr/local/bin/node" > 7097 ktrace RET execve -1 errno 12 Cannot allocate memory > 7097 ktrace CALL mprotect(0xe36158b1000,0x1000,0x3) > 7097 ktrace RET mprotect 0 > 7097 ktrace CALL mprotect(0xe36158b1000,0x1000,0x1) > 7097 ktrace RET mprotect 0 > 7097 ktrace CALL write(2,0x7f7eb1e0,0x8) > 7097 ktrace GIO fd 2 wrote 8 bytes >"ktrace: " > 7097 ktrace RET write 8 > 7097 ktrace CALL write(2,0x7f7eb2c0,0x15) > 7097 ktrace GIO fd 2 wrote 21 bytes >"exec of 'node' failed" > 7097 ktrace RET write 21/0x15 > 7097 ktrace CALL write(2,0x7f7eb1e0,0x2) > 7097 ktrace GIO fd 2 wrote 2 bytes >": " > 7097 ktrace RET write 2 > 7097 ktrace CALL write(2,0x7f7eb1e0,0x17) > 7097 ktrace GIO fd 2 wrote 23 bytes >"Cannot allocate memory >" > 7097 ktrace RET write 23/0x17 > 7097 ktrace CALL mprotect(0xe36158b1000,0x1000,0x3) > 7097 ktrace RET mprotect 0 > 7097 ktrace CALL mprotect(0xe36158b1000,0x1000,0x1) > 7097 ktrace RET mprotect 0 > 7097 ktrace CALL mprotect(0xe36158b1000,0x1000,0x3) > 7097 ktrace RET mprotect 0 > 7097 ktrace CALL mprotect(0xe36158b1000,0x1000,0x1) > 7097 ktrace RET mprotect 0 > 7097 ktrace CALL munmap(0xe36158b1000,0x1000) > 7097 ktrace RET munmap 0 > 7097 ktrace CALL exit(1) > > > dmesg: > > $ dmesg > OpenBSD 6.3-current (GENERIC.MP) #57: Thu May 31 15:57:20 MDT 2018 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 3950682112 (3767MB) > avail mem = 3822796800 (3645MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xdccb3000 (61 entries) > bios0: vendor LENOVO version "GJET98WW (2.48 )" date 03/20/2018 > bios0: LENOVO 20B7S41700 > acpi0 at bios0: rev 2 > acpi0: sleep states S0 S3 S4 S5 > acpi0: tables DSDT FACP SLIC DBGP ECDT HPET APIC MCFG SSDT SSDT SSDT SSDT > SSDT SSDT SSDT SSDT PCCT SSDT UEFI MSDM ASF! BATB FPDT UEFI DMAR > acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP2(S4) XHCI(S3) EHC1(S3) > acpitimer0 at acpi0: 3579545 Hz, 24 bits > acpiec0 at acpi0 > acpihpet0 at acpi0: 14318179 Hz > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0
Re: node: Cannot allocate memory
On Wed, Jun 06, 2018 at 09:10:59PM -0400, Thomas Frohwein wrote: > > I run ksh. Doubt that bash is the cause though... > Might wanna check if you have the same problem with ksh. > I tried in sh before submitting and got the same problem, I just tried ksh and the same. Sorry for omitting that I tried to eliminate bash from the equation first. > > ... still, you provided rather little information to understand what might be > particular about your system. In most cases, including a dmesg is MVP to > understand this better. > Sorry, I wasn't thinking a dmesg would be useful in this case. I will put at the end of this as well as the kdump from a ktrace on this. > > Yes? what about your ulimit? I put myself in the staff user group so... $ ulimit -a core file size (blocks, -c) unlimited data seg size (kbytes, -d) 2097152 file size (blocks, -f) unlimited max locked memory (kbytes, -l) 1244372 max memory size (kbytes, -m) 3710004 open files (-n) 512 pipe size(512 bytes, -p) 1 stack size (kbytes, -s) 4096 cpu time (seconds, -t) unlimited max user processes (-u) 256 virtual memory (kbytes, -v) 2101248 I also tried setting ulimit -d to my total memory size and no luck there. kdump of ktrace: $ kdump -f kt-node.out 7097 ktrace RET ktrace 0 7097 ktrace CALL execve(0x7f7eb5d0,0x7f7ebb60,0x7f7ebb78) 7097 ktrace NAMI "/bin/node" 7097 ktrace RET execve -1 errno 2 No such file or directory 7097 ktrace CALL execve(0x7f7eb5d0,0x7f7ebb60,0x7f7ebb78) 7097 ktrace NAMI "/usr/bin/node" 7097 ktrace RET execve -1 errno 2 No such file or directory 7097 ktrace CALL execve(0x7f7eb5d0,0x7f7ebb60,0x7f7ebb78) 7097 ktrace NAMI "/sbin/node" 7097 ktrace RET execve -1 errno 2 No such file or directory 7097 ktrace CALL execve(0x7f7eb5d0,0x7f7ebb60,0x7f7ebb78) 7097 ktrace NAMI "/usr/sbin/node" 7097 ktrace RET execve -1 errno 2 No such file or directory 7097 ktrace CALL execve(0x7f7eb5d0,0x7f7ebb60,0x7f7ebb78) 7097 ktrace NAMI "/usr/X11R6/bin/node" 7097 ktrace RET execve -1 errno 2 No such file or directory 7097 ktrace CALL execve(0x7f7eb5d0,0x7f7ebb60,0x7f7ebb78) 7097 ktrace NAMI "/usr/local/bin/node" 7097 ktrace RET execve -1 errno 12 Cannot allocate memory 7097 ktrace CALL mprotect(0xe36158b1000,0x1000,0x3) 7097 ktrace RET mprotect 0 7097 ktrace CALL mprotect(0xe36158b1000,0x1000,0x1) 7097 ktrace RET mprotect 0 7097 ktrace CALL write(2,0x7f7eb1e0,0x8) 7097 ktrace GIO fd 2 wrote 8 bytes "ktrace: " 7097 ktrace RET write 8 7097 ktrace CALL write(2,0x7f7eb2c0,0x15) 7097 ktrace GIO fd 2 wrote 21 bytes "exec of 'node' failed" 7097 ktrace RET write 21/0x15 7097 ktrace CALL write(2,0x7f7eb1e0,0x2) 7097 ktrace GIO fd 2 wrote 2 bytes ": " 7097 ktrace RET write 2 7097 ktrace CALL write(2,0x7f7eb1e0,0x17) 7097 ktrace GIO fd 2 wrote 23 bytes "Cannot allocate memory " 7097 ktrace RET write 23/0x17 7097 ktrace CALL mprotect(0xe36158b1000,0x1000,0x3) 7097 ktrace RET mprotect 0 7097 ktrace CALL mprotect(0xe36158b1000,0x1000,0x1) 7097 ktrace RET mprotect 0 7097 ktrace CALL mprotect(0xe36158b1000,0x1000,0x3) 7097 ktrace RET mprotect 0 7097 ktrace CALL mprotect(0xe36158b1000,0x1000,0x1) 7097 ktrace RET mprotect 0 7097 ktrace CALL munmap(0xe36158b1000,0x1000) 7097 ktrace RET munmap 0 7097 ktrace CALL exit(1) dmesg: $ dmesg OpenBSD 6.3-current (GENERIC.MP) #57: Thu May 31 15:57:20 MDT 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 3950682112 (3767MB) avail mem = 3822796800 (3645MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xdccb3000 (61 entries) bios0: vendor LENOVO version "GJET98WW (2.48 )" date 03/20/2018 bios0: LENOVO 20B7S41700 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SLIC DBGP ECDT HPET APIC MCFG SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT PCCT SSDT UEFI MSDM ASF! BATB FPDT UEFI DMAR acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP2(S4) XHCI(S3) EHC1(S3) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-4300U CPU @ 1.90GHz, 798.30 MHz cpu0:
Re: pgrep/pkill in rc script
On 6/4/2018 4:57 PM, Stuart Henderson wrote: pgrep uses regular expressions, so if you're matching the full string you'll need to escape the +'s. The 16-character limit doesn't apply here, that's if you're only matching on the command name. rc.d / pgrep -f match on the full process title instead. Run top(1) and compare before/after pressing C. Ah, that makes sense. Thanks!
Re: node: Cannot allocate memory
I can't reproduce this on -current amd64, neither with a snapshot from last
week, nor after updating today.
thfr@e5570:~$ node -v
v8.11.1
thfr@e5570:~$ node
> console.log('test log');
test log
undefined
> .exit
thfr@e5570:~$
> node -v
> bash: /usr/local/bin/node: Cannot allocate memory
I run ksh. Doubt that bash is the cause though...
Might wanna check if you have the same problem with ksh.
> I am on current, last grabbed the snapshot last Friday I think.
... still, you provided rather little information to understand what might be
particular about your system. In most cases, including a dmesg is MVP to
understand this better.
> Plenty of swap and memory available
Yes? what about your ulimit?
node: Cannot allocate memory
The subject is the problem: node -v bash: /usr/local/bin/node: Cannot allocate memory I am on current, last grabbed the snapshot last Friday I think. Plenty of swap and memory available vmstat procsmemory pagedisk traps cpu r s avm fre flt re pi po fr sr sd0 int sys cs us sy id 1 180 543M 1802M 1263 0 0 0 0 0 38 235 5252 781 3 1 95 swapctl -l Device 512-blocks UsedAvail Capacity Priority /dev/sd0b 82415360 8241536 0%0 Last I checked on a 6.3 release install node was working. Last I checked it was working in 6.3 so not sure what is going on here. Nothing else is giving me any problems. Ken
Re: Reboot loop
There is > com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo in your dmesg. So, I assume your box reports com port somehow (via ACPI probably) Some boxes may have comport built into chipset but no external cable for it. I have one, I bought cable separately. Another option is to use UART that connects to USB
Re: Reboot loop
IL Ka, The problem manifests itself before sysctl.conf is read. CTRL-ALT-ESC won't send a break. Using boot -d will drop me in ddb way too early. This machine doesn't have any means for serial output, no com port. No core is dumped. Can the system panic and still go on in an endless loop? Once in a blue moon the system actually boots. The inescapable loop happens just before it switches to a higher resolution and displays radeondrm0: ... x ... 32bpp (the actual resolution is irrelevant). After detection of the ring 2 test failure. - Mensaje original - De: IL Ka Para: francis dos santos CC: OpenBSD General Misc Enviado: Wed, 06 Jun 2018 16:01:24 -0300 (ART) Asunto: Re: Reboot loop https://www.openbsd.org/report.html See "How to create a problem report" step 5
Re: Reboot loop
Ok, then try to follow Stuart Longland's advice: use serial console. Connect your PC using null-modem cable to another pc, and in boot(8) prompt type: boot> set tty com0 On another PC run cu(1) or minicom or screen (or for Windows you may use PuTTY), connect to OpenBSD and you will see all your console output which you should be able to capture.
Re: OpenBSD on Lenovo m710q running minidlna?
On Wed, 2018-06-06 at 12:10 +, Stuart Henderson wrote: > On 2018-06-05, John Long wrote: > > I have a Lenovo m710q foobar2000 appliance under Windows 10. I like > > the > > box, it's about 1 1/2 as wide as a Lemote Fuloong Mini and about as > > deep and tall, but has slots for two, 2.5 inch drives. I thought > > about > > buying another one to use as a minidlna host under OpenBSD. > > > > Does anybody on the list have any experience with OpenBSD and > > minidlna > > on this box? > > Nothing in dmesglog, it would be nice if you could boot the one you > have > from a USB stick and email in to dmesg@. I'm up to my ass in alligators with work right now so it will take a few days. How do I capture the output? It's been a while since I installed OpenBSD... maybe it gives me an option to mail directly from the installer? I have only a vague memory about it. > Seems it may have a real serial port, if so that's a nice thing to > have on such a small machine. It appears to yes, but since I'm running Windows on it I haven't used it. They're not cheap and the hardware is just kinda meh. The one I bought has 4G of RAM, a 256G SSD (not sure which brand, it's buried in the chassis and hard to get to) and cost 500 Euros. The one I want for the minidlna server will cost about 600 Euros and have 8G of RAM. The box I have has the i3-7100T, it's a two-banger with hyperthreading, good single CPU clocks, 3.4GHz. For the same price you can get a i5- 7400T which is a four banger but no hyperthreading, and significantly slower clocks, 2.4 GHz. Not sure what the benefit to that would be. The disk tray is a flimsy, loose-fitting piece of plastic, not very reassuring. It feels like if you swap disks and out of there a dozen times you're going to be buying a new tray. I'm sure there is better hardware around, maybe even for the same price, but these boxes are readily available from my local shop in a few different variations, and have a nice form factor and some nice features. So far I'm satisfied with it. They advertised mine with a DVD drive, and it doesn't have one of course...when I complained they sent me a USB DVD drive. The enclosure is substantial aluminum, quite sturdy. Feels like you could stack them in a big pile of other gear and nothing would go wrong. And it comes with a separate aluminum tray case with rubber feet that wraps around the bottom and goes up and over both sides (the computer slides into it) and which has a slot for a separate aluminum holder (also included) that holds the power brick. It's a nice package if you don't open it up and look inside. Not sure about the cooling. The fan is tiny. > > > Or any experience in general running minidlna on OpenBSD? > > I used to run this on OpenBSD, it worked reasonably well with the > devices I tried accessing it from. I stopped running it after I moved > my > fileshares to a separate NAS box. > > We don't have inotify and minidlna doesn't have kqueue support for > file > monitoring; run it with the -r flag to do an incremental rescan if > you > add files. Thanks, this is good news. I would prefer not to have code doing things "for" me. I tend to rip a lot of discs in big batches and then move a lot of files at once. It would be ideal to update manually. > I had some problems with the multicast bits after the routing > table change to ART, but others couldn't replicate this, maybe it was > because the machine I was running it on was multihomed. I am clueless about networking but I don't anticipate any issues. I have the Windows box roped-off from my LAN so I can't move files around easily, can't use rsync or any convenient *NIX tools etc. It will be very convenient to have OpenBSD running dlna. Thanks, /jl
Re: Reboot loop
On 06/06/18 22:56, francis.dos.san...@ciudad.com.ar wrote: > About two days ago I upgraded to the version #65 below, just to see if > the game unknown-horizons would run smooth. Starting the computer anew > after evaluating the performance of the game I noticed that the machine > rebooted automatically. Many lines are printed with some weird '-> 0' > or '0 -> 1'. It scrolls by too fast to see properly. Can you plug a null modem cable into the machine's serial port (PCI/ISA one, not USB) and tell the kernel to direct its messages to that while another watches the output? Check your motherboard, some do provide "COM1" via a header which can be used exactly for this purpose. -- Stuart Longland (aka Redhatter, VK4MSL) I haven't lost my mind... ...it's backed up on a tape somewhere.
Re: Reboot loop
ddb(4): "ddb is invoked upon a kernel panic when the sysctl(8) ddb.panic is set to 1". I belive this value is default. So, kernel should be dropped into ddb on panic. Does it happen? What exactly do you see on screen along with uvm_fault? Do you see whole stacktrace? Check https://www.openbsd.org/ddb.html for "Minimum information for kernel problems" section
Re: Reboot loop
https://www.openbsd.org/report.html See "How to create a problem report" step 5
Re: Reboot loop
Theo, >> uvm_fault(0x81db7f68, 0x58, 0, 1) -> e > Just that one line? No other lines? I find that hard to believe. I should've stated that the uvm_fault messageline get's repeated ad infinitum. What can I do to get more debug info? > > Rebooting one more time resulted in an automatic reboot. Starting the > computer afresh gave me a wsconsole login. The firmware for vmm and > radeondrm were applied. Rebooting again, went in a loop, after that: > > uvm_fault(0x81db7ea8, 0x58, 0, 1) -> e > > Which piece of hardware is failing? Prior to the #65 upgrade I've seen > the ring 2 error CAFEDEAD message, but no automatic reboots before said > version. > What boot options are there to get a working stable system? > > OpenBSD 6.3-current (GENERIC.MP) #65: Fri Jun 1 17:44:06 MDT 2018 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 7966674944 (7597MB) > avail mem = 7652007936 (7297MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xe95c0 (17 entries) > bios0: vendor American Megatrends Inc. version "P1.10" date 04/01/2014 > bios0: ASRock QC5000-ITX/WiFi > acpi0 at bios0: rev 2 > acpi0: sleep states S0 S3 S4 S5 > acpi0: tables DSDT FACP APIC FPDT MCFG HPET AAFT SSDT SSDT CRAT SSDT SSDT > SSDT SSDT > acpi0: wakeup devices GFX_(S4) GPP1(S4) GPP2(S4) GPP3(S4) SBAZ(S4) PS2K(S4) > UAR1(S4) OHC1(S4) EHC1(S4) OHC2(S4) EHC2(S4) OHC3(S4) EHC3(S4) 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 A4-5000 APU with Radeon(TM) HD Graphics, 1497.37 MHz > 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,PCTRL3,ITSC,BMI1 > 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 A4-5000 APU with Radeon(TM) HD Graphics, 1497.20 MHz > 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,PCTRL3,ITSC,BMI1 > 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 A4-5000 APU with Radeon(TM) HD Graphics, 1497.20 MHz > 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,PCTRL3,ITSC,BMI1 > 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 A4-5000 APU with Radeon(TM) HD Graphics, 1497.20 MHz > 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,PCTRL3,ITSC,BMI1 > 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 5 pa 0xfec0, version 21, 24 pins > ioapic1 at mainbus0: apid 6 pa 0xfec01000, version 21, 32 pins > acpimcfg0 at
Re: rtadvd bug ?
Le mercredi 06 juin 2018 à 13:55 +0200, Bastien Durel a écrit :
> Hello,
>
> I run rtadvd on a router, which also run ospfd (on 6.3).
>
> rtadvd runs with static config (noifprefix):
> fremen# cat /etc/rtadvd.conf
> em0:\
> :rdnss="2a01:e35:8aea:ac42::10":\
> :dnssl="geekwu.org":\
> :addr0="2001:41d0:fe4b:ec21::":\
> :addr1="2a01:0e35:8aea:ac41::":\
> :noifprefix:
> em1:\
> :rdnss="2a01:e35:8aea:ac42::10":\
> :dnssl="geekwu.org":\
> :addr0="2a01:e35:8aea:ac42::":\
> :addr1="2001:41d0:fe4b:ec42::":\
> :noifprefix:
> em5:\
> :rdnss="2001:41d0:fe4b:ec42::10":\
> :dnssl="geekwu.org":\
> :addr0="2a01:e35:8aea:ac43::":\
> :noifprefix:
> em4:\
> :rdnss="2001:41d0:fe4b:ec42::10":\
> :dnssl="geekwu.org":\
> :addr="2001:41d0:fe4b:ecff::":\
> :noifprefix:
>
> if an ospf neighbour start advertising a new network (in my case
> 2001:41d0:fe4b:ecf1::/64), a route is inserted in the kernel:
>
> fremen# route -n show -inet6|grep ecf1
> 2001:41d0:fe4b:ecf1::/64 fe80::225:22ff:fe1e:bb7%em1UG
> 0 594 -32 em1
> but rtadvd starts advertising it on the link with the said neighbour.
>
> I get this from radvdump running on a Linux host on this link:
> #
> # radvd configuration generated by radvdump 2.17
> # based on Router Advertisement from fe80::8621:df60:6d70:8da
> # received by interface enp2s0
> #
>
> interface enp2s0
> {
> AdvSendAdvert on;
> # Note: {Min,Max}RtrAdvInterval cannot be obtained with
> radvdump
> AdvManagedFlag off;
> AdvOtherConfigFlag off;
> AdvReachableTime 0;
> AdvRetransTimer 0;
> AdvCurHopLimit 64;
> AdvDefaultLifetime 1800;
> AdvHomeAgentFlag off;
> AdvDefaultPreference medium;
> AdvSourceLLAddress on;
>
> prefix 2a01:e35:8aea:ac42::/64
> {
> AdvValidLifetime 2592000;
> AdvPreferredLifetime 604800;
> AdvOnLink on;
> AdvAutonomous on;
> AdvRouterAddr off;
> }; # End of prefix definition
>
>
> prefix 2001:41d0:fe4b:ec42::/64
> {
> AdvValidLifetime 2592000;
> AdvPreferredLifetime 604800;
> AdvOnLink on;
> AdvAutonomous on;
> AdvRouterAddr off;
> }; # End of prefix definition
>
>
> prefix 2001:41d0:fe4b:ecf1::/64
> {
> AdvValidLifetime 2592000;
> AdvPreferredLifetime 604800;
> AdvOnLink on;
> AdvAutonomous on;
> AdvRouterAddr off;
> }; # End of prefix definition
>
>
> RDNSS 2a01:e35:8aea:ac42::10
> {
> AdvRDNSSLifetime 900;
> }; # End of RDNSS definition
>
>
> DNSSL geekwu.org
> {
> AdvDNSSLLifetime 900;
> }; # End of DNSSL definition
>
> }; # End of interface definition
>
> Why does rtadvd start advertising this prefix ?
> If I withdraw the prefix from ospf, rtadvd stops advertising it.
>
BTW, radvd emits this log when the prefix is inserted into ospf
rtadvd[33784]: prefix 2001:41d0:fe4b:ecf1::/64 from fe80::225:22ff:fe1e:bb7 on
em1 is not in our list
--
Bastien
Re: Reboot loop
francis.dos.san...@ciudad.com.ar wrote: > Hello, > > My apologies if this should've gone to bugs@. There are 3 dmesg.boot > outputs within this text. The last successful boot of version #65 and > two outputs of #82 (xenodm enabled and disabled). > > About two days ago I upgraded to the version #65 below, just to see if > the game unknown-horizons would run smooth. Starting the computer anew > after evaluating the performance of the game I noticed that the machine > rebooted automatically. Many lines are printed with some weird '-> 0' > or '0 -> 1'. It scrolls by too fast to see properly. > > I cannot tell wether the following is relevant. After shutting down the > game 2bwm looked like it crashed and switching to a different tty seems > to weirdly copy tty5 (where xenodm starts). Say switching to tty0 > copies tty5 then switching to tty6 (I didn't know this one existed) I'm > presented with a wsconsole. Rebooting the machine resulted in it too > start over automatically. But luckily the second time around it > proceeded to a xenodm login screen. > > Today the system has become unusable. I upgraded to a newer #82 to see > if my problem would go away, but no luck. It's stuck in an endless > reboot loop. Commenting out xenodm_flags gave me the this result. > > uvm_fault(0x81db7f68, 0x58, 0, 1) -> e Just that one line? No other lines? I find that hard to believe. > > Rebooting one more time resulted in an automatic reboot. Starting the > computer afresh gave me a wsconsole login. The firmware for vmm and > radeondrm were applied. Rebooting again, went in a loop, after that: > > uvm_fault(0x81db7ea8, 0x58, 0, 1) -> e > > Which piece of hardware is failing? Prior to the #65 upgrade I've seen > the ring 2 error CAFEDEAD message, but no automatic reboots before said > version. > What boot options are there to get a working stable system? > > OpenBSD 6.3-current (GENERIC.MP) #65: Fri Jun 1 17:44:06 MDT 2018 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 7966674944 (7597MB) > avail mem = 7652007936 (7297MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xe95c0 (17 entries) > bios0: vendor American Megatrends Inc. version "P1.10" date 04/01/2014 > bios0: ASRock QC5000-ITX/WiFi > acpi0 at bios0: rev 2 > acpi0: sleep states S0 S3 S4 S5 > acpi0: tables DSDT FACP APIC FPDT MCFG HPET AAFT SSDT SSDT CRAT SSDT SSDT > SSDT SSDT > acpi0: wakeup devices GFX_(S4) GPP1(S4) GPP2(S4) GPP3(S4) SBAZ(S4) PS2K(S4) > UAR1(S4) OHC1(S4) EHC1(S4) OHC2(S4) EHC2(S4) OHC3(S4) EHC3(S4) 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 A4-5000 APU with Radeon(TM) HD Graphics, 1497.37 MHz > 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,PCTRL3,ITSC,BMI1 > 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 A4-5000 APU with Radeon(TM) HD Graphics, 1497.20 MHz > 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,PCTRL3,ITSC,BMI1 > 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 A4-5000 APU with Radeon(TM) HD Graphics, 1497.20 MHz > cpu2: >
Reboot loop
Hello, My apologies if this should've gone to bugs@. There are 3 dmesg.boot outputs within this text. The last successful boot of version #65 and two outputs of #82 (xenodm enabled and disabled). About two days ago I upgraded to the version #65 below, just to see if the game unknown-horizons would run smooth. Starting the computer anew after evaluating the performance of the game I noticed that the machine rebooted automatically. Many lines are printed with some weird '-> 0' or '0 -> 1'. It scrolls by too fast to see properly. I cannot tell wether the following is relevant. After shutting down the game 2bwm looked like it crashed and switching to a different tty seems to weirdly copy tty5 (where xenodm starts). Say switching to tty0 copies tty5 then switching to tty6 (I didn't know this one existed) I'm presented with a wsconsole. Rebooting the machine resulted in it too start over automatically. But luckily the second time around it proceeded to a xenodm login screen. Today the system has become unusable. I upgraded to a newer #82 to see if my problem would go away, but no luck. It's stuck in an endless reboot loop. Commenting out xenodm_flags gave me the this result. uvm_fault(0x81db7f68, 0x58, 0, 1) -> e Rebooting one more time resulted in an automatic reboot. Starting the computer afresh gave me a wsconsole login. The firmware for vmm and radeondrm were applied. Rebooting again, went in a loop, after that: uvm_fault(0x81db7ea8, 0x58, 0, 1) -> e Which piece of hardware is failing? Prior to the #65 upgrade I've seen the ring 2 error CAFEDEAD message, but no automatic reboots before said version. What boot options are there to get a working stable system? OpenBSD 6.3-current (GENERIC.MP) #65: Fri Jun 1 17:44:06 MDT 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 7966674944 (7597MB) avail mem = 7652007936 (7297MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xe95c0 (17 entries) bios0: vendor American Megatrends Inc. version "P1.10" date 04/01/2014 bios0: ASRock QC5000-ITX/WiFi acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT MCFG HPET AAFT SSDT SSDT CRAT SSDT SSDT SSDT SSDT acpi0: wakeup devices GFX_(S4) GPP1(S4) GPP2(S4) GPP3(S4) SBAZ(S4) PS2K(S4) UAR1(S4) OHC1(S4) EHC1(S4) OHC2(S4) EHC2(S4) OHC3(S4) EHC3(S4) 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 A4-5000 APU with Radeon(TM) HD Graphics, 1497.37 MHz 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,PCTRL3,ITSC,BMI1 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 A4-5000 APU with Radeon(TM) HD Graphics, 1497.20 MHz 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,PCTRL3,ITSC,BMI1 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 A4-5000 APU with Radeon(TM) HD Graphics, 1497.20 MHz 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,PCTRL3,ITSC,BMI1 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 A4-5000 APU with Radeon(TM) HD Graphics, 1497.20 MHz cpu3:
rtadvd bug ?
Hello,
I run rtadvd on a router, which also run ospfd (on 6.3).
rtadvd runs with static config (noifprefix):
fremen# cat /etc/rtadvd.conf
em0:\
:rdnss="2a01:e35:8aea:ac42::10":\
:dnssl="geekwu.org":\
:addr0="2001:41d0:fe4b:ec21::":\
:addr1="2a01:0e35:8aea:ac41::":\
:noifprefix:
em1:\
:rdnss="2a01:e35:8aea:ac42::10":\
:dnssl="geekwu.org":\
:addr0="2a01:e35:8aea:ac42::":\
:addr1="2001:41d0:fe4b:ec42::":\
:noifprefix:
em5:\
:rdnss="2001:41d0:fe4b:ec42::10":\
:dnssl="geekwu.org":\
:addr0="2a01:e35:8aea:ac43::":\
:noifprefix:
em4:\
:rdnss="2001:41d0:fe4b:ec42::10":\
:dnssl="geekwu.org":\
:addr="2001:41d0:fe4b:ecff::":\
:noifprefix:
if an ospf neighbour start advertising a new network (in my case
2001:41d0:fe4b:ecf1::/64), a route is inserted in the kernel:
fremen# route -n show -inet6|grep ecf1
2001:41d0:fe4b:ecf1::/64 fe80::225:22ff:fe1e:bb7%em1UG 0
594 -32 em1
but rtadvd starts advertising it on the link with the said neighbour.
I get this from radvdump running on a Linux host on this link:
#
# radvd configuration generated by radvdump 2.17
# based on Router Advertisement from fe80::8621:df60:6d70:8da
# received by interface enp2s0
#
interface enp2s0
{
AdvSendAdvert on;
# Note: {Min,Max}RtrAdvInterval cannot be obtained with radvdump
AdvManagedFlag off;
AdvOtherConfigFlag off;
AdvReachableTime 0;
AdvRetransTimer 0;
AdvCurHopLimit 64;
AdvDefaultLifetime 1800;
AdvHomeAgentFlag off;
AdvDefaultPreference medium;
AdvSourceLLAddress on;
prefix 2a01:e35:8aea:ac42::/64
{
AdvValidLifetime 2592000;
AdvPreferredLifetime 604800;
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr off;
}; # End of prefix definition
prefix 2001:41d0:fe4b:ec42::/64
{
AdvValidLifetime 2592000;
AdvPreferredLifetime 604800;
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr off;
}; # End of prefix definition
prefix 2001:41d0:fe4b:ecf1::/64
{
AdvValidLifetime 2592000;
AdvPreferredLifetime 604800;
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr off;
}; # End of prefix definition
RDNSS 2a01:e35:8aea:ac42::10
{
AdvRDNSSLifetime 900;
}; # End of RDNSS definition
DNSSL geekwu.org
{
AdvDNSSLLifetime 900;
}; # End of DNSSL definition
}; # End of interface definition
Why does rtadvd start advertising this prefix ?
If I withdraw the prefix from ospf, rtadvd stops advertising it.
Thanks,
Bastien
dmesg:
OpenBSD 6.3 (GENERIC.MP) #3: Fri May 18 00:06:26 CEST 2018
r...@syspatch-63-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 519962624 (495MB)
avail mem = 497184768 (474MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0
acpi at bios0 not configured
mpbios0 at bios0: Intel MP Specification 1.4
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Genuine Intel(R) CPU @ 600MHz, 600.08 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF,PERF,SENSOR,MELTDOWN
cpu0: 512KB 64b/line 8-way L2 cache
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, C-substates=0.2.2.0.2.0.3, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Genuine Intel(R) CPU @ 600MHz, 600.00 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF,PERF,SENSOR,MELTDOWN
cpu1: 512KB 64b/line 8-way L2 cache
cpu1: smt 1, core 0, package 0
mpbios0: bus 0 is type PCI
mpbios0: bus 64 is type ISA
ioapic0 at mainbus0: apid 0 pa 0xfec0, version 20, 24 pins
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 vendor "Intel", unknown product 0x4115 rev 0x05
pchb1 at pci0 dev 1 function 0 "Intel E600 Config" rev 0x00
ppb0 at pci0 dev 23 function 0 "Intel E600 PCIE" rev 0x00
pci1 at ppb0 bus 1
ppb1 at pci1 dev 0 function 0 "Intel EG20T PCIE" rev 0x01
pci2 at ppb1 bus 2
"Intel EG20T Packet Hub" rev 0x01 at pci2 dev 0 function 0 not configured
"Intel EG20T Ethernet" rev 0x02 at pci2 dev 0 function 1 not configured
"Intel EG20T GPIO" rev 0x01 at pci2 dev 0 function 2 not configured
ohci0 at pci2 dev 2 function 0 "Intel EG20T USB" rev 0x02: apic 0 int 19,
version 1.0
ohci1 at pci2 dev 2
Re: OpenBSD on Lenovo m710q running minidlna?
On 2018-06-05, John Long wrote: > I have a Lenovo m710q foobar2000 appliance under Windows 10. I like the > box, it's about 1 1/2 as wide as a Lemote Fuloong Mini and about as > deep and tall, but has slots for two, 2.5 inch drives. I thought about > buying another one to use as a minidlna host under OpenBSD. > > Does anybody on the list have any experience with OpenBSD and minidlna > on this box? Nothing in dmesglog, it would be nice if you could boot the one you have from a USB stick and email in to dmesg@. Seems it may have a real serial port, if so that's a nice thing to have on such a small machine. > Or any experience in general running minidlna on OpenBSD? I used to run this on OpenBSD, it worked reasonably well with the devices I tried accessing it from. I stopped running it after I moved my fileshares to a separate NAS box. We don't have inotify and minidlna doesn't have kqueue support for file monitoring; run it with the -r flag to do an incremental rescan if you add files. I had some problems with the multicast bits after the routing table change to ART, but others couldn't replicate this, maybe it was because the machine I was running it on was multihomed.
Re: Pf syntax, need help understanding an example
On 2018-06-06, Johan Mellberg wrote:
> Hi,
>
> I am working my way through "The Book of Pf" and got hung up on the
> example on page 31 of edition 3 (I am reading edition 2 but the
> example seems to be identical in edition 3):
>
> ext_if = "re0" # macro for external interface - use tun0 or pppoe0 for PPPoE
> int_if = "re1" # macro for internal interface
> localnet = $int_if:network
> # ext_if IPv4 address could be dynamic, hence ($ext_if)
> match out on $ext_if inet from $localnet nat-to ($ext_if) # NAT, match IPv4
> only
> block all
> pass from { self, $localnet
>
> So, what it does is not a problem, I understand that, but that set of
> parentheses around $ext_if confuses me. The explanation states that
> the IPv4 address could be dynamic (which is clear...) but I look at
> that example and as far as I understand, $ext_if should expand to
> "re0", not an IP address - right?
with ext_if="re0", $ext_if expands to re0.
If this if used in place of an address in a PF rule, re0's address is
looked up when pfctl is run and that is used.
If "(re0)" is used instead, that lookup is done when the firewall state
is created rather than during rule load. So if you have an address which
does *not* change, using () is unnecessary overhead at runtime for every
new state which has to evaluate this.
> Just to test I tried a simple line in my own pf.conf (on OpenBSD 6.3):
>
> ext_if = "em0"
> set skip on $ext_if
>
> and tested with pfctl -nvf /etc/pf.conf
>
> That worked so then I put parentheses around $ext_if:
>
> set skip on ($ext_if)
>
> and tested again. This time I got a syntax error!
() is only for places which take an address. "set skip" takes an "ifspec"
instead. The interface name itself is valid but "set skip on (em0)" is not.
I realise this is just testing but will mention just in case: you don't
usually want to set skip on the external *or* internal interface.
rtadvd bug ?
Hello,
I run rtadvd on a router, which also run ospfd (on 6.3).
rtadvd runs with static config (noifprefix):
fremen# cat /etc/rtadvd.conf
em0:\
:rdnss="2a01:e35:8aea:ac42::10":\
:dnssl="geekwu.org":\
:addr0="2001:41d0:fe4b:ec21::":\
:addr1="2a01:0e35:8aea:ac41::":\
:noifprefix:
em1:\
:rdnss="2a01:e35:8aea:ac42::10":\
:dnssl="geekwu.org":\
:addr0="2a01:e35:8aea:ac42::":\
:addr1="2001:41d0:fe4b:ec42::":\
:noifprefix:
em5:\
:rdnss="2001:41d0:fe4b:ec42::10":\
:dnssl="geekwu.org":\
:addr0="2a01:e35:8aea:ac43::":\
:noifprefix:
em4:\
:rdnss="2001:41d0:fe4b:ec42::10":\
:dnssl="geekwu.org":\
:addr="2001:41d0:fe4b:ecff::":\
:noifprefix:
if an ospf neighbour start advertising a new network (in my case
2001:41d0:fe4b:ecf1::/64), a route is inserted in the kernel:
fremen# route -n show -inet6|grep ecf1
2001:41d0:fe4b:ecf1::/64 fe80::225:22ff:fe1e:bb7%em1UG
0 594 -32 em1
but rtadvd starts advertising it on the link with the said neighbour.
I get this from radvdump running on a Linux host on this link:
#
# radvd configuration generated by radvdump 2.17
# based on Router Advertisement from fe80::8621:df60:6d70:8da
# received by interface enp2s0
#
interface enp2s0
{
AdvSendAdvert on;
# Note: {Min,Max}RtrAdvInterval cannot be obtained with radvdump
AdvManagedFlag off;
AdvOtherConfigFlag off;
AdvReachableTime 0;
AdvRetransTimer 0;
AdvCurHopLimit 64;
AdvDefaultLifetime 1800;
AdvHomeAgentFlag off;
AdvDefaultPreference medium;
AdvSourceLLAddress on;
prefix 2a01:e35:8aea:ac42::/64
{
AdvValidLifetime 2592000;
AdvPreferredLifetime 604800;
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr off;
}; # End of prefix definition
prefix 2001:41d0:fe4b:ec42::/64
{
AdvValidLifetime 2592000;
AdvPreferredLifetime 604800;
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr off;
}; # End of prefix definition
prefix 2001:41d0:fe4b:ecf1::/64
{
AdvValidLifetime 2592000;
AdvPreferredLifetime 604800;
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr off;
}; # End of prefix definition
RDNSS 2a01:e35:8aea:ac42::10
{
AdvRDNSSLifetime 900;
}; # End of RDNSS definition
DNSSL geekwu.org
{
AdvDNSSLLifetime 900;
}; # End of DNSSL definition
}; # End of interface definition
Why does rtadvd start advertising this prefix ?
If I withdraw the prefix from ospf, rtadvd stops advertising it.
Thanks,
Bastien
dmesg:
OpenBSD 6.3 (GENERIC.MP) #3: Fri May 18 00:06:26 CEST 2018
r...@syspatch-63-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 519962624 (495MB)
avail mem = 497184768 (474MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0
acpi at bios0 not configured
mpbios0 at bios0: Intel MP Specification 1.4
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Genuine Intel(R) CPU @ 600MHz, 600.08 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF,PERF,SENSOR,MELTDOWN
cpu0: 512KB 64b/line 8-way L2 cache
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, C-substates=0.2.2.0.2.0.3, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Genuine Intel(R) CPU @ 600MHz, 600.00 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF,PERF,SENSOR,MELTDOWN
cpu1: 512KB 64b/line 8-way L2 cache
cpu1: smt 1, core 0, package 0
mpbios0: bus 0 is type PCI mpbios0: bus 64 is type ISA ioapic0 at
mainbus0: apid 0 pa 0xfec0, version 20, 24 pins
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 vendor "Intel", unknown product 0x4115
rev 0x05
pchb1 at pci0 dev 1 function 0 "Intel E600 Config" rev 0x00
ppb0 at pci0 dev 23 function 0 "Intel E600 PCIE" rev 0x00
pci1 at ppb0 bus 1
ppb1 at pci1 dev 0 function 0 "Intel EG20T PCIE" rev 0x01
pci2 at ppb1 bus 2
"Intel EG20T Packet Hub" rev 0x01 at pci2 dev 0 function 0 not configured
"Intel EG20T Ethernet" rev 0x02 at pci2 dev 0 function 1 not configured
"Intel EG20T GPIO" rev 0x01 at pci2 dev 0 function 2 not configured
ohci0 at pci2 dev 2 function 0 "Intel EG20T USB" rev 0x02: apic 0 int
19, version 1.0
ohci1 at pci2 dev 2
Re: Banana Pi R1 - working dwge(4)
Hi, Were you able to run openBSD on bpi-r1? if yes, then can you please share the steps for it? Regards, -- Sent from: http://openbsd-archive.7691.n7.nabble.com/openbsd-user-misc-f3.html
Re: Pf syntax, need help understanding an example
hi,
$ext_if - expands to the name of the interface
($ext_if) - expands to the ip address assigned to the interface
On 06.06.18 12:21, Johan Mellberg wrote:
Hi,
I am working my way through "The Book of Pf" and got hung up on the
example on page 31 of edition 3 (I am reading edition 2 but the
example seems to be identical in edition 3):
ext_if = "re0" # macro for external interface - use tun0 or pppoe0 for PPPoE
int_if = "re1" # macro for internal interface
localnet = $int_if:network
# ext_if IPv4 address could be dynamic, hence ($ext_if)
match out on $ext_if inet from $localnet nat-to ($ext_if) # NAT, match IPv4 only
block all
pass from { self, $localnet
So, what it does is not a problem, I understand that, but that set of
parentheses around $ext_if confuses me. The explanation states that
the IPv4 address could be dynamic (which is clear...) but I look at
that example and as far as I understand, $ext_if should expand to
"re0", not an IP address - right?
Just to test I tried a simple line in my own pf.conf (on OpenBSD 6.3):
ext_if = "em0"
set skip on $ext_if
and tested with pfctl -nvf /etc/pf.conf
That worked so then I put parentheses around $ext_if:
set skip on ($ext_if)
and tested again. This time I got a syntax error!
So could someone please explain this to me? I don't think this is an
error in the book because there is a small paragraph apart from the
comment in the example specifically pointing out the value of these
parentheses - but I can't wrap my head around it. Any help
appreciated!
Sincerely, Johan
Pf syntax, need help understanding an example
Hi,
I am working my way through "The Book of Pf" and got hung up on the
example on page 31 of edition 3 (I am reading edition 2 but the
example seems to be identical in edition 3):
ext_if = "re0" # macro for external interface - use tun0 or pppoe0 for PPPoE
int_if = "re1" # macro for internal interface
localnet = $int_if:network
# ext_if IPv4 address could be dynamic, hence ($ext_if)
match out on $ext_if inet from $localnet nat-to ($ext_if) # NAT, match IPv4 only
block all
pass from { self, $localnet
So, what it does is not a problem, I understand that, but that set of
parentheses around $ext_if confuses me. The explanation states that
the IPv4 address could be dynamic (which is clear...) but I look at
that example and as far as I understand, $ext_if should expand to
"re0", not an IP address - right?
Just to test I tried a simple line in my own pf.conf (on OpenBSD 6.3):
ext_if = "em0"
set skip on $ext_if
and tested with pfctl -nvf /etc/pf.conf
That worked so then I put parentheses around $ext_if:
set skip on ($ext_if)
and tested again. This time I got a syntax error!
So could someone please explain this to me? I don't think this is an
error in the book because there is a small paragraph apart from the
comment in the example specifically pointing out the value of these
parentheses - but I can't wrap my head around it. Any help
appreciated!
Sincerely, Johan
