Re: Filesystem corruption on OpenBSD routers after power outage?
On Wed, Jun 05, 2019 at 05:12:20AM +, Roderick wrote: > > "-o union" was last in 3.7, disappeared in 3.8. Was there a reason? It was broken and complicated the filesystem code beyond measure. -Otto > > https://man.openbsd.org/OpenBSD-3.7/mount > > Rodrigo > > > What also would be practical is a "mount -o union" like in FreeBSD, > > but unfortunately I do not see it in OpenBSD. > > > > Then one could mount a mfs system over a normal one, only to be read. > > > > Rodrigo >
Re: Can't update BIOS on alix2d13 with flashrom
On Mon, Jun 03, 2019 at 05:27:52PM -, Stuart Henderson wrote:
> On 2019-06-02, Артур Истомин wrote:
> > I'm trying update BIOS on alix2d13 board with flashrom ver 1.0 on OpenBSD
> > 6.5
> >
> > # flashrom -w alix1.bin -p internal
> > flashrom v1.0 on OpenBSD 6.5 (i386)
> > flashrom is free software, get the source code at https://flashrom.org
> >
> > Calibrating delay loop... delay loop is unreliable, trying to continue OK.
> > No DMI table found.
> > Found chipset "AMD CS5536".
> > Enabling flash write... Error while opening /dev/amdmsr: Device not
> > configured
> > FAILED!
> > Warning: unexpected second chipset match: "AMD CS5536"
> > ignoring, please report lspci and board URL to flash...@flashrom.org
> > with 'CHIPSET: your board name' in the subject line.
> > No EEPROM/flash device found.
> > Note: flashrom can never write if the flash chip isn't found automatically.
> >
> > What's wrong?
>
> Looks like this flash device can only be programmed with model-specific
> registers (MSRs). On OpenBSD this is done via amdmsr(4) which requires
> 2 things: 1: it must be detected and attached in the kernel, and 2:
> machdep.allowaperture must be set (normally on OpenBSD this device
> is used for access to graphics with X).
>
> If 1 fails you get ENXIO "Device not configured", if 2 fails you get
> EPERM "Operation not permitted".
>
> On your system the device does not attach (no amdmsr attach line in dmesg).
> Looking at amdmsr_probe() in /sys/arch/i386/i386/amdmsr.c I see this
>
> 74 /* Check for AMD Geode LX CPU */
> 75 if (strcmp(cpu_vendor, "AuthenticAMD") == 0 && family == 0x5 &&
> 76 model == 0x0a) {
> 77 /* Check for graphics processor presence */
> 78 gld_msr_cap = rdmsr(GLX_CPU_GLD_MSR_CAP);
> 79 if (((gld_msr_cap >> 8) & 0x0fff) == GLX_CPU_DID) {
> 80 gld_msr_cap = rdmsr(GLX_GP_GLD_MSR_CAP);
> 81 if (((gld_msr_cap >> 8) & 0x0fff) == GLX_GP_DID)
> 82 return 1;
> 83 }
> 84 }
>
>
> >
> > dmesg:
> >
> > OpenBSD 6.5 (GENERIC) #1: Wed Apr 24 22:04:27 CEST 2019
> > r...@syspatch-65-i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
> > real mem = 267931648 (255MB)
> > avail mem = 247779328 (236MB)
> > mpath0 at root
> > scsibus0 at mpath0: 256 targets
> > mainbus0 at root
> > bios0 at mainbus0: date 11/05/08, BIOS32 rev. 0 @ 0xfd088
> > pcibios0 at bios0: rev 2.1 @ 0xf/0x1
> > pcibios0: pcibios_get_intr_routing - function not supported
> > pcibios0: PCI IRQ Routing information unavailable.
> > pcibios0: PCI bus #0 is the last bus
> > bios0: ROM list: 0xe/0xa800
> > cpu0 at mainbus0: (uniprocessor)
> > cpu0: Geode(TM) Integrated Processor by AMD PCS ("AuthenticAMD" 586-class)
> > 499 MHz, 05-0a-02
>
> The family/model (05/0a) match but the driver is not attaching so it must be
> failing the "Check for graphics processor presence" check.
>
> If you were to remove that check, maybe it will work, or maybe it will
> fail horribly and you will brick your board.
>
> Personally I would recommend following pcengines' suggested procedure
> and use their freedos image for alix.
I see. Thank you for thoughful explanation!
Re: Filesystem corruption on OpenBSD routers after power outage?
"-o union" was last in 3.7, disappeared in 3.8. Was there a reason? https://man.openbsd.org/OpenBSD-3.7/mount Rodrigo What also would be practical is a "mount -o union" like in FreeBSD, but unfortunately I do not see it in OpenBSD. Then one could mount a mfs system over a normal one, only to be read. Rodrigo
Re: Filesystem corruption on OpenBSD routers after power outage?
What also would be practical is a "mount -o union" like in FreeBSD, but unfortunately I do not see it in OpenBSD. Then one could mount a mfs system over a normal one, only to be read. Rodrigo
Re: Filesystem corruption on OpenBSD routers after power outage?
Look at -P option in mount_mfs. Rodrigo
Re: chrome pledge "", syscall 289
> On Jun 3, 2019, at 6:46 PM, Cord wrote: > > Hi, > I have found the following errors on the log: > > /bsd: chrome[18585]: pledge "", syscall 289 > > they appear everytime I start chrome.. they are about 4 or 5, what means? > It's the first time, yesterday and in the past there aren't any. > Withstanding the obvious have you tried --enable-unveil? Regards Patrick
Re: Filesystem corruption on OpenBSD routers after power outage?
On 6/4/19 3:30 PM, Mogens Jensen wrote: I'm going to build a router for use in a remote location, and I have chosen OpenBSD 6.5 for the task. Unfortunately, it's not possible to protect the router with an UPS, so it will have to be resilient enough to survive sudden power outages and still boot without manual intervention. In the past I have built a few Linux based routers and they were configured to run from RAM. I have made some research to see if this is also possible on OpenBSD and found that, while there are solutions to have / read-only, none of this is officially supported. Can anyone with experience running OpenBSD routers without UPS, tell if filesystem corruption is going to be a problem after power outages, or if there are any officially supported ways to make the system resilient enough to not break after a power outage? I'm using an mSATA disk with MLC flash in the router. Thanks in advance. Mogens Jensen As Mr. Holland points out, a UPS doesn't really help overall reliability. In practice, /, /bin, and /usr are effectively read-only except for kernel and shared library randomization at boot time. /var gets written infrequently for logs, etc. /tmp, of course, is frequently written but its contents are irrelevant after a reboot. An important way to reduce disk activity is to mount all filesystems "noatime". This suppresses effectively all writes to /, /bin, and /usr after boot. Changes to /var get pushed to disk fairly quickly. The likelihood of significant corruption is very small. In practice, I knock my router off-line once or twice a month by messing with power cables nearby. The only way I find out is by looking at the logs. I've never had to manually fsck any of my routers except after electrical storms - and only then after moving the disk to a non-smoking chassis. Physical access to a console by a trusted person or remote console access is required. Not for any failings of OpenBSD in particular but for the guaranteed perversity of electronic devices and unforseeable acts of nature and man messing up the local environment. You will [should] access the system twice a year to install the latest release. [ insert standard disclaimers here ] Geoff Steckel
Re: Security of OpenBSD
Mon, 3 Jun 2019 22:32:16 + Josef Pospisil > Hey, thank you all for this mailing list. > > I have a question regarding the security of OpebBSD. See https://www.openbsd.org/security.html
Re: Filesystem corruption on OpenBSD routers after power outage?
On 6/4/19 1:29 PM, Mogens Jensen wrote: > I'm going to build a router for use in a remote location, and I have > chosen OpenBSD 6.5 for the task. Unfortunately, it's not possible to > protect the router with an UPS, so it will have to be resilient enough > to survive sudden power outages and still boot without manual > intervention. > > In the past I have built a few Linux based routers and they were > configured to run from RAM. I have made some research to see if this is > also possible on OpenBSD and found that, while there are solutions to > have / read-only, none of this is officially supported. > > Can anyone with experience running OpenBSD routers without UPS, tell if > filesystem corruption is going to be a problem after power outages, or > if there are any officially supported ways to make the system resilient > enough to not break after a power outage? > > I'm using an mSATA disk with MLC flash in the router. I realized a few decades ago that consumer UPSs are a bad investment. Industrial UPSs are a dubious idea in business unless you have a dual-power supply machine and can hook each PS to a DIFFERENT UPS -- in my area, grid power is more reliable than cheap UPSes (your mileage may vary). And you have to MAINTAIN your UPSs, otherwise after a few years, UPSs turn minor glitches into power outages (thank you very much). I'm also fond of proving my own claims, so I very often just yank the cord on my systems rather than doing orderly shutdowns. Yes, if you drop power on an OpenBSD system, you will get an fsck on reboot. Solution: Make your partitions as small as reasonable. Just because you got a 500G disk for cheap, no reason to allocate all 500G. For a router, 10G is PLENTY, and will fsck quickly. If you have slow media (i.e., flash drives), you might want to aim for 1G. Every once in a long while, you might catch a really bad time for the power to go out, and have to manually say "Fix it!" to fsck, but for the most part, the system will just come back up after the power comes back on. The less you write to disk, the less risk you have of having to manually intervene in your system's reboot. IF you want to do some fancy logging, keep the logging partition out of the fstab file, and have a script that brings it up with a "fsck -y" AFTER the system comes up, and start the fancy logging AFTER the big logging partition successfully mounts. But don't do stupid games to try to improve your chances, just make sure there's a monitor and keyboard available to fix any problems that might happen. Simple systems have simple problems. Complex systems break in complex ways. You want me to swear you'll never have to manually intervene in boot after an "event"? Nope. But I've walked non-technical people through single-user fsck's over the phone; when your bastardized system breaks, you will be down for a lot longer and you will be going on-site to fix. Nick.
Re: Lenovo w/ AMD Ryzen CPU
On 2019-06-04, Patrick Wildt wrote: > I'd love to have one as well... I hadn't intended to buy a new laptop anytime soon, but the Thinkpad X395 is tempting... -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: Filesystem corruption on OpenBSD routers after power outage?
there is also an option for setting fsck to approve fixes without a prompt .. but I cant think of it off the top of my head... and this would be useful to set on your routers also On Tue, 4 Jun 2019 at 21:05, Tom Smyth wrote: > Hi Mogens, > > there are a number of threads on this if you search the misc archives on > marc.info, > > but setting softdep,noatime mount options on /etc/fstab is advisable > > for routers I tend to use mfs for partitions that tend to get written to > alot > > the following entries (/etc/fstab) show How I use mfs on my routers... > swap /tmp mfs > rw,nosuid,noexec,nodev,-s=512000,-P=/directorythatcontainsfilesthatwillbecopiedtomemoryatbootup/tmp > 0 0 > swap /var mfs rw,nosuid,noexec,nodev,-s=1024000,-P=/ > directorythatcontainsfilesthatwillbecopiedtomemoryatbootup/var 0 0 > swap /dev mfs rw,nosuid,noexec,-P=/ > directorythatcontainsfilesthatwillbecopiedtomemoryatbootup/dev,-i=2048,-s=102400 > 0 0 > > but bear in mind that that uses up to 1.6GB of ram ... so you might > want to tweak. to what suits your needs... > > check out conway's resflash and cappucios flashrd also > > https://www.packetmischief.ca/openbsd-compact-flash-firewall/ > > I hope this helps > Tom Smyth > > On Tue, 4 Jun 2019 at 20:31, Mogens Jensen > wrote: > >> I'm going to build a router for use in a remote location, and I have >> chosen OpenBSD 6.5 for the task. Unfortunately, it's not possible to >> protect the router with an UPS, so it will have to be resilient enough >> to survive sudden power outages and still boot without manual >> intervention. >> >> In the past I have built a few Linux based routers and they were >> configured to run from RAM. I have made some research to see if this is >> also possible on OpenBSD and found that, while there are solutions to >> have / read-only, none of this is officially supported. >> >> Can anyone with experience running OpenBSD routers without UPS, tell if >> filesystem corruption is going to be a problem after power outages, or >> if there are any officially supported ways to make the system resilient >> enough to not break after a power outage? >> >> I'm using an mSATA disk with MLC flash in the router. >> >> Thanks in advance. >> >> Mogens Jensen >> > > > -- > Kindest regards, > Tom Smyth. > -- Kindest regards, Tom Smyth.
Re: Filesystem corruption on OpenBSD routers after power outage?
Hi Mogens, there are a number of threads on this if you search the misc archives on marc.info, but setting softdep,noatime mount options on /etc/fstab is advisable for routers I tend to use mfs for partitions that tend to get written to alot the following entries (/etc/fstab) show How I use mfs on my routers... swap /tmp mfs rw,nosuid,noexec,nodev,-s=512000,-P=/directorythatcontainsfilesthatwillbecopiedtomemoryatbootup/tmp 0 0 swap /var mfs rw,nosuid,noexec,nodev,-s=1024000,-P=/ directorythatcontainsfilesthatwillbecopiedtomemoryatbootup/var 0 0 swap /dev mfs rw,nosuid,noexec,-P=/ directorythatcontainsfilesthatwillbecopiedtomemoryatbootup/dev,-i=2048,-s=102400 0 0 but bear in mind that that uses up to 1.6GB of ram ... so you might want to tweak. to what suits your needs... check out conway's resflash and cappucios flashrd also https://www.packetmischief.ca/openbsd-compact-flash-firewall/ I hope this helps Tom Smyth On Tue, 4 Jun 2019 at 20:31, Mogens Jensen wrote: > I'm going to build a router for use in a remote location, and I have > chosen OpenBSD 6.5 for the task. Unfortunately, it's not possible to > protect the router with an UPS, so it will have to be resilient enough > to survive sudden power outages and still boot without manual > intervention. > > In the past I have built a few Linux based routers and they were > configured to run from RAM. I have made some research to see if this is > also possible on OpenBSD and found that, while there are solutions to > have / read-only, none of this is officially supported. > > Can anyone with experience running OpenBSD routers without UPS, tell if > filesystem corruption is going to be a problem after power outages, or > if there are any officially supported ways to make the system resilient > enough to not break after a power outage? > > I'm using an mSATA disk with MLC flash in the router. > > Thanks in advance. > > Mogens Jensen > -- Kindest regards, Tom Smyth.
Re: Security of OpenBSD
On 04/06/2019, Stuart Henderson wrote: > Also see Ken Thompson's classic paper, "Reflections on Trusting Trust", > especially the moral. That moral brought back memories of The Hacker Crackdown by Bruce Sterling, which is freely available online and which I'd happily recommend to anyone remotely interested. Sterling's non-fiction book recounts how what Thompson described as "an explosive situation brewing" actually played out in practice. That's history now, but it's recent history and still relevant, as well as entertaining to read about: https://en.wikipedia.org/wiki/The_Hacker_Crackdown#External_links
Filesystem corruption on OpenBSD routers after power outage?
I'm going to build a router for use in a remote location, and I have chosen OpenBSD 6.5 for the task. Unfortunately, it's not possible to protect the router with an UPS, so it will have to be resilient enough to survive sudden power outages and still boot without manual intervention. In the past I have built a few Linux based routers and they were configured to run from RAM. I have made some research to see if this is also possible on OpenBSD and found that, while there are solutions to have / read-only, none of this is officially supported. Can anyone with experience running OpenBSD routers without UPS, tell if filesystem corruption is going to be a problem after power outages, or if there are any officially supported ways to make the system resilient enough to not break after a power outage? I'm using an mSATA disk with MLC flash in the router. Thanks in advance. Mogens Jensen
Re: OpenBSD 6.5 dumps to debugger when using ifconfig bridge command
I tried loading current on the device and the same result:
OpenBSD 6.5-current (GENERIC.MP) #5: Mon Jun 3 07:46:49 MDT 2019
# netstat -in
NameMtu Network Address Ipkts IfailOpkts Ofail Colls
lo0 327680 00 0 0
lo0 32768 ::1/128 ::1 0 00 0 0
lo0 32768 fe80::%lo0/ fe80::1%lo0 0 00 0 0
lo0 32768 127/8 127.0.0.10 00 0 0
em0 150000:0d:b9:43:9b:3031715 0 120479 7 0
em1 150000:0d:b9:43:9b:31 123252 11630860 0 0
em2 150000:0d:b9:43:9b:32 1672 0 625 0 0
em2 1500 128.100.103 128.100.103.831672 0 625 0 0
enc0* 00 00 0 0
bridge0 1500152255 0 151339 0 0
pflog0 331360 0 70 0 0
freenas-fw# ifconfig bridge0
bridge0: flags=4WARNING: SPL NOT LOWERED ON S1
YSCALL 5index 6 llprio 34 3 EXIT 0
groups: bridg 9
e
priorStopped at savectx+0xb1: movl$0,%gs:0x530
ddb{2}>
Russell P. Sutherland Email: russell . sutherland @ utoronto dawt ca
Network Engineer, I+TS Voice: +1.416.978.0470
4 Bancroft Ave., Rm. 102 Cell: +1.416.803.0080
University of Toronto Fax: +1.416.978.6620
Toronto, ON M5S 1C1
From: owner-m...@openbsd.org on behalf of Stuart
Henderson
Sent: Tuesday, June 4, 2019 13:53
To: misc@openbsd.org
Subject: Re: OpenBSD 6.5 dumps to debugger when using ifconfig bridge command
>There was a crash fixed in bridge(4) a few weeks ago, can you try reproducing
on -current?
On 2019-06-04, Lee Nelson wrote:
> I have twice seen kernel panics in the same situation. It drops to "ddb>"
> but the system is unresponsive. Unfortunately, other than taking a picture
> of the screen with my cellphone, I do not have any further information from
> the system. On both occasions, I was issuing "ifconfig bridge42" without
> any arguments. (and no, there aren't 41 other bridges. 42 has other
> significance in my network)
>
> On Tue, Jun 4, 2019, 08:41 Russell Sutherland <
> russell.sutherl...@utoronto.ca> wrote:
>
>> I began to install resflash (https://stable.rcesoftware.com/resflash/)
>> which is based on OpenBSD) to build a small firewall on an PC Engines apu2
>> board. Three interfaces, two bridged and one with an IP for management.
>>
>> I found the system would crash and drop down to the debugger interface
>> whenever I issued the:
>>
>> # ifconfig bridge0
>>
>> command.
>>
>> # ifconfig -a
>>
>> worked fine. After discussing this with the author we thought it good to
>> try the same configuration on vanilla 6.5 install.
>>
>> This worked better, but after a short period of operation the same
>> symptoms occured:
>>
>> # ifconfig bridge0
>>
>> bridge0: flags=4WAR1
>>
>> Nindex 6 llprio ING: SPL NOT
>>
>> groups: bridgLOWEe
>>
>> priority 327RED68 hellotime 2 f ONwddelay 15 maxag e 20 holdcnt 6
>> pSYSCALL 5roto rstp
>>
>> desi4gnated: id 00:0 3 EXIT 0:00:00:00:00 pri 9
>>
>> ority 0
>>
>> agsStopped at savectx+0xb1: movl $0,%gs:0x508
>>
>> ddb{3}>
>>
>>
>> Here is the output from dmesg:
>>
>>
>> OpenBSD 6.5 (GENERIC.MP) #3: Sat Apr 13 14:48:43 MDT 2019
>> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
>> real mem = 1996148736 (1903MB)
>> avail mem = 1926090752 (1836MB)
>> 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.28 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,BM/tmp/qwe.txt
>> (15I1,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
Re: OpenBSD 6.5 dumps to debugger when using ifconfig bridge command
There was a crash fixed in bridge(4) a few weeks ago, can you try reproducing
on -current?
On 2019-06-04, Lee Nelson wrote:
> I have twice seen kernel panics in the same situation. It drops to "ddb>"
> but the system is unresponsive. Unfortunately, other than taking a picture
> of the screen with my cellphone, I do not have any further information from
> the system. On both occasions, I was issuing "ifconfig bridge42" without
> any arguments. (and no, there aren't 41 other bridges. 42 has other
> significance in my network)
>
> On Tue, Jun 4, 2019, 08:41 Russell Sutherland <
> russell.sutherl...@utoronto.ca> wrote:
>
>> I began to install resflash (https://stable.rcesoftware.com/resflash/)
>> which is based on OpenBSD) to build a small firewall on an PC Engines apu2
>> board. Three interfaces, two bridged and one with an IP for management.
>>
>> I found the system would crash and drop down to the debugger interface
>> whenever I issued the:
>>
>> # ifconfig bridge0
>>
>> command.
>>
>> # ifconfig -a
>>
>> worked fine. After discussing this with the author we thought it good to
>> try the same configuration on vanilla 6.5 install.
>>
>> This worked better, but after a short period of operation the same
>> symptoms occured:
>>
>> # ifconfig bridge0
>>
>> bridge0: flags=4WAR1
>>
>> Nindex 6 llprio ING: SPL NOT
>>
>> groups: bridgLOWEe
>>
>> priority 327RED68 hellotime 2 f ONwddelay 15 maxag e 20 holdcnt 6
>> pSYSCALL 5roto rstp
>>
>> desi4gnated: id 00:0 3 EXIT 0:00:00:00:00 pri 9
>>
>>ority 0
>>
>> agsStopped at savectx+0xb1: movl$0,%gs:0x508
>>
>> ddb{3}>
>>
>>
>> Here is the output from dmesg:
>>
>>
>> OpenBSD 6.5 (GENERIC.MP) #3: Sat Apr 13 14:48:43 MDT 2019
>> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
>> real mem = 1996148736 (1903MB)
>> avail mem = 1926090752 (1836MB)
>> 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.28 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,BM/tmp/qwe.txt
>> (15I1,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.14 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.23 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.13 MHz, 16-30-01
>> cpu3:
>>
Re: Lenovo w/ AMD Ryzen CPU
I'd love to have one as well... On Tue, May 28, 2019 at 11:16:51AM -0600, Theo de Raadt wrote: > I am hoping to get one also... and as a rule whatever I get my hands on tends > to work out well. > > danieljb...@icloud.com wrote: > > > I just ordered some E495s (not 'T', but pretty similar). I think > > they're supposed to arrive today. I'll do a test boot and send in a > > dmesg. > > > > On Tue, May 28, 2019 at 10:44:44AM -0400, David Anthony wrote: > > > All, > > > > > > The Lenovo release of T*95 series laptops with AMD Ryzen CPU appears > > > imminent. > > > > > > Would these be poor choices for OpenBSD? Are there any anticipated > > > ???gotchas??? that I should be aware of? Any thoughts would be greatly > > > appreciated. > > > > > > Respectfully, > > > David Anthony > > > > > >
Re: OpenBSD 6.5 dumps to debugger when using ifconfig bridge command
I have twice seen kernel panics in the same situation. It drops to "ddb>"
but the system is unresponsive. Unfortunately, other than taking a picture
of the screen with my cellphone, I do not have any further information from
the system. On both occasions, I was issuing "ifconfig bridge42" without
any arguments. (and no, there aren't 41 other bridges. 42 has other
significance in my network)
On Tue, Jun 4, 2019, 08:41 Russell Sutherland <
russell.sutherl...@utoronto.ca> wrote:
> I began to install resflash (https://stable.rcesoftware.com/resflash/)
> which is based on OpenBSD) to build a small firewall on an PC Engines apu2
> board. Three interfaces, two bridged and one with an IP for management.
>
> I found the system would crash and drop down to the debugger interface
> whenever I issued the:
>
> # ifconfig bridge0
>
> command.
>
> # ifconfig -a
>
> worked fine. After discussing this with the author we thought it good to
> try the same configuration on vanilla 6.5 install.
>
> This worked better, but after a short period of operation the same
> symptoms occured:
>
> # ifconfig bridge0
>
> bridge0: flags=4WAR1
>
> Nindex 6 llprio ING: SPL NOT
>
> groups: bridgLOWEe
>
> priority 327RED68 hellotime 2 f ONwddelay 15 maxag e 20 holdcnt 6
> pSYSCALL 5roto rstp
>
> desi4gnated: id 00:0 3 EXIT 0:00:00:00:00 pri 9
>
>ority 0
>
> agsStopped at savectx+0xb1: movl$0,%gs:0x508
>
> ddb{3}>
>
>
> Here is the output from dmesg:
>
>
> OpenBSD 6.5 (GENERIC.MP) #3: Sat Apr 13 14:48:43 MDT 2019
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> real mem = 1996148736 (1903MB)
> avail mem = 1926090752 (1836MB)
> 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.28 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,BM/tmp/qwe.txt
> (15I1,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.14 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.23 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.13 MHz, 16-30-01
> cpu3:
>
Re: OpenBSD 6.5 dumps to debugger when using ifconfig bridge command
Hi Russell
I had this issue when bridging vio() interfaces in kvm / proxmox ... but
not with em() interfaces
can you try with a uni-processor kernel ... to see does it crash / dump
? mpi@ had asked me to enable witness in the kernel and send the output
of the dumps
(I haven't gotten around to that yet ) ...
On Tue, 4 Jun 2019 at 16:45, Russell Sutherland <
russell.sutherl...@utoronto.ca> wrote:
> I began to install resflash (https://stable.rcesoftware.com/resflash/)
> which is based on OpenBSD) to build a small firewall on an PC Engines apu2
> board. Three interfaces, two bridged and one with an IP for management.
>
> I found the system would crash and drop down to the debugger interface
> whenever I issued the:
>
> # ifconfig bridge0
>
> command.
>
> # ifconfig -a
>
> worked fine. After discussing this with the author we thought it good to
> try the same configuration on vanilla 6.5 install.
>
> This worked better, but after a short period of operation the same
> symptoms occured:
>
> # ifconfig bridge0
>
> bridge0: flags=4WAR1
>
> Nindex 6 llprio ING: SPL NOT
>
> groups: bridgLOWEe
>
> priority 327RED68 hellotime 2 f ONwddelay 15 maxag e 20 holdcnt 6
> pSYSCALL 5roto rstp
>
> desi4gnated: id 00:0 3 EXIT 0:00:00:00:00 pri 9
>
>ority 0
>
> agsStopped at savectx+0xb1: movl$0,%gs:0x508
>
> ddb{3}>
>
>
> Here is the output from dmesg:
>
>
> OpenBSD 6.5 (GENERIC.MP) #3: Sat Apr 13 14:48:43 MDT 2019
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> real mem = 1996148736 (1903MB)
> avail mem = 1926090752 (1836MB)
> 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.28 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,BM/tmp/qwe.txt
> (15I1,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.14 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.23 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.13 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
OpenBSD 6.5 dumps to debugger when using ifconfig bridge command
I began to install resflash (https://stable.rcesoftware.com/resflash/) which is
based on OpenBSD) to build a small firewall on an PC Engines apu2 board. Three
interfaces, two bridged and one with an IP for management.
I found the system would crash and drop down to the debugger interface whenever
I issued the:
# ifconfig bridge0
command.
# ifconfig -a
worked fine. After discussing this with the author we thought it good to try
the same configuration on vanilla 6.5 install.
This worked better, but after a short period of operation the same symptoms
occured:
# ifconfig bridge0
bridge0: flags=4WAR1
Nindex 6 llprio ING: SPL NOT
groups: bridgLOWEe
priority 327RED68 hellotime 2 f ONwddelay 15 maxag e 20 holdcnt 6
pSYSCALL 5roto rstp
desi4gnated: id 00:0 3 EXIT 0:00:00:00:00 pri 9
ority 0
agsStopped at savectx+0xb1: movl $0,%gs:0x508
ddb{3}>
Here is the output from dmesg:
OpenBSD 6.5 (GENERIC.MP) #3: Sat Apr 13 14:48:43 MDT 2019
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 1996148736 (1903MB)
avail mem = 1926090752 (1836MB)
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.28 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,BM/tmp/qwe.txt
(15I1,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.14 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.23 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.13 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
Re: Security of OpenBSD
On 2019-06-03, Josef Pospisil wrote: > Hey, thank you all for this mailing list. > > I have a question regarding the security of OpebBSD. You can't really trust an answer to this question. What if somebody put in a backdoor but they're the person who answers saying everything's fine? > I am asuming that linux has some mathematics and logic that lets you > get into every system just for e.g. because of portknocking! > That opens an Interface for people that know the system to do > everything! I also think that linux is not beeing verified ragarding > these paid programer backholes. > > Can someone be that kind and explain to me if the whole code of OpenBSD > was checked at least once since the openBSD was founded? That there are > no backholes like i was describing? OpenBSD's own code generally gets a fair bit of review (and, importantly, tries to avoid practices which are considered unsafe). One can't say the same about all 3rd party code in the OS (including the compiler toolchain) though obviously we try to avoid junk software. The existence of bugs like "heartbleed" shows that code review doesn't always find things in time anyway. Was it a backdoor or "just a bug"? Who can tell? And on another level there are various CPU bugs like the Intel ones that have been discovered over the last couple of years, it all comes down to "who do you trust?" Also see Ken Thompson's classic paper, "Reflections on Trusting Trust", especially the moral.
