Re: OpenBSD Installation Doesn't Detect NVMe SSD, but Detects My USB Drives

[Brian Conway]

On Mon, Apr 15, 2024, at 1:29 AM, aliyu...@tutanota.com wrote:
> Hello,
>
> I'm currently trying to install OpenBSD on my laptop, and I'm coming
> across a problem. The installation only detects my installation drive
> and my other USB flash drive that I use for data storage, but not my
> NVMe SSD I want to do an installation on.
>
> This same problem also occurs in NetBSD, but not FreeBSD. The UEFI
> setup acknowledges my drive as a Non-RAID disk, and Linux also shows
> it as nvme0n1, so there isn't any problems with the drive itself.
>
> Running 'sysctl hw.disknames' only shows 3 disks:
>  'sd0' (my installation drive), 'sd1' (my media drive), and 'rd0'
>
> The disk currently has Alpine Linux installed on it, if that gives
> more information.
>
> Thanks for any help!
>
> Ali Yuruk

Sorry to hear of your trouble. I recommend including some actionable 
information, such as:

- make and model of the NVMe drive
- OpenBSD installer dmesg with the drive not recognized
- FreeBSD or Linux dmesg with the drive working

Brian Conway
Owner
RCE Software, LLC

Re: / not in RO after change in fstab

[Brian Conway]

On Thu, Apr 11, 2024, at 3:31 PM, Malo Langer wrote:
> Hey, 
> I configured my root directory ('/') to be read-only in the fstab on 
> CentOS 7.5 (see dmesg output below). However, the system does not boot 
> in read-only mode; I have to switch it to read-only manually.
> Did I miss something?
>
> Please find attached a copy of the 'fstab' contents and the output of 
> the 'mount' command
>
> Kind regards
> Attachments:
> * dmesg_75.txt
> * mount_75.txt
> * fstab_75.txt

This is intended:

https://github.com/openbsd/src/blob/4365136d4e2a201819da54e3e3bc8e95c1301f8e/etc/rc#L428

If you plan on bypassing that, you're wading into unsupported land. For 
example, you'll have an unpleasant time with a read-only /dev.

Brian Conway
Owner
RCE Software, LLC

Re: ipv6 assistance

[Brian Conway]

On Sat, Apr 6, 2024, at 10:09 AM, Sonic wrote:
> I'm on Comcast (Xfinity) in the US.

Your setup will be specific to your ISP. I'm on AT Fiber, which uses SLAAC 
for the WAN interface and DHCPv6-PD for internal interfaces. I do the latter 
with dhcpcd.

A quick search indicates Xfinity uses DHCPv6 for the WAN interface and 
DHCPv6-PD for internal interfaces. I haven't confirmed any of that, as I'm not 
a customer. You should be able to translate most Xfinity guides for use with 
OpenBSD, I would think.

Brian Conway
Owner
RCE Software, LLC

Re: Bash instead of ksh

[Brian Conway]

On Tue, Apr 2, 2024, at 10:08 PM, Nick Holland wrote:
> What is it that you see bash doing so much better than stock pdksh?

Multiline command editing.

