Re: Default OpenBSD browser

[Ax0n]

lynx was in the base distribution for quite some time. I occasionally used
it to fetch http files (as opposed to getting wget from packages and using
that).

I've found that ftp(1) is quite sufficient for most of the things I need to
to as far as a CLI client for quickly grabbing files via ftp/http/https.

e.g.
$ ftp -o OpenBSD.html http://openbsd.org/
Trying 129.128.5.194...
Requesting http://openbsd.org/
Redirected to http://www.openbsd.org/
Trying 129.128.5.194...
Requesting http://www.openbsd.org/
100% |**|  4779   00:00

4779 bytes received in 0.00 seconds (5.25 MB/s)
$


On Tue, Jul 28, 2015 at 7:00 AM, Mohammad BadieZadegan 
wrote:

> Hi,
> As we know the default X Window manager for OpenBSD is fvwm
>  and that is
> very usefull for initial using of OpenBSD.
> But Does OpenBSD have any WEB browser(Text or vs Image) by default?
> If have not, What is the best and lightest browser that usefull with fvwm?
> Thanks.

Re: OpenBSD vs Notebook Speaker.

[Ax0n]

I'd just try cranking up most of those xx,xx lines to 255, one at a time,
until your speakers emit something audible.

I'd start with the ones named "Master" because of reasons.
mixerctl outputs.master=255
mixerctl outputs.master.slaves=255

I know when I'm playing stuff on VLC, inputs.dac affects the volume there.
mixerctl inputs.dac-0:1=255
mixerctl inputs.dac-2:3=255

I don't have a "mix2" or any "muters" on any of my OpenBSD machines. You
might want to crank these up, too.
mixerctl inputs.mix2_source=255
mixerctl inputs.mix2_dac-0:1=255
mixerctl inputs.mix2_dac-2:3=255
mixerctl outputs.mix2=255
outputs.spkr_muters=255

"Muters" sounds like it might decrease volume... might also try setting it
to 0.
mixerctl outputs.spkr_muters=0

Once you find out some sane settings that work well for your speakers and
headphones alike, I recommend adding them to /etc/mixerctl.conf. See
mixerctl.conf(5) for more info.

Additionally, I've had some laptops give me quite a bit of trouble with
audio. There may be nothing you can do from mixerctl to get it to work. You
may want to document the things you tried and send a dmesg and problem
report via sendbug only once you've ruled out everything else.

On Wed, Jul 29, 2015 at 1:50 PM, Mohammad BadieZadegan 
wrote:

> Hi everybody,
> I'm using multimedia on my OpenBSD with headphone but my Notebook speaker
> don't sound!
> How can I use my notebook speaker?
> Is that any mixerctl  command to turn on built-in notebook speaker?
> This is my mixerctl output:
>
> $ mixerctl
> outputs.mic_source=dac-0:1
> inputs.mic=85,85
> outputs.mic_dir=input-vr80
> outputs.mic_boost=off
> outputs.mic_eapd=on
> outputs.hp_source=dac-0:1
> outputs.hp_boost=off
> outputs.hp_eapd=on
> outputs.spkr_source=dac-2:3
> outputs.spkr_eapd=on
> outputs.line_source=dac-0:1
> inputs.line=85,85
> outputs.line_dir=output
> outputs.line_eapd=on
> outputs.mic2_source=dac-0:1
> inputs.mic2=85,85
> outputs.mic2_dir=input
> outputs.mic2_eapd=on
> inputs.mic3=85,85
> inputs.dac-0:1_mute=off
> inputs.dac-0:1=254,254
> inputs.dac-2:3_mute=off
> inputs.dac-2:3=126,126
> record.adc-0:1_source=mic3
> record.adc-0:1_mute=off
> record.adc-0:1=119,119
> record.adc-2:3_source=line
> record.adc-2:3_mute=off
> record.adc-2:3=119,119
> inputs.sel3_source=dac-0:1
> inputs.mix2_source=line,mic2,dac-0:1,dac-2:3,mic
> inputs.mix2_line=120,120
> inputs.mix2_mic2=120,120
> inputs.mix2_dac-0:1=120,120
> inputs.mix2_dac-2:3=120,120
> inputs.mix2_mic=120,120
> outputs.mix2_mute=off
> outputs.mix2=120,120
> inputs.beep_mute=off
> inputs.beep=85
> outputs.mic_sense=unplugged
> outputs.hp_sense=unplugged
> outputs.line_sense=unplugged
> outputs.mic2_sense=unplugged
> outputs.spkr_muters=mic,hp,line,mic2
> outputs.master=255,255
> outputs.master.mute=off
> outputs.master.slaves=dac-0:1,dac-2:3
> record.volume=119,119
> record.volume.mute=off
> record.volume.slaves=adc-0:1,adc-2:3
> $

Re: home keys in tmux

[Ax0n]

Do you have anything in your .tmux.conf?

On Wed, Dec 2, 2015 at 6:42 AM, Ted Unangst  wrote:

> When i push home at a ksh prompt in xterm, the cursor goes to the
> beginning of
> the line. When i do the same in tmux, nothing happens.
>
> TERM in xterm is xterm. TERM in tmux is screen.
>
> How do i fix this? (Why do i need to fix it?)

Re: LibreNMS chroot issues

[Ax0n]

I've been able to run most *AMP stuff on OpenBSD/nginx/php_fpm. I've not
tried librenms before, but the major hurdle for chroot is usually the
mariaDB socket. I overcome this by setting up mariadb to bind to localhost
and setting up a user on 127.0.0.1 to force a TCP connection instead of
sockets. This is a little slower but I've never seen it make a web app
sluggish on its own.
If you want an example of the setup I use, I wrote it up here (only up to
date with 5.7 though) http://www.h-i-r.net/p/openbsd-nginx-php-mysql.html


On Sun, Dec 27, 2015, 07:40 ludovic coues  wrote:

> On 26 Dec 2015 12:47 am, "Predrag Punosevac" 
> wrote:
>
> >
> > I was wondering if anybody tried running LibreNMS with httpd from the
> > base and even more fundamentally does httpd from the base support
> > "unsecure" mode. I read up and down httpd several times but I didn't see
> > anything about insecure mode.
> >
>
> Like many part of OpenBSD, httpd from base have a concept of "non-optional
> security". So there is no possibility to use httpd without chroot.

Re: DHCP in vmm guest

[Ax0n]

This is why I love misc@.

And Francois: If I had known a few days ago what Reyk just said, I would
have noted it. I should probably go back and edit my blog post. I spent 4
or 5 hours myself trying unsuccessfully bridge it. I had it working once in
-CURRENT in October, but never could figure it out once I upgraded to 6.1.
IO must've manually assigned an address back then, whereas I was using
dhclient on bge0 last week.

On Thu, May 4, 2017 at 8:49 AM, Reyk Floeter  wrote:


> dhclient on the host "steals" all DHCP packets via BPF.
>
>

Re: Strange characters in dmesg

[Ax0n]

My vps at RamNode does this as well. It has ever since I moved there in
2015. It doesn't seem to cause any harm. I wasn't​ curious enough to run it
down to a root cause but if someone else knows, I'm interested in the story.

On May 13, 2017 21:55, "Hrishikesh Muruk"  wrote:

> I see the following characters in dmesg.
>
> "B\M-d\M^??B\M-d\M^??B\M-d\M^??B\M-d\M^??" - continues for several lines.
>
> This appears just before the initial text "OpenBSD 6.0 (GENERIC)"
>
> I am running OpenBSD 6.1 on a VM. I havent seen this on the VM or my local
> machine before.
>
> The system is running fine and there is no problem using it. But I want to
> check if others have seen such characters in their dmesg and if it is
> something to worry about.
>
> Thanks
> Hrishi
>

Re: Interest in POWER platform?

[Ax0n]

In summary: There are 3 people who have been quite vocal about getting a
POWER port recently. None of them are developers with the knowledge or
resources to port it.

Big thread from late last year:
https://marc.info/?l=openbsd-misc&m=147680858507662&w=2

A follow-up (late December 2016):
https://marc.info/?l=openbsd-misc&m=148246956710299&w=2

Search link with some scattered and often-unrelated results:
https://marc.info/?l=openbsd-misc&w=2&r=1&s=IBM+POWER&q=b

On Wed, May 24, 2017 at 12:57 PM, Kai Wetlesen  wrote:

> Hi all,
>
> What is the current community interest in getting OpenBSD running on the
> newer POWER processors? I have a number of POWER based systems at work
> which run various Linux flavors, but it would be nice to bring OpenBSD to
> these systems as we’re been trying it out in different spaces throughout
> our division. What would it take to get a POWER port up and kicking?
>
> Regards,
> Kai
>

Niagara 2265

[Ax0n]

Has anyone messed with the Interface Masters Niagara cards on OpenBSD? This
family of cards has a passive bypass mode (electromechanical relays that
turn the two ports into, essentially, an ethernet coupler when something
goes wrong or power fails) but otherwise presents as a bog-standard 2-port
Intel 82571EB. It appears that it is currently in a bypass state, as both
interfaces show no activity from the OS, neither have link light, but it's
bridging traffic and I can access the Internet through it, as I'd expect if
it's in bypass mode. I'm hoping to build a fault-tolerant filter/bridge for
my home lab with this card. It's currently in my SunFire T2000 (as seen
from the primary domain). I got similar results with it in my amd64 desktop
right after I bought it.

Interface Masters has been zero help to me.

Full dmesg below, followed by ifconfig output. The ports in question are
em4 and em5. I'm not seeing any other devices that weren't there before I
installed this card (e.g. a way to control the relays).

console is /virtual-devices@100/console@1
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California.  All rights reserved.
Copyright (c) 1995-2017 OpenBSD. All rights reserved.
https://www.OpenBSD.org

OpenBSD 6.1 (GENERIC.MP) #58: Sat Apr  1 17:10:24 MDT 2017
dera...@sparc64.openbsd.org:/usr/src/sys/arch/sparc64/compile/GENERIC.MP
real mem = 3221225472 (3072MB)
avail mem = 3145768960 (3000MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root: Sun Fire T200
cpu0 at mainbus0: SUNW,UltraSPARC-T1 (rev 0.0) @ 1200 MHz
cpu1 at mainbus0: SUNW,UltraSPARC-T1 (rev 0.0) @ 1200 MHz
cpu2 at mainbus0: SUNW,UltraSPARC-T1 (rev 0.0) @ 1200 MHz
cpu3 at mainbus0: SUNW,UltraSPARC-T1 (rev 0.0) @ 1200 MHz
vbus0 at mainbus0
"flashprom" at vbus0 not configured
cbus0 at vbus0
vldc0 at cbus0
vldcp0 at vldc0 chan 0x0: ivec 0x0, 0x1 channel "hvctl"
"ldom-primary" at vldc0 chan 0x1 not configured
"fmactl" at vldc0 chan 0x3 not configured
vldc1 at cbus0
"ldmfma" at vldc1 chan 0x4 not configured
vldc2 at cbus0
vldcp1 at vldc2 chan 0x14: ivec 0x28, 0x29 channel "spds"
"system-management" at vldc2 chan 0xd not configured
vldcp2 at vldc2 chan 0x19: ivec 0x32, 0x33 channel "ldom-ldom0-OpenBSD-DMZ"
vldcp3 at vldc2 chan 0x1e: ivec 0x3c, 0x3d channel "ldom-ldom6-OpenBSD-Web"
vcc0 at cbus0
vcctty0 at vcc0 chan 0x18: ivec 0x30, 0x31 domain "ldom0-OpenBSD-DMZ"
vcctty1 at vcc0 chan 0x1d: ivec 0x3a, 0x3b domain "ldom6-OpenBSD-Web"
vds0 at cbus0
vdsp0 at vds0 chan 0x1a: ivec 0x34, 0x35
vdsp1 at vds0 chan 0x1f: ivec 0x3e, 0x3f
vsw0 at cbus0
vnet0 at vsw0 chan 0x1b: ivec 0x36, 0x37
vnet1 at vsw0 chan 0x1c: ivec 0x38, 0x39
vnet2 at vsw0 chan 0x20: ivec 0x40, 0x41
vcons0 at vbus0: ivec 0x111, console
vrtc0 at vbus0
"fma" at vbus0 not configured
"sunvts" at vbus0 not configured
"sunmc" at vbus0 not configured
"explorer" at vbus0 not configured
"led" at vbus0 not configured
"flashupdate" at vbus0 not configured
vpci0 at mainbus0: bus 2 to 7, dvma map 8000-
pci0 at vpci0
ppb0 at pci0 dev 0 function 0 "PLX PEX 8532" rev 0xbc
pci1 at ppb0 bus 3
ppb1 at pci1 dev 1 function 0 "PLX PEX 8532" rev 0xbc
pci2 at ppb1 bus 4
em0 at pci2 dev 0 function 0 "Intel 82571EB" rev 0x06: ivec 0x795, address
00:14:4f:9d:60:ac
em1 at pci2 dev 0 function 1 "Intel 82571EB" rev 0x06: ivec 0x796, address
00:14:4f:9d:60:ad
ppb2 at pci1 dev 2 function 0 "PLX PEX 8532" rev 0xbc
pci3 at ppb2 bus 5
ppb3 at pci1 dev 8 function 0 "PLX PEX 8532" rev 0xbc: msi
pci4 at ppb3 bus 6
ppb4 at pci1 dev 9 function 0 "PLX PEX 8532" rev 0xbc
pci5 at ppb4 bus 7
mpi0 at pci5 dev 0 function 0 "Symbios Logic SAS1064E" rev 0x02: msi
mpi0: UNUSED, firmware 1.9.0.0
scsibus1 at mpi0: 63 targets
sym0 at scsibus1 targ 0 lun 0:  SCSI3
0/direct fixed naa.5000c500061f070b
sd0 at scsibus0 targ 0 lun 0:  SCSI3
0/direct fixed naa.5000c500061f070b
sd0: 140009MB, 512 bytes/sector, 286739329 sectors
sym1 at scsibus1 targ 1 lun 0:  SCSI3
0/direct fixed naa.5000c500061f0d3b
sd1 at scsibus0 targ 1 lun 0:  SCSI3
0/direct fixed naa.5000c500061f0d3b
sd1: 140009MB, 512 bytes/sector, 286739329 sectors
sd2 at scsibus1 targ 2 lun 0:  SCSI3
0/direct fixed naa.5000ccac2b34
sd2: 140009MB, 512 bytes/sector, 286739329 sectors
sym2 at scsibus1 targ 3 lun 0:  SCSI3
0/direct fixed naa.5000c5000546b3ef
sd3 at scsibus0 targ 2 lun 0:  SCSI3
0/direct fixed naa.5000c5000546b3ef
sd3: 140009MB, 512 bytes/sector, 286739329 sectors
vpci1 at mainbus0: bus 2 to 9, dvma map 8000-
pci6 at vpci1
ppb5 at pci6 dev 0 function 0 "PLX PEX 8532" rev 0xbc
pci7 at ppb5 bus 3
ppb6 at pci7 dev 1 function 0 "PLX PEX 8532" rev 0xbc
pci8 at ppb6 bus 4
ppb7 at pci8 dev 0 function 0 "Intel 41210 PCIE-PCIX" rev 0x09
pci9 at ppb7 bus 5
ebus0 at pci9 dev 2 function 0 "Acer Labs M1533 ISA" rev 0x00
com0 at ebus0 addr 3f8-3ff ivec 0x2: ns16550a, 16 byte fifo
ohci0 at pci9 dev 5 function 0 "Acer Labs M5237 USB" rev 0x03: ivec 0x7c1,
version 1.0, legacy support
ohci1 at pci9 dev 6 functio

Re: httpd and wordpress

[Ax0n]

A very select few security-focused plugins are worth keeping around, like
WordFence. Every plugin, theme and add-on is additional attack surface, and
some popular plugins and themes have a horrifying track record with regard
to security. WordPress core has gotten a lot better recently, but there are
still some whopper vulnerabilities disclosed on occasion.

For most people, I recommend giving it lenient enough file permissions that
it can automatically apply its own updates. The most severe WP
vulnerabilities are Remote Code [Inclusion|Execution]. Disallowing _www
write access to the document root isn't going to save you from those, but
allowing write access and enabling automatic updates means critical patches
are applied faster than you'd normally be able to do it yourself.

I have experimented in my development environment with a "split
installation" where two different virtual hosts entries serve WP from two
different document roots but are pointed to the same database: A full-blown
normal install on 127.0.0.1 that you access through something such as an
SSH dynamic proxy, then a copied, locked-down install on the public IP
address. The locked-down install doesn't even have wp-admin, and uses
database credentials that are limited to SELECT queries only. This took a
lot of extra work to keep maintained, and updates applied to, and obviously
things like user-login and comments won't work on the public-facing site.
I'm not convinced this experiment is worth the hassle, because if you're
that paranoid, you're likely already looking at static-site generators and
getting away from WP by any means possible.

On Sun, Jun 4, 2017 at 4:34 PM, flipchan  wrote:

> Delete ALL readme and don't install plugins
>
> On June 3, 2017 9:52:13 PM GMT+02:00, Markus Rosjat 
> wrote:
> >Hi there,
> >
> >
> >well if it would be up to me I would skip wordpress for good but well
> >it's not my decition.
> >
> >So I was wondering if there is some recommendations on what to block in
> >
> >the httpd.conf and what file permissions to use.
> >
> >For now I have:
> >
> >- like wordpress suggest 0755 on dirs and 0644 on files
> >
> >- wp-config.php setting to 0400 is not going to work at all I need at
> >least a 0644 or nothing shows up
> >
> >- in http.conf I blocked /wp_content , /wp-content /uploads/*.php,
> >/wp-includes, /wp-includes/*.php and /wp-admin
> >
> >
> >so if there is something I can do further to harden things just let me
> >know :)
> >
> >
> >advice is most apreciated
> >
> >
> >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
>
> --
> Take Care Sincerely flipchan layerprox dev

Re: nc in inetd - under which account?

[Ax0n]

Also, this seems like something that, depending on where the destination
servers are, could be handled easily with PF by itself, or with the help of
relayd, with a lot less hassle.

On Tue, Jun 6, 2017 at 11:23 AM, Maximilian Pichler  wrote:

> On Tue, Jun 6, 2017 at 11:06 AM, Marko Cupać  wrote:
> > On Tue, 06 Jun 2017 08:18:15 -0600
> > "Theo de Raadt"  wrote:
> >> Never reuse a user intended for another purpose.
> >>
> >> Take a glance at the ptrace manual page.
>
> > I have read ptrace manual. But I guess I need to read much MUCH more if
> > I want to comprehend it :)
>
> I'm guessing the point here is that ptrace can be used to eavesdrop on
> processes of the same user id. So if the proxy user got compromised,
> an attacker could not just kill the nc processes, but also read the
> data they are forwarding.
>
>

Re: nc in inetd - under which account?

[Ax0n]

First result on Google for "relayd example" seems to be pretty thorough.
https://calomel.org/relayd.html


On Wed, Jun 7, 2017 at 7:51 AM, Marko Cupać  wrote:

> On Tue, 6 Jun 2017 12:05:10 -0500
> Ax0n  wrote:
>
> > Also, this seems like something that, depending on where the
> > destination servers are, could be handled easily with PF by itself,
> > or with the help of relayd, with a lot less hassle.
>
> Perhaps I didn't explain what I use this for. I have a vlan on private
> subnet, which has no access to other private vlans - it can contact
> only Internet hosts. One of "Internet" hosts is actually IP alias on
> external interface of my OpenBSD firewall, which redirects (rdr-to)
> internal host on my LAN:
>
> pass in on $if_ext inet proto tcp from any to $pub_srv port $web \
>rdr-to $priv_srv
>
> Now, as redirection happens to packets which are incoming to external
> interface, above rule does not hit for packets coming from internal
> vlan.
>
> That's why I combine pf redirection on internal interface to
> loopback:
> pass in quick on $if_int inet proto tcp from  to $pub_srv \
>port 80 rdr-to 127.0.0.1 port 20080
> pass in quick on $if_int inet proto tcp from  to $pub_srv \
>port 443 rdr-to 127.0.0.1 port 20443
>
> ... and proxy these packets with nc from inetd:
> 127.0.0.1:20080 stream tcp nowait _nc_proxy /usr/bin/nc \
>srv-http -w 20 PRI.VAT.EAD.DR 80
> 127.0.0.1:20443 stream tcp nowait _nc_proxy /usr/bin/nc \
>srv-https -w 20 PRI.VAT.EAD.DR 443
>
> I know that simple rdr on internal interface doesn't work out of the
> box - I would probably need some kind of NAT, as LAN server wouldn't
> return packet to firewall from where it was redirected - it would try
> to contact LAN client directly, and fail (isolated VLAN).
>
> Now as for relayd, I never used it. If someone gave me working example
> and an explanation why it is better than my current solution, I'd be
> glad to switch, and pass the word around :)
>
> Thank you all for tips and hints.
> --
> Before enlightenment - chop wood, draw water.
> After  enlightenment - chop wood, draw water.
>
> Marko Cupać
> https://www.mimar.rs/
>
>

Re: Current FreeBSD looking to switch to OpenBSD

[Ax0n]

On dual-booting:

I have set up Windows/OpenBSD dual-boot quite a few times. Windows 7 and
Windows 10 instructions are all about the same, and the information in the
FAQ on multi-booting has enough info to get you started.
https://www.openbsd.org/faq/faq4.html#Multibooting

First, always have good backups, but especially make sure anything
important is backed up and tested before you embark on dual-booting with
Windows. It works best with a fresh install of everything, though. Use the
Windows installer to partition the drive. I like to have three partitions:
1 for Windows, 1 for OpenBSD and one for sharing files between the two.
Install Windows on the first partition.

Carefully install OpenBSD on the second partition. If memory serves
correctly, I had to shell out of the installer, use fdisk to change the
partition type of the OpenBSD partition, then go back into the installer
and tell it to use that partition. BE REALLY CAREFUL using fdisk and
setting up your partitions. after install, follow the FAQ guidance on using
dd to copy the PBR. I mounted a USB stick from the install environment and
copied the PBR to that, then to Windows.

Back in Windows, if you didn't f*** it up with the OpenBSD installer,
follow the FAQ guidance on using BCDEdit, or perhaps, use the free (for
non-commercial use) BCDEdit to add OpenBSD to the Windows bootloader.
Reboot. Get into OpenBSD, if you followed the instructions correctly.
Install exfat-fuse from packages, and use the mkfs.exfat tool to format the
third partition for shared files. For whatever reason, Windows doesn't like
to format hard disk partitions as Exfat, but you can do it from OpenBSD
easily enough.

Did I mention you should back up your data? Even I have messed up a few
times. Fortunately, it was just a fresh Windows install that got clobbered
last time I botched it.

Good luck. I hope you come to enjoy OpenBSD as much as I do.

On Sat, Jun 10, 2017 at 12:30 PM, Baho Utot 
wrote:

> I am currently using FreeBSD 11.0 and win7.  I have looked over OpenBSD
> and I like what I am seeing. I have several machine to install it on an old
> laptop Dell Inspirion 1501 and newer AMD64 machines with 8 cores and 16GB
> ram.  I would also like to install into Raspberry pi versions 2 and 3.
>
> I have the following questions:
>
> 1.  Where can I get a list of graphics card that are supported?
>
> 2.  Where can I find information on dual booting OpenBSD
> and Windows?
>
> 3.  Does OpenBSD need to be on the primary disk drive or can
> it be installed on the second drive with windos on the
> first drive.
>
> 4.  Is the manul that is online, can it be obtained on a pdf?
>
> 5.  Where can I find information on wifi support?
>
> These are the important question I have for now.
>
> Thanks
>
>

Re: httpd and phpyMyAdmin

[Ax0n]

I'm generally not a fan of it, either, but sometimes the (l)users need
tools we don't like. So.

1) Run it over TLS only, so that usernames, passwords and other sensitive
data doesn't go across in the clear.
2) Lock it down to access only from trusted IP addresses (you can do this a
variety of ways with the help of pf, running on alternate ports, a
different IP, etc)
3) use the authenticate directive, e.g. authenticate "admin.example.com"
with htpasswd as a second layer of defense to the MySQL login for PHPMA
4) Make sure that MySQL users have the least privileges necessary to
operate.

On Tue, Jun 13, 2017 at 4:56 PM, Stuart Henderson 
wrote:

> On 2017-06-13, Markus Rosjat  wrote:
> > would like to get opinions on securing the whole thing  ...still :)
>
> Deleting phpmyadmin would be a good start :-)
>
>
>

vmd: cannot reset VCPU 0 - exiting

[Ax0n]

I'm having trouble booting OpenBSD 6.1-Release in vmm on recent snapshots.

I can boot an amd64 bsd.rd and do the install, but the resulting disk image
aborts silently (or hangs with no console output) with the subject line
above the only hint of what happens, found in daemon.log, and "vm_resetcpu:
failed" in dmesg.

I can boot my -stable disk image if I specify -b /bsd (and thus, use the
snapshot kernel from the host to boot the -release VM's disk image) but
this seems like a Bad Idea.

dmesg:
OpenBSD 6.1-current (GENERIC.MP) #8: Wed Jun 14 16:10:57 MDT 2017
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8560467968 (8163MB)
avail mem = 8295235584 (7910MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xdc010 (37 entries)
bios0: vendor TOSHIBA version "V2.90" date 12/10/2010
bios0: TOSHIBA Qosmio X505
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP HPET MCFG APIC BOOT SLIC DMAR SSDT
acpi0: wakeup devices EHC1(S3) EHC2(S3) HDEF(S3) PXS1(S4) RP05(S5) PXS5(S5)
RP07(S5) PXS7(S5) GLAN(S4) PEG4(S4) PEG5(S4) PEG6(S4) LID_(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7 CPU Q 740 @ 1.73GHz, 1729.23 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,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: TSC frequency 1729233020 Hz
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 132MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Core(TM) i7 CPU Q 740 @ 1.73GHz, 1729.00 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,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Core(TM) i7 CPU Q 740 @ 1.73GHz, 1729.00 MHz
cpu2:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 6 (application processor)
cpu3: Intel(R) Core(TM) i7 CPU Q 740 @ 1.73GHz, 1729.00 MHz
cpu3:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 0, core 3, package 0
cpu4 at mainbus0: apid 1 (application processor)
cpu4: Intel(R) Core(TM) i7 CPU Q 740 @ 1.73GHz, 1729.00 MHz
cpu4:
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,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR
cpu4: 256KB 64b/line 8-way L2 cache
cpu4: smt 1, core 0, package 0
cpu5 at mainbus0: apid 3 (application processor)
cpu5: Intel(R) Core(TM) i7 CPU Q 740 @ 1.73GHz, 1729.00 MHz
cpu5:
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,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR
cpu5: 256KB 64b/line 8-way L2 cache
cpu5: smt 1, core 1, package 0
cpu6 at mainbus0: apid 5 (application processor)
cpu6: Intel(R) Core(TM) i7 CPU Q 740 @ 1.73GHz, 1729.00 MHz
cpu6:
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,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR
cpu6: 256KB 64b/line 8-way L2 cache
cpu6: smt 1, core 2, package 0
cpu7 at mainbus0: apid 7 (application processor)
cpu7: Intel(R) Core(TM) i7 CPU Q 740 @ 1.73GHz, 1729.00 MHz
cpu7:
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,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR
cpu7: 256KB 64b/line 8-way L2 cache
cpu7: smt 1, core 3, package 0
ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (

Re: vmd: cannot reset VCPU 0 - exiting

[Ax0n]

Thanks, Mike. That helped.

What's the oldest viable microarch required for unrestricted guest, and can
I detect this capability in dmesg the way we can see VMX/EPT? I'm on the
hunt for a decent desktop specifically for vmm, and had been eyeballing
some dirt cheap Craigslist i5s. Now it seems that might not be the best
plan.

On Thu, Jun 15, 2017 at 1:40 AM, Mike Larkin  wrote:

> On Wed, Jun 14, 2017 at 10:25:43PM -0500, Ax0n wrote:
> > I'm having trouble booting OpenBSD 6.1-Release in vmm on recent
> snapshots.
> >
> > I can boot an amd64 bsd.rd and do the install, but the resulting disk
> image
> > aborts silently (or hangs with no console output) with the subject line
> > above the only hint of what happens, found in daemon.log, and
> "vm_resetcpu:
> > failed" in dmesg.
> >
> > I can boot my -stable disk image if I specify -b /bsd (and thus, use the
> > snapshot kernel from the host to boot the -release VM's disk image) but
> > this seems like a Bad Idea.
> >
>
> Your machine is older and doesn't have unrestricted guest capability, which
> for the moment means no BIOS. Since that's the default now, this is why it
> is breaking.
>
> I will fix this at some point but for now, use -b, and set it the same as
> the disk image. That should force it to fallback to the old faux-bootloader
> mode, loading the disk's own /bsd image (not from your host):
>
> vmctl start test -c -i 1 -d disk.img -b disk.img
>
> -ml
>
> > dmesg:
> > OpenBSD 6.1-current (GENERIC.MP) #8: Wed Jun 14 16:10:57 MDT 2017
> > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> > real mem = 8560467968 (8163MB)
> > avail mem = 8295235584 (7910MB)
> > mpath0 at root
> > scsibus0 at mpath0: 256 targets
> > mainbus0 at root
> > bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xdc010 (37 entries)
> > bios0: vendor TOSHIBA version "V2.90" date 12/10/2010
> > bios0: TOSHIBA Qosmio X505
> > acpi0 at bios0: rev 2
> > acpi0: sleep states S0 S3 S4 S5
> > acpi0: tables DSDT FACP HPET MCFG APIC BOOT SLIC DMAR SSDT
> > acpi0: wakeup devices EHC1(S3) EHC2(S3) HDEF(S3) PXS1(S4) RP05(S5)
> PXS5(S5)
> > RP07(S5) PXS7(S5) GLAN(S4) PEG4(S4) PEG5(S4) PEG6(S4) LID_(S4)
> > acpitimer0 at acpi0: 3579545 Hz, 24 bits
> > acpihpet0 at acpi0: 14318179 Hz
> > acpimcfg0 at acpi0 addr 0xe000, bus 0-255
> > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> > cpu0 at mainbus0: apid 0 (boot processor)
> > cpu0: Intel(R) Core(TM) i7 CPU Q 740 @ 1.73GHz, 1729.23 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,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,
> xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR
> > cpu0: 256KB 64b/line 8-way L2 cache
> > cpu0: TSC frequency 1729233020 Hz
> > cpu0: smt 0, core 0, package 0
> > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
> > cpu0: apic clock running at 132MHz
> > cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE
> > cpu1 at mainbus0: apid 2 (application processor)
> > cpu1: Intel(R) Core(TM) i7 CPU Q 740 @ 1.73GHz, 1729.00 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,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,
> xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR
> > cpu1: 256KB 64b/line 8-way L2 cache
> > cpu1: smt 0, core 1, package 0
> > cpu2 at mainbus0: apid 4 (application processor)
> > cpu2: Intel(R) Core(TM) i7 CPU Q 740 @ 1.73GHz, 1729.00 MHz
> > cpu2:
> > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,
> CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,
> PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,
> xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR
> > cpu2: 256KB 64b/line 8-way L2 cache
> > cpu2: smt 0, core 2, package 0
> > cpu3 at mainbus0: apid 6 (application processor)
> > cpu3: Intel(R) Core(TM) i7 CPU Q 740 @ 1.73GHz, 1729.00 MHz
> > cpu3:
> > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,
> CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,
> PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,
> xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR
> > cpu3: 256KB 64b/line 8-way L2 cache
> > cpu3: smt 0, core 3, package 0
> > cpu4 at mainbus0: apid 1 (application processor)
> > cpu4: Intel(R) Core(TM) i7 CPU Q 740 @ 1.73GHz, 1729.00 MHz
> > 

Re: Boot issue 6.1

[Ax0n]

I have two laptops that dual boot Windows due to some proprietary software
I need for amateur radio programming (okay, and Steam on occasion). Part of
my usual upgrade process is to make a new openbsd.pbr and put it on the
Windows partition every time. I've checksummed this file a number of times
before installing it, and it does occasionally change, but not between
every release.

On Sat, Jun 24, 2017 at 6:36 AM, Martin Oppegaard <
martin.oppega...@gmail.com> wrote:

> The solution here was to update the pbr file for Windows’ bootloader.
>
> On Mon, Jun 19, 2017 at 8:03 AM, Martin Oppegaard <
> martin.oppega...@gmail.com> wrote:
>
> >
> >
> > On Monday, June 19, 2017, Theo de Raadt  wrote:
> >
> >> > I get the error Message that "installboot: /mnt/usr/mdec/biosboot
> >> extends
> >> > Beyond sector 268435455. OpenBSD might not boot." I'm dual booting
> with
> >> > Windows using Windows' boot loader first.
> >>
> >> You've created an OpenBSD MBR partition too far up your disk.  It
> >> won't work in legacy mode.  The BIOS won't be able to read it.
> >>
> >> You can try EFI mode instead.
> >
> >
> > It used to work fine for many years and upgrades. I don't think it's new
> > enough to have EFI.
> >
> > In the worst case I'll reinstall on the backup HDD.
> >
>

Re: Tor Relay

[Ax0n]

does pkg_add tor
does rcctl enable tor
does rcctl start tor

Welcome to your new onion relay node. It will relay and it will also listen
on port 9050 as a socks proxy for local applications.

On Jun 25, 2017 10:41, "nicehat"  wrote:

> I'm looking for some good links on setting up a OBSD based Tor relay.
> I had a few good ones but they have since gone into hiding.
> Anyone with some experience/tips would be helpful
> Regards
> Happy Camper
>
> Sent with [ProtonMail](https://protonmail.com) Secure Email.

Re: Can I use OpenBSD in a virtual machine, for example, VirtualBox?

[Ax0n]

You'll find little official support on the lists for problems you have due
to the hypervisor, but I've found that OpenBSD works great in VirtualBox.
You can't get VirtualBox Guest Additions working, but judging from the
popularity of this post I wrote almost 8 years ago, and the comments on it,
this trick still works for many people to get an OpenBSD VM into
full-screen mode.

http://www.h-i-r.net/2009/11/virtualbox-full-screen-resolution-for.html

Don't expect acceleration, guest/host clipboard interacrion or anything
else fancy from Guest Additions, but the basics for a daily-use OpenBSD
desktop, such as Lumina or XFCE, various terminals, web browsers and the
like work fine in VBox.

On Mon, Jun 26, 2017 at 5:16 PM, Josh Stephens  wrote:

> > On Mon, 26 Jun 2017, SOUL_OF_ROOT 55 wrote:
> >
> > > Can I use OpenBSD in a virtual machine, for example, VirtualBox?
> > >
> > Yep, .. have had them for many years, VirtualBox & Xen.
> >
> > Lee
> >
> >
> I could be wrong when I say this but the only gotcha that you will run into
> with virtual box will be the guest additions. I don’t think they are
> supported
> on OpenBSD?
>
>

Re: Lenovo Notebook: No HDMI video output; DRM error; -current MP#115

[Ax0n]

What happens if you try jcs' intel_backlight utility?

https://devhub.io/repos/jcs-intel_backlight_fbsd

Take note of the machdep.allowaperture=3 change you need to make to
sysctl.conf (requires a reboot).

On Sat, Jul 22, 2017 at 5:09 PM, Michel Behr  wrote:

> Hi - I'm trying to connect my Lenovo Laptop a monitor via HDMI but I'm
> getting no output (below I'm including messages regarding xrandr, dmesg,
> and Xorg.0.log).
>
> Any pointing to the right direction would be much appreciated.
>
> Kind regards,
>
> Michel.
>
>
>
> $ uname -a
>
>
> OpenBSD S400 6.1 GENERIC.MP#115 amd64
> $ dmesg
>
>
> OpenBSD 6.1-current (GENERIC.MP) #96: Thu Jul 13 19:31:55 MDT 2017
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> RTC BIOS diagnostic error 80
> real mem = 4140773376 (3948MB)
> avail mem = 4009488384 (3823MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xe6fd0 (61 entries)
> bios0: vendor LENOVO version "6DCN92WW(V8.06)" date 02/21/2013
> bios0: LENOVO VIUS3
> acpi0 at bios0: rev 2
> acpi0: sleep states S0 S3 S4 S5
> acpi0: tables DSDT FACP SLIC UEFI ASF! HPET APIC MCFG SSDT BOOT ASPT DBGP
> FPDT MSDM SSDT SSDT DMAR
> acpi0: wakeup devices P0P1(S0) EHC1(S3) EHC2(S3) XHC_(S3) HDEF(S0) PXSX(S3)
> PXSX(S3) PXSX(S3) PXSX(S3) PXSX(S3) RP05(S0) PXSX(S3) RP06(S0) PXSX(S3)
> RP07(S0) PXSX(S3) [...]
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpihpet0 at acpi0: 14318179 Hz
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Intel(R) Core(TM) i5-3317U CPU @ 1.70GHz, 1696.40 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,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,
> XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,
> FSGSBASE,SMEP,ERMS,SENSOR,ARAT
> cpu0: 256KB 64b/line 8-way L2 cache
> cpu0: TSC frequency 1696402120 Hz
> cpu0: smt 0, core 0, package 0
> mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
> cpu0: apic clock running at 99MHz
> cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE
> cpu1 at mainbus0: apid 1 (application processor)
> cpu1: Intel(R) Core(TM) i5-3317U CPU @ 1.70GHz, 1696.14 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,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,
> XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,
> FSGSBASE,SMEP,ERMS,SENSOR,ARAT
> cpu1: 256KB 64b/line 8-way L2 cache
> cpu1: smt 1, core 0, package 0
> cpu2 at mainbus0: apid 2 (application processor)
> cpu2: Intel(R) Core(TM) i5-3317U CPU @ 1.70GHz, 1696.14 MHz
> cpu2:
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,
> CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,
> PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,
> xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,
> XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,
> FSGSBASE,SMEP,ERMS,SENSOR,ARAT
> cpu2: 256KB 64b/line 8-way L2 cache
> cpu2: smt 0, core 1, package 0
> cpu3 at mainbus0: apid 3 (application processor)
> cpu3: Intel(R) Core(TM) i5-3317U CPU @ 1.70GHz, 1696.14 MHz
> cpu3:
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,
> CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,
> PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,
> xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,
> XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,
> FSGSBASE,SMEP,ERMS,SENSOR,ARAT
> cpu3: 256KB 64b/line 8-way L2 cache
> cpu3: smt 1, core 1, package 0
> ioapic0 at mainbus0: apid 0 pa 0xfec0, version 20, 24 pins
> acpimcfg0 at acpi0 addr 0xf000, bus 0-63
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpiprt1 at acpi0: bus -1 (P0P1)
> acpiprt2 at acpi0: bus 1 (RP01)
> acpiprt3 at acpi0: bus -1 (RP02)
> acpiprt4 at acpi0: bus -1 (RP03)
> acpiprt5 at acpi0: bus -1 (RP04)
> acpiprt6 at acpi0: bus -1 (RP05)
> acpiprt7 at acpi0: bus -1 (RP06)
> acpiprt8 at acpi0: bus -1 (RP07)
> acpiprt9 at acpi0: bus -1 (RP08)
> acpiprt10 at acpi0: bus -1 (PEG0)
> acpiprt11 at acpi0: bus -1 (PEG1)
> acpiprt12 at acpi0: bus -1 (PEG2)
> acpiprt13 at acpi0: bus -1 (PEG3)
> acpiec0 at acpi0
> acpicpu0 at acpi0: C2(350@80 mwait.1@0x20), C1(1000@1 mwait.1), PSS
> acpicpu1 at acpi0: C2(350@80 mwait.1@0x20), C1(1000@1 mwait.1), PSS
> acpicpu2 at acpi0: C2(350@80 mwait.1@0x20), C1(1000@1 mwait.1), PSS
> acpicpu3 at acpi0: C2(350@80 mwait.1@0x20), C1(1000@1 mwait.1), PSS
> acpitz0 at acpi0: critical temperature is 127 degC
> "INT3F0D" at acpi0 not configured
> acpibtn0 at acpi0: PWRB
> "IDEA0100" at acpi0 not configured
> "SYN2B04" at acpi0 not configured
> "VPC2004" at acpi0 not configured
> "AOA2011" at acpi0 not configured
> acpibat0 at acpi0: BAT1 mod

Re: Lumina enable Shut Down

[Ax0n]

As one who uses Lumina on a daily-driver OpenBSD laptop, I just fire up a
terminal and "doas halt -p" (or reboot, etc) when I'm ready to shut the
system down. You could likely add a nopassd rule to doas.conf so your user
account can run shutdown, and make a launcher or script for Lumina.

On Mon, Jul 24, 2017 at 8:34 AM, Theo de Raadt  wrote:

> > I'm our maintainer of the Lumina port.  Let me chat with my friends
> > upstream and see if we can't come up with a better solution for this.
> > As a quick thought, allowing users in a particular group (perhaps
> > :wheel?) to run shutdown(8) without a password prompt using doas seems
> > like a starting point.  Thoughts on that if I push that direction?
>
> Whatever anyone wants to do to de-secure their own machine, but this
> type of thing should NEVER be default configuration applied by a
> package.
>
> I think the entire approach is dumb.
>
> It's like adding a "shutdown" built-in to ksh.  Obviously when I'm in
> ksh, I want to be able to Shutdown my machine.  Why has this feature
> been withheld from me for so long??
>
>
>

Re: Nmap Hangs while scanning

[Ax0n]

>From your dmesg, my first suggestion would be to look at the cause of
what's filling up / and /home (per the snippet from your dmesg pasted below
my response). Next, I'd upgrade to a supported release (OpenBSD 6.1) and
fully update it with syspatch, then try nmap again. If it persists, try
again using the latest snapshot (-CURRENT) if you can. I use nmap
frequently from i386, sparc64 and amd64 and haven't had this problem. It
still looks like nmap might be exhausting your hard drive space. What
arguments are you passing to nmap? We don't need to see the IP addresses
you're scanning, but it would help to know how many IPs are you scanning at
a time as well.

uid 0 on /usr: file system full
uid 0 on /usr: file system full
uid 0 on /usr: file system full
uid 0 on /usr: file system full
uid 0 on /usr: file system full
uid 0 on /usr: file system full
uid 0 on /usr: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full

On Sat, Aug 5, 2017 at 8:29 AM, Zuleyha Torku 
wrote:

> Hi
> I'm trying to scan a bunch of IP address with nmap on OpenBSD 5.9 amd64.
> After a few moments nmap hangs but not crash or fall into unresponsive
> state. When I check with tcpdump it stops packet generation. No Error
> messages, no warning. Cpu and Mem. usages are normal as usual.
>
> I could not get any error that help me to define what is the problem even
> if I set verbose option.
> Have you ever seen this behaviour ? How can I go further ?
>
>
>
>
> OpenBSD 5.9 (GENERIC) #1761: Fri Feb 26 01:15:04 MST 2016
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
> real mem = 1056817152 (1007MB)
> avail mem = 1020686336 (973MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xf6a20 (9 entries)
> bios0: vendor SeaBIOS version "
> rel-1.9.1-0-gb3ef39f-prebuilt.qemu-project.org" date 04/01/2014
> bios0: QEMU Standard PC (i440FX + PIIX, 1996)
> acpi0 at bios0: rev 0
> acpi0: sleep states S3 S4 S5
> acpi0: tables DSDT FACP APIC HPET
> acpi0: wakeup devices
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Westmere E56xx/L56xx/X56xx (Nehalem-C), 2200.29 MHz
> cpu0:
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,
> CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,PCLMUL,
> SSSE3,CX16,

Re: i386 or amd64 from small Cloud instance ?

[Ax0n]

I have a virtually identical setup on my primary laptop (i5 540M, 8GB RAM)
running amd64 and my netbook (Atom N455, 2GB RAM) running i386. The
difference in RAM usage on boot is something around a dozen megabytes. You
won't notice this. The only good reason to run i386 is if your system
doesn't support amd64.

On Thu, Sep 14, 2017 at 3:57 AM, Michael Hekeler 
wrote:

> > Regarding OS and ports performance, does it make sense to use i386
> > rather than amd64 ?
>
> What is the meaning of "OS and ports performance"?
> Do you have concerns about the memory usage? Maybe we can say:
> AMD64 installs will always use more RAM than i386, so if you are low on
> RAM, then i386 will work faster. But with 4GB you aren´t low on RAM.
>
>

Mid-2015 MacBook Pro

[Ax0n]

I have a Mid-2015 MacBook Pro that I'm trying to get OpenBSD on. I
installed from the latest snapshot and from -RELEASE (installXX.fs written
to SD card). The install goes fine (using an axen(4) USB dongle for
connectivity) but upon reboot, it gets part way through, then the screen
goes blank with the backlight on. Although I can briefly see the axen(4)
attach, it doesn't seem to get an IP address if I let it sit around for a
few minutes. I can't get the dmesg, and I can't determine what the last
message is before the screen blanks. It doesn't appear to respond to the
keyboard.

Has anyone gotten this working? Google is pointing me to a few posts from
the likes of jcs@ and others about systems that are either slightly newer
or slightly older than mine. Any suggestions on getting a good dmesg out of
it? Devices I should consider disabling from UKC to get this thing off the
ground?

TIA-
ax0n

Re: Mid-2015 MacBook Pro

[Ax0n]

This one *should* be identical to the one I've been issued by my employer
(on which I'm running OS X) -- in that case, it has the NVidia GeForce GT
750M and the Intel Iris Pro. The Plot Thickens.

There's an error about /etc/boot.conf. The keyboard works fine at the FDE
prompt, and at the boot> prompt. There's an RTC BIOS diagnostic error
before the kernel loads. At the UCK prompt, the cursor is glitching and the
keyboard is unresponsive. External keyboard isn't helping.

Photos here, if it matters: https://imgur.com/a/iL6T0

On Thu, Sep 21, 2017 at 7:22 PM, Dave Voutila  wrote:

> ax0n,
>
> Is that a model with both integrated Intel gpu and dedicated Radeon
> gpu? Maybe look at drm(4) and try removing the radeon driver since the
> intel one should work fine.
>
> The intel drivers work great on my early-2015 MBP (i5 Broadwell), but
> then again it doesn't have any dedicated graphics.
>
> -Dave
>
> On Thu, Sep 21, 2017 at 6:19 PM, Ax0n  wrote:
> > I have a Mid-2015 MacBook Pro that I'm trying to get OpenBSD on. I
> > installed from the latest snapshot and from -RELEASE (installXX.fs
> written
> > to SD card). The install goes fine (using an axen(4) USB dongle for
> > connectivity) but upon reboot, it gets part way through, then the screen
> > goes blank with the backlight on. Although I can briefly see the axen(4)
> > attach, it doesn't seem to get an IP address if I let it sit around for a
> > few minutes. I can't get the dmesg, and I can't determine what the last
> > message is before the screen blanks. It doesn't appear to respond to the
> > keyboard.
> >
> > Has anyone gotten this working? Google is pointing me to a few posts from
> > the likes of jcs@ and others about systems that are either slightly
> newer
> > or slightly older than mine. Any suggestions on getting a good dmesg out
> of
> > it? Devices I should consider disabling from UKC to get this thing off
> the
> > ground?
> >
> > TIA-
> > ax0n
>

Re: Mid-2015 MacBook Pro

[Ax0n]

I actually tried a 6.2 amd64 snap downloaded fresh yesterday first, then
tried 6.1-RELEASE after that. When I installed 6.1-RELEASE, I bailed from
the installer, attached to the existing softraid crypto volume, nuked the
first 1M of the SR_CRYPTO volume -- sd2c in my case -- as in the FAQ and
then re-partioned it, rather than re-creating that volume from scratch
again.

The first photo is from the 6.2 snapshot and is mostly just to highlight
the hilarity that ensues when you run native resolution on a Retina
display. The next two are all from that second install of 6.1-RELEASE,
installed atop the crypto volume I created with the 2017-09-21 snap.

I did verify that the cursor glitches and keyboard goes unresponsive at the
UKC prompt ( from boot -c ) even from the install images for 6.1 and
yesterday's snap. Also, before the "Copyright (c) 1982..." kernel message,
I see this both in the install kernels and otherwise and it is also shown
in the image dump:

kbc: cmd word write error

I just did a fresh install from yesterday's snapshot without using FDE or
doing anything fancy. Results are now mostly the same except for a brief
intermission of flashing-question-folder (missing EFI, I presume) followed
by the bootloader (which I can type in) and the screen going blank and the
system going unresponsive in the same way as I reported in my first post.
I'm more systems and security guy than a developer, but I don't mind
helping where I can. I'm just out of ideas, so additional suggestions are
welcome.

On Fri, Sep 22, 2017 at 12:09 PM, Dave Voutila  wrote:

> Ax0n,
>
> That RTC error seems to come from a system dependent startclocks()
> function, but it was modified in August by jcs@ removing the logic
> that would even print that very error:
> https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/arch/
> amd64/isa/clock.c.diff?r1=1.24&r2=1.25
>
> Commit message mentions it's probably a red herring.
>
> In your linked pictures it looks like you're installing a 6.2 snapshot
> (older than 11 August?), but the image with the RTC BIOS error says
> 6.1. The plot is indeed thickening. :-)
>
> On Thu, Sep 21, 2017 at 10:01 PM, Ax0n  wrote:
> > This one *should* be identical to the one I've been issued by my employer
> > (on which I'm running OS X) -- in that case, it has the NVidia GeForce GT
> > 750M and the Intel Iris Pro. The Plot Thickens.
> >
> > There's an error about /etc/boot.conf. The keyboard works fine at the FDE
> > prompt, and at the boot> prompt. There's an RTC BIOS diagnostic error
> before
> > the kernel loads. At the UCK prompt, the cursor is glitching and the
> > keyboard is unresponsive. External keyboard isn't helping.
> >
> > Photos here, if it matters: https://imgur.com/a/iL6T0
> >
> > On Thu, Sep 21, 2017 at 7:22 PM, Dave Voutila 
> wrote:
> >>
> >> ax0n,
> >>
> >> Is that a model with both integrated Intel gpu and dedicated Radeon
> >> gpu? Maybe look at drm(4) and try removing the radeon driver since the
> >> intel one should work fine.
> >>
> >> The intel drivers work great on my early-2015 MBP (i5 Broadwell), but
> >> then again it doesn't have any dedicated graphics.
> >>
> >> -Dave
> >>
> >> On Thu, Sep 21, 2017 at 6:19 PM, Ax0n  wrote:
> >> > I have a Mid-2015 MacBook Pro that I'm trying to get OpenBSD on. I
> >> > installed from the latest snapshot and from -RELEASE (installXX.fs
> >> > written
> >> > to SD card). The install goes fine (using an axen(4) USB dongle for
> >> > connectivity) but upon reboot, it gets part way through, then the
> screen
> >> > goes blank with the backlight on. Although I can briefly see the
> axen(4)
> >> > attach, it doesn't seem to get an IP address if I let it sit around
> for
> >> > a
> >> > few minutes. I can't get the dmesg, and I can't determine what the
> last
> >> > message is before the screen blanks. It doesn't appear to respond to
> the
> >> > keyboard.
> >> >
> >> > Has anyone gotten this working? Google is pointing me to a few posts
> >> > from
> >> > the likes of jcs@ and others about systems that are either slightly
> >> > newer
> >> > or slightly older than mine. Any suggestions on getting a good dmesg
> out
> >> > of
> >> > it? Devices I should consider disabling from UKC to get this thing off
> >> > the
> >> > ground?
> >> >
> >> > TIA-
> >> > ax0n
> >
> >
>

athn0: device timeout and network hanging with AR9285

[Ax0n]

Frequently -- several times per hour when I'm actively doing stuff on my
laptop, the network hangs for perhaps 30-60 seconds. This coincides with
athn0 timeout messages on the console. I don't have much data to back up my
claim that it feels like it's more frequent since the upgrade to 6.2, but
it was happening under 6.1 Stable as well. I notice it more if I am moving
large-ish files around, but that could simply be because my work gets
interrupted.

The drm error in there seems unrelated. I hadn't seen it before 6.2 but
I've had no complaints with the graphics, so I'm not concerned about that
at the moment.

OpenBSD 6.2 (GENERIC.MP) #0: Thu Oct 12 19:53:18 CEST 2017
r...@syspatch-62-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/
GENERIC.MP
real mem = 8227655680 (7846MB)
avail mem = 7971287040 (7602MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xe9d90 (47 entries)
bios0: vendor Acer version "V1.07" date 11/07/2011
bios0: Acer Aspire 5733Z
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP ASF! HPET APIC MCFG SLIC BOOT ASPT DMAR SSDT SSDT
SSDT
acpi0: wakeup devices AZAL(S3) P0P1(S4) EHC1(S3) USB1(S3) USB2(S3) USB3(S3)
USB4(S3) USB5(S3) USB6(S3) USB7(S3) RP01(S4) PEG5(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i5 CPU M 540 @ 2.53GHz, 2527.89 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,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,AES,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: TSC frequency 2527894440 Hz
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.1.1, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i5 CPU M 540 @ 2.53GHz, 2527.44 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,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,AES,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 1, core 0, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Core(TM) i5 CPU M 540 @ 2.53GHz, 2527.44 MHz
cpu2:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,AES,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 5 (application processor)
cpu3: Intel(R) Core(TM) i5 CPU M 540 @ 2.53GHz, 2527.44 MHz
cpu3:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,AES,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 2, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
, remapped to apid 2
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (P0P2)
acpiprt2 at acpi0: bus 3 (P0P1)
acpiprt3 at acpi0: bus 1 (RP01)
acpiprt4 at acpi0: bus 2 (RP02)
acpiprt5 at acpi0: bus -1 (RP03)
acpiprt6 at acpi0: bus -1 (RP04)
acpiprt7 at acpi0: bus -1 (RP05)
acpiprt8 at acpi0: bus -1 (RP06)
acpiprt9 at acpi0: bus -1 (RP07)
acpiprt10 at acpi0: bus -1 (RP08)
acpiprt11 at acpi0: bus -1 (PEG5)
acpiec0 at acpi0
acpicpu0 at acpi0: C3(350@245 mwait.3@0x20), C2(500@205 mwait.3@0x10),
C1(1000@3 mwait.1), PSS
acpicpu1 at acpi0: C3(350@245 mwait.3@0x20), C2(500@205 mwait.3@0x10),
C1(1000@3 mwait.1), PSS
acpicpu2 at acpi0: C3(350@245 mwait.3@0x20), C2(500@205 mwait.3@0x10),
C1(1000@3 mwait.1), PSS
acpicpu3 at acpi0: C3(350@245 mwait.3@0x20), C2(500@205 mwait.3@0x10),
C1(1000@3 mwait.1), PSS
"pnp0c14" at acpi0 not configured
acpibat0 at acpi0: BAT0 model "Li_Ion_4000mA " serial 716a type Lion oem
"SANYO "
acpiac0 at acpi0: AC unit offline
acpibtn0 at acpi0: PWRB
acpibtn1 at acpi0: LID0
acpibtn2 at acpi0: SLPB
"ETD0500" at acpi0 not configured
"PNP0C14" at acpi0 not configured
"PNP0C14" at acpi0 not configured
acpivideo0 at acpi0: GFX0
acpivout at acpivideo0 not configured
acpivideo1 at acpi0: VGA_
cpu0: Enhanced SpeedStep 2527 MHz: speeds: 2533, 2399, 2266, 2133, 1999,
1866, 1733, 1599, 1466, 1333, 1199 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Core Host" rev 0x02
inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics" rev 0x02
drm0 at inteldrm0
intagp0 at inteldrm0
agp0 at intagp

Re: awk in OpenBSD

[Ax0n]

You didn't really make a great case for the newer awk, either. Is there a
good reason to use the 2012 release from upstream? If so, you could submit
a diff and explain the benefits.

On Oct 19, 2017 12:15 AM, "Niels Kobschaetzki" 
wrote:


> On 19. Oct 2017, at 06:23, flipchan  wrote:
>
> Yeah blindly follow the flow of the others , DONT THINK SO

That doesn’t explain the reasoning WHY the newer awk is not used.

>> On October 19, 2017 4:25:09 AM GMT+02:00, Andras Farkas <
deepbluemist...@gmail.com> wrote:
>> On the 6.2 release page, and confirmed in the source code, one can see
>> The system includes the following major components from outside
>> suppliers:
>> Awk Aug 10, 2011 version
>> This turns out to be one release behind upstream, where the latest
>> release is from December 20 2012: a quick check shows that
>> DragonFlyBSD, FreeBSD, and NetBSD all use this version.
>>
>> Just out of curiosity, is there a reason why OpenBSD uses the 2011
>> release?

Niels

Re: Abort Trap question

[Ax0n]

A quick thought... are you extracting src.tar.gz into /usr (like you to
with ports.tar.gz)? On a few occasions, I've done this (instead of making
sure I'm in /usr/src first as I should) and had system binaries get
clobbered. When I've accidentally done this in the past, I do get a bunch
of abort trap errors and a predictably un-bootable system.  Example: This
block of stuff from src.tar.gz, if extracted whilst in /usr, would
overwrite /usr/bin/cat with a directory full of the source code for cat(1)
and so on and so forth.

drwxrwxr-x  2 axon axon 0 Oct  9 22:41 bin
drwxrwxr-x  2 axon axon 0 Oct  9 22:41 bin/CVS
-rw-rw-r--  1 axon axon 5 Oct  9 22:38 bin/CVS/Root
-rw-rw-r--  1 axon axon 8 Oct  9 22:38 bin/CVS/Repository
-rw-rw-r--  1 axon axon   439 Oct  9 22:41 bin/CVS/Entries
-rw-rw-r--  1 axon axon18 Oct  9 22:41 bin/CVS/Tag
-rw-rw-r--  1 axon axon   241 Apr 25  2016 bin/Makefile
-rw-rw-r--  1 axon axon   145 Jul 11  2014 bin/Makefile.inc
drwxrwxr-x  2 axon axon 0 Oct  9 22:38 bin/cat
drwxrwxr-x  2 axon axon 0 Oct  9 22:41 bin/cat/CVS
-rw-rw-r--  1 axon axon 5 Oct  9 22:38 bin/cat/CVS/Root
-rw-rw-r--  1 axon axon12 Oct  9 22:38
bin/cat/CVS/Repository
-rw-rw-r--  1 axon axon   172 Oct  9 22:41 bin/cat/CVS/Entries
-rw-rw-r--  1 axon axon18 Oct  9 22:41 bin/cat/CVS/Tag
-rw-rw-r--  1 axon axon93 Feb 18  2017 bin/cat/Makefile
-rw-rw-r--  1 axon axon  4848 Jul  9  2016 bin/cat/cat.1
-rw-rw-r--  1 axon axon  5567 Oct 19  2016 bin/cat/cat.c



On Wed, Nov 15, 2017 at 5:24 PM, patrick keshishian 
wrote:

> On 11/15/17, Philip Guenther  wrote:
> > On Wed, Nov 15, 2017 at 11:08 AM, Mike Coddington 
> > wrote:
> >
> >> On Wed, Nov 15, 2017 at 10:01:09AM -0600, Daniel Boyd wrote:
> >> > I've installed OpenBSD/macppc twice on my G4 Cube now and it seems to
> >> > be working fine until I go to untar src.tar.gz at which point it
> throws
> >> > some abort trap errors and crashes.  If I reboot, I get a bunch of
> >> > abort traps during the boot process followed by several:
> >> >
> >> > init: can't exec getty '/usr/libexec/getty' for pot /dev/ttyC3: ...
> >> >
> >> > What do you guys think this is...?  Hard drive failure...?
> >>
> >> Out of curiosity, does the same thing happen if you extract the tar with
> >> the pax(1) program? That'll at least let you know if it's tar causing
> >> the problem or not.
> >>
> >
> > tar _is_ pax:
> > : corwin; ls -li /bin/tar /bin/pax
> > 52015 -r-xr-xr-x  3 root  bin  433472 Nov  1 11:15 /bin/pax
> > 52015 -r-xr-xr-x  3 root  bin  433472 Nov  1 11:15 /bin/tar
> > : corwin;
> >
> > Fundamentally, unless a userspace process is poking at devices or
> similar,
> > it should be unable to panic the kernel.  An abort trap in the kernel is
> > either a kernel bug or a hardware bug.  IIRC there's some pmap bug on
> > macppc that no one has managed to track down which causes crashes on some
> > machines, but not others.  I've never hit it on the Macbook I use for
> > builds, but the ports build boxes, whatever model they are, seem to hit
> it
> > periodically...
>
> I read it as the tar process is the one aborting. which, if true,
> sounds like user-land and kernel are out-of-sync.
>
> Unfortunately, specific info is missing from the problem report.
>
> --patrick
>
>

Re: Why regexp works different in stock vi vs. vim

[Ax0n]

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

⟨*literal next*⟩Escape the next character from any special meaning. The
⟨literal next⟩ character is usually ⟨control-V⟩.

This does the trick for me:
/^V


On Fri, Feb 5, 2016 at 12:13 PM, Артур Истомин
 wrote:

> I have file where first symbols are tabs:
>
> Sally tried really really hard
> Timmy tried really really really hard
> Johnny tried really really really really hard
>
> When I search tabs in stock vi with '/\t'. It finds all words 'tried'. In
> vim it finds tabs. Why? In fact, I can't find tabs in stock vi anyhow.My
> system is OpenBSD 5.8
>
> Thanks.

Ad-hoc wifi on athn(4)?

[Ax0n]

I'm working on a project with a local group that involves running a bunch
of systems in Ad-Hoc mode to form a mesh network. I was hoping to join my
daily driver to the mesh, but I'm not seeing any way to get Ad-Hoc/IBSS
mode enabled on athn(4) or any of the USB (urtw, urtnw, run) WiFi adapters
I have kicking around.

Checking man pages of the wifi drivers and ifmedia(4), It looks like the
support just isn't there. If that's the case, I'll pursue another route.
I'm hoping I'm just missing something obvious. Ideas?

ifconfig athn0 media:
athn0: flags=8843 mtu 1500
lladdr 00:26:4d:c3:a6:b0
priority: 4
groups: wlan
media: IEEE802.11 autoselect (DS1 mode 11g)
status: no network
ieee80211: nwid HiR wpakey  wpaprotos wpa1,wpa2
wpaakms psk wpaciphers tkip,ccmp wpagroupcipher tkip
supported media:
media autoselect
media autoselect mediaopt hostap
media autoselect mediaopt monitor
media autoselect mode 11b
media autoselect mode 11b mediaopt hostap
media autoselect mode 11b mediaopt monitor
media autoselect mode 11g
media autoselect mode 11g mediaopt hostap
media autoselect mode 11g mediaopt monitor

dmesg:
OpenBSD 5.9 (GENERIC.MP) #1616: Fri Feb 26 01:28:13 MST 2016
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Intel(R) Atom(TM) CPU N455 @ 1.66GHz ("GenuineIntel" 686-class) 1.67
GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,LONG,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,LAHF,PERF,SENSOR
real mem  = 2136285184 (2037MB)
avail mem = 2082795520 (1986MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: date 06/03/10, BIOS32 rev. 0 @ 0xfdc30, SMBIOS rev. 2.5
@ 0xdc010 (21 entries)
bios0: vendor TOSHIBA version "V1.70" date 06/03/2010
bios0: TOSHIBA TOSHIBA NB305
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP TCPA HPET MCFG SLIC APIC BOOT SSDT SSDT SSDT
acpi0: wakeup devices EXP1(S4) EXP2(S4) PXS3(S4) EXP4(S4) PCIB(S3) USB1(S3)
USB2(S0) USB3(S3) USB4(S0) EUSB(S3)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 166MHz
cpu0: mwait min=64, max=64, C-substates=0.2.2.0.2, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Atom(TM) CPU N455 @ 1.66GHz ("GenuineIntel" 686-class) 1.67
GHz
cpu1:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,LONG,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,LAHF,PERF,SENSOR
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 5 (EXP1)
acpiprt2 at acpi0: bus 7 (EXP2)
acpiprt3 at acpi0: bus 9 (EXP3)
acpiprt4 at acpi0: bus -1 (EXP4)
acpiprt5 at acpi0: bus 17 (PCIB)
acpiec0 at acpi0
acpicpu0 at acpi0: !C3(100@100 mwait.3@0x30), !C2(500@20 mwait.1@0x10),
C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: !C3(100@100 mwait.3@0x30), !C2(500@20 mwait.1@0x10),
C1(1000@1 mwait.1), PSS
acpiac0 at acpi0: AC unit online
acpibat0 at acpi0: BAT1 serial 41167 type Li-Ion oem "TOSHIBA"
acpibtn0 at acpi0: LID0
acpibtn1 at acpi0: PWRB
acpivideo0 at acpi0: IGD0
acpivout0 at acpivideo0: LCD_
bios0: ROM list: 0xc/0xda00! 0xce000/0x1000 0xdc000/0x4000!
cpu0: Enhanced SpeedStep 1663 MHz: speeds: 1667, 1333, 1000 MHz
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
0:28:2: bridge mem address conflict 0xf050/0x10
pchb0 at pci0 dev 0 function 0 "Intel Pineview DMI" rev 0x00
inteldrm0 at pci0 dev 2 function 0 "Intel Pineview Video" rev 0x00
drm0 at inteldrm0
intagp0 at inteldrm0
agp0 at intagp0: aperture at 0xd000, size 0x1000
inteldrm0: msi
inteldrm0: 1024x600
wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
"Intel Pineview Video" rev 0x00 at pci0 dev 2 function 1 not configured
azalia0 at pci0 dev 27 function 0 "Intel 82801GB HD Audio" rev 0x02: msi
azalia0: codecs: Realtek ALC272
audio0 at azalia0
ppb0 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x02: apic 2 int 16
pci1 at ppb0 bus 5
ppb1 at pci0 dev 28 function 1 "Intel 82801GB PCIE" rev 0x02: apic 2 int 17
pci2 at ppb1 bus 7
athn0 at pci2 dev 0 function 0 "Atheros AR9285" rev 0x01: apic 2 int 17
athn0: AR9285 rev 2 (1T1R), ROM rev 14, address 00:26:4d:c3:a6:b0
ppb2 at pci0 dev 28 function 2 "Intel 82801GB PCIE" rev 0x02: apic 2 int 18
pci3 at ppb2 bus 9
9:0:0: mem address conflict 0xf052/0x1000
9:0:0: mem address conflict 0xf051/0x1
re0 at pci3 dev 0 function 0 "Realtek 8101E"

Re: write all files in /mnt to usb using dd

[Ax0n]

I mis-understood your first post, Teng. The .iso image confused me and I
thought you were trying to write to optical media.

It sounds like you needed to simply mount the USB removable mass storage to
/mnt.  Oddly enough, I can't find a directly relevant entry for this in the
OpenBSD FAQ to link to, though it seems like a common-enough task. I'll
outline some simple steps for you (and maybe submit a diff for the
Multimedia FAQ with some more refinement).

Typically, /mnt doesn't have any files in it before you mount it. You
should move them somewhere else to avoid confusion.

Use disklabel(8) to determine the partition you want to mount. Many
pre-formatted USB drives have a MSDOS/FAT filesystem on partition i. For
example, on my laptop, the USB stick I inserted showed up as sd2, since sd1
is taken by the built-in media card reader. disklabel shows two entries (c
is always a meta-partition that means "whole disk") and the one I want to
mount is sd2i.

[axon@zodiac ~]$ doas disklabel sd2
# /dev/rsd2c:
type: SCSI
disk: SCSI disk
label: Windrunner
duid: 
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 7
total sectors: 118672
boundstart: 0
boundend: 118672
drivedata: 0

16 partitions:
#size   offset  fstype [fsize bsize  cpg]
  c:   1186720  unused
  i:   118543   32   MSDOS

[axon@zodiac ~]$ doas mount /dev/sd2i /mnt

As you can see below, /mnt is on /dev/sd2i and ready to use.
[axon@zodiac ~]$ df -h
Filesystem SizeUsed   Avail Capacity  Mounted on
/dev/sd0a  8.2G7.3G533M93%/
/dev/sd0l 59.6G4.1G   52.5G 7%/home
/dev/sd2i 57.8M   30.4M   27.4M53%/mnt
[axon@zodiac ~]$

Any files you copy to /mnt ought to show up on the removable media now.
Remember to umount /mnt when you're done. As Ted stated, you may also wish
to use tar to archive files to external media instead.

On Thu, Aug 4, 2016 at 8:21 AM, Teng Zhang  wrote:

> excellent idea!
> i bought two DVD+R discs,and storage 01.iso using the way you told me
> (the FAQ), it works fine. Thank you very much for your advice.
> And at the same time,i realize that the DVD+RW actually can replace the
> USB at
> least in terms of storaging  files(because they can both be written a
> thousound
> times)
>
>
> On 08/04/16 10:15, Noah wrote:
>
> If you look carefully at the man page for dd(1), you'll see that you can
> use it to write an image file directly to the block device. This is good
> for writing the contents of installXX.fs to a USB stick, or for making
> images of removable media. It's not the recommended way to burn an ISO to
> optical media, though.
>
> The steps you're looking for are outlined nicely in the FAQ:
> http://www.openbsd.org/faq/faq13.html#burnCD
> The man pages for mkhybrid(8) and cdio(1) are also worth a look.
>
> To directly answer your question, the steps you likely need to take
> (assuming your burner is cd1... you didn't paste your entire dmesg, so I
> can't tell what we're dealing with here):
>
> mkhybrid -R -o 01.iso /mnt
> cdio -f cd1c tao 01.iso
>
> On Wed, Aug 3, 2016 at 8:43 PM, Teng Zhang  wrote:
>
>> hi, i want to write all files in /mnt to usb,so i issued the command:
>>
>> doas dd if=/mnt of=/dev/rsd1c bs=5M
>>
>> but it failed. I'm not pretty understand the way to operate dd, so
>> could you please tell me how can i operate it to write the files to
>> usb?
>> Some information about my system:
>>
>> the files in /mnt is created like this:
>>
>> $ doas vnconfig vnd0 01.iso
>> $ doas mount /dev/vnd0c /mnt
>>
>> $ uname -a
>> OpenBSD zhangteng.my.domain 5.9 GENERIC.MP#1888 amd64
>>
>> $ mount
>> /dev/sd0a on / type ffs (local)
>> /dev/sd0m on /home type ffs (local, nodev, nosuid)
>> /dev/sd0d on /tmp type ffs (local, nodev, nosuid)
>> /dev/sd0f on /usr type ffs (local, nodev)
>> /dev/sd0g on /usr/X11R6 type ffs (local, nodev)
>> /dev/sd0h on /usr/local type ffs (local, nodev)
>> /dev/sd0l on /usr/obj type ffs (local, nodev, nosuid)
>> /dev/sd0k on /usr/src type ffs (local, nodev, nosuid)
>> /dev/sd0e on /var type ffs (local, nodev, nosuid)
>> /dev/vnd0c on /mnt type cd9660 (local, read-only)
>>
>> dmesg:
>> umass0 at uhub2 port 1 configuration 1 interface 0 "SanDisk Cruzer Edge"
>> rev 2.10/1.00 addr 3
>> umass0: using SCSI over Bulk-Only
>> scsibus2 at umass0: 2 targets, initiator 0
>> sd1 at scsibus2 targ 1 lun 0:  SCSI4 0/direct
>> removable serial.0781556b970715105252
>> sd1: 7632MB, 512 bytes/sector, 15630336 sectors

Removal of old libraries

[Ax0n]

I've got a Toshiba NB305 netbook that's been my daily-use laptop for more
than 6 years now. The last fresh install I did was OpenBSD 4.9-RELEASE in
early May 2011. I've been quite happy with how it works, and I've been
doing bsd.rd upgrades and M:Tier binary updates ever since.

There is a lot of seemingly unused cruft in /usr/local/lib -- stuff with an
atime of my last level 0 dump several months ago.   Looks like pkg_add -u
left a bunch of stuff behind. Is there a recommended way to clean this
stuff up, or should I just start chopping away with something like:

find /usr/local/lib -type f -atime +90 | doas xargs rm

(after a new level 0 dump, obviously...)

Re: Removal of old libraries

[Ax0n]

Thank you very much, all! Giving it a shot now.

On Sat, Sep 3, 2016, 16:35 Juan Francisco Cantero Hurtado 
wrote:

> On Sat, Sep 03, 2016 at 03:12:53PM -0500, Ax0n wrote:
> > I've got a Toshiba NB305 netbook that's been my daily-use laptop for more
> > than 6 years now. The last fresh install I did was OpenBSD 4.9-RELEASE in
> > early May 2011. I've been quite happy with how it works, and I've been
> > doing bsd.rd upgrades and M:Tier binary updates ever since.
> >
> > There is a lot of seemingly unused cruft in /usr/local/lib -- stuff with
> an
> > atime of my last level 0 dump several months ago.   Looks like pkg_add -u
> > left a bunch of stuff behind. Is there a recommended way to clean this
> > stuff up, or should I just start chopping away with something like:
> >
> > find /usr/local/lib -type f -atime +90 | doas xargs rm
> >
> > (after a new level 0 dump, obviously...)
> >
>
> pkg_add sysclean
>
> man sysclean
>
> --
> Juan Francisco Cantero Hurtado http://juanfra.info

Re: OpenBSD 6-stable vmd

[Ax0n]

I suppose I'll ask here since it seems on-topic for this thread. Let me
know if I shouldn't do this in the future. I've been testing vmm for
exactly a week on two different snapshots. I have two VMs: One running the
same snapshot (amd64, Oct 22) I'm running on the host vm, the other running
amd64 6.0-RELEASE with no patches of any kind.

For some reason, the vm running a recent snapshot locks up occasionally
while I'm interacting with it via cu or occasionally ssh. Should I expect a
ddb prompt and/or kernel panic messages via the virtualized serial console?
Is there some kind of "break" command on the console to get into ddb when
it appears to hang? A "No" or "Not yet" on those two questions would
suffice if not possible. I know this isn't supported, and appreciate the
hard work.

Host dmesg:
http://stuff.h-i-r.net/2016-10-22.Aspire5733Z.dmesg.txt

VM (Oct 22 Snapshot) dmesg:
http://stuff.h-i-r.net/2016-10-22.vmm.dmesg.txt

Second:
I'm using vm.conf (contents below) to start the aforementioned snapshot vm
at boot.
There's a "disable" line inside vm.conf to keep one VM from spinning up
with vmd.  Is there a way to start this one with vmctl aside from passing
all the options to vmctl as below?

doas vmctl start -c -d OBSD-RELa -i 1 -k /home/axon/obsd/amd64/bsd -m 512M

I've tried stuff along the lines of:
doas vmctl start OBSD-RELa.vm

vm "obsdvmm.vm" {
memory 512M
kernel "bsd"
disk "/home/axon/vmm/OBSD6"
interface tap
}
vm "OBSD-RELa.vm" {
memory 512M
kernel "/home/axon/obsd/amd64/bsd"
disk "/home/axon/vmm/OBSD-RELa"
interface tap
disable
}





On Mon, Oct 24, 2016 at 4:58 PM, R0me0 ***  wrote:

> Hey @Peter, one more time thank so much for the heads up :)
>
> For those that interest.
>
> I'm running OpenBSD-Current under VMware-Workstation 12 ( just need to set
> processor proprieties to virtualize intel VT-x/EPT or AMD-V/RVI )
>
> And have fun to test VMD
>
> :)
>
> Thank you
>
>
>
>
>
> 2016-10-22 8:43 GMT-02:00 R0me0 *** :
>
> > Hey Peter ,
> >
> > Thank you for the advice, I'll get current
> >
> > Cheers dude !
> >
> > (:
> >
> >
> > 2016-10-22 6:44 GMT-02:00 Peter Hessler :
> >
> >> This isn't expected to work at all.  That is why it was disabled.
> >> You'll need to upgrade the Hypervisor to -current, or to 6.1 when it is
> >> released.
> >>
> >>
> >>
> >> On 2016 Oct 22 (Sat) at 00:06:08 -0200 (-0200), R0me0 *** wrote:
> >> :Hello misc.
> >> :
> >> :For testing purposes
> >> :
> >> :I compiled kernel with vmd support.
> >> :
> >> :After start the vm -> vmctl start "myvm" -m 512M -i 1 -d disk.img -k
> >> /bsd.rd
> >> :
> >> :I created a bridge and added vether0 and tap0
> >> :
> >> :In the vm I have configured an ip 192.168.1.30
> >> :
> >> :If I perform ping from OpenBSD Hypervisor -> ping 192.168.1.30 all
> >> packages
> >> :are send and received "on the fly"
> >> :
> >> :But if I perform the same step from "myvm", there is no packet loss but
> >> the
> >> :packets take so long to be send and consecutively replied
> >> :
> >> :I am performing this tests on Linux  running Vmware Workstation 12 .
> >> :
> >> :Is this behavior expected ?
> >> :
> >> :Any directions will be appreciated.
> >> :
> >> :Thank you
> >> :
> >> :myvm dmesg:
> >> :
> >> :OpenBSD 6.0 (RAMDISK_CD) #2100: Tue Jul 26 13:05:59 MDT 2016
> >> :   dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/
> RAMDISK_CD
> >> :RTC BIOS diagnostic error 20
> >> :real mem = 520093696 (496MB)
> >> :avail mem = 502673408 (479MB)
> >> :mainbus0 at root
> >> :bios0 at mainbus0
> >> :acpi at bios0 not configured
> >> :cpu0 at mainbus0: (uniprocessor)
> >> :cpu0: Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz, 14335.74 MHz
> >> :cpu0:
> >> :FPU,VME,DE,PSE,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,
> >> PAT,PSE36,CFLUSH,DS,MMX,FXSR,SSE,SSE2,SS,SSE3,PCLMUL,SSSE3,
> >> FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,AVX,F1
> >> :6C,RDRAND,HV,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,ARAT
> >> :pvbus0 at mainbus0: OpenBSD
> >> :pci0 at mainbus0 bus 0
> >> :pchb0 at pci0 dev 0 function 0 "OpenBSD VMM PCI Host Bridge" rev 0x00
> >> :virtio0 at pci0 dev 1 function 0 "Qumranet Virtio RNG" rev 0x00
> >> :viornd0 at virtio0
> >> :virtio0: irq 3
> >> :virtio1 at pci0 dev 2 function 0 "Qumranet Virtio Storage" rev 0x00
> >> :vioblk0 at virtio1
> >> :scsibus0 at vioblk0: 2 targets
> >> :sd0 at scsibus0 targ 0 lun 0:  SCSI3 0/direct
> >> fixed
> >> :sd0: 5120MB, 512 bytes/sector, 10485760 sectors
> >> :virtio1: irq 5
> >> :virtio2 at pci0 dev 3 function 0 "Qumranet Virtio Network" rev 0x00
> >> :vio0 at virtio2: address fe:e1:ba:d0:d0:94
> >> :virtio2: irq 9
> >> :isa0 at mainbus0
> >> :com0 at isa0 port 0x3f8/8 irq 4: ns8250, no fifo
> >> :com0: console
> >> :softraid0 at root
> >> :scsibus1 at softraid0: 256 targets
> >> :root on rd0a swap on rd0b dump on rd0b
> >> :WARNING: invalid time in clock chip
> >> :WARNING: CHECK AND RESET THE DATE!
> >> :
> >> :openbsd hypervis

Re: OpenBSD 6-stable vmd

[Ax0n]

Thanks for the update, ml.

The VM Just did it again in the middle of backspacing over uname -a...

$ uname -a
OpenBSD vmmbsd.labs.h-i-r.net 6.0 GENERIC.MP#0 amd64
$ un   <-- frozen

Spinning like mad.

[axon@transient ~]$ vmctl status
   ID   PID VCPUSMAXMEMCURMEM  TTY NAME
2  2769 1 512MB 149MB   /dev/ttyp3 -c
1 48245 1 512MB 211MB   /dev/ttyp0 obsdvmm.vm
[axon@transient ~]$ ps aux | grep 48245
_vmd 48245 98.5  2.3 526880 136956 ??  Rp 1:54PM   47:08.30 vmd:
obsdvmm.vm (vmd)

load averages:  2.43,  2.36,
2.26
transient.my.domain 18:29:10
56 processes: 53 idle, 3 on
processor
up  4:35
CPU0 states:  3.8% user,  0.0% nice, 15.4% system,  0.6% interrupt, 80.2%
idle
CPU1 states: 15.3% user,  0.0% nice, 49.3% system,  0.0% interrupt, 35.4%
idle
CPU2 states:  6.6% user,  0.0% nice, 24.3% system,  0.0% interrupt, 69.1%
idle
CPU3 states:  4.7% user,  0.0% nice, 18.1% system,  0.0% interrupt, 77.2%
idle
Memory: Real: 1401M/2183M act/tot Free: 3443M Cache: 536M Swap: 0K/4007M

  PID USERNAME PRI NICE  SIZE   RES STATE WAIT  TIMECPU COMMAND
48245 _vmd  430  515M  134M onprocthrslee  47:37 98.00% vmd
 7234 axon   20  737M  715M sleep poll 33:18 19.14% firefox
42481 _x11  550   16M   42M onproc- 2:53  9.96% Xorg
 2769 _vmd  290  514M   62M idle  thrslee   2:29  9.62% vmd
13503 axon  100  512K 2496K sleep nanosle   0:52  1.12% wmapm
76008 axon  100  524K 2588K sleep nanosle   0:10  0.73% wmmon
57059 axon  100  248M  258M sleep nanosle   0:08  0.34% wmnet
23088 axon   20  580K 2532K sleep select0:10  0.00%
wmclockmon
64041 axon   20 3752K   10M sleep poll  0:05  0.00% wmaker
16919 axon   20 7484K   20M sleep poll  0:04  0.00%
xfce4-terminal
1 root  100  408K  460K idle  wait  0:01  0.00% init
80619 _ntp   2  -20  880K 2480K sleep poll  0:01  0.00% ntpd
 9014 _pflogd40  672K  408K sleep bpf   0:01  0.00% pflogd
58764 root  100 2052K 7524K idle  wait  0:01  0.00% slim



On Mon, Oct 24, 2016 at 10:47 PM, Mike Larkin  wrote:

> On Mon, Oct 24, 2016 at 07:36:48PM -0500, Ax0n wrote:
> > I suppose I'll ask here since it seems on-topic for this thread. Let me
> > know if I shouldn't do this in the future. I've been testing vmm for
> > exactly a week on two different snapshots. I have two VMs: One running
> the
> > same snapshot (amd64, Oct 22) I'm running on the host vm, the other
> running
> > amd64 6.0-RELEASE with no patches of any kind.
> >
> > For some reason, the vm running a recent snapshot locks up occasionally
> > while I'm interacting with it via cu or occasionally ssh. Should I
> expect a
> > ddb prompt and/or kernel panic messages via the virtualized serial
> console?
> > Is there some kind of "break" command on the console to get into ddb when
> > it appears to hang? A "No" or "Not yet" on those two questions would
> > suffice if not possible. I know this isn't supported, and appreciate the
> > hard work.
> >
> > Host dmesg:
> > http://stuff.h-i-r.net/2016-10-22.Aspire5733Z.dmesg.txt
> >
> > VM (Oct 22 Snapshot) dmesg:
> > http://stuff.h-i-r.net/2016-10-22.vmm.dmesg.txt
> >
>
> These look fine. Not sure why it would have locked up. Is the associated
> vmd
> process idle, or spinning like mad?
>
> -ml
>
> > Second:
> > I'm using vm.conf (contents below) to start the aforementioned snapshot
> vm
> > at boot.
> > There's a "disable" line inside vm.conf to keep one VM from spinning up
> > with vmd.  Is there a way to start this one with vmctl aside from passing
> > all the options to vmctl as below?
> >
> > doas vmctl start -c -d OBSD-RELa -i 1 -k /home/axon/obsd/amd64/bsd -m
> 512M
> >
> > I've tried stuff along the lines of:
> > doas vmctl start OBSD-RELa.vm
> >
> > vm "obsdvmm.vm" {
> > memory 512M
> > kernel "bsd"
> > disk "/home/axon/vmm/OBSD6"
> > interface tap
> > }
> > vm "OBSD-RELa.vm" {
> > memory 512M
> > kernel "/home/axon/obsd/amd64/bsd"
> > disk "/home/axon/vmm/OBSD-RELa"
> > interface tap
> > disable
> > }
> >
>
> I think this is being worked on, but not done yet.
>
> -ml

Re: OpenBSD 6-stable vmd

[Ax0n]

I'm running vmd with the options you specified, and using tee(1) to peel it
off to a file while I can still watch what happens in the foreground. It
hasn't happened again yet, but I haven't been messing with the VMs as much
this week as I was over the weekend.

One thing of interest: inside the VM running the Oct 22 snapshot, top(1)
reports the CPU utilization hovering over 1.0 load, with nearly 100% in
interrupt state, which seems pretty odd to me.  I am also running an i386
and amd64 vm at the same time, both on 6.0-Release and neither of them are
exhibiting this high load. I'll probably update the snapshot of the
-CURRENT(ish) VM tonight, and the snapshot of my host system (which is also
my daily driver) this weekend.

load averages:  1.07,  1.09,  0.94   vmmbsd.labs.h-i-r.net
05:05:27
26 processes: 1 running, 24 idle, 1 on processor   up
 0:28
CPU states:  0.0% user,  0.0% nice,  0.4% system, 99.6% interrupt,  0.0%
idle
Memory: Real: 21M/130M act/tot Free: 355M Cache: 74M Swap: 0K/63M

  PID USERNAME PRI NICE  SIZE   RES STATE WAIT  TIMECPU COMMAND
1 root  100  420K  496K idle  wait  0:01  0.00% init
13415 _ntp   2  -20  888K 2428K sleep poll  0:00  0.00% ntpd
15850 axon   30  724K  760K sleep ttyin 0:00  0.00% ksh
42990 _syslogd   20  972K 1468K sleep kqread0:00  0.00% syslogd
89057 _pflogd40  672K  424K sleep bpf   0:00  0.00% pflogd
 2894 root   20  948K 3160K sleep poll  0:00  0.00% sshd
85054 _ntp   20  668K 2316K idle  poll  0:00  0.00% ntpd



On Tue, Oct 25, 2016 at 2:09 AM, Mike Larkin  wrote:

> On Mon, Oct 24, 2016 at 11:07:32PM -0500, Ax0n wrote:
> > Thanks for the update, ml.
> >
> > The VM Just did it again in the middle of backspacing over uname -a...
> >
> > $ uname -a
> > OpenBSD vmmbsd.labs.h-i-r.net 6.0 GENERIC.MP#0 amd64
> > $ un   <-- frozen
> >
> > Spinning like mad.
> >
>
> Bizarre. If it were I, I'd next try killing all vmd processes and
> running vmd -dvvv from a root console window and look for what it dumps
> out when it hangs like this (if anything).
>
> You'll see a fair number of "vmd: unknown exit code 1" (and 48), those
> are harmless and can be ignored, as can anything that vmd dumps out
> before the vm gets stuck like this.
>
> If you capture this and post somewhere I can take a look. You may need to
> extract the content out of /var/log/messages if a bunch gets printed.
>
> If this fails to diagnose what happens, I can work with you off-list on
> how to debug further.
>
> -ml
>
> > [axon@transient ~]$ vmctl status
> >ID   PID VCPUSMAXMEMCURMEM  TTY NAME
> > 2  2769 1 512MB 149MB   /dev/ttyp3 -c
> > 1 48245 1 512MB 211MB   /dev/ttyp0 obsdvmm.vm
> > [axon@transient ~]$ ps aux | grep 48245
> > _vmd 48245 98.5  2.3 526880 136956 ??  Rp 1:54PM   47:08.30 vmd:
> > obsdvmm.vm (vmd)
> >
> > load averages:  2.43,  2.36,
> > 2.26
> > transient.my.domain 18:29:10
> > 56 processes: 53 idle, 3 on
> > processor
> > up  4:35
> > CPU0 states:  3.8% user,  0.0% nice, 15.4% system,  0.6% interrupt, 80.2%
> > idle
> > CPU1 states: 15.3% user,  0.0% nice, 49.3% system,  0.0% interrupt, 35.4%
> > idle
> > CPU2 states:  6.6% user,  0.0% nice, 24.3% system,  0.0% interrupt, 69.1%
> > idle
> > CPU3 states:  4.7% user,  0.0% nice, 18.1% system,  0.0% interrupt, 77.2%
> > idle
> > Memory: Real: 1401M/2183M act/tot Free: 3443M Cache: 536M Swap: 0K/4007M
> >
> >   PID USERNAME PRI NICE  SIZE   RES STATE WAIT  TIMECPU
> COMMAND
> > 48245 _vmd  430  515M  134M onprocthrslee  47:37 98.00% vmd
> >  7234 axon   20  737M  715M sleep poll 33:18 19.14%
> firefox
> > 42481 _x11  550   16M   42M onproc- 2:53  9.96% Xorg
> >  2769 _vmd  290  514M   62M idle  thrslee   2:29  9.62% vmd
> > 13503 axon  100  512K 2496K sleep nanosle   0:52  1.12% wmapm
> > 76008 axon  100  524K 2588K sleep nanosle   0:10  0.73% wmmon
> > 57059 axon  100  248M  258M sleep nanosle   0:08  0.34% wmnet
> > 23088 axon   20  580K 2532K sleep select0:10  0.00%
> > wmclockmon
> > 64041 axon   20 3752K   10M sleep poll  0:05  0.00%
> wmaker
> > 16919 axon   20 7484K   20M sleep poll  0:04  0.00%
> > xfce4-terminal
> > 1 root  100  408K  460K idle  wait  0:01  0.00% init
> > 80619 _ntp   2  -20  880K 2480K sleep poll  0:01  0.00% ntpd
>

Re: OpenBSD 6-stable vmd

[Ax0n]

To circle back: I can reproduce the VM lock-up 100% of the time by typing
too quickly into the VM virtual serial console, such as my password and
longer command strings that I know by muscle memory.

I tried a few things such as slowly typing several kilobytes of text into
the console, one character at a time.

If I mash the keyboard inside cu, the VM locks up. I went to the text
console of the VM host (my daily-driver laptop), and slowly decreased the
keyboard repeat time with:

wsconsctl keyboard.repeat.deln=

And then attached to the vm virtual console using "doas vmctl console 1"

I proceeded to hold down a key and let a few lines of text show up before
exiting the console, decreasing the deln delay further, and repeating the
experiment.

100 is the default value, so holding a key down (longer than the default
400msec value of del1) will result in a 100msec delay between repeat
keystrokes on input.

I reduced this first to 75, then to 50, 25, 15, 10, and 5.

With a repeat delay of 5msec on the virtual console, I was able to reliably
lock up vms in a few dozen "keystrokes" (a matter of a second or two
holding a key down).

I was able to get three different vms to lock up, one running the october
22 snapshot, and two others running OpenBSD-6.0 Release, one i386, the
other amd64.

I cannot reproduce this, even with a high keyboard repeat rate, though an
SSH session to any of the VMs.

Mike and I have been in touch off-list (Thanks again!), but I thought the
results of my testing were relevant to misc@.



On Wed, Oct 26, 2016 at 7:15 PM, Mike Larkin  wrote:

> On Wed, Oct 26, 2016 at 06:36:25PM -0500, Ax0n wrote:
> > I'm running vmd with the options you specified, and using tee(1) to peel
> it
> > off to a file while I can still watch what happens in the foreground. It
> > hasn't happened again yet, but I haven't been messing with the VMs as
> much
> > this week as I was over the weekend.
> >
> > One thing of interest: inside the VM running the Oct 22 snapshot, top(1)
> > reports the CPU utilization hovering over 1.0 load, with nearly 100% in
> > interrupt state, which seems pretty odd to me.  I am also running an i386
> > and amd64 vm at the same time, both on 6.0-Release and neither of them
> are
> > exhibiting this high load. I'll probably update the snapshot of the
> > -CURRENT(ish) VM tonight, and the snapshot of my host system (which is
> also
> > my daily driver) this weekend.
> >
>
> I've seen that (and have seen it reported) from time to time as well. This
> is unlikely time being spent in interrupt, it's more likely a time
> accounting
> error that's making the guest think it's spending more in interrupt
> servicing
> than it actually is. This is due to the fact that both the statclock and
> hardclock are running at 100Hz (or close to it) because the host is unable
> to inject more frequent interrupts.
>
> You might try running the host at 1000Hz and see if that fixes the problem.
> It did, for me. Note that such an adjustment is really a hack and should
> just be viewed as a temporary workaround. Of course, don't run your guests
> at 1000Hz as well (that would defeat the purpose of cranking the host).
> That
> parameter can be adjusted in param.c.
>
> -ml
>
> > load averages:  1.07,  1.09,  0.94   vmmbsd.labs.h-i-r.net
> > 05:05:27
> > 26 processes: 1 running, 24 idle, 1 on processor   up
> >  0:28
> > CPU states:  0.0% user,  0.0% nice,  0.4% system, 99.6% interrupt,  0.0%
> > idle
> > Memory: Real: 21M/130M act/tot Free: 355M Cache: 74M Swap: 0K/63M
> >
> >   PID USERNAME PRI NICE  SIZE   RES STATE WAIT  TIMECPU
> COMMAND
> > 1 root  100  420K  496K idle  wait  0:01  0.00% init
> > 13415 _ntp   2  -20  888K 2428K sleep poll  0:00  0.00% ntpd
> > 15850 axon   30  724K  760K sleep ttyin 0:00  0.00% ksh
> > 42990 _syslogd   20  972K 1468K sleep kqread0:00  0.00%
> syslogd
> > 89057 _pflogd40  672K  424K sleep bpf   0:00  0.00%
> pflogd
> >  2894 root   20  948K 3160K sleep poll  0:00  0.00% sshd
> > 85054 _ntp   20  668K 2316K idle  poll  0:00  0.00% ntpd
> >
> >
> >
> > On Tue, Oct 25, 2016 at 2:09 AM, Mike Larkin 
> wrote:
> >
> > > On Mon, Oct 24, 2016 at 11:07:32PM -0500, Ax0n wrote:
> > > > Thanks for the update, ml.
> > > >
> > > > The VM Just did it again in the middle of backspacing over uname
> -a...
> > > >
> > > > $ uname -a
> > > > OpenBSD vmmbsd.labs.h-i-r.net 6.0 GENERIC.MP#0 amd64
> > > >

Building electron on OpenBSD

[Ax0n]

In talking to some folks at SpiderOak few months ago, their technical
co-founder said that the ability to get Go 1.6+ and Electron working on
OpenBSD are the major technical hurdles to getting Semaphor (which is a
privacy-friendly, security-minded collaborative platform one might compare
to Slack or HipChat) running on our favorite operating system.

https://spideroak.com/solutions/semaphor/
https://spideroak.com/solutions/semaphor/source/

I'm running current, and I see we have Go 1.7 in ports, and in binary
packages for some platforms. Electron's a different story. It's built on
nodejs and requires python 2.7 (both of which I've also already installed)
but it looks like the build scripts don't even take *BSD into consideration
and I'm at a dead end.

Electron:
https://github.com/electron/electron/

"Build Instructions":
https://github.com/electron/electron/blob/master/docs/development/build-instructions-linux.md

I am not a developer. At best, I'm an excited end-user that's got a lot of
sysadmin experience. I can apply patches to programs, compile basic stuff
if the Makefiles aren't totally hosed, and maybe sometimes tweak code a
bit, but this stuff really isn't my strong suit at all. I can sometimes get
things to work. This isn't one of them. Anyone have some pointers for me?
Would ports@ be a better place for this?

Re: Oddness with pkg_add

[Ax0n]

Can we see the contents of /etc/pkg.conf and/or your $PKG_PATH variable
from inside root's session?

On Wed, Nov 2, 2016 at 6:48 PM, Chris Huxtable  wrote:

> OpenBSD Community,
>
> I upgraded my OpenBSD router from 5.9 to 6.0 by clean install and copied a
> number of my old configs to the new install. I have almost everything in a
> working state except one program, pkg_add. I have tried to sort this out,
> done
> another clean install, reviewed all my configs, and reached the end of my
> understanding. Below are tests I have preformed and their output and
> configs I
> think may be relevant.
>
> # pkg_add nano
> Error from http://ftp.openbsd.org/pub/OpenBSD/6.0/packages/amd64/
> ftp: ftp.openbsd.org: no address associated with name
> http://ftp.openbsd.org/pub/OpenBSD/6.0/packages/amd64/ is empty
> Error from http://openbsd.cs.toronto.edu/pub/OpenBSD/6.0/packages/amd64/
> ftp: openbsd.cs.toronto.edu: no address associated with name
> http://openbsd.cs.toronto.edu/pub/OpenBSD/6.0/packages/amd64/ is empty
> Error from http://athena.caslab.queensu.ca/pub/OpenBSD/6.0/packages/amd64/
> ftp: athena.caslab.queensu.ca: no address associated with name
> http://athena.caslab.queensu.ca/pub/OpenBSD/6.0/packages/amd64/ is empty
> Can't find nano
>
> $ uname -a
> OpenBSD xyz.abc.def 6.0 GENERIC.MP#2319 amd64
>
> $ host ftp.openbsd.org
> ftp.openbsd.org is an alias for openbsd.sunsite.ualberta.ca.
> openbsd.sunsite.ualberta.ca has address 129.128.5.191
>
> $ dig ftp.openbsd.com
> […]
> ;; ANSWER SECTION:
> ftp.openbsd.com.21599   IN  CNAME
> openbsd.sunsite.ualberta.ca.
> openbsd.sunsite.ualberta.ca. 21599 IN   A   129.128.5.191
>
> ;; Query time: 789 msec
> ;; SERVER: 127.0.0.1#53(127.0.0.1)
> […]
>
> $ ping -c 1 google.com
> PING google.com (172.217.0.174): 56 data bytes
> 64 bytes from 172.217.0.174: icmp_seq=0 ttl=59 time=5.488 ms
> --- google.com ping statistics ---
> 1 packets transmitted, 1 packets received, 0.0% packet loss
> round-trip min/avg/max/std-dev = 5.488/5.488/5.488/0.000 ms
>
> $ cat /etc/resolv.conf
> search abc.def ghi.jkl mno.pqr
> nameserver 127.0.0.1
> nameserver 8.8.8.8
> nameserver 8.8.4.4
> lookup bind file
>
> $ cat /etc/hostname.pppoe0
> inet 0.0.0.0 255.255.255.255 NONE \
> pppoedev em1 authproto pap \
> authname 'thisIsNotMyAuthName' authkey 'thisIsNotMyAuthKey' up
> dest 0.0.0.1
>
> group egress
>
> !/sbin/route add default -ifp pppoe0 0.0.0.1
>
> $ cat /etc/hostname.em1
> group egress
>
> up
>
> $ ftp -o /tmp/test.html
> http://ftp.openbsd.org/pub/OpenBSD/6.0/packages/amd64/
> Trying 129.128.5.191...
> Requesting http://ftp.openbsd.org/pub/OpenBSD/6.0/packages/amd64/
> 100% |**|  1171 KB
> 00:02
> 1199135 bytes received in 2.65 seconds (441.42 KB/s)
>
>
> Would anyone have insight as to why everything works except pkg_add? Any
> help
> would be appreciated.
>
> Regards,
>
> Chris

Re: Oddness with pkg_add

[Ax0n]

That config looks completely rational. Perhaps add -v (or -vv .. -v) to
get more and more verbose error messages and see if something useful pops
up in the verbose output.

On Thu, Nov 3, 2016 at 3:19 PM, Chris Huxtable  wrote:

> # cat /etc/pkg.conf
> installpath = http://ftp.openbsd.org/%m/
> installpath += http://openbsd.cs.toronto.edu/%m/
> installpath += http://athena.caslab.queensu.ca/%m/
>
> # echo $PKG_PATH
>
> PKG_PATH is empty as I use pkg.conf
>
> On Nov 3, 2016, at 3:43 PM, Ax0n  wrote:
>
> Can we see the contents of /etc/pkg.conf and/or your $PKG_PATH variable
> from inside root's session?
>
> On Wed, Nov 2, 2016 at 6:48 PM, Chris Huxtable  wrote:
>
>> OpenBSD Community,
>>
>> I upgraded my OpenBSD router from 5.9 to 6.0 by clean install and copied a
>> number of my old configs to the new install. I have almost everything in a
>> working state except one program, pkg_add. I have tried to sort this out,
>> done
>> another clean install, reviewed all my configs, and reached the end of my
>> understanding. Below are tests I have preformed and their output and
>> configs I
>> think may be relevant.
>>
>> # pkg_add nano
>> Error from http://ftp.openbsd.org/pub/OpenBSD/6.0/packages/amd64/
>> ftp: ftp.openbsd.org: no address associated with name
>> http://ftp.openbsd.org/pub/OpenBSD/6.0/packages/amd64/ is empty
>> Error from http://openbsd.cs.toronto.edu/pub/OpenBSD/6.0/packages/amd64/
>> ftp: openbsd.cs.toronto.edu: no address associated with name
>> http://openbsd.cs.toronto.edu/pub/OpenBSD/6.0/packages/amd64/ is empty
>> Error from http://athena.caslab.queensu.ca/pub/OpenBSD/6.0/packages/amd
>> 64/
>> ftp: athena.caslab.queensu.ca: no address associated with name
>> http://athena.caslab.queensu.ca/pub/OpenBSD/6.0/packages/amd64/ is empty
>> Can't find nano
>>
>> $ uname -a
>> OpenBSD xyz.abc.def 6.0 GENERIC.MP#2319 <http://generic.mp/#2319> amd64
>>
>> $ host ftp.openbsd.org
>> ftp.openbsd.org is an alias for openbsd.sunsite.ualberta.ca.
>> openbsd.sunsite.ualberta.ca has address 129.128.5.191
>>
>> $ dig ftp.openbsd.com
>> […]
>> ;; ANSWER SECTION:
>> ftp.openbsd.com.21599   IN  CNAME
>> openbsd.sunsite.ualberta.ca.
>> openbsd.sunsite.ualberta.ca. 21599 IN   A   129.128.5.191
>>
>> ;; Query time: 789 msec
>> ;; SERVER: 127.0.0.1#53(127.0.0.1)
>> […]
>>
>> $ ping -c 1 google.com
>> PING google.com (172.217.0.174): 56 data bytes
>> 64 bytes from 172.217.0.174: icmp_seq=0 ttl=59 time=5.488 ms
>> --- google.com ping statistics ---
>> 1 packets transmitted, 1 packets received, 0.0% packet loss
>> round-trip min/avg/max/std-dev = 5.488/5.488/5.488/0.000 ms
>>
>> $ cat /etc/resolv.conf
>> search abc.def ghi.jkl mno.pqr
>> nameserver 127.0.0.1
>> nameserver 8.8.8.8
>> nameserver 8.8.4.4
>> lookup bind file
>>
>> $ cat /etc/hostname.pppoe0
>> inet 0.0.0.0 255.255.255.255 NONE \
>> pppoedev em1 authproto pap \
>> authname 'thisIsNotMyAuthName' authkey 'thisIsNotMyAuthKey' up
>> dest 0.0.0.1
>>
>> group egress
>>
>> !/sbin/route add default -ifp pppoe0 0.0.0.1
>>
>> $ cat /etc/hostname.em1
>> group egress
>>
>> up
>>
>> $ ftp -o /tmp/test.html
>> http://ftp.openbsd.org/pub/OpenBSD/6.0/packages/amd64/
>> Trying 129.128.5.191...
>> Requesting http://ftp.openbsd.org/pub/OpenBSD/6.0/packages/amd64/
>> 100% |**|  1171 KB
>> 00:02
>> 1199135 bytes received in 2.65 seconds (441.42 KB/s)
>>
>>
>> Would anyone have insight as to why everything works except pkg_add? Any
>> help
>> would be appreciated.
>>
>> Regards,
>>
>> Chris

Re: Is 6.1 expected to happen soon?

[Ax0n]

My advice: If you really want the performance boost and you think a recent
snapshot will provide it, make sure your backups are good and test the
snapshot on comparable hardware as best you can. I usually restore the dump
to a similar system, then boot from a snapshot bsd.rd and choose "Upgrade",
and if it works fine, then do the same upgrade in the production
environment. If it doesn't work right, troubleshoot it and file a bug
report, or wait a few days and try another snapshot. Or both. Whenever I've
had to do this in prod or on a system I rely on daily, I tend to stick with
that one working snapshot unless something gets strange.

You can jump back from your mid-cycle snapshot to -RELEASE when 6.1 becomes
available (presuming the changes you want are included in the release), and
then, track -STABLE with cvs, manual patches from errata or use M:Tier's
openup script.


On Thu, Nov 3, 2016 at 8:01 PM,  wrote:

> >>Aren't the snapshots running fairly well vetted code anyway - only
> >>using code that's been accepted into the source tree?  Obviously not
> >>as well vetted as the -STABLE and -RELEASE, of course.
> >
> > Snapshots are generated as fast as we can, from what is commited.
>
> Doesn't uncommitted code occasionally find its way into snapshots?
>
> sl

Re: Dell R930 server

[Ax0n]

"Nobody in their right mind would use OpenBSD for that."

That's how literally all of the projects I've used OpenBSD for have started.

On Nov 9, 2016 2:39 AM, "Martin Schröder"  wrote:

> 2016-11-09 9:06 GMT+01:00 ludovic coues :
> > I would say big data.
> >
> > Stackexchange have a pair of SQL Server, with 384Go of memory for
> > stackoverflow and 768 for everything else, a Redis server with 256, a
> > server for elasticsearch with 192 and same quantity for an HAProxy
> > server.
>
> None of this is the domain of OpenBSD and nobody in his right mind
> wants to run Stackexchange on OpenBSD.
>
> Or are you suggesting that SAP should port HANA to OpenBSD?
>
> Best
>Martin

softraid(4) full-disk encryption on SSD

[Ax0n]

I just purchased a SanDisk SSD for my daily-driver laptop which has been
running -CURRENT well. I'm considering going with FDE and a fresh snapshot
install, adding my packages then copying over what I need from my old
spinning rust drive, mostly /home and the ssh host keys from /etc/ssh.

Anything I should look out for? To be honest, this is my first experience
installing anything onto an SSD so I'd be welcome to accept any pointers
specific to OpenBSD. Searching misc@ for as long as I've been subscribed
hasn't yielded any solid input on this.

TIA!
--ax0n

Re: softraid(4) full-disk encryption on SSD

[Ax0n]

I'm less concerned about swap, and more concerned about how a fully
encrypted softraid Solid State Disk is going to act. I can't find a lot
about FDE on SSD.

On Wed, Nov 16, 2016 at 9:41 AM, trondd  wrote:

> On Wed, November 16, 2016 10:23 am, Jiri B wrote:
> > On Wed, Nov 16, 2016 at 09:14:51AM -0600, Ax0n wrote:
> >> I just purchased a SanDisk SSD for my daily-driver laptop which has been
> >> running -CURRENT well. I'm considering going with FDE and a fresh
> >> snapshot
> >> install, adding my packages then copying over what I need from my old
> >> spinning rust drive, mostly /home and the ssh host keys from /etc/ssh.
> >>
> >> Anything I should look out for? To be honest, this is my first
> >> experience
> >> installing anything onto an SSD so I'd be welcome to accept any pointers
> >> specific to OpenBSD. Searching misc@ for as long as I've been
> subscribed
> >> hasn't yielded any solid input on this.
> >
> > Not sure if encrypting swap makes still sense if you already have FDE.
> > What's recommended in this context?
> >
> > j.
> >
>
> It's been discussed previously.  Relavant comment from the thread:
>
> http://marc.info/?l=openbsd-misc&m=143206067713324&w=2
>
> And hint, you can search an online archive instead of being limited to
> searching "for as long as you've been subscribed" :)

Re: softraid(4) full-disk encryption on SSD

[Ax0n]

I'm taking the plunge now. Mostly, I was concerned about SSD longevity and
if TRIM would be a problem due to the different way data is going to be
accessed. It was the cheapest drive I could find locally anyway, and I keep
good backups (dump to a much larger external drive that's also using
softraid crypto) so I suppose if it burns up in a year it's not really that
big of a problem.

On Wed, Nov 16, 2016 at 10:33 AM, Marc Peters  wrote:

> Am 11/16/16 um 17:07 schrieb Ax0n:
> > I'm less concerned about swap, and more concerned about how a fully
> > encrypted softraid Solid State Disk is going to act. I can't find a lot
> > about FDE on SSD.
> >
>
> It acts as a normal harddisk would, just faster :). I had one in my
> worklaptop i used before for about two years and i have one in my
> worklaptop. No problems.

Expired certificate on lists.openbsd.org

[Ax0n]

Self-explanatory. I went to approve my post to bugs@ and got this. Looks
like it lapsed earlier this week.

http://imgur.com/QzYSjS8

Re: FAQ update

[Ax0n]

The first command will create a new virtual drive device ( sd2 perhaps?)
and you'll want to create your softraid crypto volume on that device, not
on sd0.

Note that I've never tried this, and that the bootloader might need some
additional help after you have the striped softraid encrypted.

On Mon, Dec 5, 2016 at 11:12 AM, Todd Carpenter 
wrote:

> Hi guys,
>
> I was wondering if you could update the documentation to show how to both
> strip and geli encrypt the device..
>
> cut --
>
> to
>
> Next, create the mirror with the bioctl(8) 
>  command.
>
> # *bioctl -c 1 -l sd0a,sd1a softraid0*
>
>
> *Thats good, but the next part shows*
>
>
> # *bioctl -c C -l sd0a softraid0*
> New passphrase:
> Re-type passphrase:
> sd1 at scsibus2 targ 1 lun 0:  SCSI2 0/direct
> fixed
> sd1: 19445MB, 512 bytes/sector, 39824607 sectors
> softraid0: CRYPTO volume attached as sd1
>
>
> The problem is that it says softraid is full. perhaps Im doing
> something wrong..
>
>
> am I doing something wrong?
>
>
> thanks!

Re: VPS default gateway in a different subnet than host

[Ax0n]

I'm guessing the default route a.k.a. gateway already exists, and you're
trying to add another, duplicate route. What's the output of the following
command before and after you do the route add?

netstat -rn -finet

On Tue, Dec 13, 2016 at 2:51 PM, Jyri Hovila [iki.fi] 
wrote:

> Hi,
>
> a brief follow-up.
>
> With Linux, default gateway that resides in different subnet than the
> host, all that has to be done is 1) adding a static route to the
> default gateway and then 2) adding the default gateway to routing table.
>
> With my OpenBSD test case, I already have a static route to the default
> gateway (thanks to correctly configured DHCP server) but when I try to
> add default gateway:
>
> # route add default 5.166.16.254
> add net default: gateway 5.166.16.254: Too many levels of symbolic links
>
> I'm still googling but haven't found a solution yet.
>
> Any tips, anyone?
>
> - Jyri

Re: doas prompting for password in script

[Ax0n]

For now, you may want to use the "nopass" keyword and set up
highly-restrictive rules. The last matching rule determines the action
taken, so you can have more general rules up top, and more specific ones
that don't require a password toward the end. For example, my wireless
network manager script relies on the ability to kill off the DHCP client
and do some other things with ifconfig.

permit nopass :wheel as root cmd /usr/bin/pkill args dhclient
permit nopass :wheel as root cmd /sbin/ifconfig
permit nopass :wheel as root cmd /sbin/dhclient

In -CURRENT, doas.conf has a "persist" keyword that will only prompt once
per session. This isn't available in OpenBSD 6.0, but should work when 6.1
is released. Here's a fairly minimal rule that would allow wheel group
users to do whatever they want with doas after authenticating once:

permit persist :wheel


On Thu, Dec 15, 2016 at 10:56 AM, jungle Boogie 
wrote:

> Hi All,
>
> Should I be prompted for a password during this scenario?
>
> $ doas date
> doas (jun...@openbsd.my.domain) password:
> Thu Dec 15 08:55:39 PST 2016
> $ ./date.sh
> doas (jun...@openbsd.my.domain) password:
> Thu Dec 15 08:55:46 PST 2016
>
> As you see, only seconds past from both commands and yet, I'm prompted
> for my password again.
>
> --
> ---
> inum: 883510009027723
> sip: jungleboo...@sip2sip.info

Re: doas prompting for password in script

[Ax0n]

I don't know how doas is keeping track of a session. If it's by interactive
tty session only, that could cause problems with non-interactive scripts.
I'll let someone closer to the code answer that question.

On Thu, Dec 15, 2016 at 11:25 AM, jungle Boogie 
wrote:

> On 15 December 2016 at 09:21, Ax0n  wrote:
> > In -CURRENT, doas.conf has a "persist" keyword that will only prompt once
> > per session. This isn't available in OpenBSD 6.0, but should work when
> 6.1
> > is released. Here's a fairly minimal rule that would allow wheel group
> users
> > to do whatever they want with doas after authenticating once:
>
> DOH! I forgot to mention that I'm running a snapshot from this morning.
>
> OpenBSD 6.0-current (GENERIC.MP) #38: Thu Dec 15 08:24:17 MST 2016
> bu...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
>
> by doas.conf:
> permit persist :wheel
> permit persist keepenv jungle as root
>
> With this, should I be re-prompted for the password?
>
>
> --
> ---
> inum: 883510009027723
> sip: jungleboo...@sip2sip.info

Re: Using "Pretty" permalinks with httpd in wordpress

[Ax0n]

This was my hack.
http://www.h-i-r.net/2016/04/pretty-wordpress-permalinks-under.html

tl;dr:
1) ln -s index.php posts
2) null out "security.limit_extensions" in the php_fpm config, restart FPM.
Beware the potential abuses of this.
3) Set up an explicit location clause for "/posts*" that uses the fastcgi
socket for FPM.
4) Configure wordpress permalinks with a custom structure that includes
/posts


On Fri, Jan 6, 2017 at 7:42 AM, Atanas Vladimirov  wrote:

> On 06.01.2017 13:35, Jiri B wrote:
>
>> On Fri, Jan 06, 2017 at 01:32:10PM +0200, Atanas Vladimirov wrote:
>>
>>> Hi,
>>>
>>> I can't figure it out.
>>> Is it possible to use Wordpress with OpenBSD httpd and configure both
>>> for "Pretty" permalinks.
>>> Does anyone have a working setup?
>>> Thanks for your time,
>>> Atanas
>>>
>>
>> Help testing this diff http://marc.info/?l=openbsd-te
>> ch&m=148370177214134&w=2
>>
>> j.
>>
> I know about the diff and I'm testing it right now.
> The problem is that I really don't know what to put in
> httpd.conf.
> I try to "translate" Wordpress .htaccess with no luck:
>
> # BEGIN WordPress
> 
> RewriteEngine On
> RewriteBase /
> RewriteRule ^index\.php$ - [L]
> ^^^ this rule doesn't rewrite index.php
> RewriteCond %{REQUEST_FILENAME} !-f
> RewriteCond %{REQUEST_FILENAME} !-d
> RewriteRule . /index.php [L]
> ^^^ this rule rewrites any single character to /index.php
> if %{REQUEST_FILENAME} is not a real file or directory
> 
> # END WordPress
>
> Do I read/understand the .htaccess file correctly?
> In my httpd.conf:
> .
> # art-katerina.com
> server "art-katerina.com" {
> listen on * tls port 443
> alias www.art-katerina.com
> directory index index.php
> root "/domains/art-katerina.com/"
> hsts
> log {
> access "art-katerina-access.log",
> error "art-katerina-error.log",
> style combined
> }
> location "/.well-known/acme-challenge/*" {
> root "/acme"
> root strip 2
> }
> tls {
> certificate "/etc/ssl/acme/art-katerina.com/fullchain.pem"
> key "/etc/ssl/acme/private/art-katerina.com/privkey.pem"
> }
> location "*.php" {
> fastcgi socket "/run/php-fpm.sock"
> }
> location match "(.)" {
> pass rewrite "/index.php"
> fastcgi socket "/run/php-fpm.sock"
> }
> .

Re: Encryption

[Ax0n]

One thing to note with FDE: power the system down completely whenever the
system is unattended. If someone steals it while it's powered on or
suspended, the disk is completely accessible to the system without a
password. There are a number of plausible attacks even if you are logged
off or have a screen lock.

I don't know that fde isn't supported. I've been using it for years exactly
as outlined in the FAQ. Obviously, no one can help you if you lose your
password.

On Mar 22, 2017 12:19 PM, "Jan Betlach"  wrote:

> Solene, Ken,
>
> thanks a lot for quick responses. Primarily I need to protect the laptop
> against losing/stealing it. Therefore FDE would be ideal, however I've red
> somewhere that FDE is not officially supported on OpenBSD.
> It would probably make sense to combine both - FDE and to have most
> sensitive data additionally encrypted using virtual block device (as I do
> not need to have these permanently mounted).
>
> Jan
>
>
> On Wed, Mar 22, 2017 at 6:11 PM, Ken  wrote:
>
> > To expand on Solène's reponse. Keep in mind if you need to cover both
> > scenarios for whatever your threat-model is... you can do both too.
> >
> > Another valuable result of FDE is that it helps ensure the integrity
> > of your boot drive (presuming your encrypting your boot volume). i.e.
> > prevents attacks like the sysadmin sticky-keys "attack" on windows
> > boxes. So someone can't just boot and mount the partition and modify
> > your shadow file to add a new root user or other backdoor. Good for
> > scenarios where physical access isn't necessarily controlled by the
> > 3Gs (guards, gates, guns).
> >
> > In my experience, setting up FDE with OpenBSD has been very easy with
> > just a couple of calls to bioctl to set it up. Pretty much seamless if
> > you have a quick tutorial on it.
> >
> > Don't lose your passphrases/keys, and have fun!
> >
> > On Wed, Mar 22, 2017 at 9:38 AM, Solène Rapenne  wrote:
> > > Le 2017-03-22 17:28, Jan Betlach a écrit :
> > >>
> > >> Hi misc,
> > >>
> > >> planning to install -current on my Thinkpad T450s (SSD).
> > >>
> > >> I need to have several data directories encrypted, however would not
> > mind
> > >> whole-disk encryption. Which method would be more supported /
> > recommended?
> > >> Whole-disk encryption or creating a container file, loop device and
> then
> > >> virtual device with the encryption layer on it?
> > >>
> > >> Thanks in advance
> > >>
> > >> Jan
> > >
> > >
> > > Hello Jan,
> > >
> > > That would depend on your need, do you want to protect against someone
> > > who would steal your computer, or against some malicious software
> > > running under your system to read your data ?
> > >
> > > In the first case, you should go with FDE (full disk encryption), your
> > > data would be available only after you type the password at boot.
> > >
> > > In the second case, you should use some kind of encrypted volume that
> > > would be available only when you need to. I think that's possible to
> > > create an encrypted ffs volume contained into a file, that you can
> > > mount when you need.
> > >
> > > Regards

Re: Is there something to replace zaurus?

[Ax0n]

Until I really wanted to mess with vmm(4) late last year (thus requiring me
to move to a more portly i5 laptop), my daily driver was a Toshiba NB305,
on which I've run OpenBSD since 2011. It still comes out to play whenever I
need excellent battery life and/or a light carry load-out. Everything from
WiFi to screen brightness, volume control and suspend worked out of the box
with OpenBSD back then, and still does today. I max'd it out to 2GB of RAM.
Gmail in Chromium and/or Firefox is usable. HTML5 videos play fine on
YouTube in Chromium. But I wouldn't call it an enjoyable experience by any
stretch, but OpenBSD runs better on that old thing than Windows 7 starter,
Ubuntu, Arch or Debian ever did.

GeminiPDA (I won't link to it here) has piqued my interest, but if it comes
to fruition the way many crowd-funded hardware projects go, I am not
holding my breath for OpenBSD on it. I have a small fleet of HP Jornadas
(mostly 720s) that run NetBSD/hpcarm well, and the Gemini seems like it
would scratch that itch for something similar in stature with more than 205
MHz and 32MB of RAM.

On Fri, Mar 31, 2017 at 10:20 PM, Nick Holland 
wrote:

> On 03/29/17 05:51, Luke Small wrote:
> > I thought I read that there is an arm7 based mobile device, but I can't
> > find anything about it.
> >
>
> Not quite as tiny, but in more capable in almost every way are the
> netbooks of a few years ago.  In addition to being small and portable,
> they can have real networking (wireless (sometimes with a hw swapout)
> and wired), several USB devices attached, huge (relatively speaking)
> disks installed, lots of RAM, usable keyboards, etc.
>
> With lots of patience (and some swap), can even run modern browsers on
> them.
>
> Nick.

vmm(4) - Virtual Machine owner and (re)starting VMs?

[Ax0n]

First: Great work, everyone. Tons of ground got covered.

vmm seems to not be respecting the "owner" directive until after I shut the
VMs down. It's completely plausible I'm doing something wrong. I haven't
messed with vmm in -CURRENT since mid-January. I'm using 6.1-RELEASE right
now.

On the host end, I have dhcpd listening on vether0  and the most basic of
pf NAT configured. Honestly, I'm okay running these as root. This is just
my personal laptop with some VMs for testing Apache/MySQL apps and new
snapshots. Using doas(8) I can connect to any of the consoles.

Also, is there a way to re-start a defined VM by its vm.conf definition
without restarting vmd, and/or start up a VM that's marked as disabled in
vm.conf?

Log and dmesg follows.

$ id
uid=1000(axon) gid=1000(axon) groups=1000(axon), 0(wheel)
$ vmctl status
   ID   PID VCPUS  MAXMEM  CURMEM TTYOWNER NAME
2  4096 1128M122M   ttyp1 root OBSDSnap64.vm
1 12592 1128M128M   ttyp0 root OBSD61.vm
$ vmctl console 1
cu: open("/dev/ttyp0"): Permission denied
$ cat /etc/vm.conf
# bridge0 for VMs, NAT and dhcpd
switch "local" {
add vether0
up
}

# OpenBSD 6.1
vm "OBSD61.vm" {
owner axon
memory 128M
disk "/home/axon/vmm/obsd61.img"
interface {
switch "local"
lladdr fe:e1:ba:d0:eb:ab
}
}

# OpenBSD amd64 Snapshot
vm "OBSDSnap64.vm" {
owner axon
memory 128M
disk "/home/axon/vmm/obsd-snap64.img"
interface {
switch "local"
lladdr fe:e1:ba:d0:eb:ac
}
}

$ ssh 10.13.37.200
axon@10.13.37.200's password:
Last login: Fri Apr 14 22:11:40 2017 from 10.13.37.1
OpenBSD 6.1 (GENERIC) #19: Sat Apr  1 13:42:46 MDT 2017

Welcome to OpenBSD: The proactively secure Unix-like operating system.

Please use the sendbug(1) utility to report bugs in the system.
Before reporting a bug, please try to reproduce it with the latest
version of the code.  With bug reports, please try to ensure that
enough information to reproduce the problem is enclosed, and if a
known fix for it exists, include that as well.

$ doas halt -p
Connection to 10.13.37.200 closed by remote host.
Connection to 10.13.37.200 closed.
$ vmctl status # after waiting 30 seconds or so for the VM to clean up...
   ID   PID VCPUS  MAXMEM  CURMEM TTYOWNER NAME
2  4096 1128M122M   ttyp1 root OBSDSnap64.vm
- - 1128M   -   - axon OBSD61.vm

## Now I'm the proud owner of a halted vm. :D

$ doas vmctl console 2
Connected to /dev/ttyp1 (speed 9600)


OpenBSD/amd64 (deepthought.labs.h-i-r.net) (tty00)

login:

[EOT]

$ dmesg
OpenBSD 6.1 (GENERIC.MP) #20: Sat Apr  1 13:45:56 MDT 2017
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
RTC BIOS diagnostic error 80
real mem = 8227655680 (7846MB)
avail mem = 7973625856 (7604MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xe9d90 (47 entries)
bios0: vendor Acer version "V1.07" date 11/07/2011
bios0: Acer Aspire 5733Z
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP ASF! HPET APIC MCFG SLIC BOOT ASPT DMAR SSDT SSDT
SSDT
acpi0: wakeup devices AZAL(S3) P0P1(S4) EHC1(S3) USB1(S3) USB2(S3) USB3(S3)
USB4(S3) USB5(S3) USB6(S3) USB7(S3) RP01(S4) PEG5(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i5 CPU M 540 @ 2.53GHz, 2527.84 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX
,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,AES,NXE,RDTSCP,LO
NG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: TSC frequency 2527838640 Hz
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.1.1, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i5 CPU M 540 @ 2.53GHz, 2527.44 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX
,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,AES,NXE,RDTSCP,LO
NG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 1, core 0, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Core(TM) i5 CPU M 540 @ 2.53GHz, 2527.44 MHz
cpu2:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX
,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,AES,NXE,RDTSCP,LO
NG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu2: 256KB

Re: vmm(4) - Virtual Machine owner and (re)starting VMs?

[Ax0n]

To answer my own question about restarting VMs that have stopped or were
disabled in vm.conf:

If you do a vmctl reload as root, it will restart any VMs that are no
longer running but are defined and enabled in /etc/vm.conf. It also looks
as if removing the "disabled" flag from a record in vm.conf and then doing
a reload will start a previously disabled VM.
using "vmctl load ${configfile}" is also handy for creating one-off
configuration clauses for VMs you want to start ad-hoc.

I'm still trying to figure out how VM ownership works.

On Fri, Apr 14, 2017 at 11:00 PM, Ax0n  wrote:

> First: Great work, everyone. Tons of ground got covered.
>
> vmm seems to not be respecting the "owner" directive until after I shut
> the VMs down. It's completely plausible I'm doing something wrong. I
> haven't messed with vmm in -CURRENT since mid-January. I'm using
> 6.1-RELEASE right now.
>
> On the host end, I have dhcpd listening on vether0  and the most basic of
> pf NAT configured. Honestly, I'm okay running these as root. This is just
> my personal laptop with some VMs for testing Apache/MySQL apps and new
> snapshots. Using doas(8) I can connect to any of the consoles.
>
> Also, is there a way to re-start a defined VM by its vm.conf definition
> without restarting vmd, and/or start up a VM that's marked as disabled in
> vm.conf?
>
> Log and dmesg follows.
>
> $ id
> uid=1000(axon) gid=1000(axon) groups=1000(axon), 0(wheel)
> $ vmctl status
>ID   PID VCPUS  MAXMEM  CURMEM TTYOWNER NAME
> 2  4096 1128M122M   ttyp1 root OBSDSnap64.vm
> 1 12592 1128M128M   ttyp0 root OBSD61.vm
> $ vmctl console 1
> cu: open("/dev/ttyp0"): Permission denied
> $ cat /etc/vm.conf
> # bridge0 for VMs, NAT and dhcpd
> switch "local" {
> add vether0
> up
> }
>
> # OpenBSD 6.1
> vm "OBSD61.vm" {
> owner axon
> memory 128M
> disk "/home/axon/vmm/obsd61.img"
> interface {
> switch "local"
> lladdr fe:e1:ba:d0:eb:ab
> }
> }
>
> # OpenBSD amd64 Snapshot
> vm "OBSDSnap64.vm" {
> owner axon
> memory 128M
> disk "/home/axon/vmm/obsd-snap64.img"
> interface {
> switch "local"
> lladdr fe:e1:ba:d0:eb:ac
> }
> }
>
> $ ssh 10.13.37.200
> axon@10.13.37.200's password:
> Last login: Fri Apr 14 22:11:40 2017 from 10.13.37.1
> OpenBSD 6.1 (GENERIC) #19: Sat Apr  1 13:42:46 MDT 2017
>
> Welcome to OpenBSD: The proactively secure Unix-like operating system.
>
> Please use the sendbug(1) utility to report bugs in the system.
> Before reporting a bug, please try to reproduce it with the latest
> version of the code.  With bug reports, please try to ensure that
> enough information to reproduce the problem is enclosed, and if a
> known fix for it exists, include that as well.
>
> $ doas halt -p
> Connection to 10.13.37.200 closed by remote host.
> Connection to 10.13.37.200 closed.
> $ vmctl status # after waiting 30 seconds or so for the VM to clean up...
>ID   PID VCPUS  MAXMEM  CURMEM TTYOWNER NAME
> 2  4096 1128M122M   ttyp1 root OBSDSnap64.vm
> - - 1128M   -   - axon OBSD61.vm
>
> ## Now I'm the proud owner of a halted vm. :D
>
> $ doas vmctl console 2
> Connected to /dev/ttyp1 (speed 9600)
>
>
> OpenBSD/amd64 (deepthought.labs.h-i-r.net) (tty00)
>
> login:
>
> [EOT]
>
> $ dmesg
> OpenBSD 6.1 (GENERIC.MP) #20: Sat Apr  1 13:45:56 MDT 2017
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> RTC BIOS diagnostic error 80
> real mem = 8227655680 (7846MB)
> avail mem = 7973625856 (7604MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xe9d90 (47 entries)
> bios0: vendor Acer version "V1.07" date 11/07/2011
> bios0: Acer Aspire 5733Z
> acpi0 at bios0: rev 2
> acpi0: sleep states S0 S3 S4 S5
> acpi0: tables DSDT FACP ASF! HPET APIC MCFG SLIC BOOT ASPT DMAR SSDT SSDT
> SSDT
> acpi0: wakeup devices AZAL(S3) P0P1(S4) EHC1(S3) USB1(S3) USB2(S3)
> USB3(S3) USB4(S3) USB5(S3) USB6(S3) USB7(S3) RP01(S4) PEG5(S4)
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpihpet0 at acpi0: 14318179 Hz
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Intel(R) Core(TM) i5 CPU M 540 @ 2.53GHz, 2527.84 MHz
> cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,

Re: ordering

[Ax0n]

I guess this is the thread where I mention that most of the OpenBSD FTP
mirrors' login motd banner say you can buy 6.1 on CD. Not really a big
deal, but mirror maintainers might want to adjust it.

On Sat, Apr 15, 2017 at 8:37 PM, Edgar Pettijohn 
wrote:

> On 04/15/17 20:28, Friedrich Locke wrote:
>
>> Hi folks,
>>
>> i would like to order obsd 6.1, butfrom the openbsd store i cannot see it
>> available for ordering.
>> May you help me ?
>>
>> thanks, gustavo.
>>
> 6.0 was the last release that the project made CD's for.

Re: GUI desktop autologin options

[Ax0n]

I'm using slim as the Display Manager on 6.1-RELEASE on my main laptop,
with Lumina for the time being as my DE. I just added the following to the
end of /etc/slim.conf and it does auto-login for me. Frustratingly, "log
out" immediately logs me back in instead of prompting. If you're okay with
that, then give it a go.

auto_login  yes
default_useraxon

Slim obeys the .xsession script for whatever Desktop Environment or Window
Manager you've chosen, or you can adjust the default sessions in slim.conf
as well. Both my .xsession and .xinitrc contain this line that starts up
Lumina.

exec start-lumina-desktop

Cheers

On Tue, Apr 18, 2017 at 10:44 PM, Sha'ul  wrote:

> I'm trying to figure how setup an auto login from boot to some kind of GUI
> desktop interface. What are my options? I'm not interested in Gnome 3, but
> I will use anything else like Lumina, KDE, XFCE, etc. as long as it can
> load straight into desktop environment when I turn on computer. Which
> ones, besides Gnome 3, support autologin?
>
>

Re: GUI desktop autologin options

[Ax0n]

Also, check the man page for the new XenoDM in base. It appears to offer
autologin via Xresources. I haven't gotten myself familiarized with it yet,
but I'd recommend looking at that before installing a third party display
manager if you want to be dropped straight into a user session on boot.

On Tue, Apr 18, 2017 at 11:12 PM, Ax0n  wrote:

> I'm using slim as the Display Manager on 6.1-RELEASE on my main laptop,
> with Lumina for the time being as my DE. I just added the following to the
> end of /etc/slim.conf and it does auto-login for me. Frustratingly, "log
> out" immediately logs me back in instead of prompting. If you're okay with
> that, then give it a go.
>
> auto_login  yes
> default_useraxon
>
> Slim obeys the .xsession script for whatever Desktop Environment or Window
> Manager you've chosen, or you can adjust the default sessions in slim.conf
> as well. Both my .xsession and .xinitrc contain this line that starts up
> Lumina.
>
> exec start-lumina-desktop
>
> Cheers
>
> On Tue, Apr 18, 2017 at 10:44 PM, Sha'ul  wrote:
>
>> I'm trying to figure how setup an auto login from boot to some kind of GUI
>> desktop interface. What are my options? I'm not interested in Gnome 3, but
>> I will use anything else like Lumina, KDE, XFCE, etc. as long as it can
>> load straight into desktop environment when I turn on computer. Which
>> ones, besides Gnome 3, support autologin?
>>
>>
>

uhci0: host controller process error / host controller halted

[Ax0n]

Preface: I'd like to know what I can do to get some more detail about this
before firing off a sendbug. I can't reliably replicate it, but I can
guarantee it will happen to me repeatedly with just a bit of normal
computing use.

On my old 2006-era MacBook (MacBook2,1), I decided I'd finally upgrade from
Snow Leopard to something a bit more modern. OpenBSD 5.7 is working great
for the most part, except I occasionally lose the USB port. Plugging into
the other port (there are only two on this model), my peripherals come
back.

Initially, I thought that this happened only under high CPU load.  I'm
running XFCE4 and in all cases, I've had Chromium up and running. The first
time, I was also extracting ports.tar.gz, sys.tar.gz and src.tar.gz at the
same time, with a 5.xx load average.

The second time, I had just logged into my GMail account and opened a tab
loading Twitter.  This most recent time a few minutes ago, not much was
going on. Chrome was open, but I was SSH'd into something else and typing
when it happened. My load average was 0.12 or so when I caught it. It seems
to happen when I'm actively typing and/or using the mouse. If I let it sit
overnight, it won't do it on its own.

I'm including a full dmesg and process list. You can see where my KVM and
USB HIDs came back at the end.

OpenBSD 5.7 (GENERIC.MP) #881: Sun Mar  8 11:04:17 MDT 2015
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 2098167808 (2000MB)
avail mem = 2038456320 (1944MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe (37 entries)
bios0: vendor Apple Inc. version "MB21.88Z.00A5.B07.0706270922" date
06/27/07
bios0: Apple Inc. MacBook2,1
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP HPET APIC MCFG ASF! SBST ECDT SSDT SSDT SSDT
acpi0: wakeup devices ADP1(S3) LID0(S3) PXS1(S4) PXS2(S4) USB1(S3) USB2(S3)
USB3(S3) USB4(S3) USB7(S3) EC__(S3)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz, 1995.33 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,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF
cpu0: 4MB 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 166MHz
cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz, 1995.01 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,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF
cpu1: 4MB 64b/line 16-way L2 cache
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 1
acpimcfg0 at acpi0 addr 0xf000, bus 0-255
acpiec0 at acpi0
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (RP01)
acpiprt2 at acpi0: bus 2 (RP02)
acpiprt3 at acpi0: bus 3 (PCIB)
acpicpu0 at acpi0: C3, C2, C1, PSS
acpicpu1 at acpi0: C3, C2, C1, PSS
acpiac0 at acpi0: AC unit online
acpibtn0 at acpi0: LID0
acpibtn1 at acpi0: PWRB
acpibtn2 at acpi0: SLPB
acpibat0 at acpi0: BAT0 not present
acpivideo0 at acpi0: GFX0
cpu0: Enhanced SpeedStep 1995 MHz: speeds: 2000, 1833, 1667, 1500, 1333,
1000 MHz
memory map conflict 0x7ef0/0x10
memory map conflict 0x7f00/0x100
memory map conflict 0xf00f8000/0x1000
memory map conflict 0xfed1c000/0x4000
memory map conflict 0xfffb/0x3
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel 82945GM Host" rev 0x03
vga1 at pci0 dev 2 function 0 "Intel 82945GM Video" rev 0x03
intagp0 at vga1
agp0 at intagp0: aperture at 0x8000, size 0x1000
inteldrm0 at vga1
drm0 at inteldrm0
inteldrm0: 1280x800
wsdisplay0 at vga1 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
"Intel 82945GM Video" rev 0x03 at pci0 dev 2 function 1 not configured
vendor "Intel", unknown product 0x27a3 (class DASP subclass Time and
Frequency, rev 0x03) at pci0 dev 7 function 0 not configured
azalia0 at pci0 dev 27 function 0 "Intel 82801GB HD Audio" rev 0x02: msi
azalia0: codecs: Sigmatel STAC9220/1
audio0 at azalia0
ppb0 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x02: msi
pci1 at ppb0 bus 1
mskc0 at pci1 dev 0 function 0 "Marvell Yukon 88E8053" rev 0x22, Yukon-2 EC
rev. A3 (0x2): apic 1 int 16
msk0 at mskc0 port A: address 00:17:f2:f2:0e:62
eephy0 at msk0 phy 0: 88E Gigabit PHY, rev. 2
ppb1 at pci0 dev 28 function 1 "Intel 82801GB PCIE" rev 0x02: msi
pci2 at ppb1 bus 2
athn0 at pci2 dev 0 function 0 "Atheros AR5418" rev 0x01: apic 1 int 17
athn0: MAC AR5418 rev 2, RF AR5133 (

Re: Acer Aspire V3-112 was Re: which netbook not to buy?

[Ax0n]

FWIW, about 5 years ago, my wife bought me a Toshiba NB305 that came with
Windows 7 Starter, which I tried to use. I'm okay with Windows when I need
to use it, but Starter edition might as well be a Windows kernel with IE
and almost no customization available. I do need Windows to program my ham
radios, and at the time, I needed a proprietary Windows-only VPN client for
work.

Worried about hardware support, I tossed Ubuntu on it. It was usable, but
none of the hot keys (volume, brightness, wifi toggle etc) worked, neither
did the webcam. It was also more sluggish than Win7 Starter. After a month
or so of that, I used the factory restore image, resized the Windows
partition, then followed the excellent instructions for multi-booting
Windows and OpenBSD 4.8 through the Microsoft bootloader and bcdedit.

I've used OpenBSD as my primary OS on that machine ever since and despite
its age, it still feels light and nimble with daily use. I have a bunch of
other Toshiba laptops (most newer), and it feels like I got *REALLY* lucky
with this NB305, because on all the other Toshibas, OpenBSD has something
that doesn't quite work right, often picky azalia (sound) or wifi. This is
why you do the research before you spend the cash instead of just assuming
a brand itself is golden.

At any rate, I am exceedingly thankful that several devs and users have
come forward with suggestions on what *TO* buy and what else works well
with OpenBSD. I am absolutely listening. This little Toshiba isn't going to
last forever, and I prefer ultrabook/netbook form-factor because I'm
frequently on-the-go, and don't require tons of computrons for the SSH,
email and basic web browsing I do on a daily basis.



On Wed, Jul 15, 2015 at 11:53 AM, Peter J. Philipp  wrote:

> On 07/15/15 18:28, li...@wrant.com wrote:
> >>> I'm considering buying a new netbook...
> >
> > So you asked what not to buy. You got some good and solid advice from
> > knowledgeable people here regarding what works great including
> > OpenBSD coverage.
>
> I'm really happy with my old netbook though.  Guess what everything
> worked on it except wifi.  So I put trust into the same brand, and it
> has bitten me.  X won't work, the intel drm driver doesn't work.
>
> I hacked a little in the kernel to see if a simple fix would fix it, it
> didn't.  However the bright news is that I bought this netbook for a
> purpose of a personal project.  Those features that I needed work.
>
> So I'm somewhat disappointed but it's not the end of the world.
>
> BTW by the time someone said "don't buy brand" I already bought it.  It
> came shipped to me here this morning.
>
> I did not chose to get a Lenovo because I felt they were pricy over the
> 350 euros that I paid.  Maybe my own fault then, but I wanted to be
> adventurous.
>
> Cheers,
> -peter

Re: httpd stops accepting connections after a few hours on current

[Ax0n]

Possibly related, I did have an http-only httpd exhibit similar behavior
after running for about 5 days.  httpd processes were running, but port 80
was wholly unresponsive. I attempted to find a way to grab a core from the
processes, but I couldn't figure it out. I had to get the sites back up and
running, so just did a restart on Sunday.

If there's anything I can do in preparation for it to happen again (debug,
etc) I would be happy to help in any way I can. I've been lurking on this
thread since it popped up (which was before my own httpd had problems) but
it doesn't seem like the TLS patch that you are talking about will have any
impact for my setup.

If it helps, included is my (ugly but functioning) httpd.conf:

ext_if="egress"
types { include "/usr/share/misc/mime.types" }
server "focushacks.com" {
listen on $ext_if port 80
alias "www.focushacks.com"
directory {index "index.html" }
directory {index "index.php" }
log access focushacks.com-access.log
log error focushacks.com-error.log
location "/.ht*"   { block }
location "/.git*"  { block }
location "/.svn*"  { block }
location "/*.php*" {
root { "/docs/www.focushacks.com" }
fastcgi socket "/run/php-fpm.sock"
}
location "/list*" {
root { "/docs/www.focushacks.com" }
fastcgi socket "/run/php-fpm.sock"
}
location "/news*" {
root { "/docs/www.focushacks.com" }
fastcgi socket "/run/php-fpm.sock"
}
location "/search*" {
root { "/docs/www.focushacks.com" }
fastcgi socket "/run/php-fpm.sock"
}
location "/mod*" {
root { "/docs/www.focushacks.com" }
fastcgi socket "/run/php-fpm.sock"
}
location "/*" {
root { "/docs/www.focushacks.com" }
}
}
server "kcmesh.h-i-r.net" {
listen on $ext_if port 80
alias "www.km3sh.com"
alias "km3sh.com"
directory {index "index.php" }
location "/*.php*" {
root { "/docs/kcmesh.h-i-r.net" }
fastcgi socket "/run/php-fpm.sock"
}
location "/*" {
root { "/docs/kcmesh.h-i-r.net" }
}
}
server "things.h-i-r.net" {
listen on $ext_if port 80
directory {index "index.php" }
location "/*.php*" {
root { "/docs/things.h-i-r.net" }
fastcgi socket "/run/php-fpm.sock"
}
location "/*" {
root { "/docs/things.h-i-r.net" }
}
}
server "h-i-r.net" {
listen on $ext_if port 80
directory {index "index.php" }
location "/*.php*" {
root { "/docs/h-i-r.net" }
fastcgi socket "/run/php-fpm.sock"
}
location "/*" {
root { "/docs/h-i-r.net" }
}
}


On Wed, Jul 15, 2015 at 9:10 AM, Jack Burton  wrote:

> On Wed, 2015-07-15 at 12:56 +, Mike Burns wrote:
> > On 2015-07-15 21.49.11 +0930, Jack Burton wrote:
> > > Sorry, didn't realise I couldn't post a patch to the misc@ (I've never
> > > needed to before).
> > >
> > > Please excuse my ignorance, but what is the accepted way to contribute
> a
> > > patch?
> >
> > Post it to tech@ .
>
> Done. See post to tech@ titled "httpd: patch to close TLS sockets that
> fail before TLS handshake".

Dell Latitude D610 screen blanking issue

[Ax0n]

I acquired a Dell Latitude D610 (including docking station, expansion-bay
HDD and a bunch of other accessories) from a friend. I've been running
OpenBSD on it since around the time 5.6 came out. I'm running 5.7-RELEASE
with all patches applied.

The screen (perhaps only the backlight) won't come back from a lid closure
screen blank. Waking from suspend or hibernate will bring it back. Using
xset s activate (which should blank the screen) followed by a key press to
wake the display will also bring it back. I have disabled
machdep.lidsuspend because I frequently run this system in the docking
station with the lid closed and generally don't want my laptops suspending
when closed.

It's a minor annoyance, but I'm wondering if there's something I could do
to fix the screen blanking issue. I'm not having much luck finding anything
useful in the wscons/wsdisplay man pages. Ideas?

Also, bwi(4) doesn't work on this system. There was a patch posted back in
December against 5.6, but I'm just running a tiny urtwn(4) that seems to be
working great.

dmesg; sysctl hw.sensors follows.


OpenBSD 5.7 (GENERIC) #0: Sun Jul 19 23:33:46 CDT 2015
r...@capture.labs.h-i-r.net:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Pentium(R) M processor 1.73GHz ("GenuineIntel" 686-class)
1.73 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,PBE,NXE,EST,TM2,PERF
real mem  = 1064652800 (1015MB)
avail mem = 1034891264 (986MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: date 10/02/05, BIOS32 rev. 0 @ 0xffe90, SMBIOS rev. 2.3
@ 0xf7860 (60 entries)
bios0: vendor Dell Inc. version "A06" date 10/02/2005
bios0: Dell Inc. Latitude D610
acpi0 at bios0: rev 0
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC ASF! MCFG SSDT SSDT SSDT
acpi0: wakeup devices LID_(S3) PBTN(S4) PCI0(S5) USB0(S0) USB1(S0) USB2(S0)
USB4(S0) USB3(S0) MODM(S3) PCIE(S4) NIC_(S5)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 133MHz
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 1
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (AGP_)
acpiprt2 at acpi0: bus 3 (PCIE)
acpicpu0 at acpi0: C3, C3, C2, C1, PSS
acpitz0 at acpi0: critical temperature is 101 degC
acpiac0 at acpi0: AC unit offline
acpibat0 at acpi0: BAT0 model "DELL MT2648" serial 2 type LION oem "Samsung
SDI"
acpibat1 at acpi0: BAT1 not present
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: PBTN
acpibtn2 at acpi0: SBTN
acpidock0 at acpi0: GDCK not docked (0)
acpivideo0 at acpi0: VID_
acpivideo1 at acpi0: VID_
acpivideo2 at acpi0: VID2
bios0: ROM list: 0xc/0xf800! 0xcf800/0x800
cpu0: Enhanced SpeedStep 1730 MHz: speeds: 1733, 1333, 1067, 800 MHz
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82915GM Host" rev 0x03
vga1 at pci0 dev 2 function 0 "Intel 82915GM Video" rev 0x03
intagp0 at vga1
agp0 at intagp0: aperture at 0xc000, size 0x1000
inteldrm0 at vga1
drm0 at inteldrm0
inteldrm0: 1024x768
wsdisplay0 at vga1 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
"Intel 82915GM Video" rev 0x03 at pci0 dev 2 function 1 not configured
ppb0 at pci0 dev 28 function 0 "Intel 82801FB PCIE" rev 0x03: apic 1 int 16
pci1 at ppb0 bus 2
bge0 at pci1 dev 0 function 0 "Broadcom BCM5751" rev 0x01, BCM5750 A1
(0x4001): apic 1 int 16, address 00:14:22:ca:e3:f1
brgphy0 at bge0 phy 1: BCM5750 10/100/1000baseT PHY, rev. 0
uhci0 at pci0 dev 29 function 0 "Intel 82801FB USB" rev 0x03: apic 1 int 16
uhci1 at pci0 dev 29 function 1 "Intel 82801FB USB" rev 0x03: apic 1 int 17
uhci2 at pci0 dev 29 function 2 "Intel 82801FB USB" rev 0x03: apic 1 int 18
uhci3 at pci0 dev 29 function 3 "Intel 82801FB USB" rev 0x03: apic 1 int 19
ehci0 at pci0 dev 29 function 7 "Intel 82801FB USB" rev 0x03: apic 1 int 16
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ppb1 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0xd3
pci2 at ppb1 bus 3
cbb0 at pci2 dev 1 function 0 "TI PCI6515 CardBus" rev 0x00: apic 1 int 19
"TI PCI6515 CardBus" rev 0x00 at pci2 dev 1 function 5 not configured
bwi0 at pci2 dev 3 function 0 "Broadcom BCM4318" rev 0x02: apic 1 int 17,
address 00:14:a4:63:ce:94
cardslot0 at cbb0 slot 0 flags 0
cardbus0 at cardslot0: bus 4 device 0 cacheline 0x10, lattimer 0x20
pcmcia0 at cardslot0
auich0 at pci0 dev 30 function 2 "Intel 82801FB AC97" rev 0x03: apic 1 int
16, ICH6 AC97
ac97: codec id 0x83847650 (SigmaTel STAC9750/51)
ac97: codec features headphone, 20 bit DAC, 20 bit ADC, SigmaTel 3D
audio0 at auich0
"Intel 82801FB Modem" rev 0x03 at pci0 dev 30 function 3 not configured
ichpcib0 at pci0 dev 3

Re: Abort Trap question

[Ax0n]

For what it's worth, bricking my main workstation in this way a few times
over the past 20 years yes the only reason I thought about it. It also got
me into a (good) habit of examining the paths and contents of archive files
every single time before I extract them.

On Nov 16, 2017 06:14, "Daniel Boyd"  wrote:

> Haha crap.  I think this is what happened.   I haven’t bothered
> downloading src.tar.gz in awhile bc of syspatch, but since this is a
> PowerPC machine, i wanted to be ready for the first errata.  This is what I
> get for doing things from memory instead of reading the FAQ.
>
> Right.  Let’s pretend that this didn’t happen, shall we?
>
> Sent from my iPhone
>
> > On Nov 15, 2017, at 8:54 PM, Ax0n  wrote:
> >
> > A quick thought... are you extracting src.tar.gz into /usr (like you to
> > with ports.tar.gz)? On a few occasions, I've done this (instead of making
> > sure I'm in /usr/src first as I should) and had system binaries get
> > clobbered. When I've accidentally done this in the past, I do get a bunch
> > of abort trap errors and a predictably un-bootable system.  Example: This
> > block of stuff from src.tar.gz, if extracted whilst in /usr, would
> > overwrite /usr/bin/cat with a directory full of the source code for
> cat(1)
> > and so on and so forth.
> >
> > drwxrwxr-x  2 axon axon 0 Oct  9 22:41 bin
> > drwxrwxr-x  2 axon axon 0 Oct  9 22:41 bin/CVS
> > -rw-rw-r--  1 axon axon 5 Oct  9 22:38 bin/CVS/Root
> > -rw-rw-r--  1 axon axon 8 Oct  9 22:38 bin/CVS/Repository
> > -rw-rw-r--  1 axon axon   439 Oct  9 22:41 bin/CVS/Entries
> > -rw-rw-r--  1 axon axon18 Oct  9 22:41 bin/CVS/Tag
> > -rw-rw-r--  1 axon axon   241 Apr 25  2016 bin/Makefile
> > -rw-rw-r--  1 axon axon   145 Jul 11  2014 bin/Makefile.inc
> > drwxrwxr-x  2 axon axon 0 Oct  9 22:38 bin/cat
> > drwxrwxr-x  2 axon axon 0 Oct  9 22:41 bin/cat/CVS
> > -rw-rw-r--  1 axon axon 5 Oct  9 22:38 bin/cat/CVS/Root
> > -rw-rw-r--  1 axon axon12 Oct  9 22:38
> > bin/cat/CVS/Repository
> > -rw-rw-r--  1 axon axon   172 Oct  9 22:41
> bin/cat/CVS/Entries
> > -rw-rw-r--  1 axon axon18 Oct  9 22:41 bin/cat/CVS/Tag
> > -rw-rw-r--  1 axon axon93 Feb 18  2017 bin/cat/Makefile
> > -rw-rw-r--  1 axon axon  4848 Jul  9  2016 bin/cat/cat.1
> > -rw-rw-r--  1 axon axon  5567 Oct 19  2016 bin/cat/cat.c
> >
> >
> >
> > On Wed, Nov 15, 2017 at 5:24 PM, patrick keshishian 
> > wrote:
> >
> >>> On 11/15/17, Philip Guenther  wrote:
> >>> On Wed, Nov 15, 2017 at 11:08 AM, Mike Coddington 
> >>> wrote:
> >>>
> >>>>> On Wed, Nov 15, 2017 at 10:01:09AM -0600, Daniel Boyd wrote:
> >>>>> I've installed OpenBSD/macppc twice on my G4 Cube now and it seems to
> >>>>> be working fine until I go to untar src.tar.gz at which point it
> >> throws
> >>>>> some abort trap errors and crashes.  If I reboot, I get a bunch of
> >>>>> abort traps during the boot process followed by several:
> >>>>>
> >>>>> init: can't exec getty '/usr/libexec/getty' for pot /dev/ttyC3: ...
> >>>>>
> >>>>> What do you guys think this is...?  Hard drive failure...?
> >>>>
> >>>> Out of curiosity, does the same thing happen if you extract the tar
> with
> >>>> the pax(1) program? That'll at least let you know if it's tar causing
> >>>> the problem or not.
> >>>>
> >>>
> >>> tar _is_ pax:
> >>> : corwin; ls -li /bin/tar /bin/pax
> >>> 52015 -r-xr-xr-x  3 root  bin  433472 Nov  1 11:15 /bin/pax
> >>> 52015 -r-xr-xr-x  3 root  bin  433472 Nov  1 11:15 /bin/tar
> >>> : corwin;
> >>>
> >>> Fundamentally, unless a userspace process is poking at devices or
> >> similar,
> >>> it should be unable to panic the kernel.  An abort trap in the kernel
> is
> >>> either a kernel bug or a hardware bug.  IIRC there's some pmap bug on
> >>> macppc that no one has managed to track down which causes crashes on
> some
> >>> machines, but not others.  I've never hit it on the Macbook I use for
> >>> builds, but the ports build boxes, whatever model they are, seem to hit
> >> it
> >>> periodically...
> >>
> >> I read it as the tar process is the one aborting. which, if true,
> >> sounds like user-land and kernel are out-of-sync.
> >>
> >> Unfortunately, specific info is missing from the problem report.
> >>
> >> --patrick
> >>
> >>
>
>

Re: Image viewer alternative to eog

[Ax0n]

I use xloadimage from ports. Grok the man page. Several useful CLI flags.

On Nov 25, 2017 3:06 PM, "x9p"  wrote:

> Hi,
>
> Is there a good/safe and light image viewer? Was used to eog, but it has
> too many "vfprintf %s NULL" in messages. gimp is too big and good for play
> with images, In need of smth fast.
>
> cheers.
>
> x9p
>
>

Re: Flatbed scanner that works well with OpenBSD?

[Ax0n]

Slightly related, I have a CanoScan LiDE 100 that used to work great with
OpenBSD, using either ScanImage or simple-scan. It's detected, but sometime
around OpenBSD-5.6 it stopped working. I use it infrequently enough, and I
have enough computers that I usually just give up and have my wife use her
Windows laptop to scan for me. I have a slightly vested interest in having
my only scanner work with my main daily desktop/laptop OS.

I'll try installing some old versions of OpenBSD and see if I can find
where it broke, and post dmesg's of the before/after mess, if anyone thinks
that would help.

On Fri, Jan 19, 2018 at 11:38 AM, Anthony J. Bentley 
wrote:

> Base Pr1me writes:
> > Did you give your userland user/group permissions to use the uhub/ugen
> > device?
>
> Of course; without that I wasn't able to detect the scanner in the first
> place.
>
> > On Fri, Jan 19, 2018 at 9:59 AM, Anthony J. Bentley 
> > wrote:
> >
> > > Bryan Linton writes:
> > > > Hello misc@
> > > >
> > > > I'm currently looking to purchase a scanner that works well with
> OpenBSD.
> > > >
> > > > I'm aware of the list provided at:
> > > >
> > > >   http://www.sane-project.org/sane-mfgs.html
> > > >
> > > > but I recently purchased (and returned) a scanner that was listed as
> > > being
> > > > fully supported on that list because no matter what I did, I couldn't
> > > > get it to work right with xsane or scanimage.  Though I purchased it
> > > used,
> > > > so it's possible it may have simply been broken from the get-go.
> > > >
> > > > Does anyone happen to know of a scanner that is *known* to work well
> > > > with OpenBSD?
> > >
> > > Well, I just bought a CanoScan 9000F MkII specifically because it was
> > > marked as fully supported on that list, and I can say it does NOT work
> > > on OpenBSD; scanimage -L detects it just fine but attempting to scan
> > > gives an I/O error. As a workaround I plugged it into a Linux laptop,
> > > started saned, and scan seamlessly from OpenBSD with scanimage's
> network
> > > support, until I find the time to make a proper bug report.
> > >
> > > In the past I used a CanoScan LiDE 20 quite regularly from OpenBSD, but
> > > that was several years ago.
> > >
> > >
>
>

Re: For a FFS on an SSD, which of "-o" nil, "sync" &/ "softdep" is more data-safe and fast?

[Ax0n]

I use ls -lu and find -atime quite frequently. I've also been using OpenBSD
as a desktop (with all the insane disk activity of a browser cache, temp
files, git, etc) while doing absolutely nothing special using SATA SSD
drives. I'm running Softraid crypto on one, running without softraid on the
other. No snazzy mount options outside the defaults. It's been as reliable
as any spinning rust I've used. You're keeping good backups regardless,
right? Because that protects you from many more likely failure modes than
wear-level-exhaustion on SSD.

On Sat, Feb 10, 2018 at 10:38 AM,  wrote:

> > From tom.sm...@wirelessconnect.eu Sat Feb 10 11:28:46 2018
> > From: Tom Smyth 
> > Date: Sat, 10 Feb 2018 09:10:30 +
> > Subject: Re: For a FFS on an SSD, which of "-o" nil, "sync" &/ "softdep"
> is
> >  more data-safe and fast?
> > To: mar...@martinbrandenburg.com
> >
> > Hi Martin... can you give a specific case where you have experienced
> > negative impacts from thevmount options i suggested...
> > It would be good to know...
>
> Well I don't run noatime, so I can't give specific examples.
>
> The point I was making is that noatime is a tradeoff.  You give up
> adherence to POSIX and historical Unix behavior in exchange for
> performance and less disk wear.
>
> Now I will admit that programs that rely on atime updates are few and
> far between.  It was always a bit niche.  Nowadays, most software is
> written on Linux, and most Linux systems use relatime.
>
> It might be an acceptable tradeoff.  To use the examples from the
> manpage, if you know you're not going run any programs that need it and
> that you'll never leave your laptop up for seven days or if you know
> your news server doesn't need it, go ahead and disable it.
>
> Just don't forget to consider it as a potential problem if you run into
> trouble.
>
> Here are some lines from /etc/daily.  Without atime updates, it could
> delete files.  (Some of these might get more frequent mtime or ctime
> updates which would bump the atime under noatime.)
>
> The second set might be uncommented on a big multiuser system to clear
> out /tmp since users don't.  They might be a little irritated when the
> file they've been reading for the last day gets deleted.
>
> next_part "Removing scratch and junk files:"
> if [ -d /tmp -a ! -L /tmp ]; then
> cd /tmp && {
> find -x . \
> \( -path './ssh-*' -o -path ./.X11-unix -o -path ./.ICE-unix \
> -o -path './tmux-*' \) \
> -prune -o -type f -atime +7 -execdir rm -f -- {} \; 2>/dev/null
> find -x . -type d -mtime +1 ! -path ./vi.recover ! -path
> ./.X11-unix \
> ! -path ./.ICE-unix ! -name . \
> -execdir rmdir -- {} \; >/dev/null 2>&1; }
> fi
>
> # Additional junk directory cleanup would go like this:
> #if [ -d /scratch -a ! -L /scratch ]; then
> #   cd /scratch && {
> #   find . ! -name . -atime +1 -execdir rm -f -- {} \;
> #   find . ! -name . -type d -mtime +1 -execdir rmdir -- {} \; \
> #   >/dev/null 2>&1; }
> #fi
>
> Martin
>
>

iwi(4) fatal firmware error

[Ax0n]

I have a Motorola ML900 which seems to be running OpenBSD with X and
WindowMaker just fine. Every few hours it gets a group of errors within the
span of a few seconds (about 1 second between them in /var/log/messages)

Apr  4 04:30:01 luggy /bsd: iwi0: fatal firmware error
Apr  4 05:17:37 luggy /bsd: iwi0: fatal firmware error
Apr  4 05:17:39 luggy /bsd: iwi0: unknown authentication state 1
Apr  4 05:17:40 luggy /bsd: iwi0: reused group key update received from
60:38:e0:89:9b:dc
Apr  4 06:51:05 luggy /bsd: iwi0: fatal firmware error
Apr  4 06:51:06 luggy /bsd: iwi0: unknown authentication state 1
Apr  4 06:51:07 luggy /bsd: iwi0: reused group key update received from
60:38:e0:89:9b:dc
Apr  4 10:11:48 luggy /bsd: iwi0: fatal firmware error
Apr  4 10:11:51 luggy /bsd: iwi0: unknown authentication state 1
Apr  4 10:11:52 luggy /bsd: iwi0: reused group key update received from
60:38:e0:89:9b:dc

I was seeing this same behavior with 6.2-STABLE, which I just installed a
few weeks ago.

Full dmesg (before any of the above errors) is below.

OpenBSD 6.3 (GENERIC) #490: Sat Mar 24 14:31:33 MDT 2018
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Mobile Intel(R) Pentium(R) 4 - M CPU 1.70GHz ("GenuineIntel"
686-class) 1.70 GHz
cpu0:
FPU,V86,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,CNXT-ID,xTPR,PERF
real mem  = 1073168384 (1023MB)
avail mem = 1039679488 (991MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: date 02/23/01, BIOS32 rev. 0 @ 0xe9b30, SMBIOS rev. 2.3
@ 0xecc1a (38 entries)
bios0: vendor Insyde Software version "Version R0.16" date 02/23/2001
bios0: MOTOROLA ML900
acpi0 at bios0: rev 0
acpi0: APIC checksum error
acpi0: sleep states S0 S1 S3 S4 S5
acpi0: tables DSDT FACP APIC BOOT
acpi0: wakeup devices SLPB(S3) LAN0(S3) USB3(S3) USB4(S3) USB5(S3) COM1(S4)
COM4(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
, remapped to apid 1
acpiprt0 at acpi0: bus 1 (PCI1)
acpiprt1 at acpi0: bus 2 (PCI2)
acpiprt2 at acpi0: bus 0 (PCI0)
acpiec0 at acpi0
acpicpu0 at acpi0: C1(@1 halt!), FVS, 1700, 1200 MHz
acpitz0 at acpi0: critical temperature is 100 degC
acpibat0 at acpi0: BAT0 not present
acpiac0 at acpi0: AC unit online
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
acpivideo0 at acpi0: VID_
bios0: ROM list: 0xc/0xe000 0xe4000/0x1800 0xe6000/0x1000!
0xeb000/0x5000!
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82845 Host" rev 0x04
intelagp0 at pchb0
agp0 at intelagp0: aperture at 0xa000, size 0x400
ppb0 at pci0 dev 1 function 0 "Intel 82845 AGP" rev 0x04
pci1 at ppb0 bus 1
radeondrm0 at pci1 dev 0 function 0 "ATI Radeon Mobility M9" rev 0x02
drm0 at radeondrm0
radeondrm0: apic 1 int 16
ppb1 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0x42
pci2 at ppb1 bus 2
bktr0 at pci2 dev 3 function 0 "Brooktree BT878" rev 0x11: apic 1 int 23
bktr0: Warning - card vendor 0x (model 0x) unknown.
bktr0: Pinnacle/Miro TV,  tuner.
"Brooktree BT878 Audio" rev 0x11 at pci2 dev 3 function 1 not configured
uhci0 at pci2 dev 5 function 0 "VIA VT83C572 USB" rev 0x50: apic 1 int 16
uhci1 at pci2 dev 5 function 1 "VIA VT83C572 USB" rev 0x50: apic 1 int 17
ehci0 at pci2 dev 5 function 2 "VIA VT6202 USB" rev 0x51: apic 1 int 18
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 configuration 1 interface 0 "VIA EHCI root hub" rev 2.00/1.00
addr 1
iwi0 at pci2 dev 6 function 0 "Intel PRO/Wireless 2200BG" rev 0x05: apic 1
int 19, address 00:15:00:0d:b5:d6
cbb0 at pci2 dev 7 function 0 "TI PCI4451 CardBus" rev 0x00: apic 1 int 16,
CardBus support disabled
cbb1 at pci2 dev 7 function 1 "TI PCI4451 CardBus" rev 0x00: apic 1 int 16,
CardBus support disabled
"TI PCI4451 FireWire" rev 0x00 at pci2 dev 7 function 2 not configured
fxp0 at pci2 dev 8 function 0 "Intel PRO/100 VE" rev 0x42, i82562: apic 1
int 20, address 00:40:d0:6e:75:a0
inphy0 at fxp0 phy 1: i82562ET 10/100 PHY, rev. 0
puc0 at pci2 dev 9 function 0 "Oxford OX16PCI952" rev 0x00: ports: 2 com
com4 at puc0 port 0 apic 1 int 20: st16650, 32 byte fifo
com4: probed fifo depth: 16 bytes
com5 at puc0 port 1 apic 1 int 20: st16650, 32 byte fifo
com5: probed fifo depth: 16 bytes
usb1 at uhci0: USB revision 1.0
uhub1 at usb1 configuration 1 interface 0 "VIA UHCI root hub" rev 1.00/1.00
addr 1
usb2 at uhci1: USB revision 1.0
uhub2 at usb2 configuration 1 interface 0 "VIA UHCI root hub" rev 1.00/1.00
addr 1
cardslot0 at cbb0 slot 0 flags 0
pcmcia0 at cardslot0
cardslot1 at cbb1 slot 1 flags 0
pcmcia1 at cardslot1
ichpcib0 at pci0 dev 31 function 0 "Intel 82801CAM LPC" rev 0x02
pciide0 at pci0 dev 31 function 1 "Intel 82801CAM IDE" rev 0x02: DMA,
channel 0 confi

Re: iwi(4) fatal firmware error

[Ax0n]

On Thu, Apr 5, 2018 at 3:37 AM, Stefan Sperling  wrote:
>
> Is this a purely cosmetic issue or does it actually prevent your
> wifi connection from working?
>
> These looks like potentially harmless errors which happen during
> association.
> Does the driver recover from these errors automatically? It should be able
> to.
>
> As to why the firmware reports such errors: We have no idea. It's a black
> box.
>

As far as I can tell, it recovers. Lately, it's been doing it at odd hours
when I'm
not actually using it, but I've never come back to it being disconnected or
anything like that. I had it next to me streaming music with Pianobar for a
few hours yesterday without any hiccups. I'll just ignore these. Thanks,
stsp!

How to build with VMM_DEBUG

[Ax0n]

I'm trying to hunt down a recent breakage with my VMM virtual machines
refusing to start, and I'm getting errors like this:

vcpu_run_loop: vm 5 / vcpu 0 run ioctl failed: Invalid argument

It looks like previous requests for help with this error have resulted in
being asked to build with the VMM_DEBUG macro, but I don't know how to do
that. I do not see VMM_DEBUG in the GENERIC config, and just a few ifdefs
in the code.

I'd like to gather more info to provide a more complete bug report. Ideas?

--ax0n

Re: How to build with VMM_DEBUG

[Ax0n]

On Sat, Jun 23, 2018 at 5:56 AM, Christian Barthel  wrote:

> I am having the same problem after installing "010_intelfpu" on OpenBSD
> 6.3 stable.  If you revert back, does it work for you again?
>

The only vmm(4) capable machine I have is running -CURRENT, so no reverting
syspatches.


> I think you have to uncomment the following line in vmm.c (for amd64,
> this is /usr/src/sys/arch/amd64/amd64/vmm.c):
>
> /* #define VMM_DEBUG */
>
> Then, recompile as usually (release(8)).
>
>
Thanks! I'll give that a shot if the patch posted up-thread by stsp@
doesn't fix it.

Re: How to build with VMM_DEBUG

[Ax0n]

On Sat, Jun 23, 2018 at 6:10 AM, Stefan Sperling  wrote:

> See https://marc.info/?l=openbsd-bugs&m=152960299009667&w=2 for
> a patch you could test.
> (raw patch: https://marc.info/?l=openbsd-bugs&m=152960299009667&q=raw)
>

FWIW, that patch didn't apply cleanly to a fresh pull of the tree from
GitHub. I know it's not OFFICIALLY -CURRENT for realsies but it's what I
have been using on this laptop for months. It sounds like it was probably
patched against -STABLE? I didn't read the entire thread on bugs@. I have
tried with 3 daily snapshots in a row and I'm having the same problem. I
haven't actually fired up vmm in a few weeks, so I'm not sure exactly when
it quit working. I'm re-building with VMM_DEBUG first.

Mike, I'll send all relevant info (dmesg, vmd -dvvv, vm.conf) to bugs@ once
I have it, unless this sounds like an ongoing thing you probably have on
your radar already. I'm not in a huge rush, so I can wait a bit if you
think you have something that'll make it into -CURRENT in a while.

VMs not booting (was: How to build with VMM_DEBUG)

[Ax0n]

On Sat, Jun 23, 2018 at 3:54 PM, Ax0n  wrote:

>
> FWIW, that patch didn't apply cleanly to a fresh pull of the tree from
> GitHub. I know it's not OFFICIALLY -CURRENT for realsies but it's what I
> have been using on this laptop for months. It sounds like it was probably
> patched against -STABLE? I didn't read the entire thread on bugs@. I have
> tried with 3 daily snapshots in a row and I'm having the same problem. I
> haven't actually fired up vmm in a few weeks, so I'm not sure exactly when
> it quit working. I'm re-building with VMM_DEBUG first.
>
> Mike, I'll send all relevant info (dmesg, vmd -dvvv, vm.conf) to bugs@
> once I have it, unless this sounds like an ongoing thing you probably have
> on your radar already. I'm not in a huge rush, so I can wait a bit if you
> think you have something that'll make it into -CURRENT in a while.
>

Following up and cc bugs@ I built the system with VMM_DEBUG enabled.

>Synopsis:  vmm(4) VMs fail to start: ioctl failed: Invalid argument
>Category:  amd64
>Environment:
System  : OpenBSD 6.3
Details : OpenBSD 6.3-current (GENERIC.MP) #49: Sat Jun 23
09:32:05 MDT 2018
 dera...@amd64.openbsd.org:
/usr/src/sys/arch/amd64/compile/GENERIC.MP

Architecture: OpenBSD.amd64
Machine : amd64
>Description:
VMs fail to boot.
[axon@transient ~]$ doas vmd -dvvv
startup
/etc/vm.conf:4: switch "local" registered
/etc/vm.conf:8: switch "internal" registered
/etc/vm.conf:12: switch "wired" registered
vm_register: registering vm 1
/etc/vm.conf:28: vm "OBSD-Stable.vm" registered (disabled)
vm_register: registering vm 2
/etc/vm.conf:41: vm "OBSD-Stable-alt.vm" registered (disabled)
vm_register: registering vm 3
/etc/vm.conf:53: vm "OBSDSnap64.vm" registered (disabled)
config_setconfig: setting config
vm_priv_brconfig: interface bridge0 description switch1-local
vm_priv_brconfig: interface bridge1 description switch2-internal
vm_priv_brconfig: interface bridge0 description switch3-wired
vmd_configure: not creating vm OBSD-Stable.vm (disabled)
vmd_configure: not creating vm OBSD-Stable-alt.vm (disabled)
vmd_configure: not creating vm OBSDSnap64.vm (disabled)
config_getconfig: priv retrieving config
config_getconfig: control retrieving config
config_getconfig: vmm retrieving config
vm_opentty: vm OBSDSnap64.vm tty /dev/ttyp3 uid 1000 gid 4 mode 620
vm_register: registering vm 3
vm_priv_ifconfig: interface tap0 description vm3-if0-OBSDSnap64.vm
vm_priv_ifconfig: switch "local" interface bridge0 add tap0
OBSDSnap64.vm: started vm 3 successfully, tty /dev/ttyp3
loadfile_bios: loaded BIOS image
run_vm: initializing hardware for vm OBSDSnap64.vm
pic_set_elcr: setting level triggered mode for irq 3
pic_set_elcr: setting level triggered mode for irq 5
pic_set_elcr: setting level triggered mode for irq 6
virtio_init: vm "OBSDSnap64.vm" vio0 lladdr fe:e1:ba:d0:eb:ac
pic_set_elcr: setting level triggered mode for irq 7
run_vm: starting vcpu threads for vm OBSDSnap64.vm
vcpu_reset: resetting vcpu 0 for vm 2
run_vm: waiting on events for VM OBSDSnap64.vm
vcpu_run_loop: vm 2 / vcpu 0 run ioctl failed: Invalid argument
vmm_sighdlr: handling signal 20
vmm_sighdlr: attempting to terminate vm 3
terminate_vm: terminating vmid 2
vmm_sighdlr: calling vm_remove
vm_remove: removing vm id 3 from running config
vm_remove: calling vm_stop
vm_stop: stopping vm 3
vmd_dispatch_vmm: handling TERMINATE_EVENT for vm id 3 ret 22
vmd_dispatch_vmm: about to stop vm id 3
vm_stop: stopping vm 3
vm_opentty: vm OBSDSnap64.vm tty /dev/ttyp4 uid 1000 gid 4 mode 620
vm_register: registering vm 3
vm_priv_ifconfig: interface tap0 description vm3-if0-OBSDSnap64.vm
vm_priv_ifconfig: switch "local" interface bridge0 add tap0
OBSDSnap64.vm: started vm 3 successfully, tty /dev/ttyp4
loadfile_bios: loaded BIOS image
run_vm: initializing hardware for vm OBSDSnap64.vm
pic_set_elcr: setting level triggered mode for irq 3
pic_set_elcr: setting level triggered mode for irq 5
pic_set_elcr: setting level triggered mode for irq 6
virtio_init: vm "OBSDSnap64.vm" vio0 lladdr fe:e1:ba:d0:eb:ac
pic_set_elcr: setting level triggered mode for irq 7
run_vm: starting vcpu threads for vm OBSDSnap64.vm
vcpu_reset: resetting vcpu 0 for vm 3
run_vm: waiting on events for VM OBSDSnap64.vm
vcpu_run_loop: vm 3 / vcpu 0 run ioctl failed: Invalid argument
vmm_sighdlr: handling signal 20
vmm_sighdlr: attempting to terminate vm 3
terminate_vm: terminating vmid 3
vmm_sighdlr: calling vm_remove
vm_remove: removing vm id 3 from running config
vm_remove: calling vm_stop
vm_stop: stopping vm 3
vmd_dispatch_vmm: handling TERMINATE_EVENT for vm id 3 ret 22
vmd_dispatch_vmm: about to stop vm id 3
vm_stop: stopping vm 3


Contents of vm.co

Re: VMs not booting (was: How to build with VMM_DEBUG)

[Ax0n]

3
#2  acpivout_get_param+0xc8
#3  inteldrm_backlight_get_brightness+0x39
#4  get_properties+0x166
#5  drm_mode_getconnector+0x33b
#6  drm_do_ioctl+0x221
#7  drmioctl+0xf9
#8  VOP_IOCTL+0x5a
#9  vn_ioctl+0x6b
#10 sys_ioctl+0x477
#11 syscall+0x32a
#12 Xsyscall_untramp+0xe4
video0 detached
uvideo0 detached
sd1 detached
scsibus2 detached
umass0 detached
uhub2 detached
uhub0 detached
uhub3 detached
uhub1 detached
uhub0 at usb0 configuration 1 interface 0 "Intel EHCI root hub" rev
2.00/1.00 addr 1
uhub1 at usb1 configuration 1 interface 0 "Intel EHCI root hub" rev
2.00/1.00 addr 1
uhub2 at uhub0 port 1 configuration 1 interface 0 "Intel Rate Matching Hub"
rev 2.00/0.00 addr 2
uvideo0 at uhub2 port 1 configuration 1 interface 0 "SuYin 1.3M HD WebCam"
rev 2.00/1.02 addr 3
video0 at uvideo0
umass0 at uhub2 port 2 configuration 1 interface 0 "Generic USB2.0-CRW" rev
2.00/38.82 addr 4
umass0: using SCSI over Bulk-Only
scsibus2 at umass0: 2 targets, initiator 0
sd1 at scsibus2 targ 1 lun 0:  SCSI0 0/direct
removable serial.0bda013851638820
uhub3 at uhub1 port 1 configuration 1 interface 0 "Intel Rate Matching Hub"
rev 2.00/0.00 addr 2
vm_impl_init_vmx: created vm_map @ 0x80d3aa00
vm_resetcpu: resetting vm 2 vcpu 0 to power on defaults
Guest EPTP = 0x1f95bb01e
vmm_alloc_vpid: allocated VPID/ASID 1
vmm_fpurestore: guest attempted to set invalid bits in xcr0
vmm_free_vpid: freed VPID/ASID 1





On Sun, Jun 24, 2018 at 2:33 PM, Mike Larkin  wrote:

> On Sun, Jun 24, 2018 at 01:41:47AM -0500, Ax0n wrote:
> > On Sat, Jun 23, 2018 at 3:54 PM, Ax0n  wrote:
> >
> > >
> > > FWIW, that patch didn't apply cleanly to a fresh pull of the tree from
> > > GitHub. I know it's not OFFICIALLY -CURRENT for realsies but it's what
> I
> > > have been using on this laptop for months. It sounds like it was
> probably
> > > patched against -STABLE? I didn't read the entire thread on bugs@. I
> have
> > > tried with 3 daily snapshots in a row and I'm having the same problem.
> I
> > > haven't actually fired up vmm in a few weeks, so I'm not sure exactly
> when
> > > it quit working. I'm re-building with VMM_DEBUG first.
> > >
> > > Mike, I'll send all relevant info (dmesg, vmd -dvvv, vm.conf) to bugs@
> > > once I have it, unless this sounds like an ongoing thing you probably
> have
> > > on your radar already. I'm not in a huge rush, so I can wait a bit if
> you
> > > think you have something that'll make it into -CURRENT in a while.
> > >
> >
> > Following up and cc bugs@ I built the system with VMM_DEBUG enabled.
> >
>
> This does not look like the output from a kernel with VMM_DEBUG enabled.
> You'll
> be seeing all sorts of debug output to dmesg as the VM starts, runs, and
> ultimately in your case aborts.
>
> -ml
>
> > >Synopsis:  vmm(4) VMs fail to start: ioctl failed: Invalid argument
> > >Category:  amd64
> > >Environment:
> > System  : OpenBSD 6.3
> > Details : OpenBSD 6.3-current (GENERIC.MP) #49: Sat Jun 23
> > 09:32:05 MDT 2018
> >  dera...@amd64.openbsd.org:
> > /usr/src/sys/arch/amd64/compile/GENERIC.MP
> >
> > Architecture: OpenBSD.amd64
> > Machine : amd64
> > >Description:
> > VMs fail to boot.
> > [axon@transient ~]$ doas vmd -dvvv
> > startup
> > /etc/vm.conf:4: switch "local" registered
> > /etc/vm.conf:8: switch "internal" registered
> > /etc/vm.conf:12: switch "wired" registered
> > vm_register: registering vm 1
> > /etc/vm.conf:28: vm "OBSD-Stable.vm" registered (disabled)
> > vm_register: registering vm 2
> > /etc/vm.conf:41: vm "OBSD-Stable-alt.vm" registered (disabled)
> > vm_register: registering vm 3
> > /etc/vm.conf:53: vm "OBSDSnap64.vm" registered (disabled)
> > config_setconfig: setting config
> > vm_priv_brconfig: interface bridge0 description switch1-local
> > vm_priv_brconfig: interface bridge1 description switch2-internal
> > vm_priv_brconfig: interface bridge0 description switch3-wired
> > vmd_configure: not creating vm OBSD-Stable.vm (disabled)
> > vmd_configure: not creating vm OBSD-Stable-alt.vm (disabled)
> > vmd_configure: not creating vm OBSDSnap64.vm (disabled)
> > config_getconfig: priv retrieving config
> > config_getconfig: control retrieving config
> > config_getconfig: vmm retrieving config
> > vm_opentty: vm OBSDSnap64.vm tty /dev/ttyp3 uid 1000 gid 4 mode 620
> > vm_register: registering vm 3
&

Re: how to know the progressive state of dd

[Ax0n]

When I'm dd-ing images (e.g. flashing SD Cards for raspberry pi), I
occasionally use pv from packages to do the file reading e.g.

pv armv7.img | doas dd bs=1M of=/dev/rsd1c

pv will send the file/device contents to stdout as fast as it can read it,
and dd will read stdin to write the file to disk (or to the raw device). pv
outputs a status bar, throughput statistics and ETA to stderr so you can
watch the progress.

On Tue, Jun 26, 2018 at 4:21 AM, Tuyosi T  wrote:

> thanks for kind advises .
>
> on linux
> -
> # dd if=/dev/sdb of=./OpenBSD-8G-snapshot.img bs=32k
> 58195+0 records in
> 58194+0 records out
> 1906900992 bytes (1.9 GB, 1.8 GiB) copied, 25.1818 s, 75.7 MB/s
> 109011+0 records in
> 109010+0 records out
> 3572039680 bytes (3.6 GB, 3.3 GiB) copied, 56.2196 s, 63.5 MB/s
> 154198+0 records in
> 154198+0 records out
> 5052760064 bytes (5.1 GB, 4.7 GiB) copied, 87.9162 s, 57.5 MB/s
> 185970+0 records in
> 185970+0 records out
> 6093864960 bytes (6.1 GB, 5.7 GiB) copied, 116.37 s, 52.4 MB/s
> 227547+0 records in
> 227546+0 records out
> 7456227328 bytes (7.5 GB, 6.9 GiB) copied, 147.202 s, 50.7 MB/s
> 241920+0 records in
> 241920+0 records out
> 7927234560 bytes (7.9 GB, 7.4 GiB) copied, 154.806 s, 51.2 MB/s
>
> 
> regards
>

Re: VMs not booting (was: How to build with VMM_DEBUG)

[Ax0n]

I don't have another box to run these on, but with Hexdump, it looks like
these two particular VMs are:
OpenBSD 6.1-current (GENERIC) #54: Fri Apr 14 13:51:22 MDT 2017
OpenBSD 6.3 (GENERIC) #1: Sat Apr 21 13:49:17 CEST 2018

Neither one boots.


On Wed, Jun 27, 2018 at 12:58 AM, Mike Larkin  wrote:

> On Tue, Jun 26, 2018 at 08:22:08AM -0500, Ax0n wrote:
> > Finally got around to recompiling again. Sorry for the noise between the
> > two VM start attempts -- I suspended it to head to the office.
> >
> > OpenBSD 6.3-current (GENERIC.MP) #1: Tue Jun 26 06:58:23 CDT 2018
> > a...@transient.attlocal.net:/mnt/src/sys/arch/amd64/compile/
> GENERIC.MP
> > real mem = 8227655680 (7846MB)
> > avail mem = 7902162944 (7536MB)
> > mpath0 at root
> > scsibus0 at mpath0: 256 targets
> > mainbus0 at root
> > bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xe9d90 (47 entries)
> > bios0: vendor Acer version "V1.07" date 11/07/2011
> > bios0: Acer Aspire 5733Z
> > acpi0 at bios0: rev 2
> > acpi0: sleep states S0 S3 S4 S5
> > acpi0: tables DSDT FACP ASF! HPET APIC MCFG SLIC BOOT ASPT DMAR SSDT SSDT
> > SSDT
> > acpi0: wakeup devices AZAL(S3) P0P1(S4) EHC1(S3) USB1(S3) USB2(S3)
> USB3(S3)
> > USB4(S3) USB5(S3) USB6(S3) USB7(S3) RP01(S4) PEG5(S4)
> > acpitimer0 at acpi0: 3579545 Hz, 24 bits
> > acpihpet0 at acpi0: 14318179 Hz
> > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> > cpu0 at mainbus0: apid 0 (boot processor)
> > cpu0: Intel(R) Core(TM) i5 CPU M 540 @ 2.53GHz, 2527.97 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,SMX,EST,TM2,SSSE3,
> CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,AES,NXE,RDTSCP,
> LONG,LAHF,PERF,ITSC,SENSOR,ARAT,MELTDOWN
> > cpu0: 256KB 64b/line 8-way L2 cache
> > cpu0: smt 0, core 0, package 0
> > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
> > cpu0: apic clock running at 133MHz
> > cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE
> > cpu1 at mainbus0: apid 1 (application processor)
> > cpu1: Intel(R) Core(TM) i5 CPU M 540 @ 2.53GHz, 2527.43 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,SMX,EST,TM2,SSSE3,
> CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,AES,NXE,RDTSCP,
> LONG,LAHF,PERF,ITSC,SENSOR,ARAT,MELTDOWN
> > cpu1: 256KB 64b/line 8-way L2 cache
> > cpu1: smt 1, core 0, package 0
> > cpu2 at mainbus0: apid 4 (application processor)
> > cpu2: Intel(R) Core(TM) i5 CPU M 540 @ 2.53GHz, 2527.43 MHz
> > cpu2:
> > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,
> CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,
> PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,
> CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,AES,NXE,RDTSCP,
> LONG,LAHF,PERF,ITSC,SENSOR,ARAT,MELTDOWN
> > cpu2: 256KB 64b/line 8-way L2 cache
> > cpu2: smt 0, core 2, package 0
> > cpu3 at mainbus0: apid 5 (application processor)
> > cpu3: Intel(R) Core(TM) i5 CPU M 540 @ 2.53GHz, 2527.43 MHz
> > cpu3:
> > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,
> CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,
> PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,
> CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,AES,NXE,RDTSCP,
> LONG,LAHF,PERF,ITSC,SENSOR,ARAT,MELTDOWN
> > cpu3: 256KB 64b/line 8-way L2 cache
> > cpu3: smt 1, core 2, package 0
> > ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
> > , remapped to apid 2
> > acpimcfg0 at acpi0 addr 0xe000, bus 0-255
> > acpiprt0 at acpi0: bus 0 (PCI0)
> > acpiprt1 at acpi0: bus -1 (P0P2)
> > acpiprt2 at acpi0: bus 3 (P0P1)
> > acpiprt3 at acpi0: bus 1 (RP01)
> > acpiprt4 at acpi0: bus 2 (RP02)
> > acpiprt5 at acpi0: bus -1 (RP03)
> > acpiprt6 at acpi0: bus -1 (RP04)
> > acpiprt7 at acpi0: bus -1 (RP05)
> > acpiprt8 at acpi0: bus -1 (RP06)
> > acpiprt9 at acpi0: bus -1 (RP07)
> > acpiprt10 at acpi0: bus -1 (RP08)
> > acpiprt11 at acpi0: bus -1 (PEG5)
> > acpiec0 at acpi0
> > acpicpu0 at acpi0: C3(350@245 mwait.3@0x20), C1(1000@3 mwait.1), PSS
> > acpicpu1 at acpi0: C3(350@245 mwait.3@0x20), C1(1000@3 mwait.1), PSS
> > acpicpu2 at acpi0: C3(350@245 mwait.3@0x20), C1(1000@3 mwait.1), PSS
> > acpicpu3 at acpi0: C3(350@245 mwait.3@0x20), C1(1000@3 mwait.1), PSS
> > "pnp0c14" at acpi0 not configured
> > acpibat0 at acpi0: BAT0 model "Li_Ion_4000mA " serial 78da t

Re: VMs not booting (was: How to build with VMM_DEBUG)

[Ax0n]

Trying to spin up a diskless vmm with the latest bsd.rd:
[axon@transient vmm]$ doas vmctl start foo -c -b /bsd.rd -m 512m -i 1 -n
local
vmctl: starting without disks
Connected to /dev/ttyp3 (speed 115200)

[EOT]
[axon@transient vmm]$ dmesg | tail
Guest EPTP = 0x112d3001e
vmm_alloc_vpid: allocated VPID/ASID 1
vmm_fpurestore: guest attempted to set invalid bits in xcr0
vmm_free_vpid: freed VPID/ASID 1
vm_impl_init_vmx: created vm_map @ 0x80730600
vm_resetcpu: resetting vm 4 vcpu 0 to power on defaults
Guest EPTP = 0x112d3001e
vmm_alloc_vpid: allocated VPID/ASID 1
vmm_fpurestore: guest attempted to set invalid bits in xcr0
vmm_free_vpid: freed VPID/ASID 1


On Wed, Jun 27, 2018 at 4:56 AM, Ax0n  wrote:

> I don't have another box to run these on, but with Hexdump, it looks like
> these two particular VMs are:
> OpenBSD 6.1-current (GENERIC) #54: Fri Apr 14 13:51:22 MDT 2017
> OpenBSD 6.3 (GENERIC) #1: Sat Apr 21 13:49:17 CEST 2018
>
> Neither one boots.
>
>
> On Wed, Jun 27, 2018 at 12:58 AM, Mike Larkin 
> wrote:
>
>> On Tue, Jun 26, 2018 at 08:22:08AM -0500, Ax0n wrote:
>> > Finally got around to recompiling again. Sorry for the noise between the
>> > two VM start attempts -- I suspended it to head to the office.
>> >
>> > OpenBSD 6.3-current (GENERIC.MP) #1: Tue Jun 26 06:58:23 CDT 2018
>> > a...@transient.attlocal.net:/mnt/src/sys/arch/amd64/compile/
>> GENERIC.MP
>> > real mem = 8227655680 (7846MB)
>> > avail mem = 7902162944 (7536MB)
>> > mpath0 at root
>> > scsibus0 at mpath0: 256 targets
>> > mainbus0 at root
>> > bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xe9d90 (47 entries)
>> > bios0: vendor Acer version "V1.07" date 11/07/2011
>> > bios0: Acer Aspire 5733Z
>> > acpi0 at bios0: rev 2
>> > acpi0: sleep states S0 S3 S4 S5
>> > acpi0: tables DSDT FACP ASF! HPET APIC MCFG SLIC BOOT ASPT DMAR SSDT
>> SSDT
>> > SSDT
>> > acpi0: wakeup devices AZAL(S3) P0P1(S4) EHC1(S3) USB1(S3) USB2(S3)
>> USB3(S3)
>> > USB4(S3) USB5(S3) USB6(S3) USB7(S3) RP01(S4) PEG5(S4)
>> > acpitimer0 at acpi0: 3579545 Hz, 24 bits
>> > acpihpet0 at acpi0: 14318179 Hz
>> > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
>> > cpu0 at mainbus0: apid 0 (boot processor)
>> > cpu0: Intel(R) Core(TM) i5 CPU M 540 @ 2.53GHz, 2527.97 MHz
>> > cpu0:
>> > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMO
>> V,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,
>> SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16
>> ,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,AES,NXE,RDTSCP,LONG,
>> LAHF,PERF,ITSC,SENSOR,ARAT,MELTDOWN
>> > cpu0: 256KB 64b/line 8-way L2 cache
>> > cpu0: smt 0, core 0, package 0
>> > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
>> > cpu0: apic clock running at 133MHz
>> > cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE
>> > cpu1 at mainbus0: apid 1 (application processor)
>> > cpu1: Intel(R) Core(TM) i5 CPU M 540 @ 2.53GHz, 2527.43 MHz
>> > cpu1:
>> > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMO
>> V,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,
>> SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16
>> ,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,AES,NXE,RDTSCP,LONG,
>> LAHF,PERF,ITSC,SENSOR,ARAT,MELTDOWN
>> > cpu1: 256KB 64b/line 8-way L2 cache
>> > cpu1: smt 1, core 0, package 0
>> > cpu2 at mainbus0: apid 4 (application processor)
>> > cpu2: Intel(R) Core(TM) i5 CPU M 540 @ 2.53GHz, 2527.43 MHz
>> > cpu2:
>> > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMO
>> V,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,
>> SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16
>> ,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,AES,NXE,RDTSCP,LONG,
>> LAHF,PERF,ITSC,SENSOR,ARAT,MELTDOWN
>> > cpu2: 256KB 64b/line 8-way L2 cache
>> > cpu2: smt 0, core 2, package 0
>> > cpu3 at mainbus0: apid 5 (application processor)
>> > cpu3: Intel(R) Core(TM) i5 CPU M 540 @ 2.53GHz, 2527.43 MHz
>> > cpu3:
>> > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMO
>> V,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,
>> SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16
>> ,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,AES,NXE,RDTSCP,LONG,
>> LAHF,PERF,ITSC,SENSOR,ARAT,MELTDOWN
>> > cpu3: 256KB 64b/line 8-way L2 cache
>> > cpu3: smt 1, core 2, package 0
>> > ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
>> > , remapped 

Re: Employers, Jobs and OpenBSD

[Ax0n]

On Fri, Jul 13, 2018 at 9:05 PM, Man Hobby  wrote:

> Hi,
>
> What is the opinion of employers about OpenBSD?
>

As a hiring manager, I see OpenBSD experience on a resume as a sign that
one likely has a firm grasp of UNIX. Several of my employers have used it
for mission critical work such as application cluster servers, firewalls,
load balancers, mail servers and front-end web servers. At one point, I had
well over 200 OpenBSD systems (several racks full of 1U servers) under my
care.


> There is reason for to learn use OpenBSD to find job?
>

No.


> If not, why?
>

Initially, in 1998 I just wanted a stable UNIX-like operating system for my
laptop which had been flaky under Linux and FreeBSD. OpenBSD delivered
that, and more. I bounced around to other BSDs and Linux distros on my
laptops and desktops between 2000 and 2010, but I came home to OpenBSD in
2010 and haven't looked back.

If there is not reason for to learn use OpenBSD to find job, why use
> OpenBSD?
>

Simply put, it's the OS I'm most comfortable with using on a daily basis.
My day job has my team using Windows, Amazon Linux, RHEL and OS X. I come
home and I sigh in relief at the simplicity, excellent documentation, and
stability of the software that this community has built.

rying to get meta-data configured for cloud-image VMM instances

[Ax0n]

I'm hoping someone on-list has actually gotten this to work and can point
out where I'm going wrong.

I've been trying for months off and on to get this to work. I have a
feeling I just don't understand the documentation for meta-data (
https://github.com/reyk/meta-data ) though I see at least one httpd.conf
anachronism in the documentation. "Strip" isn't allowed in the "root"
definition of httpd.conf, so httpd won't even start with this chunk of
config:

server "meta-data" {
listen on 169.254.169.254 port 80
fastcgi socket "/run/httpd.sock"
root { "/", strip 1 }
}

I've removed ", strip 1 " from the httpd.conf, so my whole config looks
like this. N.B. This may be my actual problem, but I don't know how to
solve it.

ext_addr="*"
server "default" {
root "/htdocs/"
directory auto index
listen on $ext_addr port 80
}

# Include MIME types instead of the built-in ones
types {
include "/usr/share/misc/mime.types"
}

server "meta-data" {
listen on 169.254.169.254 port 80
fastcgi socket "/run/httpd.sock"
root { "/" }
}

I've otherwise installed meta-data as the instructions say, and started it
with this command-line:

doas kfcgi -r -n 2 -u www -p / -- /usr/local/libexec/meta-data

The meta-data directory structure is as follows:
[axon@transient ~]$ find /home/vm/meta-data/ -type f
/home/vm/meta-data/vmmbuntu/instance-id
/home/vm/meta-data/vmmbuntu/username
/home/vm/meta-data/vmmbuntu/public-keys/0/openssh-key

Where instance-id contains "vm1", username contains "puffy" and the
openssh-key is the public key for this laptop I'm running on.

I downloaded xenial-server-cloudimg-amd64-disk1.img and converted it to raw
with the qemu-img utility. I also made a 10GB image that I intended to
install some stuff permanently to (ubuntu.img)

I then started the vm like this:

doas vmctl start vmmubuntu -d xenial-server-cloudimg-amd64-disk1.raw -d
ubuntu.img -n local -m 2G -c
Connected to /dev/ttyp2 (speed 115200)
SeaBIOS (version 1.11.0p0-OpenBSD-vmm)


   [0.00] Initializing
cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Initializing cgroup subsys cpuacct
[0.00] Linux version 4.4.0-130-generic (buildd@lgw01-amd64-039)
(gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9) ) #156-Ubuntu
SMP Thu Jun 14 08:53:28 UTC 2018 (Ubuntu 4.4.0-130.156-generic 4.4.134)
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
[0.00] KERNEL supported cpus:
[0.00]   Intel GenuineIntel
[0.00]   AMD AuthenticAMD
[0.00]   Centaur CentaurHauls
[0.00] Disabled fast string operations
[0.00] x86/fpu: Legacy x87 FPU detected.
[0.00] x86/fpu: Using 'eager' FPU context switches.
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009f7ff] usable
[0.00] BIOS-e820: [mem 0x0009f800-0x0009]
reserved
[0.00] BIOS-e820: [mem 0x000f-0x000f]
reserved
[0.00] BIOS-e820: [mem 0x0010-0x7fffbfff] usable
[0.00] BIOS-e820: [mem 0x7fffc000-0x7fff]
reserved
[0.00] BIOS-e820: [mem 0xfffc-0x]
reserved
[0.00] NX (Execute Disable) protection: active
[0.00] SMBIOS 2.4 present.
[0.00] e820: last_pfn = 0x7fffc max_arch_pfn = 0x4
[0.00] MTRR: Disabled
[0.00] x86/PAT: MTRRs disabled, skipping PAT initialization too.
[0.00] x86/PAT: Configuration [0-7]: WB  WT  UC- UC  WB  WT  UC-
UC
[0.00] Scanning 1 areas for low memory corruption
[0.00] RAMDISK: [mem 0x36aa4000-0x37549fff]
[0.00] ACPI: Early table checksum verification disabled
[0.00] ACPI BIOS Error (bug): A valid RSDP was not found
(20150930/tbxfroot-243)
[0.00] No NUMA configuration found
[0.00] Faking a node at [mem 0x-0x7fffbfff]
[0.00] NODE_DATA(0) allocated [mem 0x7fff7000-0x7fffbfff]
[0.00] Zone ranges:
[0.00]   DMA  [mem 0x1000-0x00ff]
[0.00]   DMA32[mem 0x0100-0x7fffbfff]
[0.00]   Normal   empty
[0.00]   Device   empty
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x1000-0x0009efff]
[0.00]   node   0: [mem 0x0010-0x7fffbfff]
[0.00] Initmem setup node 0 [mem 0x1000-
0x7fffbfff]
[0.00] SFI: Simple Firmware Interface v0.81
http://simplefirmware.org
[0.00] smpboot: Allowing 1 CPUs, 0 hotplug CPUs
[0.00] No local APIC present
[0.00] APIC: disable apic facility
[0.00] APIC: switched to apic NOOP
[0.00] PM: Register