(I don't use bash, but it would be a nice feature.)

Brian

Re: Request for a check 'relinking in progress' before a reboot

[Brian Conway]

On Fri, Mar 22, 2024, at 6:10 PM, Dan wrote:
> Hello,
>
> To avoid prbs with the relinking of the kernel happening in background
> I propose to set a little check during the shutdown to avoid to interrup it..
>
> Thnx!
>
> -Dan

I have frequently rebooted or shut down shortly after boot, for example when 
booting the wrong VM by accident, and it has never caused a problem on 
subsequent reboots. What problem are you actually experiencing, just the 
message being printed to the console?

My concern with the proposed patch is for my painfully slow system (embedded, 
i386, whatever) that may be locked out of reboot/halt for 3-5 minutes after 
booting.

Brian

Re: New (for me,) dmesg warning during system bootup.

[Brian Conway]

On Sun, Feb 25, 2024, at 4:27 PM, Avon Robertson wrote:
> I have noticed several posts related to endbr64 in the last week, so I
> thought this might be of interest to someone.
>
> Performed a 'sysupgrade -s' earlier today to:
> kern.version=OpenBSD 7.5-beta (GENERIC.MP) #25: Sat Feb 24 20:50:14 MST 2024
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
>
> The below was subsequently noticed in the system bootup messages.
>
> 
> pf enabled
> starting network
> reordering: ld.sold: warning: _dl_start: missing endbr64 libcld: 
> warning: __mcount: missing endbr64 libcrypto sshd.
> 
>
> -- 
> aer

https://marc.info/?t=17088928881

"It is unimportant and temporary."

Brian

Re: KeyTrap DNS vulnerability

[Brian Conway]

On Tue, Feb 13, 2024, at 9:55 PM, b...@fea.st wrote:
> “A single packet can exhaust the processing 
> capacity of a vulnerable DNS server, effectively
> disabling the machine, by exploiting a 
> 20-plus-year-old design flaw in the DNSSEC
> specification.
>
> https://www.theregister.com/2024/02/13/dnssec_vulnerability_internet/

-current and both -stable branches have been updated:

https://marc.info/?l=openbsd-cvs=2=1=CVE-2023-50387=b

Brian Conway
Owner
RCE Software, LLC

Re: Single partition fs layout

[Brian Conway]

On Tue, Feb 13, 2024, at 6:37 AM, Odhiambo Washington wrote:
> Is there a disadvantage to having this layout style where everything is on
> 1 partition?

Beyond the plethora of responses you've already received, the Installation 
section of the FAQ covers this thoroughly:

https://www.openbsd.org/faq/faq4.html#Partitioning

Brian Conway
Owner
RCE Software, LLC

Re: New postfix-3.8.20221007p12 broken TLS for Gmail servers?

[Brian Conway]

On Fri, Feb 2, 2024, at 6:44 PM, Herbert J. Skuhra wrote:
> On Sat, Feb 03, 2024 at 03:00:10AM +0300, Mark wrote:
>> Hi.
>> 
>> It seems that the recent Postfix update under 7.4-amd64,
>> (package: postfix-3.8.20221007p12-sasl2-mysql) breaks TLS connections,
>> coming from Gmail servers, throwing a TLS library problem.
>> 
>> Here's the log output;
>> 
>> postfix/smtpd[32879]: connect from mail-yw1-f178.google.com[209.85.128.178]
>> 
>> postfix/smtpd[7374]: Trusted TLS connection established from
>> mail-lf1-f45.google.com[209.85.167.45]: TLSv1.3
>> with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519
>> server-signature ECDSA (prime256v1) server-digest SHA256 client-signature
>> RSA-PSS (2048 bits) client-digest SHA256
>> 
>> postfix/smtpd[7374]: warning: TLS library problem: error:0A000126:SSL
>> routines::unexpected eof while reading:ssl/record/rec_layer_s3.c:308:
>> postfix/smtpd[7374]: lost connection after STARTTLS from
>> mail-lf1-f45.google.com[209.85.167.45]
>> postfix/smtpd[7374]: disconnect from mail-lf1-f45.google.com[209.85.167.45]
>> ehlo=1 starttls=1 commands=2
>> 
>> Before updating the package, I had postfix-3.8.20221007p11, and it had no
>> such problem.
>
> Why do you run such an outdated postfix snapshot?

That is the latest version that is supported/available in packages-stable:

https://cdn.openbsd.org/pub/OpenBSD/7.4/packages-stable/amd64/

Brian Conway
Owner
RCE Software, LLC

Re: Communication between hosts on different network interfaces

[Brian Conway]

On Sat, Jan 6, 2024, at 2:09 PM, Ibsen S Ripsbusker wrote:
> I also tried setting different subnets.
>
>   /etc/hostname.igc1:
>   inet 192.168.2.1/24
>
>   /etc/hostname.igc2:
>   inet 192.168.3.1/24

This is what I have done, with a pf rule to block connections originating from 
my less-trusted network to my more-trusted network. With the IP forwarding 
sysctl set, no routing magic or NAT is required. It works well for both IPv4 
and IPv6.

Brian

Re: Installing openBSD

[Brian Conway]

On Mon, Jul 31, 2023, at 12:00 PM, ykla wrote:
> Any manually created efi
> partition system will not be recognized.

I can assure you, it will (when done correctly). I have done so 
manually/scripted with EFI+GPT and EFI+MBR many times. An example of the less 
common EFI+MBR approach for the installer ramdisk is here:

https://github.com/openbsd/src/blob/master/distrib/amd64/ramdisk_cd/Makefile#L19

Maybe you can work backwards from it to see what you're doing wrong.

Brian

Re: High ACPI CPU load

[Brian Conway]

On Sat, Jul 15, 2023, at 5:38 PM, Julian Huhn wrote:
> On Sat, Jul 15, 2023 at 06:05:06PM +, Mike Larkin wrote:
>>On Sat, Jul 15, 2023 at 04:34:20PM +0200, Julian Huhn wrote:
>>> Since I got many DMARC rejection mails and therefore don't know how many
>>> people this mail reached at all, once again with less restrictive DMARC
>>> settings.
>>>
>>> On Sat, Jul 15, 2023 at 02:28:56PM +0200, Julian Huhn wrote:
>>> > Moin!
>>> >
>>> > A few weeks ago, I put a new system into operation, where I notice a
>>> > permanently high CPU load. With the help of top it appears that
>>> > permanently the process acpi0 is executed.
>>> >
>>> > Is this a bug?
>>> >
>>> > I'm happy to help with more logs, if you tell me what you need.
>>> >
>>> > --Huhn
>>> >
>>
>>This is a stuck GPE. This board in particular is a known issue; search
>>the lists.
>>
>>mbuhl@ suggested a few months back that I get one of these machines to fix
>>the issue, but when I started looking at it, the simplest fix was to just
>>install a new bios.  Since this is likely one of these super cheap 4 port
>>igc(4) aliexpress "firewall PCs", you may need to search a bit to find a
>>compatible bios since most of these don't have a real brand site associated
>>with them.
>>
>>FWIW, the machines with "techvision" bios (like yours) exhibit this issue.
>>Mine had techvision bios (and the same problem) before I flashed it to the
>>image described below.
>>
>>You need to find this bios:
>>
>>bios0: vendor American Megatrends International, LLC. version "JK4LV107" date 
>>04/17/2023
>
> I just found this Reddit Post [0], describing a related issue with this 
> kind of board. There's also a download link [1] in the comments for the 
> bios update. As soon as I found some time I will install the update. 
> Thanks!
>
>>That one works on my machine, with exactly the same config as yours. No
>>more ACPI GPE storm.
>>
>>I don't have the link anymore for where I found the BIOS image, but I
>>think it was on servethehome in one of the long threads about these
>>machines. You need to do some digging.
>>
>>While the root cause may be due to us lacking some driver for the device
>>owning that GPE, or our lack of activating GPEs based on attached
>>hardware, the 5-minute bios update fix was a good enough fix for me and
>>I moved on to other things.
>>
>>The other lesson I learned is that you get what you pay for; buying $100
>>PCs from aliexpress means you're just going to be paying for it somewhere
>>else. In this case, dealing with shoddy engineering and unsupported boards.
>>
>>-ml
>>
>>>
>
> [0] 
> https://www.reddit.com/r/PFSENSE/comments/14vv90w/topton_5105_n6005_owners_any_issues_running_on/
> [1] 
> https://pan.x86pi.cn/BIOS%E6%9B%B4%E6%96%B0/1.Intel%E8%BF%B7%E4%BD%A0%E4%B8%BB%E6%9C%BA%E7%B3%BB%E5%88%97BIOS/N5105%20V3-V5%20%E5%BE%AE%E7%A0%81%E6%9B%B4%E6%96%B023-04-18

I can confirm that the linked BIOS update resolves the stuck GPE on my board. I 
ended up using unetbootin to get the ISO in a state that my board was willing 
to boot and flash.

I appear to have lost the ability to redirect the BIOS via serial console with 
this update, but as noted, you get what you pay for.

Thanks all.

Brian

Re: patch-008 missing in CVS repo

[Brian Conway]

On Thu, Jul 13, 2023, at 9:13 AM, Stefan Sperling wrote:
> On Thu, Jul 13, 2023 at 08:49:06AM -0500, Brian Conway wrote:
>> I'm seeing the same. The commit email for 7.3-stable is here:
>> 
>> https://marc.info/?l=openbsd-cvs=168919043301821
>> 
>> But exec_elf.c shows no changes in the past 4 weeks to any branch:
>> 
>> https://cvsweb.openbsd.org/src/sys/kern/exec_elf.c
>> 
>> I see similar results when I try pulling from a couple anoncvs mirrors. 
>> Perhaps a bug or oops in the CVS update process?
>
> Keep waiting while more of Canada wakes up and it will likely get resolved.
> In the meantime you could fetch the patch from the errata page and apply
> it locally.

Looks resolved now, thanks all.

Brian

Re: patch-008 missing in CVS repo

[Brian Conway]

On Thu, Jul 13, 2023, at 12:40 AM, Yoshihiro Kawamata wrote:
> Of the recently announced OpenBSD 7.3 patches 006 through 009,
> 008 cannot be found on CVSweb.
>
> And even after cvs update, sys/kern/exec_elf.c remains unfixed.
>
> But, I was able to find patch-008 on GitHub.
>
> 
> Yoshihiro Kawamata
> https://fuguita.org

I'm seeing the same. The commit email for 7.3-stable is here:

https://marc.info/?l=openbsd-cvs=168919043301821

But exec_elf.c shows no changes in the past 4 weeks to any branch:

https://cvsweb.openbsd.org/src/sys/kern/exec_elf.c

I see similar results when I try pulling from a couple anoncvs mirrors. Perhaps 
a bug or oops in the CVS update process?

Brian Conway
Owner
RCE Software, LLC

Re: RSS or Atom syndication for security advisories?

[Brian Conway]

On Mon, May 22, 2023, at 9:59 AM, Xavier wrote:
> I don't know if you say it seriously. If you do, I think it's the best. 
> Perhaps you could write some semantic file and convert them to desired 
> format (html, RSS, etc.).
> I saw the www repo 
> (https://github.com/openbsd/www/blob/38884496ed89e3041dcaaeadaf21e20a918581ee/errata73.html)
>  
> and it seems you make things manually. Don't you think an static site 
> generator or some kind of tool to make things more automatic (I'm 
> thinking in mandoc conversion because all the web is really a big 
> documentation project)?
>
> Regards,
> Xavier

Done.

https://www.mail-archive.com/announce@openbsd.org/maillist.xml

Enjoy. Bye.

-b

Re: 7.2 panic and "reorder_kernel: failed" ...

[Brian Conway]

On Sun, Apr 30, 2023, at 8:14 AM, Why 42? The lists account. wrote:
> After running fsck manually to clean one of the filesystems I did an
> additional reboot, just to be sure the system would/could come up
> cleanly.
>
> I noticed this message on the console, seemingly as the system was
> shutting down:
>> stopping package daemons: nginx slowcgi postfix cyrus_imapd(killed) amavisd 
>> clamd sshguardreorder_kernel: failed -- see 
>> /usr/share/relink/kernel/GENERIC.MP/relink.log
>
> That relink.log file looks like this:
>> root:[~]# ls -ltr /usr/share/relink/kernel/GENERIC.MP/relink.log
>> -rw-r--r--  1 root  wheel  142 Apr 30 14:29 
>> /usr/share/relink/kernel/GENERIC.MP/relink.log
>
>> root:[~]# cat /usr/share/relink/kernel/GENERIC.MP/relink.log
>> (SHA256) /bsd: OK
>> LD="ld" sh makegap.sh 0x gapdummy.o
>> ld -T ld.script -X --warn-common -nopie -o newbsd ${SYSTEM_HEAD} vers.o 
>> ${OBJS}
>> root:[~]# 
>
> What might that mean? Is it significant?

I can't speak to the panic, but I think the relink error is just the background 
process getting killed when you rebooted the system immediately after finishing 
boot.

Brian Conway
RCE Software, LLC

Re: A messed-up fresh install due to a careless user

[Brian Conway]

On Sat, Apr 29, 2023, at 3:48 AM, Odd Martin Baanrud wrote:
> Yes, off course one should have a firewall.
> That was why I installed OpenBSD on the actual machine in the first place.
> I prepared it when it was on the LAN only, and then moved it into production.
> And now it works perfectely.
> But the firewall needed to be disabled while the machine was on the LAN only.

The default pf.conf is very sufficient for allowing incoming traffic in a LAN 
environment.

Brian Conway

Re: PC Engines APU2 infinite loop rebooting immediate after kernel loads

[Brian Conway]

On Mon, Apr 17, 2023, at 7:23 PM, Jonathan Thornburg wrote:
> Since two different kernels and boot devices result in the same
> infinite-reboot loop, with the reboot happening at the same place
> in the boot sequence (immediately after the kernel entry point address
> is printed), I don't think my problem is a corrupted kernel file.
> I've also tried swapping power supplies, with no change in the outcome.
>
> Has anyone seen this sort of problem (infinite reboot loop, rebooting
> immediately after kernel entry point address is printed) before?  Should
> I be looking at reflashing the BIOS with a newer (or older) version?

My first thought was bad power supply, but it looks like you've tried that. 
Your BIOS isn't *that* old, but you might consider trying a newer one 
(https://pcengines.github.io/). I'm using 4.17.0.3 successfully on a couple 
different apu2 configurations.

You could also try booting from a USB stick, I've run these devices with mSATA, 
SD card, or USB flash.

Brian Conway

Re: File system is full after using dd

[Brian Conway]

On Sat, Apr 15, 2023, at 9:14 AM, Lorenzo Torres wrote:
> Hello, I've run the dd command to wipe the data of an SD card:dd 
> if=/dev/zero of=/dev/rsdb1c bs=1MAfter quite some time it crashed 
> saying that the / filesystem is full and even after a reboot the same 
> happens. Now I can't even run xorg because the fs is full. Any idea on 
> why this happened?

Yes, you filled up your / partition with a garbage file. Run `ls -lS 
/dev/|head` and you will surely find it.

/dev/rsdb1c is not a valid drive and partition/slice combination. You probably 
meant rsd1c, but be careful to verify that when wiping.

Brian Conway
Lead Software Engineer, Owner
RCE Software, LLC

Re: Recent changes in the FAQ.

[Brian Conway]

On Fri, Mar 3, 2023, at 9:09 AM, Pascal Deveaux wrote:
> I want to install OpenBSD with full disk encryption.
>
> Why these recent changes in the FAQ in the section "Full Disk Encryption":
>
> -old-
> "if you use GPT for UEFI booting, do: # fdisk -iy -g -b 960 sd0"
>
> -new-
> "if you use GPT for UEFI booting, do: # fdisk -gy -b 532480 sd0"

This is the commit (prior to the www update) and rationale:

https://marc.info/?l=openbsd-cvs=166843427315447

Brian Conway
RCE Software, LLC

Re: PC Engines APU alternative for OpenBSD - 2022h2

[Brian Conway]

On Fri, Jan 13, 2023, at 8:34 PM, patrick keshishian wrote:
>> Search with keywords like "mini pc router", "pfsense router" etc,
>> you will find a load of boxes along these lines (to pick the first
>> one I found, there are loads of choices of all very similar hardware)
>> - https://www.aliexpress.com/item/1005004420642522.html?
>> They do have video out as well but you can just configure OpenBSD
>> to use serial console.
>>
>> Now that the 1G em(4) chips are out of stock everywhere, the common
>> NICs these days are igc(4) 2.5G ethernet (very common, to the extent that
>> "I225" will probably also do as a search term ..).
>
> I picked up one of these and just got it unpacked.
> I am failing to figure out how to boot from an external
> USB CDR to get OpenBSD installed on there.
>
> I'm connecting through the serial/COM port, but it
> automatically goes through the Pfsense/FreeBSD
> boot process and starts the "configuration" questions.
>
> Some reddit discussions seem to suggest pressing
> either F2 or Delete key at the first beep. But either
> I'm not quick enough, or I'm misunderstand something.
>
> Can someone offer any hints?
>
> --patrick

While they might exist, none of the mini PC/firewalls I've received from China 
support BIOS redirection over serial. If yours is the same, you'll want to hook 
up a monitor and keyboard and then either redirect bsd.rd over serial, or 
complete the installation and then set up a serial console going forward.

Another issue I've run into are BIOSes that disable all the CPU C-states by 
default. You will likely want to enable those for decent power 
management/cooling/power consumption.

Overall, I've enjoyed my AliExpress cheapies, but the firmware leaves a lot to 
be desired. They seem to be compiled with every option under the sun present, 
even if they don't apply to the hardware in question - other than the 
aforementioned serial BIOS redirection.

Brian Conway

Re: poor routing/nat performance

[Brian Conway]

On Mon, Dec 19, 2022, at 10:35 AM, David Hajes wrote:
> I am guessing HW is not issue.

I would not be totally sure on that. The CPU in the APU2 is pretty slow. While 
you can no doubt find some tweaked Linux or FreeBSD configurations that push it 
close to wire speed, the best I've ever been able to accomplish with the 
simplest pf.conf and forwarding between em0-em1 is 500-550 Mbps sustained, with 
occasional bursts to 600 Mbps. Research indicates others have had similar 
experiences.

If you check the misc@ list archive, you've find a bunch of threads with people 
looking for inexpensive alternatives to the APU2+ platform, and there are 
plenty in the $100-200 USD range for amd64. Most of my APU2s have been retired 
to terminal/console server duty.

> CPU bored, max. load 25%

It sounds like 1 of your 4 cores is maxed, which would not be surprising.

Brian Conway

Re: OpenBSD File systems , on Flash / SSD CPE (in sites with uncontrolled power (CPE customer sites)

[Brian Conway]

On Mon, Nov 28, 2022, at 4:06 PM, Tom Smyth wrote:
> /dev/sd0a / ffs rw,softdep,noatime 1 1
> /dev/sd0d /usr/local ffs rw,wxallowed,nodev,softdep,noatime 1 1

softdep is a useful option for metadata-heavy workloads, but it is not a 
magical go-fast flag. While it's possible that characterization is true for 
your /usr/local mount, I would guess it is probably not for /.

Brian

Re: CyberPower cp1500PPFCLCD

[Brian Conway]

On Sun, Nov 13, 2022, at 3:49 PM, Kenneth Hendrickson wrote:
> --- On Sunday, November 13, 2022, 01:56:12 PM EST, Peter Fraser 
>  wrote:
>
>> I replace it with a new CyberPower cp1500PPFCLCD.
>
> You poor bastard. If this company has anything to do with the 
> CyberPower PC

It does not.

https://www.cyberpowersystems.com/

Brian

Re: Slow clock on vmd guest, i386-specific

[Brian Conway]

Understood, thanks for the update. At least the i386 angle it will be
a little more searchable now.

Brian Conway

On Thu, Jan 10, 2019 at 12:28 AM Mike Larkin  wrote:
>
> On Wed, Jan 09, 2019 at 11:18:16PM -0600, Brian Conway wrote:
> > After looking through the mailing list archives, I'm seeking advice on
> > running an OpenBSD i386 guest successfully without losing too much
> > time. My host is an 8th-gen Intel NUC (dmesg *2 follows), and both the
> > host and any OpenBSD amd64 guest keep time beautifully using the tsc
> > time source. I've needed to make no changes to sysctl or HZ as
> > compiled in the kernel.
> >
> > When firing up an i386 guest to do some release(8) builds, I have no
> > issues with running those tasks, but the system loses time on the
> > order of 4-5 for every 20, even when sitting idle. It appears that
> > there is no tsc source found on i386, and taking a peak at
> > src/sys/arch/i386/i386 indicates that perhaps this isn't available?
> >
> > What's the preferred method to get such a guest in line? I've included
> > various sysctl, ntpd, and dmesg output below. All systems are running
> > 6.4-stable. Thanks!
> >
> > Brian Conway
> >
> > amd64 host kern.timecounter (amd64 guest is similar):
> > # sysctl kern.timecounter
> > kern.timecounter.tick=1
> > kern.timecounter.timestepwarnings=0
> > kern.timecounter.hardware=tsc
> > kern.timecounter.choice=i8254(0) acpihpet0(1000) tsc(2000)
> > acpitimer0(1000) dummy(-100)
> >
> > i386 guest:
> > kern.timecounter.tick=1
> > kern.timecounter.timestepwarnings=0
> > kern.timecounter.hardware=i8254
> > kern.timecounter.choice=i8254(0) dummy(-100)
> >
> > i386 guest after 20 minutes of uptime (jitter and delay reflect
> > redirection to a local ntp server):
> > -
> > $ ntpctl -s all
> > 4/4 peers valid, 1/1 sensors valid, constraint offset 3s (4 errors),
> > clock unsynced, clock offset is 26743.868ms
> >
> > peer
> >wt tl st  next  poll  offset   delay  jitter
> > 107.181.191.189 from pool us.pool.ntp.org
> > 1 10  3 1945s 3135s  6537.870ms 1.062ms 0.316ms
> > 142.147.92.5 from pool us.pool.ntp.org
> > 1 10  3 1898s 3086s  5915.575ms 0.854ms 0.082ms
> > 216.229.4.69 from pool us.pool.ntp.org
> > 1 10  3 1928s 3115s  5919.290ms 0.887ms 0.110ms
> > 216.6.2.70 from pool us.pool.ntp.org
> > 1 10  3 1825s 3017s  3889.790ms 0.852ms 0.115ms
> >
> > sensor
> >wt gd st  next  poll  offset  correction
> > vmmci0
> > 1  1  0   10s   15s   1277789.475ms 0.000ms
> > -
> >
> > i386 guest ntpd logs:
> > -
> > Jan 10 01:41:46 b64-i386 ntpd[5306]: ntp engine ready
> > Jan 10 01:41:47 b64-i386 ntpd[98096]: set local clock to Thu Jan 10
> > 01:41:47 UTC 2019 (offset 0.647554s)
> > Jan 10 01:41:47 b64-i386 savecore: no core dump
> > Jan 10 01:41:49 b64-i386 ntpd[5306]: constraint reply from
> > 172.217.2.228: offset 2.592767
> > Jan 10 01:42:09 b64-i386 ntpd[5306]: peer 216.229.4.69 now valid
> > Jan 10 01:42:11 b64-i386 ntpd[5306]: peer 216.6.2.70 now valid
> > Jan 10 01:42:12 b64-i386 ntpd[5306]: peer 142.147.92.5 now valid
> > Jan 10 01:42:14 b64-i386 ntpd[5306]: peer 107.181.191.189 now valid
> > Jan 10 01:43:05 b64-i386 ntpd[81307]: adjusting local clock by 33.008869s
> > Jan 10 01:44:06 b64-i386 ntpd[5306]: reply from 216.6.2.70: constraint
> > check failed
> > Jan 10 01:44:08 b64-i386 ntpd[5306]: reply from 107.181.191.189:
> > constraint check failed
> > Jan 10 01:44:10 b64-i386 ntpd[5306]: reply from 142.147.92.5:
> > constraint check failed
> > Jan 10 01:44:11 b64-i386 ntpd[5306]: reply from 216.229.4.69:
> > constraint check failed
> > ...
> > -
> >
> > amd64 host dmesg:
> > -
> > OpenBSD 6.4-stable (GENERIC.MP) #3: Mon Jan  7 01:46:29 UTC 2019
> > 
> > bcon...@nc.int.rcesoftware.com:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> > real mem = 8452431872 (8060MB)
> > avail mem = 8187002880 (7807MB)
> > mpath0 at root
> > scsibus0 at mpath0: 256 targets
> > mainbus0 at root
> > bios0 at mainbus0: SMBIOS rev. 2.8 @ 0x7a9a4000 (76 entries)
> > bios0: vendor Intel Corp. version "BECFL357.86A.0056.2018.1128.1717"
> > date 11/28/2018
> > bios0: Intel(R) Client Systems NUC8i5BEH
> > acpi0 at bios0: rev 2
> > acpi0: sleep states S0 S3 S4 S5
> > acpi0: tables DSDT FACP APIC FPDT FIDT MCFG SSDT SSDT SSDT HPET SSDT
> > SSDT UEFI LP

Slow clock on vmd guest, i386-specific

[Brian Conway]

After looking through the mailing list archives, I'm seeking advice on
running an OpenBSD i386 guest successfully without losing too much
time. My host is an 8th-gen Intel NUC (dmesg *2 follows), and both the
host and any OpenBSD amd64 guest keep time beautifully using the tsc
time source. I've needed to make no changes to sysctl or HZ as
compiled in the kernel.

When firing up an i386 guest to do some release(8) builds, I have no
issues with running those tasks, but the system loses time on the
order of 4-5 for every 20, even when sitting idle. It appears that
there is no tsc source found on i386, and taking a peak at
src/sys/arch/i386/i386 indicates that perhaps this isn't available?

What's the preferred method to get such a guest in line? I've included
various sysctl, ntpd, and dmesg output below. All systems are running
6.4-stable. Thanks!

Brian Conway

amd64 host kern.timecounter (amd64 guest is similar):
# sysctl kern.timecounter
kern.timecounter.tick=1
kern.timecounter.timestepwarnings=0
kern.timecounter.hardware=tsc
kern.timecounter.choice=i8254(0) acpihpet0(1000) tsc(2000)
acpitimer0(1000) dummy(-100)

i386 guest:
kern.timecounter.tick=1
kern.timecounter.timestepwarnings=0
kern.timecounter.hardware=i8254
kern.timecounter.choice=i8254(0) dummy(-100)

i386 guest after 20 minutes of uptime (jitter and delay reflect
redirection to a local ntp server):
-
$ ntpctl -s all
4/4 peers valid, 1/1 sensors valid, constraint offset 3s (4 errors),
clock unsynced, clock offset is 26743.868ms

peer
   wt tl st  next  poll  offset   delay  jitter
107.181.191.189 from pool us.pool.ntp.org
1 10  3 1945s 3135s  6537.870ms 1.062ms 0.316ms
142.147.92.5 from pool us.pool.ntp.org
1 10  3 1898s 3086s  5915.575ms 0.854ms 0.082ms
216.229.4.69 from pool us.pool.ntp.org
1 10  3 1928s 3115s  5919.290ms 0.887ms 0.110ms
216.6.2.70 from pool us.pool.ntp.org
1 10  3 1825s 3017s  3889.790ms 0.852ms 0.115ms

sensor
   wt gd st  next  poll  offset  correction
vmmci0
1  1  0   10s   15s   1277789.475ms 0.000ms
-

i386 guest ntpd logs:
-
Jan 10 01:41:46 b64-i386 ntpd[5306]: ntp engine ready
Jan 10 01:41:47 b64-i386 ntpd[98096]: set local clock to Thu Jan 10
01:41:47 UTC 2019 (offset 0.647554s)
Jan 10 01:41:47 b64-i386 savecore: no core dump
Jan 10 01:41:49 b64-i386 ntpd[5306]: constraint reply from
172.217.2.228: offset 2.592767
Jan 10 01:42:09 b64-i386 ntpd[5306]: peer 216.229.4.69 now valid
Jan 10 01:42:11 b64-i386 ntpd[5306]: peer 216.6.2.70 now valid
Jan 10 01:42:12 b64-i386 ntpd[5306]: peer 142.147.92.5 now valid
Jan 10 01:42:14 b64-i386 ntpd[5306]: peer 107.181.191.189 now valid
Jan 10 01:43:05 b64-i386 ntpd[81307]: adjusting local clock by 33.008869s
Jan 10 01:44:06 b64-i386 ntpd[5306]: reply from 216.6.2.70: constraint
check failed
Jan 10 01:44:08 b64-i386 ntpd[5306]: reply from 107.181.191.189:
constraint check failed
Jan 10 01:44:10 b64-i386 ntpd[5306]: reply from 142.147.92.5:
constraint check failed
Jan 10 01:44:11 b64-i386 ntpd[5306]: reply from 216.229.4.69:
constraint check failed
...
-

amd64 host dmesg:
-
OpenBSD 6.4-stable (GENERIC.MP) #3: Mon Jan  7 01:46:29 UTC 2019
bcon...@nc.int.rcesoftware.com:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8452431872 (8060MB)
avail mem = 8187002880 (7807MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0x7a9a4000 (76 entries)
bios0: vendor Intel Corp. version "BECFL357.86A.0056.2018.1128.1717"
date 11/28/2018
bios0: Intel(R) Client Systems NUC8i5BEH
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT FIDT MCFG SSDT SSDT SSDT HPET SSDT
SSDT UEFI LPIT SSDT SSDT DBGP DBG2 SSDT DMAR BGRT WSMT
acpi0: wakeup devices SIO1(S3) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4)
PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) PXSX(S4)
RP06(S4) PXSX(S4) RP07(S4) PXSX(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-8259U CPU @ 2.30GHz, 2195.91 MHz, 06-8e-0a
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,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,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 24MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Core(TM) i5-8259U CPU @ 2.30GHz, 2

Re: NFS daemon is very slow in server-to-client direction in TCP mode

[Brian Conway]

I ran into that same behavior with a Debian client before lowering the
readsize and writesize in the NFS mount options (they defaulted to 64K I
believe). Try starting at 8096 and working your way up until you find the
failure point.

Brian Conway
Software Engineer, Owner
RCE Software, LLC

I was using nfs service on OpenBSD (amd64) since version 5.6.

The whole setup process repeats the steps in official FAQ on the OpenBSD's
homepage.
The problem was and remains (now in version 5.9 amd64):
in TCP mode the upload speed is about 20-30MB/s
which is quite acceptable for my needs, but the download speed is about
32Kb/s.

As a workaround I had set up the debain client to connect to my NFS-server
in UDP mode.
In that mode the speed was good in both directions.

In recent versions of debian OS the UDP option for NFS-client disappeared.
The question is: is it possible to fix TCP mode in NFS server or is it
still the problem of the NFS client?

Best Regards
Rodin Maxim

Re: Does a softraid partition require an fdisk partition

[Brian Conway]

> Since the softraid volume doesn't have the base OS installed on it, and will
> never be used as a "boot device," I think I am ok, but am not sure.

You are correct.

Brian

Re: unbound eats up buffer space

[Brian Conway]

Are you using pf queues? I most frequently see that happen when there's no
space left in a queue. `pfctl -v -s queue`

Brian Conway


On Mar 8, 2016 1:52 AM, "Marko Cupać" <marko.cu...@mimar.rs> wrote:

> Hi,
>
> I have 5.8 i386 box as my home network gateway, with unbound as a
> resolver for local LAN. I am getting these in my log:
>
> Mar  8 08:21:42 kerber unbound: [24074:0] notice: sendto failed: No
> buffer space available
> Mar  8 08:21:42 kerber unbound: [24074:0] notice: remote address is
> 192.168.33.1 port 60829
>
> Any advices? Thank you in advance.
> --
> Before enlightenment - chop wood, draw water.
> After  enlightenment - chop wood, draw water.
>
> Marko Cupać
> https://www.mimar.rs/

Re: openbsd 4.7 virtual machine on hyper-v

[Brian Conway]

If this is the de interface from hyper-v, there were fixes for it a release
or two back. 4.7 is ancient, you need to upgrade.

Brian Conway


On Mar 1, 2016 7:10 AM, "Markus Rosjat" <ros...@ghweb.de> wrote:

> Hi there,
>
> I ported a vm from vmware to hyper-v. the machine boots up, weel some
> services are failing for now but thats not the issue. I can dont get the
> network adapter working properly. I get the nic and I changed some stuff
> like ip, mygate added a new default route but I cant really ping anything
> (not from or to the machine). PF is disabled for now so Im sure thats not
> the problem, I wrote some post on the net about problems with openBSD and
> hyper-v so general question is...
>
> is hyper-v able to run a openbsd vm at all?
>
> regards
>
> --
> Markus Rosjatfon: +49 351 8107223mail: 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: [SOLVED] with pain / was: APU2 WLE200NX ATHN0: Device timeout

[Brian Conway]

> I still experienced hangup on reboot after rebuilding 5.9-beta amd64 ...
> So a switch has to be manually flipped for restarting the box after /bsd
> upgrade.
>
> Do you have the same ?

[OT] I experience the flaky reboot issue (usually after running for a
few days) on my apu2b2 with 5.8-stable. I spoke with the folks at PC
Engines and they believe it to be a hardware issue and are sending me
a replacement board. This is with the 190 BIOS, I haven't had a chance
to try the newer apu2_160120.zip at http://pcengines.ch/howto.htm#bios
.

Brian

Re: xz: (stdin): Cannot allocate memory

[Brian Conway]

Have you read the xz man page, specifically on memory requirements?
9-extreme is probably not what you want - it's fairly insane/placebo. Full
dmesg with memory information is needed beyond that.

Brian Conway


On Jan 30, 2016 7:18 AM, "Lampshade" <lampsh...@poczta.fm> wrote:

> Hello
> I have this OS with packages as of yesterday (Jan 29):
> kern.version=OpenBSD 5.9-beta (GENERIC.MP) #1865: Thu Jan 28 20:18:15 MST
> 2016
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
>
> and also tested on with packages around Jan 17:
> kern.version=OpenBSD 5.9-beta (GENERIC.MP) #1846: Sun Jan 17 02:34:54 MST
> 2016
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
>
> I have following error:
> cat archive.tar | xz -zf --format=xz -9e --threads=2 - > archive.tar.xz
> xz: (stdin): Cannot allocate memory

Re: bandwidth usage limits with pf, etc.

[Brian Conway]

systat will show you most of what pftop does, no package necessary.

http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man1/systat.1?query=systat=1

Brian Conway

On Dec 31, 2015 2:30 PM, "Mark Carroll" <m...@ixod.org> wrote:

> I was wondering recently what the biggest bandwidth hogs were on my home
> network at a certain moment. On Linux I use iftop on the router for
> this, but I wonder in OpenBSD if, rather than install the iftop package,
> there's something different -- more OpenBSD-ish -- I should be doing
> with clients to pflow or whatever to achieve this same near-instanteous
> view of machines' Internet usage across the router (which NATs them from
> their LAN).
>
> Lately I've been reading about CARP and discovering that the packet
> filter code has all kinds of cool stuff built in for transparent
> load-balancing and failover. And, I like the keep-state stuff that lets
> me do things like rate-limit ssh connections. So, I'm thinking that PF
> may offer me all manner of wonders. So, I got to thinking today:
>
> I wondered about my kids' use of YouTube and suchlike, and I wondered if
> there's a good way of using PF on the router to give them a weekly
> download limit, perhaps cumulative over their devices, after which it
> gets limited to a slow crawl or even cut off. Is this (or some variant
> thereof) something that PF makes easy (any pointers?), or is tricky but
> clearly described in the latest Book of PF, or just not worth the effort
> of attempting -- any thoughts? I may have just picked the wrong web
> search terms, or maybe this just isn't yet at all easy.
>
> (... and Happy New Year!)
>
> -- Mark

Re: APU2: no boot from internal mSATA storage

[Brian Conway]

You probably need to contact the folks at PC Engines for a newer beta
bios. I've seen rel-1.8.0-143, -181, and -190, and I recall at least
one of them included updated boot support. There may be newer
available as well.

Brian Conway

On Wed, Dec 23, 2015 at 12:32 PM, Kapfhammer, Stefan <sk...@skapf.de> wrote:
> Hello,
>
> recently I got it and installed OpenBSD 5.8 on an APU-2 to the internal
> mSATA SSD (16 GByte).
> After rebooting the system it's running into memtest instead of booting the
> internal sd0.
> When I boot from the USB storage, I can mount the mSATA storage and see,
> that the installation
> is IMHO correct. Also /etc/boot.conf (on sd0) contains the correct
> redirection to com0 with 115200 baud.
>
> At boot time I changed the boot order to mSATA in first line and saved with
> "E"
>
> Won't boot from sd0.
>
> Have I overseen something important?

Re: APU2: no boot from internal mSATA storage

[Brian Conway]

Bios and APU2 flashing tools here (3rd post):

http://www.pcengines.info/forums/?page=post=44BEA6F6-FC84-4F4B-BCE8-34A00764910B=DF5ACB70-99C4-4C61-AFA6-4C0E0DB05B2A

Brian Conway

On Wed, Dec 23, 2015 at 2:01 PM, Kapfhammer, Stefan <sk...@skapf.de> wrote:
> Hello Brian,
>
> thank you for your quick reply. Do you have an URL, where the beta bios are
> available?
> No one in the office right now :-( and tomorrow I don't believe they are, too.
>
> Friendly regards,
>
> Stefan
>
>
>
> You probably need to contact the folks at PC Engines for a newer beta bios.
> I've seen rel-1.8.0-143, -181, and -190, and I recall at least one of them
> included updated boot support. There may be newer available as well.

Re: Understanding 'disklabel -T' math

[Brian Conway]

Great, thanks. I was about to make a diff for the -T template section
below that and change "and percentage of disk" to "and percentage of
remaining space", but that certainly clarifies it.

Brian Conway

On Mon, Dec 21, 2015 at 1:43 PM, Otto Moerbeek <o...@drijf.net> wrote:
> On Mon, Dec 21, 2015 at 05:16:31PM +0100, Otto Moerbeek wrote:
>
>> On Mon, Dec 21, 2015 at 09:30:12AM -0600, Brian Conway wrote:
>>
>> > I'm hoping someone can enlighten me, as I think I'm misunderstanding
>> > the man page.
>> >
>> > I'm using a simplified test case with a 12 GB disk and a template of
>> > the following:
>> > / 256M
>> > swap  256M
>> > /tmp  256M
>> > /var  256M
>> > /usr  5.5G-* 80%
>> > /home 1G-*   20%
>> >
>> > Based on how I'm reading the man page, disklabel should first allocate
>> > all the minimums, and then allocate the remaining free space evenly
>> > between /usr and /home. It would first hit the 20% limit on /home
>>
>> nope, it will add 80% of the unallocated space to /usr and 20% to
>> /home, neither of them has a maxium size.
>>
>>   -Otto
>
> This difff explaines it a bit better in the man page, I believe,
>
> -Otto
>
>
> Index: disklabel.8
> ===
> RCS file: /cvs/src/sbin/disklabel/disklabel.8,v
> retrieving revision 1.117
> diff -u -p -r1.117 disklabel.8
> --- disklabel.8 16 Oct 2015 04:20:54 -  1.117
> +++ disklabel.8 21 Dec 2015 19:41:39 -
> @@ -505,9 +505,9 @@ and are not modified during the allocati
>  Disk size determines the set of partitions which are created.
>  Each partition is allocated space between a specified minimum
>  and maximum.
> -Each partition is allocated its minimum and remaining space
> -is split between the partitions up to their maximum allowed space,
> -which is a fixed percentage.
> +Initially, each partition is allocated its minimum and remaining space
> +is split between the partitions according to the given percentages,
> +up to their maximum allowed space.
>  Space left after all partitions have reached their maximum size
>  is left unallocated.
>  The sizes below are approximations,

Understanding 'disklabel -T' math

[Brian Conway]

I'm hoping someone can enlighten me, as I think I'm misunderstanding
the man page.

I'm using a simplified test case with a 12 GB disk and a template of
the following:
/ 256M
swap  256M
/tmp  256M
/var  256M
/usr  5.5G-* 80%
/home 1G-*   20%

Based on how I'm reading the man page, disklabel should first allocate
all the minimums, and then allocate the remaining free space evenly
between /usr and /home. It would first hit the 20% limit on /home
after allocating 1.4 GB to both, and then give the rest to /usr up to
the size of the disk. I'd envision the following totals:
/ 256M
swap  256M
/tmp  256M
/var  256M
/usr  8.6G
/home 2.4G

Instead, what I see after autoinstall is the following:
# echo 'p m\nq'|disklabel -E sd0
Label editor (enter '?' for help at any prompt)
> OpenBSD area: 64-25157790; size: 12284.0M; free: 0.0M
#size   offset  fstype [fsize bsize  cpg]
  a:   256.0M   64  4.2BSD   2048 163841 # /
  b:   256.0M   524352swap   # none
  c: 12288.0M0  unused
  d:   256.0M  1048640  4.2BSD   2048 163841 # /tmp
  e:   256.0M  1572928  4.2BSD   2048 163841 # /var
  f:  9315.2M  2097216  4.2BSD   2048 163841 # /usr
  g:  1944.8M 21174752  4.2BSD   2048 163841 # /home
> No label changes.
#

I tried using M(egabytes) across the board in my template, in case it
was some weird unit issue, but no change. Thanks for any insight.

Brian Conway

OpenBSD 5.8-current (GENERIC.MP) #1757: Sat Dec 19 08:17:18 MST 2015
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 1056899072 (1007MB)
avail mem = 1020792832 (973MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xe1000 (10 entries)
bios0: vendor innotek GmbH version "VirtualBox" date 12/01/2006
bios0: innotek GmbH VirtualBox
acpi0 at bios0: rev 2
acpi0: sleep states S0 S5
acpi0: tables DSDT FACP APIC SSDT
acpi0: wakeup devices
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-3615QM CPU @ 2.30GHz, 2295.35 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,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,RDRAND,HV,NXE,LONG,LAHF,ITSC
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: CPU supports MTRRs but not enabled by BIOS
cpu0: apic clock running at 999MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i7-3615QM CPU @ 2.30GHz, 2294.95 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,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,RDRAND,HV,NXE,LONG,LAHF,ITSC
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Core(TM) i7-3615QM CPU @ 2.30GHz, 2295.07 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,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,RDRAND,HV,NXE,LONG,LAHF,ITSC
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 0, package 1
ioapic0 at mainbus0: apid 3 pa 0xfec0, version 11, 24 pins
acpiprt0 at acpi0: bus 0 (PCI0)
acpicpu0 at acpi0: C1(@1 halt!)
acpicpu1 at acpi0: C1(@1 halt!)
acpicpu2 at acpi0: C1(@1 halt!)
acpibat0 at acpi0: BAT0 model "1" serial 0 type VBOX oem "innotek"
acpiac0 at acpi0: AC unit online
acpivideo0 at acpi0: GFX0
pvbus0 at mainbus0: KVM
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02
pcib0 at pci0 dev 1 function 0 "Intel 82371SB ISA" rev 0x00
vga1 at pci0 dev 2 function 0 "InnoTek VirtualBox Graphics Adapter" rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
em0 at pci0 dev 3 function 0 "Intel 82540EM" rev 0x02: apic 3 int 19,
address 08:00:27:33:b5:e0
"InnoTek VirtualBox Guest Service" rev 0x00 at pci0 dev 4 function 0
not configured
piixpm0 at pci0 dev 7 function 0 "Intel 82371AB Power" rev 0x08: SMBus disabled
ahci0 at pci0 dev 13 function 0 "Intel 82801HBM AHCI" rev 0x02: apic 3
int 21, AHCI 1.1
ahci0: device on port 0 didn't come ready, TFD: 0x171
ahci0: port 0: 3.0Gb/s
scsibus1 at ahci0: 32 targets
sd0 at scsibus1 targ 0 lun 0: <ATA, VBOX HARDDISK, 1.0> SCSI3 0/direct
fixed t10.ATA_VBOX_HARDDISK_VBe8683464-c47fcb99_
sd0: 12288MB, 512 bytes/sector, 25165824 sectors
isa0 at pcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
wsmouse0 at pms0 mux 0
pcppi0 at isa0 port 0x61
spk

Re: home keys in tmux

[Brian Conway]

Spending a little time with 'cat -v', I ended up with the following
non-.tmux.conf approach to making home/end happy in tmux with an
otherwise-unmodified ksh shell:

bind '^[[1~'=beginning-of-line
bind '^[[4~'=end-of-line

It doesn't appear to break normal xterm[-256color] use.

These are still workarounds, of course.

Brian Conway

On Wed, Dec 2, 2015 at 10:17 AM, Ted Unangst <t...@tedunangst.com> wrote:
> Ax0n wrote:
>> Do you have anything in your .tmux.conf?
>
> No, don't have one. (i don't want one)

Re: apu1d as an NTP server

[Brian Conway]

How large is your network?

Brian Conway


On Oct 23, 2015 5:42 PM, "Gene" <gh5...@gmail.com> wrote:

> Howdy,
>
> Has anyone here used the PC Engines apu1d system board as an NTP server?
>
> I'm looking at setting up some in house stratum-2 servers so I can be a
> better neighbor.  Wondering what kind of performance/capacity others have
> seen with this board.
>
> Thanks for your time.
>
> -Gene

Re: "dd if=/dev/srandom of=/dev/wd0e bs=1024 count=1" WIPES my wd0 disklabel. Is this intended, bug, how come, how workaround ??? Incl reproduction script+console output+dmesg

[Brian Conway]

There were also some excellent diagrams generated the last time this
came up for discussion:

https://marc.info/?l=openbsd-misc=141520160709490=2

FWIW.

Brian

Re: UEFI boot attempt on AM1 platform with logs (9/16 snapshot)

[Brian Conway]

> +   /* must not reach here */
> return (EFI_SUCCESS);
>  }
>
> @@ -212,6 +235,15 @@ efi_memprobe(void)
>  {
> u_intn = 0;
> bios_memmap_t   *bm;
> +   EFI_STATUS   status;
> +   EFI_PHYSICAL_ADDRESS
> +addr = 0x1000ULL;  /* Below 256MB */
> +
> +   status = EFI_CALL(BS->AllocatePages, AllocateMaxAddress, 
> EfiLoaderData,
> +   EFI_SIZE_TO_PAGES(KERN_LOADSPACE_SIZE), );
> +   if (status != EFI_SUCCESS)
> +   panic("BS->AllocatePages()");
> +   efi_loadaddr = addr;
>
> printf(" mem[");
> efi_memprobe_internal();
> @@ -236,7 +268,7 @@ efi_memprobe_internal(void)
> UINT32   mmver;
> EFI_MEMORY_DESCRIPTOR   *mm0, *mm;
> int  i, n;
> -   bios_memmap_t*bm, bm0;
> +   bios_memmap_t   *bm, bm0;
>
> cnvmem = extmem = 0;
> bios_memmap[0].type = BIOS_MAP_END;
> Index: sys//arch/amd64/stand/libsa/exec_i386.c
> ===
> RCS file: /cvs/src/sys/arch/amd64/stand/libsa/exec_i386.c,v
> retrieving revision 1.14
> diff -u -p -r1.14 exec_i386.c
> --- sys//arch/amd64/stand/libsa/exec_i386.c 2 Sep 2015 04:09:24 - 
>   1.14
> +++ sys//arch/amd64/stand/libsa/exec_i386.c 5 Oct 2015 04:42:04 -
> @@ -37,6 +37,7 @@
>
>  #include "disk.h"
>  #include "libsa.h"
> +#include "cmd.h"
>
>  #ifdef SOFTRAID
>  #include 
> @@ -72,8 +73,11 @@ run_loadfile(u_long *marks, int howto)
> bios_bootsr_t bootsr;
> struct sr_boot_volume *bv;
>  #endif
> +#if defined(EFIBOOT)
> +   int i;
> +   u_long delta;
> +   extern u_long efi_loadaddr;
>
> -#ifdef EFIBOOT
> if ((av = alloc(ac)) == NULL)
> panic("alloc for bootarg");
> efi_makebootargs();
> @@ -131,17 +135,29 @@ run_loadfile(u_long *marks, int howto)
> printf("entry point at 0x%lx [%x, %x, %x, %x]\n", entry,
> ((int *)entry)[0], ((int *)entry)[1],
> ((int *)entry)[2], ((int *)entry)[3]);
> -
> -#if defined(EFIBOOT)
> +#ifndef EFIBOOT
> +   /* stack and the gung is ok at this point, so, no need for asm setup 
> */
> +   (*(startfuncp)entry)(howto, bootdev, BOOTARG_APIVER, marks[MARK_END],
> +   extmem, cnvmem, ac, (int)av);
> +#else
> +   /*
> +    * Move the loaded kernel image to the usual place after calling
> +* ExitBootServervice()
> +*/
> +   delta = DEFAULT_KERNEL_ADDRESS - efi_loadaddr;
> efi_cleanup();
> -#endif
> -#if defined(EFIBOOT) && defined(__amd64__)
> +   memcpy((void *)marks[MARK_START] + delta, (void *)marks[MARK_START],
> +   marks[MARK_END] - marks[MARK_START]);
> +   for (i = 0; i < MARK_MAX; i++)
> +   marks[i] += delta;
> +   entry += delta;
> +#ifdef __amd64__
> (*run_i386)((u_long)run_i386, entry, howto, bootdev, BOOTARG_APIVER,
> marks[MARK_END], extmem, cnvmem, ac, (intptr_t)av);
>  #else
> -   /* stack and the gung is ok at this point, so, no need for asm setup 
> */
> (*(startfuncp)entry)(howto, bootdev, BOOTARG_APIVER, marks[MARK_END],
> extmem, cnvmem, ac, (int)av);
> -   /* not reached */
>  #endif
> +#endif
> +   /* not reached */
>  }
>
>
> On Wed, 30 Sep 2015 21:24:09 -0500
> Brian Conway <bcon...@rcesoftware.com> wrote:
>> Fantastic!
>>
>> Brian Conway
>> Software Engineer, Owner
>> RCE Software, LLC
>>
>> On Sep 30, 2015 9:11 PM, "YASUOKA Masahiko" <yasu...@openbsd.org> wrote:
>>
>>> I got a AM1l and I could repeat the problem.  I'll try to fix the
>>> problem on this weekend.
>>>
>>> On Sun, 27 Sep 2015 19:55:07 -0500
>>> Brian Conway <bcon...@rcesoftware.com> wrote:
>>> > Thanks for all your hard work. Let me know if there's any additional
>>> > testing I can provide.
>>> >
>>> > Brian Conway
>>> > Software Engineer, Owner
>>> > RCE Software, LLC
>>> >
>>> >
>>> > On Sun, Sep 27, 2015 at 6:23 PM, YASUOKA Masahiko <yasu...@openbsd.org>
>>> wrote:
>>> >> Thank you for your report.
>>> >>
>>> >> On Sun, 27 Sep 2015 14:08:49 -0500
>>> >> Brian Conway <bcon...@rcesoftware.com> wrote:
>>> >>> Great, we're getting closer! The kernel finishes loading, there's a
>>> >>> quick screen flash with a resolution change and I see "entry point at
>>> >>> ..." for a split second, and then the system reboots and the bios
>>> >>> loading screen comes up.
>>> >>>
>>> >>> Thanks again.
>>> >>>
>>> >>> Brian Conway

Re: mini itx from intel

[Brian Conway]

> We don't have a boot 'failure' per se (the board technically boots fine with
> no display), rather if there's no screen attached during boot then it
> completely disables video and never recognizes a screen attached later, ie;
> you have to reboot to get video back.
>
> Do these 'dummy plugs' help solve issues like that? And/or is there a way to
> 'kickstart' the video back in to life without having to reboot?

Different issue, I think. In the case of my NUC DN2820FYKH, the system
powers up and remains powered on, but never advances to booting the OS
unless a valid monitor or dummy plug is attached.

I can't speak to the kickstarting the video case, unfortunately.

Brian

Re: mini itx from intel

[Brian Conway]

FYI- My 2820 won't boot reliably headless without an HDMI dummy plug
attached (such as
http://www.amazon.com/CompuLab-fit-Headless-Display-Emulator/dp/B00FLZXGJ6),
even with the latest BIOS. These seem to be hit or miss in a headless
configuration, and not everyone has the HDMI boot failure issue, so
you may luck out.

Brian Conway
Software Engineer, Owner
RCE Software, LLC


On Fri, Oct 2, 2015 at 10:55 AM, frantisek holop <min...@obiit.org> wrote:
> thanks everyone for the dmesg.
> i bought 2 of these with 8G of RAM
> and intel SSD drives.
>
> they will be used as headless servers,
> so DRM is not an issue, i was aware of that.
>
> they are remote, so openbsd is not installed
> on them yet, and i had the techie remove
> the wlans, as they will be in a small
> server room connected to a switch,
> so hopefully overheating won't be a problem.
>
> i was surprised they have fans,
> i was aiming for a fanless configuration,
> but the offer is not that big here in
> the eu, at least from what i saw.
>
> i know they are not powerhouses,
> but compared to what i have now,
> they actually are.
>
> -f
> --

Re: UEFI boot attempt on AM1 platform with logs (9/16 snapshot)

[Brian Conway]

> This picture shows
>
>   Load address: Loader Data (2) 0xd0 for 4096KB FATAL
>
> This is what I want to know.  0xd0 + 4M is overlapping the kernel
> area.
>
> I think the following diff or
>
>   http://yasuoka.net/~yasuoka/BOOTX64.EFI
>   (updated)
>
> will fix the problem.

Great, thanks. I grabbed the updated binary. `machine memory` is
looking better, but no improvement on the boot situation, yet. This is
with the latest install58.fs from 9/23 with BOOTX64.EFI replaced.

http://i.imgur.com/oiEO3fr.jpg

http://i.imgur.com/adwNcnk.jpg

Re: UEFI boot attempt on AM1 platform with logs (9/16 snapshot)

[Brian Conway]

> Can you try the diff following or
>
>   http://yasuoka.net/~yasuoka/BOOTX64.EFI
>
> ?  Then enter "machine memory" on "boot> " prompt and check the last line.
> It shows whether the memory area for kernel is free or not.  Like
>
>   Load address: Conventional(7) 0x for KB
>
> is good sign.

Great, thanks. I grabbed the binary.

machine memory:

http://i.imgur.com/gtiAIxc.jpg

Another boot attempt, with hang (hd0d is intentional):

http://i.imgur.com/tcVm4r6.jpg

>> boot> machine disk
>> DiskBIOS#   TypeCylsHeads   SecsFlags   Checksum
>> hd0 0x80label   956 64  32  0x2 0xe4afa028
>> hd1 0x81label   1023255 63  0x0 0x0
>> boot>
>
> Isn't this a result of BIOS boot?

Yes, my bad.

Thanks.

Brian

Re: rc.shutdown powerdown

[Brian Conway]

Powerdown went away in July 2014.

https://marc.info/?l=openbsd-cvs=140532869022004=2

Also, rc.shutdown doesn't exist by default anymore (/etc/examples).

Brian Conway
Software Engineer, Owner
RCE Software, LLC


On Sun, Sep 20, 2015 at 1:01 PM, Quartz <qua...@sneakertech.com> wrote:
> Can someone explain in better detail what exactly the "powerdown=" line in
> rc.shutdown does? I have a few machines that range from full apm/acpi
> support to hardly none, but that line doesn't seem to affect anything on any
> of them, regardless what it's set to or if it's omitted completely.

Re: Cheap hardware for router, perhaps fileserver?

[Brian Conway]

Consider PC Engines APU series for relative low cost, fanless, and runs
amd64. Soekris are also popular, and a bit more expensive.

Brian

UEFI boot attempt on AM1 platform with logs (9/16 snapshot)

[Brian Conway]

sector, 1953525168 sectors
ohci0 at pci0 dev 18 function 0 "AMD Hudson-2 USB" rev 0x39: apic 5
int 18, version 1.0, legacy support
ehci0 at pci0 dev 18 function 2 "AMD Hudson-2 USB2" rev 0x39: apic 5 int 17
usb1 at ehci0: USB revision 2.0
uhub1 at usb1 "AMD EHCI root hub" rev 2.00/1.00 addr 1
ohci1 at pci0 dev 19 function 0 "AMD Hudson-2 USB" rev 0x39: apic 5
int 18, version 1.0, legacy support
ehci1 at pci0 dev 19 function 2 "AMD Hudson-2 USB2" rev 0x39: apic 5 int 17
usb2 at ehci1: USB revision 2.0
uhub2 at usb2 "AMD EHCI root hub" rev 2.00/1.00 addr 1
"AMD Hudson-2 SMBus" rev 0x3a at pci0 dev 20 function 0 not configured
"AMD Hudson-2 LPC" rev 0x11 at pci0 dev 20 function 3 not configured
pchb2 at pci0 dev 24 function 0 "AMD AMD64 16h Link Cfg" rev 0x00
pchb3 at pci0 dev 24 function 1 "AMD AMD64 16h Address Map" rev 0x00
pchb4 at pci0 dev 24 function 2 "AMD AMD64 16h DRAM Cfg" rev 0x00
pchb5 at pci0 dev 24 function 3 "AMD AMD64 16h Misc Cfg" rev 0x00
pchb6 at pci0 dev 24 function 4 "AMD AMD64 16h CPU Power" rev 0x00
pchb7 at pci0 dev 24 function 5 vendor "AMD", unknown product 0x1535 rev 0x00
usb3 at ohci0: USB revision 1.0
uhub3 at usb3 "AMD OHCI root hub" rev 1.00/1.00 addr 1
usb4 at ohci1: USB revision 1.0
uhub4 at usb4 "AMD OHCI root hub" rev 1.00/1.00 addr 1
isa0 at mainbus0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com0: console
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard, using wsdisplay1
umass0 at uhub0 port 3 configuration 1 interface 0 "USB Flash Disk"
rev 2.00/11.00 addr 2
umass0: using SCSI over Bulk-Only
scsibus1 at umass0: 2 targets, initiator 0
sd1 at scsibus1 targ 1 lun 0: <USB, Flash Disk, 1100> SCSI2 0/direct
removable serial.090c1000108230611421
sd1: 956MB, 512 bytes/sector, 1957888 sectors
softraid0 at root
scsibus2 at softraid0: 256 targets
root on rd0a swap on rd0b dump on rd0b
erase ^?, werase ^W, kill ^U, intr ^C, status ^T

Welcome to the OpenBSD/amd64 5.8 installation program.
(I)nstall, (U)pgrade, (A)utoinstall or (S)hell?

Brian Conway

Re: Native EFI Bootloader Support

[Brian Conway]

I get similar behavior (EFI boot blocks run, boot loader 3.29 shows,
but kernel fails to finish loading and reboots) on an Intel NUC
DN2820FYKH using the latest snapshot (9/9) with install58.fs. I tried
both bsd.rd and bsd for good measure. Installing via CSM works as
expected.

Firing up the same installer in VirtualBox's EFI mode installs and
runs beautifully, though, for whatever that's worth.

Dmesg of the BIOS-booted NUC is below. Thanks.

Brian

OpenBSD 5.8-current (GENERIC.MP) #1364: Wed Sep  9 17:32:01 MDT 2015
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8473788416 (8081MB)
avail mem = 8213020672 (7832MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT FIDT MCFG LPIT HPET SSDT SSDT SSDT UEFI
acpi0: wakeup devices UAR5(S4) UAR8(S4) PS2K(S3) PS2M(S3) XHC1(S4)
EHC1(S4) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) PWRB(S0) BRCM(S0)
BRC3(S0)
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) Celeron(R) CPU N2820 @ 2.13GHz, 2133.82 MHz
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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,RDRAND,NXE,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT
cpu0: 1MB 64b/line 16-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 133MHz
cpu0: mwait min=64, max=64, C-substates=0.2.0.0.0.0.3.3, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Celeron(R) CPU N2820 @ 2.13GHz, 2133.34 MHz
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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,RDRAND,NXE,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT
cpu1: 1MB 64b/line 16-way L2 cache
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 87 pins
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (RP01)
acpiprt2 at acpi0: bus 2 (RP02)
acpiprt3 at acpi0: bus 3 (RP03)
acpiprt4 at acpi0: bus 4 (RP04)
acpiec0 at acpi0: not present
acpicpu0 at acpi0: C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: C1(1000@1 mwait.1), PSS
acpipwrres0 at acpi0: PLPE
acpipwrres1 at acpi0: PLPE
acpipwrres2 at acpi0: USBC, resource for EHC1, OTG1
acpipwrres3 at acpi0: CLK0, resource for CAM1
acpipwrres4 at acpi0: CLK1, resource for CAM0, CAM2
acpibat0 at acpi0: BAT0 not present
acpibat1 at acpi0: BAT1 not present
acpibat2 at acpi0: BAT2 not present
acpibtn0 at acpi0: PWRB
acpibtn1 at acpi0: SLPB
acpibtn2 at acpi0: LID0
acpivideo0 at acpi0: GFX0
cpu0: Enhanced SpeedStep 2133 MHz: speeds: 2129, 2128, 1995, 1862,
1729, 1596, 1463, 1330, 1197, 1064, 931, 798, 665, 532 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Bay Trail Host" rev 0x0c
vga1 at pci0 dev 2 function 0 "Intel Bay Trail Video" rev 0x0c
intagp at vga1 not configured
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
ahci0 at pci0 dev 19 function 0 "Intel Bay Trail AHCI" rev 0x0c: msi, AHCI 1.3
ahci0: port 0: 3.0Gb/s
scsibus1 at ahci0: 32 targets
sd0 at scsibus1 targ 0 lun 0:  SCSI3
0/direct fixed naa.500a07510c06ed9d
sd0: 228936MB, 512 bytes/sector, 468862128 sectors, thin
xhci0 at pci0 dev 20 function 0 "Intel Bay Trail xHCI" rev 0x0c: msi
usb0 at xhci0: USB revision 3.0
uhub0 at usb0 "Intel xHCI root hub" rev 3.00/1.00 addr 1
"Intel Bay Trail TXE" rev 0x0c at pci0 dev 26 function 0 not configured
ppb0 at pci0 dev 28 function 0 "Intel Bay Trail I2C" rev 0x0c: msi
pci1 at ppb0 bus 1
ppb1 at pci0 dev 28 function 1 "Intel Bay Trail PCIE" rev 0x0c: msi
pci2 at ppb1 bus 2
ppb2 at pci0 dev 28 function 2 "Intel Bay Trail PCIE" rev 0x0c: msi
pci3 at ppb2 bus 3
re0 at pci3 dev 0 function 0 "Realtek 8168" rev 0x0c: RTL8168G/8111G
(0x4c00), msi, address c0:3f:d5:63:f3:5a
rgephy0 at re0 phy 7: RTL8251 PHY, rev. 0
ppb3 at pci0 dev 28 function 3 "Intel Bay Trail PCIE" rev 0x0c: msi
pci4 at ppb3 bus 4
pcib0 at pci0 dev 31 function 0 "Intel Bay Trail LPC" rev 0x0c
ichiic0 at pci0 dev 31 function 3 "Intel Bay Trail SMBus" rev 0x0c:
apic 1 int 18
iic0 at ichiic0
iic0: addr 0x18 00=00 01=00 02=00 03=00 04=00 05=c2 06=1b 07=0a 08=00
09=00 0a=00 0b=00 0c=00 0d=00 0e=00 0f=00 words 00=007f 01=
02= 03= 04= 05=c27c 06=1b09 07=0a01
spdmem0 at iic0 addr 0x50: 8GB DDR3 SDRAM PC3-12800 SO-DIMM with thermal sensor
isa0 at pcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at 

Re: Ubiquiti EdgeRouter Lite

[Brian Conway]

http://ftp.openbsd.org/pub/OpenBSD/snapshots/octeon/INSTALL.octeon

Brian Conway

On Sun, Aug 16, 2015 at 11:06 AM, Predrag Punosevac
punoseva...@gmail.com wrote:
 Dear All,

 I am contemplating buying a new machine which will act as a router/DNS
 caching server for my home network. Is anybody currently running OpenBSD
 on the Ubiquiti Networks EdgeRouter LITE in that capacity? I saw that in
 June 2015 USB support was added which allows installing to local disk on
 machine. Can anybody point me to a work in progress documentation diff
 for installing 5.8 octeon port.  I am reading right now

 http://ftp.openbsd.org/pub/OpenBSD/5.7/octeon/INSTALL.octeon

 Best,
 Predrag

Re: Repartitioning

[Brian Conway]

Yes. Use VBoxManage convertfromraw on the dd'ed image.

Brian

On Aug 7, 2015 11:37 AM, Quartz qua...@sneakertech.com wrote:

 You could also make a raw image of the disk and run a copy of that image
 in qemu on another computer, something which would give you a chance to
 do some experimenting with growfs(8)  friends without having to risk
 anything.


 Oh, now that's a really good idea actually, I never thought of that. Would
 that also work for VirtualBox or some other VM? VB can be weird about disk
 images.

Re: 5.7-stable i386: crunchgen-produced programs segfault

[Brian Conway]

Thanks, working from /usr/src/distrib/special helped get things sorted out.

Brian Conway

On Tue, Apr 7, 2015 at 4:00 PM, Ted Unangst t...@tedunangst.com wrote:
 Brian Conway wrote:
 I get similar results when swapping in ls, pax, and so on. However,
 the make release process generates a working instbin binary as used by
 bsd.rd, so it's working elsewhere and it's not clear if there's a user
 step I'm missing.

 There have been changes to the -fPIE defaults, which is where'd I start
 looking, but you should know that crunchgen isn't supported. It exits solely
 to make the installation media. You're mostly on your own here.

5.7-stable i386: crunchgen-produced programs segfault

[Brian Conway]

softraid0 at root
scsibus3 at softraid0: 256 targets
root on sd0a (b44646522fd3f596.a) swap on sd0b dump on sd0b

Brian Conway

Re: 5.7-stable i386: crunchgen-produced programs segfault

[Brian Conway]

Thanks, I'll start looking there. This is in the context of flashrd
not being bootable on i386 at the moment:

https://github.com/yellowman/flashrd/issues/30

Brian Conway
Founder, Owner
RCE Software, LLC


On Tue, Apr 7, 2015 at 4:00 PM, Ted Unangst t...@tedunangst.com wrote:
 Brian Conway wrote:
 I get similar results when swapping in ls, pax, and so on. However,
 the make release process generates a working instbin binary as used by
 bsd.rd, so it's working elsewhere and it's not clear if there's a user
 step I'm missing.

 There have been changes to the -fPIE defaults, which is where'd I start
 looking, but you should know that crunchgen isn't supported. It exits solely
 to make the installation media. You're mostly on your own here.

Re: useradd refusing encrypt output with 5.6

[Brian Conway]

(Apologies for potentially breaking threading, replying for a list archive.)

I brought this up previously[1] and can confirm that it is fixed in
5.6-stable. Thanks to all.

Brian Conway

[1] https://www.mail-archive.com/misc@openbsd.org/msg133393.html

Behavior with nested vnd's/filesystems

[Brian Conway]

Greetings. I'm curious whether the behavior I'm seeing is intended
when dealing with the situation of nested vnd files where the
lower/outer device is read-only (or whether I'm misunderstanding some
filesystem semantics). Full steps to reproduce are below (a little
verbose, I apologize) on 5.6-stable. The summary is:

Expected: Mount outer vnd as ro, mount inner vnd as ro.
Expected: Mount outer vnd as ro, attempt to mount inner vnd as rw, fails.
Unexpected: Mount outer vnd as ro, mount inner vnd as ro. Attempt to
remount inner vnd as rw, it succeeds despite outer vnd remaining ro.
Mounted inner vnd will accept changes, which appear to be retained in
the filesystem after unmounting everything and remounting.

-

Create a 50 MB a.vnd...

# dd if=/dev/zero of=a.vnd bs=1m count=50
...
# vnconfig vnd0 a.vnd
# fdisk -i vnd0
...
# disklabel -Aw vnd0
# newfs /dev/rvnd0a
...
# mount /dev/vnd0a /tmp/a

Repeat the process for a 25 MB b.vnd inside the mounted a.vnd...

# cd /tmp/a
# dd if=/dev/zero of=b.vnd bs=1m count=25
...
# vnconfig vnd1 b.vnd
# fdisk -i vnd1
...
# disklabel -Aw vnd1
# newfs /dev/rvnd1a
...
# mount /dev/vnd1a /tmp/b

Looks good so far, both are mounted rw. Unconfigure and unmount each
vnd, outer first.

Mount both as ro...

# vnconfig vnd0 a.vnd
# mount -o ro /dev/vnd0a /tmp/a
# vnconfig vnd1 /tmp/a/b.vnd
# mount -o ro /dev/vnd1a /tmp/b
# mount|grep vnd
/dev/vnd0a on /tmp/a type ffs (local, read-only)
/dev/vnd1a on /tmp/b type ffs (local, read-only)

Start over, mount a.vnd as ro, attempt to mount b.vnd as rw...

# vnconfig vnd0 a.vnd
# mount -o ro /dev/vnd0a /tmp/a
# vnconfig vnd1 /tmp/a/b.vnd
# mount -o rw /dev/vnd1a /tmp/b
mount_ffs: /dev/vnd1a on /tmp/b: filesystem must be mounted read-only;
you may need to run fsck

Start over, mount both as ro, then switch /tmp/b to rw...

# vnconfig vnd0 a.vnd
# mount -o ro /dev/vnd0a /tmp/a
# vnconfig vnd1 /tmp/a/b.vnd
# mount -o ro /dev/vnd1a /tmp/b
# mount|grep vnd
/dev/vnd0a on /tmp/a type ffs (local, read-only)
/dev/vnd1a on /tmp/b type ffs (local, read-only)
# mount -oupdate,rw /tmp/b
# mount|grep vnd
/dev/vnd0a on /tmp/a type ffs (local, read-only)
/dev/vnd1a on /tmp/b type ffs (local)

Verify /tmp/a still ro, write to the newly-rw /tmp/b, and unmount...

# echo hi  /tmp/a/test
ksh: cannot create /tmp/a/test: Read-only file system
# echo hi  /tmp/b/test
# umount /tmp/b
# vnconfig -u vnd1
# umount /tmp/a
# vnconfig -u vnd0

Verify write succeeded...

# vnconfig vnd0 a.vnd
# mount -o ro /dev/vnd0a /tmp/a
# vnconfig vnd1 /tmp/a/b.vnd
# mount -o ro /dev/vnd1a /tmp/b
# cat /tmp/b/test
hi

I was surprised that a.) the /tmp/b mount allowed itself to be changed
to rw, and that b.) the /tmp/a mount accepted changes to its
filesystem despite being read-only.