Re: linux under vm on openbsd tutorial

[Ax0n]

I created that article. My guess is your hardware doesn't support VMX/EPT.

Please post the full output of dmesg.

On Jul 16, 2018 05:26, "Rudolf Sykora"  wrote:

Hello,

please, is there some good (easy to follow, up to date)
tutorial about how to set up a linux distribution
under virtual machine on OpenBSD?

[
I found eg

http://www.h-i-r.net/2017/04/openbsd-vmm-hypervisor-part-2.html

but as soon as I issue
rcctl start vmd
I get 'failed'
]

Thanks
Ruda

Re: linux under vm on openbsd tutorial

[Ax0n]

On Mon, Jul 16, 2018 at 6:24 AM, Ax0n  wrote:

> I created that article. My guess is your hardware doesn't support VMX/EPT.
>
> Please post the full output of dmesg.
>

Also, try, as root, running vmd in verbose debug mode, e.g.

doas vmd -dvvv

And then post the output of that as well.

Re: rying to get meta-data configured for cloud-image VMM instances

[Ax0n]

On Mon, Jul 16, 2018 at 4:56 AM, Rickard von Essen <
rickard.von.es...@gmail.com> wrote:

> It looks like cloud-init in the VM can't even reach 169.254.169.254. Does
> it have routing to get there? Is there a fw blocking the calls from the VM
> to 169.254.169.254?
>

I don't think so. This is my pf.conf (n.b. it's mostly just additional
stuff so that I can access the permanently-configired VMs through the NAT)

#   $OpenBSD: pf.conf,v 1.55 2017/12/03 20:40:04 sthen Exp $
#
# See pf.conf(5) and /etc/examples/pf.conf
ext_if="athn0"
#ext_if="bge0"
vmd_if="vether0"

set skip on lo

block return# block stateless traffic
pass# establish keep-state

# By default, do not permit remote connections to X11
block return in on ! lo0 proto tcp to port 6000:6010

# vmm setup: outbound nat, inbound port mapping
match out on $ext_if inet from $vmd_if:network to any nat-to ($ext_if)
pass in on $ext_if proto tcp from any to any port 2200 rdr-to 10.13.37.200
port 22
pass in on $ext_if proto tcp from any to any port 2201 rdr-to 10.13.37.201
port 22
pass in on $ext_if proto tcp from any to any port 2202 rdr-to 10.13.37.202
port 22
pass in on $ext_if proto tcp from any to any port 2203 rdr-to 10.13.37.203
port 22
pass in on $ext_if proto tcp from any to any port 2204 rdr-to 10.13.37.204
port 22
pass in on $ext_if proto tcp from any to any port 8000 rdr-to 10.13.37.200
port 80
pass in on $ext_if proto tcp from any to any port 8001 rdr-to 10.13.37.201
port 80
pass in on $ext_if proto tcp from any to any port 8002 rdr-to 10.13.37.202
port 80
pass in on $ext_if proto tcp from any to any port 8003 rdr-to 10.13.37.203
port 80