Thanks.

Brian Conway

encrypt(1) + `usermod -p` compatibility in 5.6

[Brian Conway]

As part of a larger build script, I'm pre-populating passwords with
usermod. When upgrading to 5.6, I ran into the error below:

5.5-stable:

# encrypt -b 8
onetwothree
$2a$08$vCs1eIrJAPAvWUGLR7wKJucQdCmalmQhU/9StF8QJDYz.E126wHeG

# usermod -p '$2a$08$vCs1eIrJAPAvWUGLR7wKJucQdCmalmQhU/9StF8QJDYz.E126wHeG' root

#

5.6-stable:

# encrypt -b 9
onetwothree
$2b$09$bacE5YNJiTzsuE8m.WJdUOHJO9U/lJq.tlSfwC/FKIL5EhqYpUsgC

# usermod -p '$2b$09$bacE5YNJiTzsuE8m.WJdUOHJO9U/lJq.tlSfwC/FKIL5EhqYpUsgC' root
usermod: Invalid password:
`$2b$09$bacE5YNJiTzsuE8m.WJdUOHJO9U/lJq.tlSfwC/FKIL5EhqYpUsgC'

#

Incorrect usage on my part or something else? Thanks.

Brian Conway

Re: encrypt(1) + `usermod -p` compatibility in 5.6

[Brian Conway]

On Wed, Nov 5, 2014 at 2:00 PM, Ted Unangst t...@tedunangst.com wrote:
 On Wed, Nov 05, 2014 at 12:35, Brian Conway wrote:
 As part of a larger build script, I'm pre-populating passwords with
 usermod. When upgrading to 5.6, I ran into the error below:

 5.5-stable:

 # encrypt -b 8
 onetwothree
 $2a$08$vCs1eIrJAPAvWUGLR7wKJucQdCmalmQhU/9StF8QJDYz.E126wHeG

 # usermod -p
 '$2a$08$vCs1eIrJAPAvWUGLR7wKJucQdCmalmQhU/9StF8QJDYz.E126wHeG' root

 #

 5.6-stable:

 # encrypt -b 9
 onetwothree
 $2b$09$bacE5YNJiTzsuE8m.WJdUOHJO9U/lJq.tlSfwC/FKIL5EhqYpUsgC

 # usermod -p
 '$2b$09$bacE5YNJiTzsuE8m.WJdUOHJO9U/lJq.tlSfwC/FKIL5EhqYpUsgC' root
 usermod: Invalid password:
 `$2b$09$bacE5YNJiTzsuE8m.WJdUOHJO9U/lJq.tlSfwC/FKIL5EhqYpUsgC'

 our (my) mistake. Note that the 5.6 password starts with $2b$.
 Unfortunately, usermod wasn't taught to recognize such passwords until
 after 5.6.

Gotcha. Just saw the fix on OPENBSD_5_6, thanks.

Brian