So that you can get a feel for my setup:
vether0 is static-configured 10.13.37.1 255.255.255.0. dhcpd is bound only
to vether0 (to assign a mix of reserved and pool IPs to VMM guests) and
vether0 is added to bridge0 at boot via hostname.bridge0.

bridge0 is tied to the "local" switch in vm.conf, and that's what all of my
VMs connect to.


On Mon, Jul 16, 2018 at 12:20 PM,  wrote:

>
> I thought it was:
>
> root "/" strip 1
>
> No curlies and no comma, but I haven't tried it.
>
>
httpd doesn't like that syntax, either:

[axon@transient ~]$ doas httpd -d
startup
/etc/httpd.conf:16: syntax error
logger exiting, pid 63722
server exiting, pid 24069
server exiting, pid 34562
server exiting, pid 69335
[axon@transient ~]$ cat -n /etc/httpd.conf
 1  ext_addr="*"
 2  server "default" {
 3  root "/htdocs/"
 4  directory auto index
 5  listen on $ext_addr port 80
 6  }
 7
 8  # Include MIME types instead of the built-in ones
 9  types {
10  include "/usr/share/misc/mime.types"
11  }
12
13  server "meta-data" {
14  listen on 169.254.169.254 port 80
15  fastcgi socket "/run/httpd.sock"
16  root  "/" strip 1
17  }
18

Re: Best pf practices to limit ddos attacks

[Ax0n]

On Mon, Jul 16, 2018, 19:39 Walt  wrote:

>
> I'm not sure what would be useful for when we are the target of an
> attack.  It seems to me that when the attack is going on, our bandwidth is
> so saturated that I'm not sure what we can do except to wait it out or to
> pay our provider to help mitigate the attack.
>

This is pretty much the gist of it. One cannot stop this class of DDoS from
the customer's end. There are a variety of solutions involving reverse
proxies and big, scalable clusters, but the fact is if the attacker knows
your real IP address, they can food your residential or small business
connection easily.

On the other hand, there are steps that we can take to limit any unwitting
> participation in an attack from our side.  For example, I have already been
> blocking all incoming UDP, TCP, and ICMP packets from the internet that
> claim to originate from our IP addresses and all outgoing UDP, TCP, and
> ICMP packets to the internet that are not from our IP addresses.
>

This is a great start. Most recent attacks rely on either a fleet of many
hacked IoT/"Smart" devices to generate a bill of coordinated traffic from
thousands or even millions of networks, or they rely on UDP amplification
attacks.

It sounds like you are taking adequate precautions against publicly
accessible assets that might get hijacked, so I'll focus on amplification
attacks.

UDP amplification is where an unwitting third party (such as yourself) is
hosting a UDP service that is capable of responding back with a much larger
payload than that which is sent to it. The simplest and most obvious
example is hosting an open, recursive DNS resolver. The attacker spoofs a
request for a large record (often a TXT entry) using the IP address of the
real victim. Your resolver, in return, recursively fetches and caches the
answer, then forwards the rather large response to the victim, which, of
course, didn't actually make the request and is not expecting this data.
The attacker does this repeatedly, and in tandem with a large corpus of
similarly misconfigured services hosted by other unwitting third parties.
Now tens of thousands of unsolicited DNS responses per second are
exhausting the bandwidth of the victim, and the attackers' real address
isn't even involved. Similar attacks have used misconfigured NTP servers.

Make sure your public, likely-authoritative DNS servers are not publicly
recursive for domains you don't control.
https://en.m.wikipedia.org/wiki/Split-horizon_DNS

With the ever increasing sophistication of ddos attacks, is anything else
> we can do in order to keep anything on our network from being used as part
> of a botnet or in order to reduce the severity of an incoming ddos attack.
>
> Walt
>
>
> ​Sent with ProtonMail Secure Email.​
>
>
>

Re: rying to get meta-data configured for cloud-image VMM instances

[Ax0n]

On Mon, Jul 16, 2018 at 4:30 PM, Reyk Floeter  wrote:

> https://www.openbsd.org/faq/current.html#r20180613b
>
> I can respond in more details when I’m back online later this week.
>
> Reyk
>
>
Thanks, Reyk. I missed that in the -CURRENT docs. Indeed, this clause seems
to work, as far as httpd starting:

-
server "meta-data" {
listen on 169.254.169.254 port 80
fastcgi socket "/run/httpd.sock"
root  "/"
request strip 1
}
-

I also added an alias of 169.254.168.254 to vether0 (not with
hostname.vether0, just from the command-line) and re-started httpd to see
what happens.

This is what I'm getting from cloud-init now:

 Starting Initial cloud-init job (metadata service crawler)...
[   10.292630] cloud-init[939]: Cloud-init v. 18.2 running 'init' at Thu,
19 Jul 2018 14:22:12 +. Up 5.16 seconds.
[   10.340633] cloud-init[939]: ci-info:
++Net device
info++
[   10.392636] cloud-init[939]: ci-info:
++--+-+---+---+---+
[   10.448639] cloud-init[939]: ci-info: | Device |  Up  |
Address   |  Mask | Scope | Hw-Address|
[   10.504643] cloud-init[939]: ci-info:
++--+-+---+---+---+
[   10.560646] cloud-init[939]: ci-info: | enp0s4 | True |
10.13.37.47 | 255.255.255.0 |   .   | fe:e1:bb:d1:03:a8 |
[   10.620650] cloud-init[939]: ci-info: | enp0s4 | True |
fe80::fce1:bbff:fed1:3a8/64 |   .   |  link | fe:e1:bb:d1:03:a8 |
[   10.676654] cloud-init[939]: ci-info: |   lo   | True |
 127.0.0.1  |   255.0.0.0   |   .   | . |
[   10.728657] cloud-init[939]: ci-info: |   lo   | True |
::1/128   |   .   |  host | . |
[   10.784660] cloud-init[939]: ci-info:
++--+-+---+---+---+
[   10.840664] cloud-init[939]: ci-info: Route
IPv4 info+
[   10.892667] cloud-init[939]: ci-info:
+---+-++---+---+---+
[   10.940670] cloud-init[939]: ci-info: | Route | Destination |  Gateway
|Genmask| Interface | Flags |
[   10.992673] cloud-init[939]: ci-info:
+---+-++---+---+---+
[   11.040676] cloud-init[939]: ci-info: |   0   |   0.0.0.0   | 10.13.37.1
|0.0.0.0|   enp0s4  |   UG  |
[   11.092680] cloud-init[939]: ci-info: |   1   |  10.13.37.0 |  0.0.0.0
| 255.255.255.0 |   enp0s4  |   U   |
[   11.140683] cloud-init[939]: ci-info:
+---+-++---+---+---+
[   11.192686] cloud-init[939]: 2018-07-19 14:22:18,108 -
url_helper.py[WARNING]: Calling '
http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [0/120s]:
bad status code [404]
[   11.296692] cloud-init[939]: 2018-07-19 14:22:19,112 -
url_helper.py[WARNING]: Calling '
http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [1/120s]:
bad status code [404]
[   12.300755] cloud-init[939]: 2018-07-19 14:22:20,116 -
url_helper.py[WARNING]: Calling '
http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [2/120s]:
bad status code [404]
[   13.308818] cloud-init[939]: 2018-07-19 14:22:21,124 -
url_helper.py[WARNING]: Calling '
http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [3/120s]:
bad status code [404]
[   14.312881] cloud-init[939]: 2018-07-19 14:22:22,128 -
url_helper.py[WARNING]: Calling '
http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [4/120s]:
bad status code [404]
[   15.320944] cloud-init[939]: 2018-07-19 14:22:23,136 -
url_helper.py[WARNING]: Calling '
http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [5/120s]:
bad status code [404]
[   17.329069] cloud-init[939]: 2018-07-19 14:22:25,145 -
url_helper.py[WARNING]: Calling '
http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [7/120s]:
bad status code [404]
[   19.333195] cloud-init[939]: 2018-07-19 14:22:27,149 -
url_helper.py[WARNING]: Calling '
http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [9/120s]:
bad status code [404]
[   21.541333] cloud-init[939]: 2018-07-19 14:22:29,357 -
url_helper.py[WARNING]: Calling '
http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [11/120s]:
bad status code [404]
[   23.545458] cloud-init[939]: 2018-07-19 14:22:31,361 -
url_helper.py[WARNING]: Calling '
http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [13/120s]:
bad status code [404]
[   26.141620] cloud-init[939]: 2018-07-19 14:22:33,957 -
url_helper.py[WARNING]: Calling '
http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [15/120s]:
bad status code [404]
[   29.145808] cloud-init[939]: 2018-07-19 14:22:36,961 -
url_helper.py[WARNING]: Calling '
http://169.254.169.254/200

Re: Status of Owncloud?

[Ax0n]

On Jul 22, 2018 10:11, "Nicolas Schmidt"  wrote:

Hi,

I just installed and configured owncloud on OpenBSD 6.3, and so far
everything seems to work (except for owncloud complaining about not having
an internet connection). However, when visiting http://localhost/owncloud/
after installation, I was greeted by an unfriendly message telling me that
owncloud doesn't run properly on OpenBSD. This message didn't go into more
details, nor could I find anything on owncloud.com or openbsd.org regarding
this.

So I'm wondering, what's the status of owncloud on OpenBSD? Is it still
supported? Are there plans to remove support for it in future releases?

Best,
Nicolas


I know this doesn't directly answer your question, but it seems like many
users (especially within but not limited to the OpenBSD community) started
preferring NextCloud ( https://nextcloud.com ) which appears to be
maintained by several of the original OwnCloud developers.

--ax0n

Re: "Missing operating system" after i386 dual boot install

[Ax0n]

On Sat, Aug 4, 2018, 19:00 Sijmen J. Mulder  wrote:

> Hi all,
>
> I've installed OpenBSD 6.3 on a Pentium III machine alongside existing
> installations of Windows 95 and Windows NT 4 by manually setting up a
> partition in the fdisk step and using the suggested disklabel
> configuration. As recommended in INSTALL.i386, I've emarked the OpenBSD
> partition as active.
>
> After booting the PC pauses for a few seconds before displaying "Missing
> operating system".
>
> What I've tried:
>  - "boot hd0a:/bsd" from the installation CD: works
>  - mark partition 0 active: works, brings up NT's bootloader
>  - "installboot -v wd0": no change
>
> Any ideas?
>
> Output of "fdisk wd0", "disklabel wd0", and "installboot -nv wd0"
> reproduced below.
>
> Thanks,
> Sijmen J. Mulder
>
>
> --> fdisk wd0
>
>   Disk: wd0 geometry: 4998/255/63 [80293248 Sectors]
>   Offset: 0 Signature: 0xAA55
>   Starting Ending LBA Info:
>#: id  C   H   S -  C   H   S [   start:size ]
>
> ---
>0: 06  0   1   1 -260 254  63 [  63: 4192902 ]
> FAT16B
>1: 05261   0   1 -   1023 254  63 [ 4192965:12257595 ]
> Extended DOS
>   *2: A6   1024   0   1 -   3071 254  63 [16450560:32901120 ]
> OpenBSD
>3: 00  0   0   0 -  0   0   0 [   0:   0 ]
> unused
>   Disk: wd0 geometry: 4998/255/63 [80293248 Sectors]
>   Offset: 4192965   Signature: 0xAA55
>   Starting Ending LBA Info:
>#: id  C   H   S -  C   H   S [   start:size ]
>
> ---
>0: 07261   1   1 -521 254  63 [ 4193028: 4192902 ]
> NTFS
>1: 00  0   0   0 -  0   0   0 [   0:   0 ]
> unused
>2: 00  0   0   0 -  0   0   0 [   0:   0 ]
> unused
>3: 00  0   0   0 -  0   0   0 [   0:   0 ]
> unused
>
>
> --> disklabel wd0
>
>   # /dev/rwd0c:
>   type: ESDI
>   disk: ESDI/IDE disk
>   label: Maxtor 6K040L0
>   duid: bcc4a547f3b61211
>   flags:
>   bytes/sector: 512
>   sectors/track: 63
>   tracks/cylinder: 255
>   sectors/cylinder: 16065
>   cylinders: 4998
>   total sectors: 80293248
>   boundstart: 16450560
>   boundend: 49351680
>   drivedata: 0
>
>   16 partitions:
>   #size   offset  fstype [fsize bsize   cpg]
> a:  1075232 16450560  4.2BSD   2048 16384  8366 # /
> b:  1045744 17525792swap# none
> c: 802932480  unused
> d:  1474592 18571552  4.2BSD   2048 16384 11474 # /tmp
> e:  2160704 20046144  4.2BSD   2048 16384 12958 # /var
> f:  2611232 22206848  4.2BSD   2048 16384 12958 # /usr
> g:  1247232 24818080  4.2BSD   2048 16384  9744 #
> /usr/X11R6
> h:  4401248 26065312  4.2BSD   2048 16384 12958 #
> /usr/local
> i:  4192902   63   MSDOS
> j:  4192902  4193028NTFS
> k:  2969600 30466560  4.2BSD   2048 16384 12958 #
> /usr/src
> l:  6905856 33436160  4.2BSD   2048 16384 12958 #
> /usr/obj
> m:  9009664 40342016  4.2BSD   2048 16384 12958 # /home
>
>
> --> installboot -nv wd0
>
>   Using / as root
>   would install bootstrap on /dev/rwd0c
>   using first-stage /usr/mdec/biosboot, second-stage /usr/mdec/boot
>   would copy /usr/mdec/boot to /boot
>   /boot is 6 blocks x 16384 bytes
>   fs block shift 2; part offset 16450560; inode block 104, offset 2472
>   master boot record (MBR) at sector 0
> partition 0: type 0x06 offset 63 size 4192902
> partition 1: type 0x05 offset 4192965 size 12257595
> partition 2: type 0xA6 offset 16450560 size 32901120
>   /usr/mdec/biosboot will be written at sector 16450560
>

Did you read the FAQ on multi-booting where they talk about creating the
openbsd.pbr file and using bcdedit? In running dual-boot with Win7/OpenBSD
on one system, and Win10/OpenBSD on another, and the procedure in the FAQ
has worked well for me. https://www.openbsd.org/faq/faq4.html#Multibooting

>

Re: "Missing operating system" after i386 dual boot install

[Ax0n]

On Sun, Aug 5, 2018 at 5:02 AM Sijmen J. Mulder  wrote:

> Success!
>
> Unfortunately NT4 predates the BCD but I managed to do something
> similar by adding the following line to C:\boot.ini:
>
>   C:\openbsd.pbr="OpenBSD"
>
> I still wonder why it wouldn't boot from the partition directly but at
> least it works and I'm happy to report that OpenBSD performs remarkably
> well on this old hardware (PIII 800 MHz, 128 MB RAM).
>
> Sijmen
>

That's awesome! I've been dual-booting OpenBSD since the Win2000 era using
the NT Boot loader, and don't recall how I had to do it back then, but I
don't think it had BCDEdit either. I probably had to do the same thing.
Anyhow, happy to help, and enjoy OpenBSD on that thing.

Re: rying to get meta-data configured for cloud-image VMM instances

[Ax0n]

On Thu, Jul 19, 2018 at 9:41 AM Ax0n  wrote:

>
>
> On Mon, Jul 16, 2018 at 4:30 PM, Reyk Floeter  wrote:
>
>> https://www.openbsd.org/faq/current.html#r20180613b
>>
>> I can respond in more details when I’m back online later this week.
>>
>> Reyk
>>
>>
> Ping?

I still haven't quite figured out how to get meta-data to work with the
Ubuntu cloud image :(

sndio: way to play and record from different devices?

[Ax0n]

I have a nice microphone attached to a USB sound device, but I'd like to
rely on my computer's built-in line out for speakers from the same program
(e.g. Audacity, Firefox). It feels like sndio might have some way to let
programs use snd/0.play and snd/1.rec, or a way to make snd/1 the default
device for record and snd/0 the default for play, or maybe even a virtual
sound device, but I haven't been able to sort out how to make it work.

Ideas?

Sparc64 LDOM not working past OpenBSD 6.5

[Ax0n]

I have a SunFire T2000 that I originally installed 6.1 on. I set up LDOMs
way back in May 2017. I kept all of the domains up to date until OpenBSD
6.6. After that, LDOMs would no longer work. The system would not boot
unless I reverted back to the single domain default using
bootmode config="factory-default"

I kind of just forgot about the machine until 6.7 came out. I upgraded, and
got the same errors upon trying to boot. I re-generated the LDOM config as
outlined in this blog post I wrote:

http://www.h-i-r.net/2017/05/logical-domains-on-sunfire-t2000-with.html

That is, I dumped the factory-default config, used it as a template for the
new LDOM configuration, edited a config file, applied the config to the
directory and used ldomctl download to apply the LDOM config before
resetting the system.

Specifically, the errors I get now (and yes, some are repeats, but it's ALL
I get from the console while booting) are:

ERROR: /pci@780: Invalid hypervisor argument(s). function: b4
ERROR: /pci@780: Invalid hypervisor argument(s). function: b4
ERROR: /pci@780: Invalid hypervisor argument(s). function: b5
WARNING: /pci@7c0/pci@0/pci@1/network: Missing network-vpd MD node
WARNING: /pci@7c0/pci@0/pci@1/network: Missing network-vpd MD node

And after that, the system hangs and I must exit to the ALOM system
controller prompt to do anything further, such as revert the configuration
and reset to make the system able to boot again.

I searched and found one other person with this problem a while back ago,
but no resolution. I have hardware right here in front of me and I'm not
afraid to run -CURRENT and/or test patches to help. I am also willing to
provide remote SSH access to the system controller if someone wants to hack
on the hardware directly if it would help, though I think there are a few
LDOM-capable sparc64 machines in developers' hands already.

dmesg:
console is /virtual-devices@100/console@1
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California.  All rights reserved.
Copyright (c) 1995-2021 OpenBSD. All rights reserved.
https://www.OpenBSD.org

OpenBSD 6.9 (GENERIC.MP) #794: Sun Apr 18 12:34:31 MDT 2021
dera...@sparc64.openbsd.org:/usr/src/sys/arch/sparc64/compile/GENERIC.MP
real mem = 34225520640 (32640MB)
avail mem = 33608228864 (32051MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root: Sun Fire T200
cpu0 at mainbus0: SUNW,UltraSPARC-T1 (rev 0.0) @ 1200 MHz
cpu1 at mainbus0: SUNW,UltraSPARC-T1 (rev 0.0) @ 1200 MHz
cpu2 at mainbus0: SUNW,UltraSPARC-T1 (rev 0.0) @ 1200 MHz
cpu3 at mainbus0: SUNW,UltraSPARC-T1 (rev 0.0) @ 1200 MHz
cpu4 at mainbus0: SUNW,UltraSPARC-T1 (rev 0.0) @ 1200 MHz
cpu5 at mainbus0: SUNW,UltraSPARC-T1 (rev 0.0) @ 1200 MHz
cpu6 at mainbus0: SUNW,UltraSPARC-T1 (rev 0.0) @ 1200 MHz
cpu7 at mainbus0: SUNW,UltraSPARC-T1 (rev 0.0) @ 1200 MHz
cpu8 at mainbus0: SUNW,UltraSPARC-T1 (rev 0.0) @ 1200 MHz
cpu9 at mainbus0: SUNW,UltraSPARC-T1 (rev 0.0) @ 1200 MHz
cpu10 at mainbus0: SUNW,UltraSPARC-T1 (rev 0.0) @ 1200 MHz
cpu11 at mainbus0: SUNW,UltraSPARC-T1 (rev 0.0) @ 1200 MHz
cpu12 at mainbus0: SUNW,UltraSPARC-T1 (rev 0.0) @ 1200 MHz
cpu13 at mainbus0: SUNW,UltraSPARC-T1 (rev 0.0) @ 1200 MHz
cpu14 at mainbus0: SUNW,UltraSPARC-T1 (rev 0.0) @ 1200 MHz
cpu15 at mainbus0: SUNW,UltraSPARC-T1 (rev 0.0) @ 1200 MHz
cpu16 at mainbus0: SUNW,UltraSPARC-T1 (rev 0.0) @ 1200 MHz
cpu17 at mainbus0: SUNW,UltraSPARC-T1 (rev 0.0) @ 1200 MHz
cpu18 at mainbus0: SUNW,UltraSPARC-T1 (rev 0.0) @ 1200 MHz
cpu19 at mainbus0: SUNW,UltraSPARC-T1 (rev 0.0) @ 1200 MHz
cpu20 at mainbus0: SUNW,UltraSPARC-T1 (rev 0.0) @ 1200 MHz
cpu21 at mainbus0: SUNW,UltraSPARC-T1 (rev 0.0) @ 1200 MHz
cpu22 at mainbus0: SUNW,UltraSPARC-T1 (rev 0.0) @ 1200 MHz
cpu23 at mainbus0: SUNW,UltraSPARC-T1 (rev 0.0) @ 1200 MHz
cpu24 at mainbus0: SUNW,UltraSPARC-T1 (rev 0.0) @ 1200 MHz
cpu25 at mainbus0: SUNW,UltraSPARC-T1 (rev 0.0) @ 1200 MHz
cpu26 at mainbus0: SUNW,UltraSPARC-T1 (rev 0.0) @ 1200 MHz
cpu27 at mainbus0: SUNW,UltraSPARC-T1 (rev 0.0) @ 1200 MHz
cpu28 at mainbus0: SUNW,UltraSPARC-T1 (rev 0.0) @ 1200 MHz
cpu29 at mainbus0: SUNW,UltraSPARC-T1 (rev 0.0) @ 1200 MHz
cpu30 at mainbus0: SUNW,UltraSPARC-T1 (rev 0.0) @ 1200 MHz
cpu31 at mainbus0: SUNW,UltraSPARC-T1 (rev 0.0) @ 1200 MHz
vbus0 at mainbus0
"flashprom" at vbus0 not configured
cbus0 at vbus0
vldc0 at cbus0
vldcp0 at vldc0 chan 0x0: ivec 0x0, 0x1 channel "hvctl"
"ldom-primary" at vldc0 chan 0x1 not configured
"fmactl" at vldc0 chan 0x3 not configured
vldc1 at cbus0
"ldmfma" at vldc1 chan 0x4 not configured
vldc2 at cbus0
vldcp1 at vldc2 chan 0x14: ivec 0x28, 0x29 channel "spds"
"system-management" at vldc2 chan 0xd not configured
vcons0 at vbus0: ivec 0x111: console
vrtc0 at vbus0
"fma" at vbus0 not configured
"sunvts" at vbus0 not configured
"sunmc" at vbus0 not configured
"explorer" at vbus0 not configured
"led" at vbus0 not configured
"flashupdate" at vbus0 not configured
"ncp" at vbus0 not configur

Re: ix(4) stopped working after upgrade to OpenBSD 6.8

[Ax0n]

On Sun, Jan 16, 2022 at 4:46 PM Stuart Henderson 
wrote:

> Do both ix0 and ix1 break, or just ix1?
>
> One important difference visible in dmesg is that ix starts using MSI-X.
>

Some time ago, I noticed that ix1 isn't usable. I don't think it even shows
up in ifconfig -a on OpenBSD 6.7. I didn't worry much about it because I
was only using ix0, but it could be a clue. I'm going to see if I can get
the patch working that Patrick sent to the list recently.

Microphone not working on Gen8 ThinkPad X1 Carbon

[Ax0n]

I initially noticed it when I hopped in a video room on Discord in Firefox
and folks could see me and I could hear them, but Discord got no audio. It
turns out, nothing gets any audio. sysctl has audio and video recording
enabled, and pledge/unveil has been tweaked just a little for firefox to
pick up the webcam.

aucat isn't picking up any audio. playing back the WAV I recorded with
aucat or audacity is just silence. Audacity visibly shows very very low
audio levels in the "monitor" VU meter when recording, but no amount of
tinkering with mixerctl, audioctl, or sndioctl seems to make a difference
in the recorded audio -- it's just silent. Audio output is good (videos on
youtube for example) and aucat can play other WAV files just fine. I use
the pianobar package daily to stream Pandora while I work.

I switched over to the latest snapshot and upgraded packages last night,
and there's no change.

Relevant output follows:

OpenBSD 6.9-beta (GENERIC.MP) #431: Sat Mar 27 01:45:57 MDT 2021
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 16774819840 (15997MB)
avail mem = 16251035648 (15498MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.2 @ 0x6cbac000 (70 entries)
bios0: vendor LENOVO version "N2WET26W (1.16 )" date 01/21/2021
bios0: LENOVO 20U9S1QP00
acpi0 at bios0: ACPI 6.1
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT SSDT SSDT SSDT SSDT TPM2 SSDT HPET APIC MCFG
ECDT SSDT SSDT SSDT NHLT BOOT SSDT LPIT WSMT SSDT DBGP DBG2 MSDM BATB DMAR
ASF! UEFI FPDT
acpi0: wakeup devices GLAN(S4) XHC_(S3) XDCI(S4) HDAS(S4) RP01(S4) PXSX(S4)
RP02(S4) PXSX(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) PXSX(S4) RP06(S4)
PXSX(S4) RP07(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 2399 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-10610U CPU @ 1.80GHz, 7903.91 MHz, 06-8e-0c
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,SMX,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,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
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) i7-10610U CPU @ 1.80GHz, 1797.69 MHz, 06-8e-0c
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,SMX,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,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Core(TM) i7-10610U CPU @ 1.80GHz, 1795.82 MHz, 06-8e-0c
cpu2:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,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,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 6 (application processor)
cpu3: Intel(R) Core(TM) i7-10610U CPU @ 1.80GHz, 1795.82 MHz, 06-8e-0c
cpu3:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,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,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 0, core 3, package 0
cpu4 at mainbus0: apid 1 (application processor)
cpu4: Intel(R) Core(TM) i7-10610U CPU @ 1.80GHz, 1795.82 MHz, 06-8e-0c
cpu4:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,API

Re: Microphone not working on Gen8 ThinkPad X1 Carbon

[Ax0n]

On Mon, Mar 29, 2021 at 4:17 AM Alexandre Ratchov  wrote:

> in short, on these machines, the microphone is not connected to the HD
> audio codec (exposed by the azalia driver), but to another "intel
> smart sound technology" chip for which OpenBSD has no driver.
>
> If gen8 are the same, until this get fixed, I'd suggest using a
> *full-duplex* USB audio headset for audio-conferencing.
>

Thanks for the hints, Alexandre. Your TRRS comment in particular got my
creative juices flowing.

I have a ham radio handheld microphone with a TRRS plug on it, and while
it's wired COMPLETELY wrong for a TRRS headset, plugging it in and yelling
into the speaker while recording with Audacity shows audio levels on the VU
meter, and I can play it back properly. This tells me the Gen8 Thinkpads
have a TRRS jack and that the azalia(5) driver microphone input is using
the back-most contact as microphone input regardless if a device is plugged
in (hence the very low level of static-looking movement on the VU meters in
Audacity when trying to record earlier). I am positive I can just go get a
cheap TRRS headset and I should be good to go.

I do also have a broken-in-two Turtle Beach gaming headset my wife used to
use, with a USB sound device built-in. Plugging that in and frobbing
sndiod's flags per the Multimedia FAQ, I was also able to record audio from
snd/1 handily, so I now have two quite reasonable options for all my
streaming/recording/conferencing needs. I'd love to help test patches for
the integrated mic should someone attempt to tackle it. I'm not much of a
software developer, though, and don't have much to add aside from testing.

Ty,
--ax0n

Firefox, Chrome, Libreoffice bogus syscall on -current

[Ax0n]

I had been running #1471 since December 5th without issue, and this week
upgraded to the latest snapshot (#1567) after which some apps such as
Firefox won't run. They display "msyscall  a8000 error" followed by a
core dump. dmesg(1) shows a bogus syscall. I did ensure that I had properly
sysmerged and updated packages.I waited until the next snapshot hit
mirrors, and verified that this issue persists with build #1572 and fresh
packages as well. Lenovo X1 Carbon Gen 8. dmesg in body. I can put core
dumps somewhere if it helps.

OpenBSD 7.4-current (GENERIC.MP) #1572: Wed Dec 27 03:22:15 MST 2023
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 16758042624 (15981MB)
avail mem = 16230166528 (15478MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.2 @ 0x6cbac000 (70 entries)
bios0: vendor LENOVO version "N2WET36W (1.26 )" date 03/25/2022
bios0: LENOVO 20U9S1QP00
efi0 at bios0: UEFI 2.7
efi0: Lenovo rev 0x1260
acpi0 at bios0: ACPI 6.1
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT SSDT SSDT SSDT SSDT TPM2 SSDT HPET APIC MCFG
ECDT SSDT SSDT SSDT NHLT BOOT SSDT LPIT WSMT SSDT DBGP DBG2 MSDM BATB DMAR
ASF! UEFI FPDT
acpi0: wakeup devices GLAN(S4) XHC_(S3) XDCI(S4) HDAS(S4) RP01(S4) PXSX(S4)
RP02(S4) PXSX(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) PXSX(S4) RP06(S4)
PXSX(S4) RP07(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 2399 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-10610U CPU @ 1.80GHz, 1880.50 MHz, 06-8e-0c,
patch 00f8
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,SMX,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,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,IBRS_ALL,SKIP_L1DFL,MDS_NO,TSX_CTRL,MISC_PKG_CT,ENERGY_FILT,FB_CLEAR,RRSBA,GDS_CTRL,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB
64b/line 4-way L2 cache, 8MB 64b/line 16-way L3 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) i7-10610U CPU @ 1.80GHz, 1795.08 MHz, 06-8e-0c,
patch 00f8
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,SMX,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,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,IBRS_ALL,SKIP_L1DFL,MDS_NO,TSX_CTRL,MISC_PKG_CT,ENERGY_FILT,FB_CLEAR,RRSBA,GDS_CTRL,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
cpu1: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB
64b/line 4-way L2 cache, 8MB 64b/line 16-way L3 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Core(TM) i7-10610U CPU @ 1.80GHz, 1791.52 MHz, 06-8e-0c,
patch 00f8
cpu2:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,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,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,IBRS_ALL,SKIP_L1DFL,MDS_NO,TSX_CTRL,MISC_PKG_CT,ENERGY_FILT,FB_CLEAR,RRSBA,GDS_CTRL,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
cpu2: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB
64b/line 4-way L2 cache, 8MB 64b/line 16-way L3 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 6 (application processor)
cpu3: Intel(R) Core(TM) i7-10610U CPU @ 1.80GHz, 1791.22 MHz, 06-8e-0c,
patch 00f8
cpu3:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,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,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,IBRS_ALL,SKIP_L1DFL,MDS_NO,TSX_CT

Re: Firefox, Chrome, Libreoffice bogus syscall on -current

[Ax0n]

On Thu, Dec 28, 2023, 11:00 Stuart Henderson 
wrote:

Not sure how much core dumps will help, but if you can try running
the binaries with problems with LD_DEBUG set in the environment (to
anything) and capture output (e.g. using script(1) as it will likely be
copious) that might give clues.

I'll  likely try another new snapshot today, then try the above if it
persists.

How are you updating packages / which mirror? Do you have anything left
in /usr/local/{bin,sbin,lib} etc which still reference any libc.so.97?

Upgrade process:
doas sysupgrade
login
doas sysmerge
doas pkg_add -uiv
doas reboot

/etc/installurl is http://mirrors.sonic.net/pub/OpenBSD

And yes, quite a lot of stuff referencing libc.so.97.1  in /usr/local - 223
files in bin, 361 in lib, 0 in sbin.

I've been running -current and just rolling snapshots on this machine since
March 2021, somewhere between 6.8 and 6.9-RELEASE. It was initially
configured with softraid crypto the old manual-intervention-during-install
way. Several times along the way, I've ended up with a box that thinks it's
on -RELEASE but is a chimaera of -CURRENT snapshot stuff. The most recent
happened in the days leading up to 7.4-RELEASE. In these cases, I just add
-s the sysupgrade and/or -D snap to pkg_add to get past it.

It's possible I need a fresh install. Everything is backed up weekly.

Are you doing anything unusual with LD_PRELOAD (e.g. using a socks
wrapper)?

No. Not at all.

Re: Firefox, Chrome, Libreoffice bogus syscall on -current

[Ax0n]

On Fri, Dec 29, 2023, 11:21 Theo de Raadt  wrote:

> Then your machine is not -current, not by a long shot.
>
> We moved to libc.so.98.0 on Dec 12.
>
> At least two rounds of new packages have shown up since then.
>
> I do believe there are circumstances where pkg_add fails to update
> library packages.


It turns out there was a list of 100 some packages that couldn't be
upgraded with pkg_add -u and I just wasn't reading it, as the heart of the
message scrolled way off the screen.

I programmatically pkg_delete'd those and those which relied upon them, and
re-installed only what I really needed and all is well in the world once
again.

Sorry for the distraction, and thanks for the guidance.  Even this little
adventure was still smoother than any other OS I've used.

Re: Firefox, Chrome, Libreoffice bogus syscall on -current

[Ax0n]

On Fri, Dec 29, 2023 at 7:33 PM Stuart Henderson 
wrote:

> Pity, without the deletes a transcript of a run of pkg_add -u -v
> might have shown why the packages didn't get updated. They should have,
> and in most cases they do.
>

Here's the pkg_add -uiv output that I saved while removing stuff. There's a
bit of detail there, maybe enough to unwind the problem?

https://gist.github.com/n0xa/934776b75ef520738c0fca16aa8b1071

Re: accidentally overwritten wrong drive with DD, please help

[Ax0n]

cd /dev && doas sh MAKEDEV sdX (or whatever the base device name is).

man 8 MAKEDEV for more info on that

On Sun, Jun 23, 2024 at 6:59 AM Anon Loli  wrote:

> ...
> problem with the computer detecting the drives (they aren't in /dev at
> all, but
> dmesg is reading them OK),
>