Re: ubnt unfi stable from ports doesn??t start with rcctl but as root

[Bryan Vyhmeister]

On Tue, Jan 08, 2019 at 03:27:39PM +0100, Thomas Huber wrote:
> just upgrade the Unifi Controller net/unifi/stable (version 5.8.30) from
> ports.
> The controller service doesn??t start wit rcctl(8) but works fine when
> running as root.
> My guess is that _unifi is not allowed to start monogd but don??t have a
> clue how to fix this...
> Does it matter if databases/mongo is install from ports or pkg?
> I installed all dependecies manually with pkg_add(1)
> 
> Any idea where to look?

On my UniFi box (which is running -current and unifi-5.9.32), I also enabled
mongod to start at boot.

rcctl enable mongod
rcctl enable unifi

It has been running fine for me for years that way.

Bryan

Re: join id cannot be integer

[Bryan Vyhmeister]

On Wed, Aug 08, 2018 at 05:43:08PM +0200, Stefan Sperling wrote:
> join and nwid are mutually exclusive commands.

Apparently I did not read the join info properly. Thanks for the clue
stick and sorry for the noise.

Bryan

join id cannot be integer

[Bryan Vyhmeister]

I have not investigated the full scenario here but using the new join
option for wireless network configuration does not seem to work if I use
an ID of 0, 1, or 2 and probably others. Is this expected? The man page
seems to indicate that this should work fine. From ifconfig(8):

"The id can either be any text string up to 32 characters in length, or
a series of hexadecimal digits up to 64 digits. Any necessary wpakey or
nwkey arguments should be specified on the same line."

Here is the scenario to test.

/etc/hostname.iwm0:
join 0 nwid TEST wpakey 1234567890
dhcp

This will not work and I will end up associated to the AP but status
will always stay as no network.

/etc/hostname.iwm0:
join TEST nwid TEST wpakey 1234567890
dhcp

This will work as expected.

Bryan

Re: Stockholm anoncvs rsync mirror not updating

[Bryan Vyhmeister]

This is probably due to the Hackathon from July 8-13 and that at least
some developers are probably still traveling. Snapshots are often not
built for public use during that time from my observation but it is
unusual for cvs changes to not be fanning out to the mirrors. Perhaps
some maintenantce issue or something else is going on. It is not
specific to one mirror as far as I can tell from two other Canadian and
US mirrors using cvsync or rsync for cvs.

Bryan

Re: Configuration of a umb device

[Bryan Vyhmeister]

On Mon, Jul 09, 2018 at 12:37:42AM +, salan...@ouvaton.org wrote:
> Could someone direct me as to how to set up my computer such that I can
> get internet access through? I installed a this model of US Mobile SIM card.
> https://www.usmobile.com/shop/product/Triple-Cut-GSM-SIM-Card
> 
> Then I ran the commands below. What do I need to do next?
> 
> $ dmesg|grep umb 
> umb0 at uhub0 port 4 configuration 1 interface 6 "Lenovo N5321 gw" rev 
> 2.00/0.00 addr 2
> $ ifconfig apn pwg pin 1234 class 2G roaming up
> $ ifconfig
> umb0: flags=8851 mtu 1500
> index 5 priority 0 llprio 3
> roaming enabled registration home network
> state up cell-class EDGE rssi -77dBm speed 60.4Kps up 242Kps down
> SIM initialized PIN valid (3 attempts left)
> subscriber-id 310260855911295 ICC-id 8901260851159112954 provider US Mobile
> device KRD 131 30/123 - R1A/1 IMEI 004401701565398 firmware R3C11 (Pro), 
> R4A10 (App)
> APN pwg
> dns 10.177.0.34 10.177.0.210
> status: active
> inet 100.144.58.19 --> 100.144.58.18 netmask 0xfff8

The general idea is you need to add a route that points to the
interface rather than the IP address. You still need an IP address for
the route command. I wrote a script that automates bringing up a umb(4)
connection. It is configured by default for AT

https://raw.githubusercontent.com/brycv/openbsd-scripts/master/cell-setup

To add the default route, use the following command.

route add -ifp umb0 default 100.144.58.19

This command would be correct for the information you have above. The
-ifp option allows you to specify the name of the interface you are
using for the default route. Then you also add the IP address you are
assigned since route(8) requires an IP address for the command.

The script also adds the dns entry (AT only provides one where it
looks like you get two on the dns line) to /etc/resolv.conf so
everything works as expected.

Bryan

Re: 4k display on integrated Intel graphics?

[Bryan Vyhmeister]

On Fri, Jun 29, 2018 at 11:04:12PM +0200, Maximilian Pichler wrote:
> Thanks for explaining. Some shaking could be lived with...

I went ahead and bought a Plugable USB-C to DisplayPort cable to confirm
that there are no issues. I unplugged my mDP to DP cable from the
NUC6i7KYK and the HP Z27s 3840x2160 monitor and replaced it with the
USB-C to DP cable and everything works exactly as before. Running xrandr
reports that I am running on DP-2 at 3840x2160 at 60Hz.

> I just realized that some monitors (e.g. LG 27UD88) can connect via
> USB-C directly, whilest serving as a USB hub and power source. Would
> this be expected to work as well?

This type of thing should work fine as the other poster said also. This
charging functionality is not OS-dependent and should work because of
device firmware. USB-C can carry different types of signals that have
been around a while and can be quite convenient as a result.

Bryan

Re: 4k display on integrated Intel graphics?

[Bryan Vyhmeister]

On Fri, Jun 29, 2018 at 06:01:06PM +0200, Maximilian Pichler wrote:
> Does this mean it's unlikely to work with an USB-C-to-DP adapter or
> just hasn't been tried?

It should work fine because the USB-C ports have DisplayPort signaling
built-in and I would not expect any issues.

https://www.displayport.org/displayport-over-usb-c/

HDMI 1.4 does not support 4k at 60Hz like HDMI 2.0 does but HDMI 2.0 is
not supported as you found out. I have not tested USB-C to DP
specifically with my NUC6i7KYK but it does drive 4k over DisplayPort
which should be the same with USB-C to DP. I do get some weird artifacts
like the screen "shaking" back and forth a bit until I launch Xorg which
then works perfectly.

Bryan

Re: FAQ: dmesg archive

[Bryan Vyhmeister]

Looking at Supermicro's page, it's pretty easy to get some answers.

http://www.supermicro.com/products/system/Mini-ITX/SYS-E300-9A-8CN8.cfm

The 4 gigabit Intel i350-AM4 controllers should work fine since they do
on other systems of the previous C2xxx systems. However, the 4 gigabit
Marvell 88E1543 controllers are unlikely to work as best I can tell.
Doing an apropos search for Marvell does not yield a man page that
mentions this chipset. Not much has happened with msk(4) or sk(4)
recently.

https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pci/if_msk.c
https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pci/if_sk.c

So you probably will not have great support at this time. Something like
the E300-8D might be a better choice. I have been looking at the X10SDV
boards (especially the X10SDV-2C-TP4F and X10SDV-2C-TP8F) personally and
will be building some firewalls with them soon.

Bryan

Re: Ubiquiti Networks EdgeRouter 6P

[Bryan Vyhmeister]

On Fri, May 25, 2018 at 06:43:57PM +, Chris Jones wrote:
> I see that the Ubiquiti EdgeRouter 6P is supported under octeon port.
> Just wondering if anyone on the list is running OpenBSD 6.3 or current
> on the EdgeRouter 6P? I'm mainly interested in the performance of this
> unit as a home firewall but also interested in using it for other SMB
> applications.

Yes, I am running -current on a number of EdgeRouter 4 and 6P units.
They seem to work quite well. Some cursory routing between subnets
performance tested with iperf3 yields a max of around 450 Mbps
throughput. There is a new octcrypto(4) driver which should be
interesting and is on my list to test for ipsec.

http://man.openbsd.org/octcrypto

The caveat I have seen is that the USB 3.0 controller is more finicky
than I would like but it seems to be working better recently with
xhci(4) fixes that have gone in over the last few months. I have had
good success with Samsung Fit USB 3.0 flash drives but had some initial
problems with Samsung T3/T5 USB 3.0 SSD drives erroring out with USB
problems. I use OpenBSD through resflash for the most part but vanilla
OpenBSD works fine although the library reordering is fairly slow (a
minute or two I think) on boot.

> I would generally be running standard network services plus 
> isakmpd/iked, ospfd, unbound. Also, is it fair to assume the PoE ports 
> are just active by default?

I have not done any ipsec but the rest work fine. The PoE ports do not
work at all under OpenBSD. PoE is off unless enabled through the EdgeOS
interface and there is no way to do that through OpenBSD. I would
recommend the EdgeRouter 4 unless you need to run from 24V DC power or
need the extra ports but PoE is useless unfortunately. Also, unlike with
the shared copper/fiber ports on the EdgeRouter Pro and UniFi Security
Gateway Pro, the fiber port on the ER-4/ER-6P works fine as an
additional port (cnmac0 actually).

Bryan

Re: gcc-4.9.4 package build signal 11 [Segmentation fault] on Ubiquiti Unifi Security Gateway

[Bryan Vyhmeister]

I have had a few discussions with visa@ about builds on OpenBSD/octeon.
For ports builds, 1GB of memory like in the EdgeRouter 4 and 6 is too
little to build big things like gcc which is required for quite a few
things. The EdgeRouter Lite, EdgeRouter PoE, and USG are even worse with
512MB of memory. Also, the EdgeRouter 4 and 6 have some issues with the
USB 3.0 controller that visa@ has not been able to work out yet. It's
pretty difficult to get any insight into what is happening with the USB
3.0 controller. The ER4 and ER6 work reasonably well with Samsung USB
Fit USB 3.0 flash drive but occasionally weird errors happen and the
system freezes up or panics. I was not able to get a Samsung T3 or T5
USB SSD to work with the ER4 or ER6.

The best route for a readily available machine for OpenBSD/octeon builds
is either the USG Pro 4 or the EdgeRouter Pro. They both come with 2GB
of memory but can be upgraded with up to 8GB of memory. Unlike the USB
flash drives in the USG and EdgeRouter Lite/PoE, the internal storage is
soldered on as was said in this thread already. The best route for
storage I have found thus far is a USB SSD like the Samsung T3 or T5. I
have not tested any others at this point but others probably work as
well.

For the EdgeRouter Pro, I have it running from a 250GB Samsung T3 USB
SSD and have upgraded it with an 8GB SODIMM of DDR3 1333MHz memory. The
part number that worked for the EdgeRouter Pro is Patriot PSD38G13332S.
I found this information from the UBNT forums.

For the USG Pro 4, I bought the same Patriot memory but had all sorts of
crashes and problems. I'm not sure if the memory chip is bad or if it is
just expecting different memory (have not had time to test) but I looked
at the factory memory in the USG Pro 4 and bought similar memory which
works fine. The factory chip is Kingston KVR16S11S6/2. I bought a set of
Kingston KVR16S11K2/16 which is two 8GB chips. They work perfectly and I
plan to get another USG Pro 4 for a second build machine to utilize the
second 8GB chip I have.

With 8GB of memory, most ports builds work fine including gcc but
occasionally I see some weird error that usually disappears with
restarting the dpb(1) build.

Bryan

Re: AMD Pro A10/A12 Radeon R7 Support

[Bryan Vyhmeister]

On Tue, Jan 23, 2018 at 02:51:37PM +1100, Jonathan Gray wrote:
> The GCN parts like the 7750 (Cape VERDE) 7870 (PITCAIRN) will use
> the radeon xorg driver but will not have acceleration until the userland
> parts are sorted out which involves changing how LLVM is built, adding
> additional dependencies like libelf to base or xenocara and changing
> how Mesa is built.
> 
> I am looking into a radeondrm update that would add modesetting support
> for second generation GCN/sea islands parts and some more first
> generation southern islands parts.
> 
> ie, OLAND/HAINAN/BONAIRE/KABINI/MULLINS/KAVERI/HAWAII.

Thanks for the clarification. I will stick with Intel integrated
graphics for now until that gets sorted out somewhere down the line.
Thank you!

Bryan

Re: AMD Pro A10/A12 Radeon R7 Support

[Bryan Vyhmeister]

On Tue, Jan 23, 2018 at 11:57:35AM +1100, Jonathan Gray wrote:
> On Mon, Jan 22, 2018 at 10:43:03AM -0800, Bryan Vyhmeister wrote:
> > I have been looking at the new Lenovo ThinkPad A275 which is much like
> > the X260/X270 but with AMD Pro A10 or A12 chip and graphics. I am
> > interested in looking at something other than Intel for the first time
> > in more than a decade. I am interested in radeondrm(4) support for any
> > of the options available which are the AMD Pro A10-8730B, AMD Pro
> > A10-9700B, or AMD Pro A12-9800B. I am personally most interested in
> > ordering the AMD Pro A12-9800B. Any possilibity that radeondrm(4) might
> > work for these chips in some fashion?
> 
> CARRIZO parts like that would require a new amdgpu drm driver.

Understood. I will not get an A275 then. As far as radeondrm(4) support
goes, is my understanding from previous discussions correct that Radeon
HD 7750 or 7870 cards have kernel support but would have to be used
through the modesetting(4) driver in Xorg? I am still looking at those
cards for 4k monitor support for multiple monitors on a system that does
not have integrated graphics (Xeon E5 for example). In particular the
four mDP or six mDP cards are interesting to me. Thanks again.

Bryan

AMD Pro A10/A12 Radeon R7 Support

[Bryan Vyhmeister]

I have been looking at the new Lenovo ThinkPad A275 which is much like
the X260/X270 but with AMD Pro A10 or A12 chip and graphics. I am
interested in looking at something other than Intel for the first time
in more than a decade. I am interested in radeondrm(4) support for any
of the options available which are the AMD Pro A10-8730B, AMD Pro
A10-9700B, or AMD Pro A12-9800B. I am personally most interested in
ordering the AMD Pro A12-9800B. Any possilibity that radeondrm(4) might
work for these chips in some fashion?

Bryan

Re: iwm0 can't load firmware AC-3168

[Bryan Vyhmeister]

On Mon, Nov 13, 2017 at 08:55:36PM +, Stuart Henderson wrote:
> On 2017-11-13, Bryan Vyhmeister <br...@bsdjournal.net> wrote:
> > On Mon, Nov 13, 2017 at 11:08:32AM -0800, Sha'ul wrote:
> >> Running 6.2-release, after install rebooted and got iwm0 firmware from
> >> re0. Now can not load firmware. If this makes a difference, Intel graphics
> >> 620 only gives me a black screen, no kernel panic, and system seems to
> >> hang when I manually do startx.
> >
> > You have a Coffee Lake CPU which is not yet supported by inteldrm(4).
> > Up to Kaby Lake is supported by 6.2. You should be able to use wsfb(4)
> > for Xorg until inteldrm(4) support arrives. As for the iwm(4) firmware,
> > see:
> >
> > https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pci/if_iwmreg.h
> >
> > At the point of version 1.25, 3168 firmware had to be installed by hand.
> > The iwm-firmware package has not yet been updated to include those files
> > as far as I can tell. Someone else can point you to where the firmware
> > might be available from.
> >
> 3168 firmware was added in April, it is included in the version that
> will be installed if you run fw_update on 6.2.

Sorry for the misinformation. I should have checked /etc/firmware first.
The iwm-3168-22 file is right there from fw_update as you said.

Bryan

Re: iwm0 can't load firmware AC-3168

[Bryan Vyhmeister]

On Mon, Nov 13, 2017 at 11:08:32AM -0800, Sha'ul wrote:
> Running 6.2-release, after install rebooted and got iwm0 firmware from
> re0. Now can not load firmware. If this makes a difference, Intel graphics
> 620 only gives me a black screen, no kernel panic, and system seems to
> hang when I manually do startx.

You have a Coffee Lake CPU which is not yet supported by inteldrm(4).
Up to Kaby Lake is supported by 6.2. You should be able to use wsfb(4)
for Xorg until inteldrm(4) support arrives. As for the iwm(4) firmware,
see:

https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pci/if_iwmreg.h

At the point of version 1.25, 3168 firmware had to be installed by hand.
The iwm-firmware package has not yet been updated to include those files
as far as I can tell. Someone else can point you to where the firmware
might be available from.

Bryan

Re: Helping out

[Bryan Vyhmeister]

On Tue, Aug 01, 2017 at 08:19:23PM -0400, Radoslav_Mirza wrote:
> Dear Group, Are there any places to start helping out for a beginner?
> Any junior jobs or todo lists?
> 
> I have a new Ryzen 1700 running OpenBSD so maybe I could help with
> some benchmark tests etc.
> 
> Any pointers of where to go would be great!

There was a recent discussion about ProtonMail not sending plain text
email which this list expects. I would suggest sending with another
address and sending in plain text. Check the archives for more info
about it but base64 encoded emails (like from ProtonMail) will likely be
ignored. Hopefully ProtonMail will correct this problem but they have
"started" on it for more than a year.

Bryan

Re: touchpad input driver: testing needed

[Bryan Vyhmeister]

On Tue, Aug 01, 2017 at 10:12:05PM +0200, Ulf Brosziewski wrote:
> I have the impression that multi-finger clicks are popular
> among Mac users, is it correct?  However, if the new driver
> works it should offer software button areas at the bottom
> edge of the touchpad, as elsewhere.  Are they missing?
> Are they too small?  Or is it "simply" not your habit? Anyway,
> there must be some bug or misconfiguration, the "tp" fields
> are missing in the wsconsctl output:

You are correct. Having used Macs for years and years, I am very
accustomed to multi-finger clicks and they are my "habit" now. I was not
aware of the software button areas. If I hold down a click in the middle
of the touchpad but at the bottom edge for about one second or a little
more, when I release that click, I get a button2 which allows paste.
That works well enough. I have not yet figured out how to get button3
except for Ctrl click.

> > # wsconsctl | grep mouse
> > mouse.type=usb
> > mouse.rawmode=1
> > mouse.scale=0,0,0,0,0,0,0
> > mouse1.type=elantech
> > mouse1.rawmode=0
> > mouse1.scale=-4620,5140,-150,6600,0,0,0
> >
> 
> Would you mind to report the output of the following command?
> # wsconsctl mouse1.tp.param=64,65

Here is the output:

mouse1.tp.param -> 64:1,65:1

> And special thanks again for all your work,

Thank you for your development. I am very excited to see these changes
in OpenBSD.

Bryan

Re: touchpad input driver: testing needed

[Bryan Vyhmeister]

On Mon, Jul 31, 2017 at 05:37:00PM -0700, Bryan Vyhmeister wrote:
> On Mon, Jul 31, 2017 at 08:09:31PM -0400, Ted Unangst wrote:
> > Bryan Vyhmeister wrote:
> > > On Mon, Jul 31, 2017 at 11:02:28PM +0200, Ulf Brosziewski wrote:
> > > > for you.  As always, a dmesg would be appreciated.  The output of
> > > > # wsconsctl | grep 'mouse'
> > > > could also be of interest here (you must run it as root).
> > > 
> > > This report is from a MacBookAir7,2 which is a 2015 13-inch MacBook Air.
> > > Anything more than a regular click is not working as can be seen from
> > > the wsconsctl output. I was using synclient to configure previously
> > > which did allow the other settings.
> > 
> > Can you also share your synclient settings?
> 
> Sure. I was using synclient(1) with the following settings but
> synclient(1) no longer works with this driver.
> 
> synclient ClickFinger2=2 ClickFinger3=3 PalmDetect=0 PalmMinWidth=4 
> PalmMinZ=100

I wanted to clarify this for the record. Regular click is working fine
as is two finger scrolling on the MacBook Air. What is not working is
multi-finger click but that is not currently part of the driver which is
probably why my synclient settings are significant. I noticed this on
the MacBook Air because there are no separate touchpad buttons as there
are on everything else I tested. I would love to see multi-finger click
as part of the driver since it is essential on any touchpad without
separate buttons which seems to be the more common scenario these days
for laptops. Thanks again.

Bryan

Re: touchpad input driver: testing needed

[Bryan Vyhmeister]

On Mon, Jul 31, 2017 at 11:02:28PM +0200, Ulf Brosziewski wrote:
> for you.  As always, a dmesg would be appreciated.  The output of
> # wsconsctl | grep 'mouse'
> could also be of interest here (you must run it as root).

Here is another report from a Lenovo N22. This system has a Synaptics
touchpad as well and works perfectly with the new driver.

# wsconsctl | grep mouse
mouse.type=synaptics
mouse.rawmode=0
mouse.scale=1472,5788,1408,4966,0,58,94
mouse.tp.tapping=0
mouse.tp.scaling=0.164
mouse.tp.swapsides=0
mouse.tp.disable=0

Bryan


OpenBSD 6.1-current (GENERIC.MP) #27: Mon Jul 31 12:56:47 MDT 2017
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 4117872640 (3927MB)
avail mem = 3986718720 (3802MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xe0840 (61 entries)
bios0: vendor Lenovo version "0YCN17WW" date 03/31/2016
bios0: LENOVO 80S6
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP UEFI MCFG SSDT SSDT SSDT SSDT SSDT APIC UEFI MSDM BATB 
FPDT UEFI BGRT tCSR
acpi0: wakeup devices XHC1(S4) BRC1(S0) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimcfg0 at acpi0 addr 0xe000, bus 0-63
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Celeron(R) CPU N3050 @ 1.60GHz, 1600.36 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT
cpu0: 1MB 64b/line 16-way L2 cache
cpu0: TSC frequency 1600363400 Hz
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 80MHz
cpu0: mwait min=64, max=64, C-substates=0.2.0.0.0.0.3.3, IBE
cpu1 at mainbus0: apid 4 (application processor)
cpu1: Intel(R) Celeron(R) CPU N3050 @ 1.60GHz, 1600.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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT
cpu1: 1MB 64b/line 16-way L2 cache
cpu1: smt 0, core 2, package 0
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 115 pins
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (RP01)
acpiprt2 at acpi0: bus -1 (RP02)
acpiprt3 at acpi0: bus 2 (RP03)
acpiprt4 at acpi0: bus -1 (RP04)
acpiec0 at acpi0
acpicpu0 at acpi0
C2: state 6: substate 8 >= num 3
C3: state 7: substate 4 >= num 3: C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0
C2: state 6: substate 8 >= num 3
C3: state 7: substate 4 >= num 3: C1(1000@1 mwait.1), PSS
acpipwrres0 at acpi0: CLK0
acpipwrres1 at acpi0: CLK1
acpipwrres2 at acpi0: ID3C, resource for ISP3
acpipwrres3 at acpi0: USBC, resource for XHC1
acpipwrres4 at acpi0: FN00, resource for FAN0
acpitz0 at acpi0: critical temperature is 90 degC
acpibat0 at acpi0: BAT1 model "Harris Beach" serial 123456789 type LION oem 
"Intel SR 1"
"VPC2004" at acpi0 not configured
"MSFT0001" at acpi0 not configured
"SYN2F02" at acpi0 not configured
sdhc0 at acpi0: SDHA addr 0x91319000/0x1000 irq 45
sdhc0: SDHC 3.0, 200 MHz base clock
sdmmc0 at sdhc0: 8-bit, sd high-speed, mmc high-speed, dma
sdhc1 at acpi0: SDHB addr 0x91317000/0x1000 irq 46
sdhc1: SDHC 3.0, 200 MHz base clock
sdmmc1 at sdhc1: 4-bit, sd high-speed, mmc high-speed, dma
acpiac0 at acpi0: AC unit online
acpibtn0 at acpi0: LID0
acpibtn1 at acpi0: PWRB
"INT3400" at acpi0 not configured
"INT3403" at acpi0 not configured
"PNP0C0B" at acpi0 not configured
acpivideo0 at acpi0: GFX0
acpivout0 at acpivideo0: DD1F
cpu0: Enhanced SpeedStep 1600 MHz: speeds: 1601, 1600, 1520, 1440, 1360, 1280, 
1200, 1120, 1040, 960, 880, 800, 720, 640, 560, 480 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Braswell Host" rev 0x21
inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics" rev 0x21
drm0 at inteldrm0
inteldrm0: msi
inteldrm0: 1366x768, 32bpp
wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
"Intel Braswell Power" rev 0x21 at pci0 dev 11 function 0 not configured
sdhc2 at pci0 dev 18 function 0 vendor "Intel", unknown product 0x2296 rev 
0x21: apic 1 int 18
sdhc2: SDHC 3.0, 200 MHz base clock
sdmmc2 at sdhc2: 4-bit, sd high-speed, mmc high-speed, dma
ahci0 at pci0 dev 19 function 0 "Intel Braswell AHCI" rev 0x21: msi, AHCI 1.3.1
ahci0: PHY offline on port 0
ahci0: PHY offline on port 1
scsibus1 at ahci0: 32 targets
xhci0 at pci0 dev 20 function 0 "Intel Braswell xHCI" rev 0x21: msi
usb0 at xhci0: USB revision 3.0
uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev 3.00/1.00 
addr 1
"Intel Braswell TXE" rev 0x21 at pci0 dev 26 

Re: touchpad input driver: testing needed

[Bryan Vyhmeister]

On Mon, Jul 31, 2017 at 08:09:31PM -0400, Ted Unangst wrote:
> Bryan Vyhmeister wrote:
> > On Mon, Jul 31, 2017 at 11:02:28PM +0200, Ulf Brosziewski wrote:
> > > for you.  As always, a dmesg would be appreciated.  The output of
> > > # wsconsctl | grep 'mouse'
> > > could also be of interest here (you must run it as root).
> > 
> > This report is from a MacBookAir7,2 which is a 2015 13-inch MacBook Air.
> > Anything more than a regular click is not working as can be seen from
> > the wsconsctl output. I was using synclient to configure previously
> > which did allow the other settings.
> 
> Can you also share your synclient settings?

Sure. I was using synclient(1) with the following settings but
synclient(1) no longer works with this driver.

synclient ClickFinger2=2 ClickFinger3=3 PalmDetect=0 PalmMinWidth=4 PalmMinZ=100

Bryan

Re: touchpad input driver: testing needed

[Bryan Vyhmeister]

On Mon, Jul 31, 2017 at 11:02:28PM +0200, Ulf Brosziewski wrote:
> for you.  As always, a dmesg would be appreciated.  The output of
> # wsconsctl | grep 'mouse'
> could also be of interest here (you must run it as root).

This report is from a MacBookAir7,2 which is a 2015 13-inch MacBook Air.
Anything more than a regular click is not working as can be seen from
the wsconsctl output. I was using synclient to configure previously
which did allow the other settings.

# wsconsctl | grep mouse
mouse.type=usb
mouse.rawmode=1
mouse.scale=0,0,0,0,0,0,0
mouse1.type=elantech
mouse1.rawmode=0
mouse1.scale=-4620,5140,-150,6600,0,0,0

Bryan


OpenBSD 6.1-current (GENERIC.MP) #27: Mon Jul 31 12:56:47 MDT 2017
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
RTC BIOS diagnostic error 
ff
real mem = 8469352448 (8077MB)
avail mem = 8206315520 (7826MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0x8afad000 (32 entries)
bios0: vendor Apple Inc. version "MBA71.88Z.0166.B26.1703211638" date 03/21/2017
bios0: Apple Inc. MacBookAir7,2
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP HPET APIC SBST ECDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT 
SSDT DMAR MCFG
acpi0: wakeup devices PEG0(S3) EC__(S3) HDEF(S3) RP01(S3) RP02(S3) RP03(S4) 
ARPT(S4) RP05(S3) RP06(S3) SPIT(S3) XHC1(S3) ADP1(S3) LID0(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) i7-5650U CPU @ 2.20GHz, 2200.37 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,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,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: TSC frequency 2200371760 Hz
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 100MHz
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-5650U CPU @ 2.20GHz, 2200.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,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,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) Core(TM) i7-5650U CPU @ 2.20GHz, 2200.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,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,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 1, core 0, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i7-5650U CPU @ 2.20GHz, 2200.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,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,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins
acpiec0 at acpi0
acpimcfg0 at acpi0 addr 0xe000, bus 0-155
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG0)
acpiprt2 at acpi0: bus 1 (RP01)
acpiprt3 at acpi0: bus 2 (RP02)
acpiprt4 at acpi0: bus 3 (RP03)
acpiprt5 at acpi0: bus 5 (RP05)
acpiprt6 at acpi0: bus 4 (RP06)
acpicpu0 at acpi0: C3(200@530 mwait.1@0x60), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: C3(200@530 mwait.1@0x60), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu2 at acpi0: C3(200@530 mwait.1@0x60), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu3 at acpi0: C3(200@530 mwait.1@0x60), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpisbs0 at acpi0: SBS0 model "bq20z451" serial 36068 type LION oem "DP"
"APP0001" at acpi0 not configured
"ACPI0008" at acpi0 not 

Re: touchpad input driver: testing needed

[Bryan Vyhmeister]

On Mon, Jul 31, 2017 at 11:02:28PM +0200, Ulf Brosziewski wrote:
> for you.  As always, a dmesg would be appreciated.  The output of
> # wsconsctl | grep 'mouse'
> could also be of interest here (you must run it as root).

Here is another report. This one is from a Lenovo LaVie Z with an
Elantech touchpad. So far seems to work just fine as well.

# wsconsctl | grep mouse
mouse.type=elantech
mouse.rawmode=0
mouse.scale=0,2800,0,1820,0,0,0
mouse.tp.tapping=0
mouse.tp.scaling=0.275
mouse.tp.swapsides=0
mouse.tp.disable=0

Thanks again!

Bryan


OpenBSD 6.1-current (GENERIC.MP) #27: Mon Jul 31 12:56:47 MDT 2017
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8485908480 (8092MB)
avail mem = 8222367744 (7841MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xdcef (23 entries)
bios0: vendor LENOVO version "/763A0400" date 04/02/2015
bios0: LENOVO 20FG0013US
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT FIDT ECDT MCFG HPET SSDT UEFI SSDT ASF! MSDM 
SSDT SSDT SSDT BGRT SSDT
acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) 
LID0(S3) PXSX(S3) RP01(S4) PXSX(S3) RP02(S4) PXSX(S3) RP03(S4) PXSX(S3) 
RP04(S4) PXSX(S3) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz, 2394.86 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,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,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,PT,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: TSC frequency 2394859830 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.2.4.1.1.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz, 2394.47 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,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,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,PT,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz, 2394.47 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,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,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,PT,SENSOR,ARAT
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 1, core 0, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz, 2394.47 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,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,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,PT,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins
acpimadt0: bogus nmi for apid 2
acpimadt0: bogus nmi for apid 1
acpimadt0: bogus nmi for apid 3
acpiec0 at acpi0
acpimcfg0 at acpi0 addr 0xf800, bus 0-63
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG0)
acpiprt2 at acpi0: bus -1 (PEG1)
acpiprt3 at acpi0: bus -1 (PEG2)
acpiprt4 at acpi0: bus 1 (RP01)
acpiprt5 at acpi0: bus -1 (RP02)
acpiprt6 at acpi0: bus 2 (RP03)
acpiprt7 at acpi0: bus 3 (RP04)
acpiprt8 at acpi0: bus -1 (RP05)
acpiprt9 at acpi0: bus -1 (RP06)
acpiprt10 at acpi0: bus -1 (RP07)
acpiprt11 at acpi0: bus -1 (RP08)
acpiec at acpi0 not configured
acpiec at acpi0 not configured
acpicpu0 at acpi0: C3(200@506 mwait.1@0x60), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: C3(200@506 mwait.1@0x60), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu2 at acpi0: C3(200@506 mwait.1@0x60), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu3 at acpi0: C3(200@506 mwait.1@0x60), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpipwrres0 at acpi0: PG00, resource 

Re: touchpad input driver: testing needed

[Bryan Vyhmeister]

On Mon, Jul 31, 2017 at 11:02:28PM +0200, Ulf Brosziewski wrote:
> for you.  As always, a dmesg would be appreciated.  The output of
> # wsconsctl | grep 'mouse'
> could also be of interest here (you must run it as root).

This is from a Lenovo ThinkPad X1 Carbon (4th Gen) which has a Synaptics
touchpad which has been working fine otherwise and appears to continue
to work fine with your driver.

# wsconsctl | grep mouse
mouse.type=synaptics
mouse.rawmode=0
mouse.scale=1472,5678,1408,4754,0,46,68
mouse.tp.tapping=0
mouse.tp.scaling=0.171
mouse.tp.swapsides=0
mouse.tp.disable=0
mouse1.type=ps2

Thanks for your work on this!

Bryan


OpenBSD 6.1-current (GENERIC.MP) #26: Mon Jul 31 08:42:35 MDT 2017
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 17011994624 (16223MB)
avail mem = 16490065920 (15726MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xb705e000 (65 entries)
bios0: vendor LENOVO version "N1FET49W (1.23 )" date 02/08/2017
bios0: LENOVO 20FBCTO1WW
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP UEFI SSDT SSDT ECDT HPET APIC MCFG SSDT SSDT DBGP DBG2 
BOOT BATB SSDT SSDT MSDM DMAR ASF! FPDT UEFI
acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP9(S4) XHCI(S3)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpiec0 at acpi0
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-6600U CPU @ 2.60GHz, 2808.00 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,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: TSC frequency 280800 Hz
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-6600U CPU @ 2.60GHz, 2808.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,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,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz, 2808.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,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,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 1, core 0, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz, 2808.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,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,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 120 pins
acpimcfg0 at acpi0 addr 0xf800, bus 0-63
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG0)
acpiprt2 at acpi0: bus -1 (PEG1)
acpiprt3 at acpi0: bus -1 (PEG2)
acpiprt4 at acpi0: bus 2 (EXP1)
acpiprt5 at acpi0: bus 4 (EXP3)
acpiprt6 at acpi0: bus 5 (EXP5)
acpiprt7 at acpi0: bus -1 (EXP9)
acpicpu0 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu2 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu3 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpipwrres0 at acpi0: PUBS, resource for XHCI
acpipwrres1 at acpi0: PG00, resource for PEG0
acpipwrres2 at acpi0: PG01, resource for PEG1
acpipwrres3 at acpi0: PG02, resource for PEG2

Re: 6.1 dhcpd

[Bryan Vyhmeister]

On Tue, Apr 18, 2017 at 11:01:47AM +0200, Bastien Durel wrote:
> Since I upgraded to 6.1, my printer does not get its IP from dhcpd
> anymore.
> 
> Printer is a xerox phaser 6022.
> 
> dhcpd gets dhcp requests and reponds to it (I've show packets with
> tcpdump, and here are the logs)

I am seeing this same thing on my core router cluster. It's the
DHCPDISCOVER followed up with DHCPOFFER that never gets a DHCPACK. I
have a single customer with a router made by Hon Hai Precision (I think
it's a Vonage something or other) that will now not get an IP address
after upgrading to 6.1 on Sunday. Everything was working fine with 6.0
up until now.

Bryan

Re: OpenBSD 6.1-snapshot boot issues in bhyve

[Bryan Vyhmeister]

On Wed, Apr 05, 2017 at 12:46:27PM +1000, Jason Tubnor wrote:
> Just wondering if anyone else is seeing the same issue I am booting a
> 6.1-snapshot in bhyve? In preparation for the 6.1 pending release, I
> have tried to spin up 6.1-snap to iron out any issues in bhyve but I
> don't get very far into the installation process:

I noticed the same thing last week but was not able to report until
yesterday and noticed you already had. Michael Dexter suggested using
the bhyve "-w" flag and that works as a workaround for now.

Bryan

Re: Hardware recommendations for compact 1U firewall

[Bryan Vyhmeister]

On Thu, Dec 15, 2016 at 02:04:04PM -0800, OpenBSD lists wrote:
> I recently replaced a pair of Soekris 6501's (BIOSes on both went blank)
> with some SuperMicro X11SBA-LN4F-O boards, SATA-DOM-064s, the CSE505-203B
> and 4 GB 1600 Mhz DRR3 sticks.
> 
> Draws so little power that it looks like the Power Supply is wasting more in
> the AC-DC conversion process than the system itself is using. Considering
> replacing it with a 60w 12v power adapter like some of the other systems
> use.
> 
> Memory latency is very low and very consistent since the CPU cores and the
> memory run at the same frequency.
> 
> I was considering the A1SAi-2550F, but these were cheaper, lower power, had
> a shorter time to ship, and don't have the Intel Management Engine in them.
> 
> Only problem is that most of the sensors don't seem to be supported:
> 
> # sysctl hw.sensors
> hw.sensors.cpu0.temp0=39.00 degC
> hw.sensors.acpitz0.temp0=26.80 degC (zone temperature)

I also have three X11SBA-LN4F and two X11SBA-F boards. They also have
the benefit of using mSATA SSDs which most of the Atom C2X5X boards
(except for A1SRM-LN5F/LN7F) do not. They can also run direct from DC.
One of my projects for the new year is get these up and running but I
did notice the same with sensors. Prior to shortly before 6.0, xhci(4)
would fail (I forget the message) and the machine was unusable for
OpenBSD. Now that xhci(4) has been fixed, it works fine.

I asked Supermicro about the 12V voltage range and they said 12V +/- 10%
on A1SAi/A1SRi and 12V +/- 5% on the X11SBA. I was originally planning
on hooking these direct to batteries but decided to use a DC-DC power
supply from mini-box.com which allows hooking to 12V or 24V battery
banks without being worried about voltage changes. I put this in the
CSE-505-203B case in place of the original power supply.

One of my goals is to run performance tests between the A1SAi/A1SRi
boards and the X11SBA.

Bryan

Re: Hardware recommendations for compact 1U firewall

[Bryan Vyhmeister]

On Thu, Dec 15, 2016 at 07:51:40PM +0100, Hrvoje Popovski wrote:
> On 15.12.2016. 12:30, Stuart Henderson wrote:
> > If you want to cut down on weight+noise at the expense of more cost
> > and a less powerful cpu, maybe APU2 in a 1U case or something like
> > supermicro SYS-5018A-FTN4.
> 
> has anyone dmesg from SYS-5018A-FTN4 box? i'm interesting in intel qat

There is no support for Intel QAT (sometimes called Quick Assist) in
OpenBSD and that's not likely to change anytime soon. Some support is
supposedly coming to FreeBSD (by way of pfSense and some commerical
sponsorship or something) but I have not seen anything recently about
that.

Because Intel QAT is not supported, it is better to use one of the
Supermicro A1SAi boards (for the slight speed increase) rather than the
A1SRi-2758F that comes in the SYS-5018A-FTN4. The A1SRi boards do work
fine though.

I put together my own systems like this which only takes a few minutes
with Supermicro parts. I use the same case which is the Supermicro
CSE-505-203B, a few Noctua 40mm fans (which are much quieter and
probably not necessary), and then one of the A1SAi-2750F, A1SAi-2550F,
A1SRM-LN7F-2758F, A1SRM-LN7F-2358F, A1SRi-2758F, or A1SRi-2558F. I also
have a few A1SAM-2550F boards but those are not booting from USB sticks
for some reason. All of the others above work just fine. All that's left
is some sort of storage (like a 64GB SanDisk SSD, Supermicro SuperDom,
or USB stick with resflash) and memory (I use Kingston ECC SO-DIMMs) and
it works great. I have quite a few of these at tower sites, datacenter
installations, and as home and business routers. As a bonus, all of the
above can be powered directly from 12V if you want to wire them up that
way. I have started doing that at DC sites and to run from batteries.

Where portability is needed, the CSE-505-203B fits great in any of the
SKB short depth cases like hte SKB R4S or R6S.

Below is a dmesg for the A1SRi-2758F. This particular router is running
BGP, OSPF, and CARP on the inside as well as DNS and DHCP. It is running
5.8 so not the most recent (it is due to be upgraded in the next week)
but Intel QAT does show up as:

vendor "Intel", unknown product 0x1f18 (class processor subclass Co-processor, 
rev 0x02) at pci0 dev 11 function 0 not configured

Bryan



OpenBSD 5.8-stable (GENERIC.MP) #9: Thu May 26 22:05:56 PDT 2016
r...@amd64.example.com:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 17134739456 (16340MB)
avail mem = 16611545088 (15842MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0x7f4ee000 (53 entries)
bios0: vendor American Megatrends Inc. version "1.1" date 01/09/2015
bios0: Supermicro A1SAi
acpi0 at bios0: rev 2
acpi0: sleep states S0 S5
acpi0: tables DSDT FACP FPDT FIDT SPMI MCFG WDAT UEFI APIC BDAT HPET SSDT
acpi0: wakeup devices PEX1(S0) PEX2(S0) PEX3(S0) PEX4(S0) EHC1(S0)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
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) Atom(TM) CPU C2758 @ 2.40GHz, 2400.45 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT
cpu0: 1MB 64b/line 16-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.0.0.0.0.3, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Atom(TM) CPU C2758 @ 2.40GHz, 2399.99 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT
cpu1: 1MB 64b/line 16-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Atom(TM) CPU C2758 @ 2.40GHz, 2399.99 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,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT
cpu2: 1MB 64b/line 16-way L2 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 6 (application processor)
cpu3: Intel(R) Atom(TM) CPU C2758 @ 2.40GHz, 2399.99 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,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT
cpu3: 1MB 64b/line 

Re: CARP, BGP and OpenBSD routers - integration tips/suggestions needed

[Bryan Vyhmeister]

On Sun, Dec 11, 2016 at 09:45:08AM +, Bob Jones wrote:
> I have a planned network topology that will run on OpenBSD that (at
> the moment) will constitute of three boxes :
> 
> 1 x Router (Openbsd running bgpd for connection to the outside world)
> 2 x Firewalls (running Openbsd)
> 
> I can't quite figure out the best way to deal with the "external" side
> of the firewalls ? (Obviously the "internal" side would be CARP).

The missing piece here is OSPF. The paper below is what I used as my
template to setup my network which is very much like your design. I then
added the CARP configuration which I will explain below.

http://www.openbsd.org/papers/linuxtag06-network.pdf

> At the moment, since the devices are located in the same rack, I am
> thinking of running a patch cable directly from each firewall to two
> ports on the Router (i.e. F1a -> R1a and F2a to R1b).  The reason for
> this is to avoid going via a switch and adding a point of failure
> (yes, I know, I only have one "router" but hopefully that will
> change in the not too distant future !)

I have an external router running BGP with my provider with four
ethernet ports. The first interface (em0) is connected to my provider.
The other ports (em1, em2, and em3) are all part of bridge0 which is
what my other two routers are connected to. The internal IP address
(which is .1 of a /29 and the beginning of my /24) of my external router
exists on vether0 also added to bridge0. I run iBGP and OSPF between the
three routers as in the paper above. That means the first internal
router would have .3 on its em0 and the second internal router would
have .4 on its em1. I am actually changing out to use a switch because
once in a while the external router stops seeing OSPF from the internal
routers. I can't be positive it has anything to do with bridge(4)
because the routers have not been upgraded recently past 5.8 and there
have been improvements to lots of areas. This week I am upgrading them
to 6.0-stable and replacing some hardware. I have this same setup in a
datacenter as well all running 6.0-stable that uses a switch and has
worked perfectly for several years.

> The problem is I can't quite figure out the OpenBSD software
> configuration for that concept and how it inter-relate with CARP
> running on the "internal" side of the firewalls ?  Should I be running
> OSPF ? iBGP ?  Or something else (switchd ? vether ?)

Like I mentioned above, you want BGP to your provider on the external
router. On its internal interface use iBGP and OSPF to the other two
routers. You can use vether(4) and bridge(4) on the external router's
internal interfaces like I did which seems to work fairly well. On the
two internal routers, the key point for CARP to work is to use the
"demote carp" option as documented in ospfd.conf(5) and use the carp
interface(s) rather than the physical in ospfd.conf on the internal side
of the internal routers. You also have to have a link between the
internal routers for pfsync(4) and an OSPF link. Here is a simplified
snippet from my ospfd.conf on one of the internal routers.

area 0.0.0.0 {
demote carp
interface em0 { metric 10 }
interface em1 { metric 20 }
interface carp2 { passive }
}

In this case, em0 connects to the external router. Interface em1 is a
cable between the two internal routers which provides both a /30 link
between them for OSPF and also pfsync for CARP to work correctly. I
simplified my snippet above because I have some other things working
that would complicate your setup. In a setup like you want, carp2 would
correspond to em2 for example. I am using a /25 for the internal network
using CARP. So carp2 has the .125 IP address shared bewteen both
internal routers, em2 on the first internal router has .126, and em2 on
the second internal router has .127 to allow CARP to work correctly.

Hopefully this helps you get things going. This setup works very well
for me at multiple sites and can easily be expanded by adding another
external router to another provider in the future.

Bryan

Re: HP Proliant MicroServer G8: not seeing disks [solved]

[Bryan Vyhmeister]

On Sat, Dec 03, 2016 at 02:21:15PM +0100, Stephane HUC "CIOTBSD" wrote:
> Hi Stuart.
> 
> What microserver would you recommend?!
> 
> Le 12/03/16 ? 12:08, Stuart Henderson a ?crit :
> > On 2016-12-02, Peter N. M. Hansteen  wrote:
> >> My only complaint is that due to the maze of twisty nonsense that is the
> >> HPE web site I never got the BIOS upgrade
> > 
> > It's at
> > http://h20564.www2.hpe.com/hpsc/swd/public/readIndex?sp4ts.oid=5390291=8=4168
> > but HP restrict BIOS downloads for computers, afaik it needs to either be
> > under warranty or you need a support contract.
> > 
> > As a result I don't buy HP machines any more, either new or second-hand.

I was considering looking for one of those HP MicroServers but I refuse
to deal with a support contract.

My suggestion for an alternative would be one of the several systems
based on the Supermicro CSE-721TQ-250B chassis.

https://www.supermicro.com/products/chassis/tower/721/SC721TQ-250B.cfm

Although I am not personally using that particular chassis, I am using
some similar custom built systems with Silverstone cases.

Bryan

Re: Lenovo Yoga 2 11

[Bryan Vyhmeister]

On Tue, Dec 06, 2016 at 09:30:06AM +0800, Denny White wrote:
> Trying to find out if anyone has had any luck with OBSD on a Lenovo
> Yoga 2 11 or anything close to that model in the Yoga line. I got it
> to boot off usb using amd64 iso due to the Yoga using UEFI.  I
> hadn???t ran OBSD in quite a while, dumbassed out & forgot to save a
> dmesg or ifconfig output, but I know from both the system didn???t
> recognize any network device like fxp0, eth0, etc., e.g. Only showed
> the lo0, enc0, & pflog0. I???m aware of /etc/firmware and from what I
> read it recognizes the network device & sees it needs a firmware fix
> the system does it on it???s own, but I guess that???s not gonna
> happen if the system doesn???t even recognize a network device. If
> anyone???s had any luck at all with a Yoga 2 series I would surely
> appreciate push in the right direction. Thx.

It is very hard to say much without a dmesg. As far as I am aware, the
Yoga type system do not have ethernet ports and probably only have
wireless network interfaces. The easiest route is to use a USB ethernet
adapter to connect to a network in order to run fw_update to get
whatever firmware is needed. That is not a guarantee though. All of the
Lenovo systems I have right now (ThinkPad X1 Carbon 1st Gen, ThinkPad
X230, ThinkPad 11e, LaVie Z, ThinkPad X260, and ThinkPad X1 Carbon 4th
Gen) all use Intel wireless cards supported by the iwm(4) or iwm(4)
drivers. However, none of these are "Yoga" type systems and they might
have some other wireless network interface.

OpenBSD has excellent UEFI support and almost all of the systems I
listed above are working great with a UEFI install. Again, a dmesg would
answer most of these questions.

Bryan

Re: FAQ update

[Bryan Vyhmeister]

On Mon, Dec 05, 2016 at 09:12:49AM -0800, Todd Carpenter wrote:
> 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..

There are a couple of gaps in your understanding. I'm not sure what the
status of nested softraid(4) is but once you run the first command which
creates the mirror (bioctl -c 1), the softraid(4) device will now be a
new device called sd2. You would now setup the sd2 device with a
partition of type RAID and then use bioctl(8) on that new softraid(4)
disk device.

I believe it would then be:

bioctl -c C -l sd2a softraid0

After this command (and inputting a password) you will have a new volume
which would presumably be sd3. You would do your normal install on sd3.
In theory, to be bootable, you would then run:

installboot -v sd3

It's very possible that this will not be bootable and might not work
right but I know some work happened on nested softraid(4).

One reason this might be somewhat confusing is that the examples section
of bioctl(8) uses wd(4) devices for the chunks that make up the
softraid(4) device. The wd(4) driver is for older IDE drives while
modern SATA devices (and USB attached drives) show up as sd(4) as well.

Bryan

Re: Logic Supply Nuvo-5000 / Intel Q170 Chipset

[Bryan Vyhmeister]

On Tue, Nov 29, 2016 at 03:10:10PM -0600, Joe Crivello wrote:
> Does anyone out there on the list have experience with the Intel Q170
> chipset on OpenBSD 6.0?
> 
> We are looking into using the Logic Supply Nuvo 5000LP (
> http://www.logicsupply.com/nuvo-5000lp/#specs) as a high performance router
> in some challenging environmental conditions. It would use an Intel Q170
> chipset with an Intel i7-6700TE CPU and I210 and I219 GbE controllers.
> 
> Thanks in advance for any responses...

I am not currently using the Q170 chipset but am ordering a Supermicro
board with the same chipset shortly here. That's the business oriented
Skylake chipset. I can also confirm that the Intel i210 and i219
Ethernet controllers work just fine. The i219 is on my ThinkPad X260 and
most other Skylake boards and the i210 is working fine on multiple
server boards I have. The Core i7 6700TE is a low power (35W TDP) and
embedded variant which should also work just fine. You will not be using
X I presume so lack of inteldrm(4) for Skylake will not make any
difference. Even if you did, efifb(4) (via UEFI booting) and wsfb(4)
would work fine.

That system looks quite interesting and should work nicely.

Bryan

Re: umb(4) connection issues

[Bryan Vyhmeister]

On Wed, Nov 23, 2016 at 08:37:04PM +0100, Ingo Feinerer wrote:
> Indeed, it works for me when an appropriate (default) route is manually
> added and the listed DNS entries are manually set in /etc/resolv.conf.

I forgot to mention about DNS. The script I came up with just grabs the
values from the ifconfig output and adds the default route and then puts
the DNS entries in place.

Bryan

Re: umb(4) connection issues

[Bryan Vyhmeister]

On Tue, Nov 22, 2016 at 06:14:28PM +0100, Ingo Feinerer wrote:
> --8<-
> umb0: flags=8851 mtu 1500
> index 5 priority 0 llprio 3
> roaming disabled registration home network
> state up cell-class custom rssi -69dBm speed 5.5Mps up 20.0Mps down
> SIM initialized PIN valid
> subscriber-id 012345678901234 ICC-id 0123456789012345689 provider 3 AT
> device KRD 131 30/123 - R1A IMEI 012345689012345 firmware R3C11 
> (Pro), R4A10 (App)
> APN drei.at
> dns 213.94.78.17 213.94.78.16
> status: active
> inet 10.72.61.158 --> 10.72.61.155 netmask 0xfff8
> --8<-

Due to some conflicts with umb(4) and MP safe work going on, a default
route is not automatically created for a umb(4) connection. You have to
do it manually like the following for your example above:

route add -ifp umb0 default 10.72.61.155

I created a shell script to set this up.

Bryan

Lenovo IdeaPad N22 OpenBSD Report

[Bryan Vyhmeister]

I just picked up an inexpensive Lenovo IdeaPad N22 from their outlet
store and found that it runs OpenBSD quite nicely. It cost me $185
delivered to my door. I picked up another inexpensive Lenovo system last
year and it was a terrible experience. This is a Braswell based system
with a Celeron N3050 paired with 4GB of memory and 32GB of eMMC storage.
I finally figured out that the BIOS is accessible via F2. I disabled
Secure Boot and then did the install with a USB stick that I manually
setup for UEFI booting and the install sets. I also configured
softraid(4) crypto while I was at it. I used a USB Ethernet adapter to
install the required firmware for iwm(4) to function and it also pulled
in uvideo(4) firmware as well. Since there is no inteldrm(4) support at
this point, I am using wsfb(4) which works along with efifb(4) for Xorg.
My dmesg is below along with my xorg.conf and the modified auto
partition layout I went with. I did see a few fatal firmware errors from
iwm(4) but it seems to work fine after those errors.

There is a slightly nicer model that includes 128GB of SATA storage and
a slightly updated Celeron N3160 which might be an even better OpenBSD
system since 32GB of storage can be a little tight. Both of these
systems are the Windows 10 Home 64 models, not the Chromebook models. If
someone is looking for a very inexpensive OpenBSD laptop, this is a
pretty decent choice.

Bryan


OpenBSD 6.0-current (GENERIC.MP) #2485: Fri Sep 23 00:23:06 MDT 2016
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 4117872640 (3927MB)
avail mem = 3988566016 (3803MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0x77429000 (61 entries)
bios0: vendor Lenovo version "0YCN17WW" date 03/31/2016
bios0: LENOVO 80S6
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP UEFI MCFG SSDT SSDT SSDT SSDT SSDT APIC UEFI MSDM BATB 
FPDT UEFI BGRT tCSR
acpi0: wakeup devices XHC1(S4) BRC1(S0) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimcfg0 at acpi0 addr 0xe000, bus 0-63
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Celeron(R) CPU N3050 @ 1.60GHz, 2160.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,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT
cpu0: 1MB 64b/line 16-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 79MHz
cpu0: mwait min=64, max=64, C-substates=0.2.0.0.0.0.3.3, IBE
cpu1 at mainbus0: apid 4 (application processor)
cpu1: Intel(R) Celeron(R) CPU N3050 @ 1.60GHz, 2160.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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT
cpu1: 1MB 64b/line 16-way L2 cache
cpu1: smt 0, core 2, package 0
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 115 pins
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (RP01)
acpiprt2 at acpi0: bus -1 (RP02)
acpiprt3 at acpi0: bus 2 (RP03)
acpiprt4 at acpi0: bus -1 (RP04)
acpiec0 at acpi0
acpicpu0 at acpi0
C2: state 6: substate 8 >= num 3
C3: state 7: substate 4 >= num 3: C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0
C2: state 6: substate 8 >= num 3
C3: state 7: substate 4 >= num 3: C1(1000@1 mwait.1), PSS
acpipwrres0 at acpi0: CLK0
acpipwrres1 at acpi0: CLK1
acpipwrres2 at acpi0: ID3C, resource for ISP3
acpipwrres3 at acpi0: USBC, resource for XHC1
acpipwrres4 at acpi0: FN00, resource for FAN0
acpitz0 at acpi0: critical temperature is 90 degC
acpibat0 at acpi0: BAT1 model "CRB Battery 1" serial Battery 1 type Real oem 
"-Real Battery 1-"
"VPC2004" at acpi0 not configured
"PNP0501" at acpi0 not configured
"MSFT0001" at acpi0 not configured
"SYN2F02" at acpi0 not configured
sdhc0 at acpi0: SDHA addr 0x91319000/0x1000 irq 45
sdhc0: SDHC 3.0, 200 MHz base clock
sdmmc0 at sdhc0: 8-bit, sd high-speed, mmc high-speed, dma
sdhc1 at acpi0: SDHB addr 0x91317000/0x1000 irq 46
sdhc1: SDHC 3.0, 200 MHz base clock
sdmmc1 at sdhc1: 4-bit, sd high-speed, mmc high-speed, dma
acpiac0 at acpi0: AC unit online
acpibtn0 at acpi0: LID0
acpibtn1 at acpi0: PWRB
"INT3400" at acpi0 not configured
"INT3403" at acpi0 not configured
"PNP0C0B" at acpi0 not configured
acpivideo0 at acpi0: GFX0
acpivout0 at acpivideo0: DD1F
cpu0: Enhanced SpeedStep 2160 MHz: speeds: 1601, 1600, 1520, 1440, 1360, 1280, 
1200, 1120, 1040, 960, 880, 800, 720, 640, 560, 480 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Braswell Host" rev 0x21
"Intel HD Graphics" rev 0x21 at pci0 dev 2 

Re: AMD graphics adapter hcl

[Bryan Vyhmeister]

On Fri, Sep 09, 2016 at 02:44:33AM +1000, Jonathan Gray wrote:
> > Am I understanding that using a newer, say Radeon HD 7750 or HD 7870
> > card, with the modesetting(4) Xorg driver would work as long as there is
> > kernel support (which there is)? That would obviously not allow for
> > 2d/3d acceleration.
> 
> For cape verde, pitcairn and tahiti based designs with pci ids recognised
> by the kernel, yes.  The marketing names don't encode the generation
> of the hardware and radeon product lines often reuse older generation
> designs rebadged.

Thank you for the clarification. I will have to try out one of those
cards.

Bryan

Re: AMD graphics adapter hcl

[Bryan Vyhmeister]

On Fri, Sep 09, 2016 at 02:17:03AM +1000, Jonathan Gray wrote:
> The LLVM in the tree will not be installed as libraries suitable
> for Mesa initially.
> 
> I'm not aware of anyone working on updating radeondrm at the moment
> and doing so for basic modesetting support is not tied to LLVM.
> 2d/3d acceleration for GCN hardware is however.

Am I understanding that using a newer, say Radeon HD 7750 or HD 7870
card, with the modesetting(4) Xorg driver would work as long as there is
kernel support (which there is)? That would obviously not allow for
2d/3d acceleration.

Bryan

Re: AMD graphics adapter hcl

[Bryan Vyhmeister]

On Wed, Sep 07, 2016 at 06:35:26PM +0200, Simon Mages wrote:
> can somebody tell me which AMD graphics adapters are supported by the
> OpenBSD kernel?
> 
> radeon(4) has a very big list of supported adapters or chip families.
> I greped a bit in /usr/src/sys/dev/pci/drm/radeon to see which ones
> are supported.

I asked a related question not too long back.

http://marc.info/?l=openbsd-misc=146915801029888=2

The answer is essentially that cards up to the HD 6870 are currently
well supported. The Radeon HD 5450 is a good choice that can be
purchased in several configurations and is still available in retail
channels. It also has the bonus of being reasonably priced.

The more recent (HD 7xxx and later) are supported in the kernel but not
in userland due to needing LLVM. LLVM was just imported into base last
week and has not been hooked to the build yet. Hopefully over the winter
we will see updated radeondrm(4) support. It is being worked on but it's
a big project and has been waiting on LLVM.

Bryan

Re: Driving 4k Display for OpenBSD Workstation

[Bryan Vyhmeister]

I neglected one solution to having a 4k Display with OpenBSD. I was
reading about Haswell and 4k in context of the Mac mini which uses a low
power series of processors that do not support 4k at 60 Hz. The regular
Haswell chips like the Xeon E3 1275 v3 I am using now, do support 4k at
60 Hz using DisplayPort. My Dell P4317Q seems to be working fine at 4k
with inteldrm(4) and this processor. Thanks for the suggestions.

I will also test my Skylake build with efifb(4) and wsfb(4) once my Xeon
E3 1275 v5 arrives in a few days but I suspect it will be very slow as
has been predicted.

Bryan

Re: Driving 4k Display for OpenBSD Workstation

[Bryan Vyhmeister]

On Fri, Jul 22, 2016 at 02:05:07PM +1000, Jonathan Gray wrote:
> There is no kernel support for skylake and it will require firmware.
> https://01.org/linuxgraphics/intel-linux-graphics-firmwares
> 
> The intel code in Mesa does not use gallium or LLVM.
> 
> Using efifb with a 4k display would likely be horribly slow due to the
> high number of pixels to push.

I guess I will find out just how slow. I have two 4k monitors on the
way (the Dell P4317W and also an HP Z27s). Perhaps I will pick up some
more 30-inch 2560x1600 monitors for now. Thanks for all the info.

Bryan

Re: Driving 4k Display for OpenBSD Workstation

[Bryan Vyhmeister]

On Fri, Jul 22, 2016 at 01:25:58PM +1000, Jonathan Gray wrote:
> There is kernel support for TAHITI/PITCAIRN/CAPE VERDE southern
> islands but no userland acceleration as both 2d and 3d acceleration
> require LLVM.
> 
> The marketing names are a mess, see
> https://www.x.org/wiki/RadeonFeature/
> to decode them.

Thanks for the clarification. That makes sense. Sounds like the better
option is to wait for Skylake inteldrm(4) and use efifb(4) and wsfb(4)
for now. Does Skylake inteldrm(4) require LLVM or anything like that?

Bryan

Re: Driving 4k Display for OpenBSD Workstation

[Bryan Vyhmeister]

On Thu, Jul 21, 2016 at 10:27:18PM +0300, li...@wrant.com wrote:
> Thu, 21 Jul 2016 11:45:01 -0700 Bryan Vyhmeister <br...@bsdjournal.net>
> > My goal for this project is to have an OpenBSD workstation (I run
> > -current) built around 4k displays.
> 
> Short answer from user level: I'd personally get more 2560x1440 27" IPS
> monitors for now, and use the excess budget for another set of the same.
> You'd probably have to get a slightly older & cheaper video card (6450).
> I know of no justification for a 5K monitor yet, though I want one too..

I am not interested in a 5k monitor, only 4k monitors. I recognize the
Radeon HD 6450 cards work well. I have one now. I also have a 30-inch
2560x1600 and 34-inch 3440x1440 monitor which all work well. I would
just like more screen real estate which is why 4k monitors are
interesting, particularly the 43-inch Dell P4317W. I would like some
feedback if the Radeon HD 7750 cards work decently with radeondrm(4). I
also know Skylake inteldrm(4) is in the works but is not here yet.

Bryan

Driving 4k Display for OpenBSD Workstation

[Bryan Vyhmeister]

My goal for this project is to have an OpenBSD workstation (I run
-current) built around 4k displays. I have a Dell P4317W 4k display on
order and I am going to order a couple of other 4k displays as well. I
have a Radeon HD 6870 Eyefinity 6 card which should be supported by
radeondrm(4) but it does not support 4k displays at 60Hz. There is a
Radeon HD 7750 card that also has six Mini DisplayPort connectors and
does support 4k displays but I am not totally clear if it will work well
with radeondrm(4). Reading the archives is not quite clear on this.

The alternative is to use a Skylake processor with integrated graphics
and use efifb(4) and wsfb(4) for now which I presume would work well
enough although not as well as something supported by inteldrm(4). I am
using my ThinkPad X260 with efifb(4) and wsfb(4) which works pretty well
but it would be nice to have properly accelerated Xorg.

Any recommendations? Thank you.

Bryan

Mac mini acpiec(4) panic with Unsupported RegionSpace

[Bryan Vyhmeister]

I have two different Macmini7,1 systems (the late 2014 and most recent
Mac mini model). On one of them, I was using OpenBSD -current in April
but haven't used the system or upgraded it to a newer snapshot. I
purchased another similar system and went to install OpenBSD -current on
it from the June 22 and found that I had a panic early in the boot
process. The panic is from below which I hand copied. This is from
bsd.rd but the panic is identical with bsd.mp as well. I did not get far
enough to get a full dmesg with the recent kernels but could pull an old
one as well if needed. Also, this is using EFI boot from a USB stick
which has worked fine in the past.


real mem = 17032085504 (16243MB)
avail mem = 16514179072 (15749MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0x88d1 (49 entries)
...
(snip)
...
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins
acpiec0 at acpi0
Unsupported RegionSpace
panic: aml_die aml_rwfield:2475

The operating system has halted.
Press press any key to reboot.

rebooting...


I believe the panic stems from revision 1.53 of acpiec.c. I can try
reverting that commit on -current now and see if I can avoid the issue
but there may be more to it than that. Any idea how to resolve this?

There is also a separate issue that I will report in another message
with "halt -p" causing a panic related to aml but that has been around
for quite a while including in the April snapshot I am running on one of
those systems. It isn't as important since reboot works fine.

Bryan

Re: pf changes port on udp nat-to and rdr-to reply packets (RTP stream)

[Bryan Vyhmeister]

On Thu, Jun 9, 2016, at 10:48 AM, Markus Wernig wrote:
> Short question:
> How do I prevent pf from changing the source port of outgoing
> natted udp
> packets?
 
Did you look at static-port in pf.conf(5)?
 
Bryan

Re: MacBook 9,1 or 8,1

[Bryan Vyhmeister]

On Wed, Apr 27, 2016, at 12:53 PM, Joerg Jung wrote:
> On Wed, Apr 27, 2016 at 09:41:50AM -0400, Bryan Everly wrote:
> > 
> > Has anyone had success with either of the new 12" Retina MacBooks?  My
> > search of marc.info came up empty.
> 
> I own a MacBook8,2 and efiboot as well as inteldrm graphics seems to
> work fine.  However, internal nvme(4) ssd is not detected and the SPI
> connected trackpad/mouse also does not work.  The built-in WLAN might
> never work.  A standard USB3 HUB (connected via adapter), I tested was
> not really working. So you you can either only attach a USB keyboard or
> disk or wlan card to the single USB-C port, your choice :) 
> 
> Due to this fact I can not provide a copy dmesg.
> Linux support seems not much better [1].
> 
> I have no idea about the 9,x but would like to see a dmesg. 
> Newer MacbookAir might have the same nvme(4) problem.

The MacBookAir7,2 (13-inch 2015 MacBook Air which is currently the
latest version) does not use nvme(4) and works very well with OpenBSD
and efiboot (I have one issue with the keyboard not mapping tilde right
but haven't looked further into that). I also have a MacBook8,1 which I
tried booting OpenBSD on but ran into various problems mentioned above
about six months ago. Now that nvme(4) is supported I was going to try
it again but it sounds like that doesn't make any difference. I have an
OWC USB-C External Docking station for it and both of Apple's USB-C to
HDMI/VGA with USB dongles but haven't had a chance to try them.

Bryan

Re: umsm(4) for Sierra Wireless EM7455 in ThinkPad X260

[Bryan Vyhmeister]

On Wed, Apr 20, 2016 at 08:15:34PM +0200, David Coppa wrote:
> On Wed, Apr 20, 2016 at 5:28 PM, Bryan Vyhmeister <br...@bsdjournal.net> 
> wrote:
> > On Wed, Apr 20, 2016 at 11:12:04AM +0200, David Coppa wrote:
> >> It's a MBIM (Mobile Broadband Interface Model) device:
> >>
> >> https://www.kernel.org/doc/Documentation/networking/cdc_mbim.txt
> >
> > Thanks for the info. Sounds like a new driver is needed or lots of work
> > to extend umsm(4). If my research is correct, the older cards supported
> > by umsm(4) would be supported by the qcserial driver in Linux which is
> > totally different than this cdc_mbim driver. I will research the
> > situation further. For now I have an expensive Mini PCIe slot filler.
> 
> The vast majority of the devices supported by umsm(4) under OpenBSD
> require the "option" kernel module on Linux, the USB driver for GSM
> and CDMA modems.
> 
> http://lxr.free-electrons.com/source/drivers/usb/serial/option.c
> 
> https://wiki.gentoo.org/wiki/USB_mobile_broadband_modem

Assuming MBIM is something that would be worked on, would it make sense
to extend umsm(4) to support it or would it make more sense to have a
new driver like umbim(4) or something?

Bryan

Re: umsm(4) for Sierra Wireless EM7455 in ThinkPad X260

[Bryan Vyhmeister]

On Wed, Apr 20, 2016 at 11:12:04AM +0200, David Coppa wrote:
> On Wed, Apr 20, 2016 at 10:40 AM, Stuart Henderson <s...@spacehopper.org> 
> wrote:
> > On 2016-04-20, Bryan Vyhmeister <br...@bsdjournal.net> wrote:
> >> I recently purchased a Lenovo ThinkPad X260 and I decided to also order
> >> the Sierra Wireless EM7455 LTE Wireless WAN device installed as well.
> >
> > I'd look for other OS which support this device and see which driver
> > they attach to..
> 
> I'm sorry,
> 
> It's a MBIM (Mobile Broadband Interface Model) device:
> 
> https://www.kernel.org/doc/Documentation/networking/cdc_mbim.txt

Thanks for the info. Sounds like a new driver is needed or lots of work
to extend umsm(4). If my research is correct, the older cards supported
by umsm(4) would be supported by the qcserial driver in Linux which is
totally different than this cdc_mbim driver. I will research the
situation further. For now I have an expensive Mini PCIe slot filler.

Bryan

umsm(4) for Sierra Wireless EM7455 in ThinkPad X260

[Bryan Vyhmeister]

I recently purchased a Lenovo ThinkPad X260 and I decided to also order
the Sierra Wireless EM7455 LTE Wireless WAN device installed as well. I
was hoping it might work easily with umsm(4) but that does not appear to
be the case. Based on the output of usbdevs -vv, I added the EM7455
product ID (0x9079) to src/sys/dev/usb/usbdevs and regenerated it. I
then also added the proper match to src/sys/dev/usb/umsm.c so that
umsm(4) would attach but that is apparently not enough to get things
working. I get an error stating "missing endpoint" as is listed in my
dmesg below. My patch as well as dmesg prior to the patch and after the
patch are inline. Any ideas as to where to go from here? I'm happy to do
any testing or investigation. Thank you.

Bryan


Index: sys/dev/usb/umsm.c
===
RCS file: /cvs/src/sys/dev/usb/umsm.c,v
retrieving revision 1.104
diff -u -p -r1.104 umsm.c
--- sys/dev/usb/umsm.c  29 Sep 2015 08:34:28 -  1.104
+++ sys/dev/usb/umsm.c  20 Apr 2016 05:59:22 -
@@ -247,6 +247,7 @@ static const struct umsm_type umsm_devs[
{{ USB_VENDOR_SIERRA, USB_PRODUCT_SIERRA_USB305}, 0},
{{ USB_VENDOR_SIERRA, USB_PRODUCT_SIERRA_TRUINSTALL }, DEV_TRUINSTALL},
{{ USB_VENDOR_SIERRA, USB_PRODUCT_SIERRA_MC8355}, 0},
+   {{ USB_VENDOR_SIERRA, USB_PRODUCT_SIERRA_EM7455}, 0}, 
 
{{ USB_VENDOR_TCTMOBILE, USB_PRODUCT_TCTMOBILE_UMASS }, DEV_UMASS3},
{{ USB_VENDOR_TCTMOBILE, USB_PRODUCT_TCTMOBILE_UMASS_2 }, DEV_UMASS3},
Index: sys/dev/usb/usbdevs
===
RCS file: /cvs/src/sys/dev/usb/usbdevs,v
retrieving revision 1.663
diff -u -p -r1.663 usbdevs
--- sys/dev/usb/usbdevs 31 Mar 2016 12:27:48 -  1.663
+++ sys/dev/usb/usbdevs 20 Apr 2016 05:59:22 -
@@ -3832,6 +3832,7 @@ product SIERRA AC885U 0x6880  885U
 product SIERRA C01SW   0x6890  C01SW
 product SIERRA USB305  0x68a3  USB305
 product SIERRA MC8355  0x9013  MC8355
+product SIERRA EM7455  0x9079  EM7455
 
 /* Sigmatel products */
 product SIGMATEL IRDA  0x4200  IrDA



OpenBSD 5.9-current (GENERIC.MP) #1988: Mon Apr 18 06:49:50 MDT 2016
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 17024274432 (16235MB)
avail mem = 16503939072 (15739MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xb7c01000 (66 entries)
bios0: vendor LENOVO version "R02ET44W (1.17 )" date 01/25/2016
bios0: LENOVO 20F6CTO1WW
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP UEFI SSDT SSDT ECDT HPET APIC MCFG SSDT SSDT DBGP DBG2 
BOOT BATB SSDT SSDT MSDM DMAR ASF! FPDT UEFI
acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) PXSX(S4) PXSX(S4) PXSX(S4) 
PXSX(S4) EXP8(S4) PXSX(S4) XHCI(S3)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpiec0 at acpi0
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-6600U CPU @ 2.60GHz, 2485.91 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT
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 23MHz
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-6600U CPU @ 2.60GHz, 2494.18 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz, 2494.19 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 1, core 0, package 0
cpu3 at mainbus0: apid 3 (application 

Re: ThinkPad X260 or other Skylake Laptop

[Bryan Vyhmeister]

On Wed, Mar 30, 2016 at 12:15:05AM +1100, Jonathan Gray wrote:
> On Tue, Mar 29, 2016 at 02:50:26PM +0200, Stefan Sperling wrote:
> > On Mon, Mar 28, 2016 at 05:04:02PM -0700, Bryan Vyhmeister wrote:
> > > Is there a way screen brightness can still be adjusted in some
> > > form even with wsfb(4)?
> > 
> > wsconsctl display.brightness should work.
> 
> I don't see how.  efifb(4) does not handle
> WSDISPLAYIO_SETPARAM/WSDISPLAYIO_PARAM_BRIGHTNESS and inteldrm(4)
> won't attach.

Thanks for the responses. Any current work toward updating the code for
Skylake chips? I know it's a huge amount of work and thanks for all your
work on getting us as far as we are with inteldrm(4).

Bryan

Re: (2nd) Syntax error with pf rules

[Bryan Vyhmeister]

On Tue, Mar 29, 2016, at 10:26 AM, Adam Smith wrote:
> set debug urgent
>
> comes with the following error message:
>
> pfctl: unknown debug level "urgent"
> /etc/pfcustom.conf 13: error setting debuglevel "urgent"
> pfctl: Syntax error in config file: pf rules not loaded.
 
Although you didn't specify (a dmesg would have been helpful), you are
running -current that is post-5.8 and possibly close to what 5.9 will
be. Although 5.9 is not officially released yet and this document is not
necessarily complete, the issue is listed here:
 
http://www.openbsd.org/faq/upgrade59.html
 
It used to be listed at http://www.openbsd.org/faq/current.html
 
Bryan

ThinkPad X260 or other Skylake Laptop

[Bryan Vyhmeister]

I am considering purchasing a ThinkPad X260 for OpenBSD use. I am aware
that inteldrm(4) does not yet support Skylake chips (Broadwell support
is not perfect yet either). I presume wsfb(4) should work decently at
least but I am wondering if anyone currently has an X260 and is using it
for OpenBSD. Is there a way screen brightness can still be adjusted in
some form even with wsfb(4)? I know my X230 has hardware methods for
adjusting brightness but lots has changed with the X240, X250, and X260.
I am also aware that the Intel 8260 wireless chipset does not yet work
(perhaps support could be added to iwm(4) or maybe I can replace the
8260 with a 7260) but I am more concerned about the reports of problems
with xhci(4) with Skylake systems. Has anyone had any experience with a
Skylake laptop and OpenBSD? Thank you.

Bryan

vfs_syscalls.c PLEDGE_DPATH undeclared

[Bryan Vyhmeister]

I'm running the latest snapshot pretty much each day and then compiling
my own kernel and userland to enable vmm and, for a few days now, kernel
compilation fails with these errors. I believe userland failed to build
as well but I didn't continue since I did not want mismatched kernel and
userland.

cc  -Werror -Wall -Wimplicit-function-declaration  -Wno-main
-Wno-uninitialized  -Wframe-larger-than=2047 -mcmodel=kernel
-mno-red-zone -mno-sse2 -mno-sse -mno-3dnow  -mno-mmx -msoft-float
-fno-omit-frame-pointer -fno-builtin-printf -fno-builtin-snprintf
-fno-builtin-vsnprintf -fno-builtin-log  -fno-builtin-log2
-fno-builtin-malloc -fno-pie -O2 -pipe -nostdinc -I../../../.. -I.
-I../../../../arch -DDDB -DDIAGNOSTIC -DKTRACE -DACCOUNTING -DKMEMSTATS
-DPTRACE -DPOOL_DEBUG -DCRYPTO -DSYSVMSG -DSYSVSEM -DSYSVSHM
-DUVM_SWAP_ENCRYPT -DFFS -DFFS2 -DFFS_SOFTUPDATES -DUFS_DIRHASH -DQUOTA
-DEXT2FS -DMFS -DNFSCLIENT -DNFSSERVER -DCD9660 -DUDF -DMSDOSFS -DFIFO
-DTMPFS -DFUSE -DSOCKET_SPLICE -DTCP_SACK -DTCP_ECN -DTCP_SIGNATURE
-DINET6 -DIPSEC -DPPP_BSDCOMP -DPPP_DEFLATE -DPIPEX -DMROUTING -DMPLS
-DBOOT_CONFIG -DUSER_PCICONF -DAPERTURE -DMTRR -DNTFS -DHIBERNATE
-DPCIVERBOSE -DUSBVERBOSE -DWSDISPLAY_COMPAT_USL
-DWSDISPLAY_COMPAT_RAWKBD -DWSDISPLAY_DEFAULTSCREENS="6"
-DWSDISPLAY_COMPAT_PCVT -DX86EMU -DONEWIREVERBOSE -DMULTIPROCESSOR
-DMAXUSERS=80 -D_KERNEL -MD -MP  -c ../../../../kern/vfs_syscalls.c
../../../../kern/vfs_syscalls.c: In function 'domknodat':
../../../../kern/vfs_syscalls.c:1238: error: 'PLEDGE_DPATH' undeclared
(first use in this function)
../../../../kern/vfs_syscalls.c:1238: error: (Each undeclared identifier
is reported only once
../../../../kern/vfs_syscalls.c:1238: error: for each function it
appears in.)
*** Error 1 in /usr/src/sys/arch/amd64/compile/GENERIC.MP (Makefile:940
'vfs_syscalls.o')

This is a fresh src tree from this morning. Last night, I redownloaded
an entirely new src tree just to be sure something wasn't wrong in my
tree and then updated this morning with some more commits overnight. I
don't tend to report these kind of errors unless they go on for a while
since -current is moving target right now but this error isn't going
away. Any ideas?

Bryan

Re: vfs_syscalls.c PLEDGE_DPATH undeclared

[Bryan Vyhmeister]

Thanks to those that responded to this message off-list. The problem was
indeed that my src tree was corrupt probably as a result of a botched
cvsync of my private anoncvs mirror from a cvsync mirror that is
currently down. I'm currently syncing my mirror from another cvsync
mirror to restore its functionality but I grabbed a new src tree from a
public anoncvs mirror and all is well on my laptop.

Bryan

Re: OpenBSD 5.8 on VMware 5.5

[Bryan Vyhmeister]

On Wed, Dec 02, 2015 at 02:40:48PM -0200, Felipe Gomes wrote:
> I'm kinda worried with the performance: the host is a Dell R815 4 CPU
> Opteron 6136 / 64GB. There are no other VMs at the moment, just a single
> stance of OpenBSD 5.8 installed, 4 virtual CPUs, 8 GB RAM.
> 
> I've already enabled softdep on fstab, however it's taking more than 45
> minutes to compile the kernel (no modifications, GENERIC and GENERIC.MP
> aswell, and no installation -- I'm just doing this to benchmark).
> 
> Two hours ago I've started the make build and it seems its stalled on the
> cleaning phase yet.
> 
> I don't think this is right...
> 
> If needed, I can provide dmesg or any other information related to this.
> 
> Once again, thanks a lot.

I'm not sure how much you've worked with VMware ESXi before but does
this host have a battery backed RAID controller configured? If you're
using a single SATA disk or even a RAID array without battery backed
cache, all caching is disabled and all disk access will be extremely
slow (I forget all the exact details now). This can be mitigated for the
most part by using an SSD but the best performance is definitely with a
battery backed RAID controller. I've used LSI SAS9261-8i with the
appropriate BBU module very successfully with my own custom ESXi servers
with excellent success.

As far as OpenBSD on ESXi goes, I've never personally had any issues
except for an issue five years ago where a NetApp filer would run some
maintenance routines at 2am which caused the NFS-backed datastore to not
respond briefly and that caused OpenBSD VMs to sense something was wrong
at the filesystem level and panic. Just before I arrived on the scene,
the change had been made for the ESXi hosts to connect to the NetApp
filer using NFS rather than Fibre Channel and I think this change made a
big difference but wasn't able to fully prove this out.

Otherwise, I've used OpenBSD VMs on ESXi 4, 5, 5.5, and 6 without issue
using direct attached storage (LSI SAS9261-8i with BBU and 4-8 drives in
RAID 10) and also with SSDs temporarily in some cases. I'm happy for the
more precise information in this thread regarding some of the VM
settings but I've mostly used the defaults and also found that the
vmt(4) driver tends to change my OpenBSD/amd64 VMs to show as "FreeBSD
32-bit" although I normally select "Other 64-bit" although this seems to
have no functional change that I have observed.

Bryan

Re: A branded USB stick as an alternative to the CD set?

[Bryan Vyhmeister]

Let's not waste any more of Theo's time. USB sticks are not the magic
device that some seem to think. Some are not very reliable and prone to
failure. I've had very mixed results with budget USB sticks in
particular. Going with a more expensive USB stick like a major brand
name *usually* turns out better but that's still no guarantee. If you
don't want a CD set, simply donate the amount the CD set costs directly
to the project. That provides funding for OpenBSD while also not wasting
anyone's time.

http://www.openbsd.org/donations.html

Bryan

Re: A branded USB stick as an alternative to the CD set?

[Bryan Vyhmeister]

On Mon, Nov 30, 2015 at 06:20:02PM -0700, Bal??zs Nagy wrote:
> On Nov 30, 2015, at 2:34 PM, Theo de Raadt  wrote:
> >
> > These days the CD revenue is about what a cashier at a store makes.
> 
> I'm sick to my stomack when I read this. I won't get into how unjust,
> unfair, unethical this situation is, we all know that life is unfair.
> We also all know that Theo could have a high six figure, probably even
> seven figure salary if he chose to. I don't think the issue is what
> new technology to deliver the CD sets on. I think the question is how
> to deliver Theo a recurring revenue so that he gets to draw a salary
> that is at least somewhat commensurate with his contribution to the IT
> industry. Just like a lot of us do recurring contributions to the
> OpenBSD Foundation, we need to find a way to provide Theo directly as
> well. Am I beeing too naive, am I missing somthing here?

I agree completely. This is the core issue we need to look at and find
solutions to.

Bryan

xbacklight(1) not functional on MacBookAir7,2

[Bryan Vyhmeister]

I've posted several times about the MacBookAir7,2 (2015 Broadwell) and
how it's working fairly well. One thing that is not working is
xbacklight(1) to change the screen brightness. The similar MacBookAir6,1
(2013/2014 Haswell) works perfectly with xbacklight(1). What I'm
mostly wondering is if this is more related to inteldrm(4) or
xf86-video-intel (intel(4)) or something else in Xorg. Is this something
that's fixable on its own or is this part of a much larger drm update or
that sort of thing? I know that even in Linux kernel 4.2, things are
still not that great for Broadwell graphics and many fixes went into
Linux kernel 4.3 and 4.4.

For comparison, I installed Fedora 23 and the brightness buttons did
work in that they displayed a bar that was changing on the screen but
the brightness never actually changed for the display. This made me
wonder about drm as I wrote above. Fedora 23 is running on a Linux
kernel 4.2 train. 

Attached are my Xorg.0.log and dmesg from this evening. The only reason
I am compiling my own kernel is to enable vmm(4).

Bryan


OpenBSD 5.8-current (GENERIC.MP) #13: Sat Nov 28 21:16:50 PST 2015
r...@air.rebsd.com:/usr/src/sys/arch/amd64/compile/GENERIC.MP
RTC BIOS diagnostic error 
ff
real mem = 8469352448 (8077MB)
avail mem = 8208519168 (7828MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0x8afad000 (32 entries)
bios0: vendor Apple Inc. version "MBA71.88Z.0166.B06.1506051511" date 06/05/2015
bios0: Apple Inc. MacBookAir7,2
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP HPET APIC SBST ECDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT 
SSDT MCFG DMAR
acpi0: wakeup devices PEG0(S3) EC__(S3) HDEF(S3) RP01(S3) RP02(S3) RP03(S4) 
ARPT(S4) RP05(S3) RP06(S3) SPIT(S3) XHC1(S3) ADP1(S3) LID0(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) i7-5650U CPU @ 2.20GHz, 2100.26 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Core(TM) i7-5650U CPU @ 2.20GHz, 2100.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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) Core(TM) i7-5650U CPU @ 2.20GHz, 2100.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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,SENSOR,ARAT
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 1, core 0, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i7-5650U CPU @ 2.20GHz, 2100.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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins
acpiec0 at acpi0
acpimcfg0 at acpi0 addr 0xe000, bus 0-155
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG0)
acpiprt2 at acpi0: bus 1 (RP01)
acpiprt3 at acpi0: bus 2 (RP02)
acpiprt4 at acpi0: bus 3 (RP03)
acpiprt5 at acpi0: bus 5 (RP05)
acpiprt6 at acpi0: bus 4 (RP06)
acpicpu0 at acpi0: C3(200@276 mwait.1@0x60), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: C3(200@276 mwait.1@0x60), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS

Re: athn0: device timeout

[Bryan Vyhmeister]

On Sat, Nov 28, 2015 at 09:24:23AM -0700, bluesun08 wrote:
> ok, now i tested my adapter on 
> a) another machine
> b) another usb port.
> 
> Result: The adapter don't work on a) and don't work on b).
> 
> Is there any other Wifi-USB-adapter which work reasonably reliable on
> OpenBSD in HostAP mode?

I have what I believe is the exact same device you do (TP-Link
TL-WN722N) and I just plugged it in to my MacBookAir7,2 where uhub0 is
attached to usb0 which is attached to xhci0 and, after running fw_update
to get the athn(4) firmware, was able to reattach and bring it up in
hostap mode without any issues.

athn0 at uhub0 port 1 configuration 1 interface 0 "ATHEROS USB2.0 WLAN"
rev 2.00/1.08 addr 8
athn0: AR9271 rev 1 (1T1R), ROM rev 13, address f8:1a:67:1f:cc:89

athn0: flags=8843 mtu 1500
lladdr f8:1a:67:1f:cc:89
priority: 4
groups: wlan
media: IEEE802.11 autoselect (autoselect hostap)
status: active
ieee80211: nwid "hostap test" chan 1 bssid f8:1a:67:1f:cc:89


I think stsp@ is correct that something else is going on with xhci(4) on
your machine since this USB device works pretty well. I also tested an
older rum(4) device I have as well and that also works.

Bryan

Re: MacbookPro 11,1

[Bryan Vyhmeister]

On Thu, Nov 26, 2015 at 09:00:48AM +0100, Joerg Jung wrote:
> Can you send a dmesg for this Air7,2 please?

Here's my dmesg from today's snapshot for the MacBookAir7,2.

Bryan



OpenBSD 5.8-current (GENERIC.MP) #1667: Thu Nov 26 08:27:08 MST 2015
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
RTC BIOS diagnostic error 
ff
real mem = 8469352448 (8077MB)
avail mem = 8208547840 (7828MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0x8afad000 (32 entries)
bios0: vendor Apple Inc. version "MBA71.88Z.0166.B06.1506051511" date 06/05/2015
bios0: Apple Inc. MacBookAir7,2
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP HPET APIC SBST ECDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT 
SSDT MCFG DMAR
acpi0: wakeup devices PEG0(S3) EC__(S3) HDEF(S3) RP01(S3) RP02(S3) RP03(S4) 
ARPT(S4) RP05(S3) RP06(S3) SPIT(S3) XHC1(S3) ADP1(S3) LID0(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) i7-5650U CPU @ 2.20GHz, 2100.32 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,SENSOR,ARAT
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 100MHz
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-5650U CPU @ 2.20GHz, 2100.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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) Core(TM) i7-5650U CPU @ 2.20GHz, 2100.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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,SENSOR,ARAT
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 1, core 0, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i7-5650U CPU @ 2.20GHz, 2100.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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins
acpiec0 at acpi0
acpimcfg0 at acpi0 addr 0xe000, bus 0-155
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG0)
acpiprt2 at acpi0: bus 1 (RP01)
acpiprt3 at acpi0: bus 2 (RP02)
acpiprt4 at acpi0: bus 3 (RP03)
acpiprt5 at acpi0: bus 5 (RP05)
acpiprt6 at acpi0: bus 4 (RP06)
acpicpu0 at acpi0: C3(200@276 mwait.1@0x60), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: C3(200@276 mwait.1@0x60), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu2 at acpi0: C3(200@276 mwait.1@0x60), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu3 at acpi0: C3(200@276 mwait.1@0x60), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpibat0 at acpi0: BAT0 model "3545797981023400290" type 3545797981528607052 
oem "3545797981528608836"
acpiac0 at acpi0: AC unit online
acpibtn0 at acpi0: LID0
acpibtn1 at acpi0: PWRB
acpibtn2 at acpi0: SLPB
acpivideo0 at acpi0: IGPU
acpivout0 at acpivideo0: DD01
cpu0: Enhanced SpeedStep 2100 MHz: speeds: 2201, 2200, 2100, 1800, 1600, 1300, 
1100, 900, 700, 500 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Core 5G Host" rev 0x09
inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics 6000" rev 0x09
drm0 at inteldrm0
inteldrm0: msi
inteldrm0: 1440x900
wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)

Re: MacbookPro 11,1

[Bryan Vyhmeister]

On Thu, Nov 26, 2015 at 12:02:18AM +0100, Joerg Jung wrote:
> The problem with the MacBook8,1 is the USB trackpad/keyboard is connected
> via SPI internally.  No SPI driver in OpenBSD.
> Moreover, the internal SSD is connected via NVMe, also not supported.
> 
> Also, both seem not really working in any other open source OS yet.
> See here http://moepi.net/?page_id=213
> 
> Interesting is, MacBookPro12,1 seems to use same SPI Trackpad as well, 
> but (ACPI?) behaves differently and seems working using Linux, see here:
> http://www.spinics.net/lists/linux-acpi/msg61848.html

Perhaps all the "Force Touch" trackpads are SPI connected?

> > His solution was a
> > USB keyboard and a USB hub. I didn't have either handy but may try that
> > later today. In the case of the 12-inch Retina MacBook, there is only
> > that single USB-C port so I'm not sure if the USB hub was needed for any
> > reason other than to provide at least two ports (one for USB flash drive
> > and one for USB keyboard).
> 
> No real success here, the USB 3.x hub I tried was passive (likely not enough 
> power) 
> and crashed the machine on attach/detach.

It sounds like the MacBook8,1 does not work for now then. That's too
bad. I wonder if the MacBookPro11,4 (2015 15-inch with integrated
graphics) also has the same SPI trackpad? I wonder if it also has
storage issues with OpenBSD?

My goal is to document how well OpenBSD works on all the recent Apple
hardware I can. I'm intending to purchase a MacBookPro11,1 (2014
13-inch) which it sounds like from the thread works pretty well. I am
interested to find out if the SD card slot works.

I'm also hoping to find out more about the storage, SD card, and
trackpad of the MacBookPro11,4 (2015 15-inch with integrated graphics)
and also of the MacBookPro11,2 (2014 15-inch with integrated graphics).
Both of these machines still have Haswell chips (unlike the
MacBookPro12,1).

The MacBookAir6,1 (2013/2014 11-inch MacBook Air) I have works very well
in all respects but since it's the 11-inch it does not have an SD card
and my MacBookAir7,2 (2015 13-inch MacBook Air) works reasonably well
but lacks X acceleration (due to Broadwell) and the brightness cannot be
adjusted with xbacklight(1). The SD card slot also is not detected in
any way. I'm hoping to get some feedback on the SD card slot on the
MacBookAir6,2 if possible as well.

Bryan

Re: MacbookPro 11,1

[Bryan Vyhmeister]

On Tue, Nov 24, 2015 at 05:17:56PM -0500, Bryan C. Everly wrote:
> The rsu driver I'm using as an external USB network adapter appears to be a
> bit flaky on this hardware (dropping packets and connections entirely
> sometimes) so that's been a barrier as well necessitating multiple retries
> of pkg_add.

I have had excellent success with urtwn(4). I have an Edimax EW-7811Un
and also now a TP-Link TL-WN725N v2 that work great. I believe jcs@ uses
a urtwn(4) as well. As a bonus, the urtwn(4) devices I have are pretty
compact sticking out of the USB port.

> The HiDPI support in Gnome 3.18 worked flawlessly and everything looks
> "normal".

That's good to hear. I'm using spectrwm on my machine. I haven't tried
GNOME yet on either of these MacBook Airs. It sounds like acceleration
is working well for you in X or GNOME would not run well at all.

> tldr; looks pretty promising - thanks to everyone who put in the massive
> hard work to get us to this point!

Likewise! Thanks to everyone for all the hard work!

Bryan

Re: WLAN Card AP feature

[Bryan Vyhmeister]

On Tue, Nov 24, 2015 at 12:20:31PM -0700, bluesun08 wrote:
> In FreeBSD there is the command "ifconfig  list caps". This displays
> the adaptor's capabilities, including the operating modes supported.
> 
> 1) Is there a similar command in OpenBSD?

See "ifconfig  media" for some of that information.

> 2) Is there a WLAN-USB-Stick which can act as access point?

"apropos wireless" is your friend here. A quick perusal shows that
rum(4) and ural(4) are USB and provide Host AP modes. I have personally
used rum(4) as an access point briefly but wireless is limited to
802.11g for now in general and rum(4) and ural(4) are 802.11a/b/g and
802.11b/g respectively. Work is ongoing to add 802.11n support to
OpenBSD starting with iwm(4).

Bryan

Re: MacbookPro 11,1

[Bryan Vyhmeister]

On Mon, Nov 23, 2015 at 06:28:04PM -0500, Bryan Everly wrote:
> I only had to bless my thumb drive so the keyboard worked. Everything
> else is native when booting from the hard drive afaik.

Very good. I didn't think about "blessing" the thumb drive. Good idea.

Bryan

Re: MacbookPro 11,1

[Bryan Vyhmeister]

On Mon, Nov 23, 2015 at 09:22:04AM -0500, Bryan C. Everly wrote:
> I tried a few months ago to boot this into OpenBSD and one of the big
> problems I ran into was that this is a USB 3 only machine and as such, the
> keyboard worked at the boot prompt but did not work when I got to the first
> installer prompt.

I never had any success with any Apple machine of recent vintage until
efiboot became available very recently. Now with the changes to
inteldrm(4) over the weekend, most things are working well for me.

> I'm seeing people talking about working on Macbook Air machines (some of
> quite recent vintage) so I'm wondering if:
> 
> 1.  There is a patch I can apply to get keyboard support working on the
> Macbook Pro Retina; or

I was corresponding with Joerg Jung about his 2015 12-inch Retina
MacBook and he also has the same issue. I also booted up my 2015 12-inch
Retina MacBook yesterday and had no keyboard at all. His solution was a
USB keyboard and a USB hub. I didn't have either handy but may try that
later today. In the case of the 12-inch Retina MacBook, there is only
that single USB-C port so I'm not sure if the USB hub was needed for any
reason other than to provide at least two ports (one for USB flash drive
and one for USB keyboard).

> 2.  The Macbook Air doesn't have all USB 3 ports so this isn't a problem
> for that hardware

The last several generations only show xhci(4) rather than any uhci(4).
I don't know what is different about the MacBook Air systems that allows
the keyboard to work since the keyboard does attach as ukbd(4).

> Any suggestions would be appreciated.

My solution was to create an OpenBSD efiboot flash drive and then things
worked fairly well. In your case, you probably need a USB keyboard and
possibly a USB hub. I will post a separate post soon with more
information about both of my MacBook Air systems but, in short, the 2013
MacBook Air, which is a Haswell system like your MacBook Pro, works
quite well.  Obviously wireless is not supported but a urtwn(4) USB
wireless adapter works fine. X acceleration works fine as does
xbacklight(1) to set screen brightness. The brightness buttons on the
keyboard do not work though. Keyboard backlight is functional (although
not yet adjustable) due to Joerg Jung's recent asmc(4) driver.

The 2015 MacBook Air which is a Broadwell system works almost as well
but does not have X acceleration at this time (disabled for now due to
instability) and also does not respond to xbacklight(1) so there is no
way to adjust screen brightness. To see the state of things in Linux, I
also installed Fedora 23 last week which comes with Linux kernel 4.2 and
that also could not adjust the brightness of the display at all even
though it acted as though it was working.

I am interested to see what you find with your system since I am looking
to pick up a similar Haswell Retina MacBook Pro from the refurbished
store to use with OpenBSD as well.

Bryan

Re: MacbookPro 11,1

[Bryan Vyhmeister]

On Mon, Nov 23, 2015 at 04:20:56PM -0500, Bryan C. Everly wrote:
> The /usr/sbin/bless command was the key that unlocked this for me.  I have
> managed to get the latest snapshot installed and booting on this machine.
> I'm in the process of installing a desktop (I run gnome) so I'll let you
> know how that goes.

You must be using BIOS emulation then? My goal with my install was to
avoid using BIOS emulation if possible. I wanted to be able to install
OpenBSD on a Mac without needing to use OS X at all or dual boot. As I'm
sure you've read, jcs@ has a gist about this process and jasper@ has a
blog post detailing how to do the efiboot like I did.

I'm looking forward to finding out how it works out for you.

Bryan

Re: inteldrm(4) display corruption on MacBook

[Bryan Vyhmeister]

Thanks so much for that commit. The system boots up and has a very brief
moment of display corruption before it switches to inteldrm(4) and works
perfectly. This works on both my 2013 MacBook Air (Haswell HD 5000
graphics)) and 2015 MacBook Air (Broadwell HD 6000 graphics). I haven't
had a chance to test the 12-inch Retina MacBook or any other system yet
but should be able to test some more in a few days. The only problem I
have found so far now is that xbacklight does not seem to work on the
Broadwell system although it works fine on the Haswell one. Thanks
again! I am really happy to be able to finally use a Mac system with
OpenBSD, efiboot, and inteldrm(4)!

Bryan

Re: inteldrm(4) display corruption on MacBook

[Bryan Vyhmeister]

I just tested a 2015 MacBook Air (HD 6000 graphics) and still see the
same display corruption. This seems to happen on all Intel Graphics Macs
at least from HD 4000 and up and specifically your system, the 12-inch
Retina MacBook, 2013 MacBook Air, and 2015 MacBook Air. Hopefully
kettenis@ will have time to look at this eventually but he is very busy
at the moment.

Bryan

Re: (U)EFI install and boot not finding hd0a:/bsd

[Bryan Vyhmeister]

On Tue, Nov 3, 2015, at 03:23 AM, YASUOKA Masahiko wrote:
> I fixed the problem with the booted device on cvs repository.
> Thank for your report.
> 
> > Is this something unique to Apple hardware or is this something that
> > all (U)EFI installs have trouble with?
> 
> efiboot had used a protocol of UEFI which macbook doesn't support.

Wonderful! I rebuilt my BOOTX64.EFI and installed it to the EFI boot
partition and the MacBook Air finds the kernel perfectly. The EFI boot
no longer shows anything other than hd0 as I would expect. No more fd0
or errors about it. Should a softraid(4) crypto root also work fine with
EFI boot? Thank you so much!

Bryan

Re: (U)EFI install and boot not finding hd0a:/bsd

[Bryan Vyhmeister]

On Tue, Nov 3, 2015, at 10:34 AM, YASUOKA Masahiko wrote:
> > Wonderful! I rebuilt my BOOTX64.EFI and installed it to the EFI boot
> > partition and the MacBook Air finds the kernel perfectly. The EFI boot
> > no longer shows anything other than hd0 as I would expect. No more fd0
> > or errors about it. Should a softraid(4) crypto root also work fine with
> > EFI boot? Thank you so much!
> 
> Yes, softraid will work with efiboot.

Excellent! Thank you very much.

Bryan

Re: (U)EFI install and boot not finding hd0a:/bsd

[Bryan Vyhmeister]

On Mon, Nov 2, 2015, at 01:53 AM, Sevan / Venture37 wrote:
> With miniroot58.fs can't boot and if I use the traditional media with
> BIOS support, I have to keep on pressing a key on my keyboard to
> prevent the screen from going to sleep so everything is a little
> frantic.

Interesting. I booted to do the install with miniroot58.fs written to a
USB flash drive. I then added an additional partition to the same USB
flash drive and put all my sets in there (long story short). Normally I
have been unable to get to the install prompt successfully with
traditional non-(U)EFI boot media. The install has always frozen with
various problems. This time, after booting from EFI, everything went
just fine. Now, if I disabled inteldrm(4) and switched back to efifb(4)
and used wsfb(4) in X, I could have a mostly working install. I’m hoping
changes come through on inteldrm(4) attachment to fix this display
corruption and this system might be an excellent OpenBSD option (with a
USB urtwn(4) or other for wireless).

Bryan

Re: Missing libcrypto file in -current

[Bryan Vyhmeister]

On Mon, Nov 2, 2015, at 07:47 PM, Ted Unangst wrote:
> The version of libcrypto recently changed, but the snapshot was built
> with the old file list, so it wasn't included. until next time...

Thank you. That confirmation is very much appreciated.

Bryan

Re: Missing libcrypto file in -current

[Bryan Vyhmeister]

On Mon, Nov 2, 2015, at 06:10 PM, Dutch Ingraham wrote:
> Hi all:
>
> I just installed 5.8 on the x86_64 arch.  Immediately after installing,
> I upgraded to -current.  Upon rebooting into the new -current, a number
> of errors appeared in the dmesg after the network started.  The first
> error was:
>
> ssh-keygen: can't load library 'libcrypto.so.36.1'
>
> A cascade of errors followed: syslogd, pflogd, ntpd, and smtpd.
>
> In fact, I don't have 'libcrypto.so.36.1' but 'libcrypto.so.35.0.'
>
> Did I possibly miss something obvious in the upgrade (??) or should I
> take this over to tech@?

I just experienced the same thing several hours ago. I’ve been using the
Nov 1 and Nov 2 snapshots on several machines and VMs but I did a new
install of the Nov 2 snapshot in a new VM and ran into this error. I
don’t have libcrypto.so. at all but only libcrypto.a and one other form.
Just to be sure something wasn’t wrong with install58.iso, I rebooted
into bsd.rd and did an upgrade and pulled the sets from the master site
and nothing changed. Still the same errors and no libcrypto.so.36.1.

Bryan

(U)EFI install and boot not finding hd0a:/bsd

[Bryan Vyhmeister]

Perhaps this is related to something else but on my 2013 MacBook Air
with an OpenBSD-only EFI install, boot fails to attempt booting from
hd0a:/bsd but instead tries fd0a:/bsd several times. I tried adding
/etc/boot.conf with boot hd0a:/bsd in both sd0i (the EFI boot partition)
and sd0a. Is this something unique to Apple hardware or is this
something that all (U)EFI installs have trouble with?

Bryan

Re: (U)EFI install and boot not finding hd0a:/bsd

[Bryan Vyhmeister]

On Sun, Nov 1, 2015, at 04:18 PM, Sevan / Venture37 wrote:
> On 1 November 2015 at 18:09, Bryan Vyhmeister <br...@bsdjournal.net>
> wrote:
> > Perhaps this is related to something else but on my 2013 MacBook Air
> > with an OpenBSD-only EFI install, boot fails to attempt booting from
> > hd0a:/bsd but instead tries fd0a:/bsd several times. I tried adding
> > /etc/boot.conf with boot hd0a:/bsd in both sd0i (the EFI boot partition)
> > and sd0a. Is this something unique to Apple hardware or is this
> > something that all (U)EFI installs have trouble with?
> 
> Same issue on the mid-2012 Air
> https://pbs.twimg.com/media/CSvkrgcWEAAF0xI.jpg

Do you have the same issues with inteldrm(4) attaching to pci(4) and
then the display getting garbled?

Bryan

Re: EFI Install on 2013 MacBook Air and Display Corruption

[Bryan Vyhmeister]

After the additional commits by Mark Kettenis here:

http://marc.info/?l=openbsd-cvs=144620412406055=2

I still have the same errors. The dmesg from today looks the same (link
here and inline below):

http://www.bsdjournal.net/files/macbookair/dmesg.20151030.txt

Thanks again.

Bryan


OpenBSD 5.8-current (GENERIC.MP) #1551: Fri Oct 30 08:18:12 MDT 2015
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
RTC BIOS diagnostic error
ff
real mem = 8509276160 (8115MB)
avail mem = 8247255040 (7865MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0x8cd14000 (42 entries)
bios0: vendor Apple Inc. version "MBA61.88Z.0099.B20.1509081314" date
09/08/2015
bios0: Apple Inc. MacBookAir6,1
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP HPET APIC SBST ECDT SSDT SSDT SSDT SSDT SSDT
SSDT SSDT SSDT MCFG DMAR
acpi0: wakeup devices P0P2(S3) EC__(S3) HDEF(S3) RP01(S3) RP02(S3)
RP03(S3) ARPT(S4) RP05(S3) RP06(S3) SPIT(S3) XHC1(S3) ADP1(S3) LID0(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) i7-4650U CPU @ 1.70GHz, 1600.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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,SENSOR,ARAT
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 100MHz
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-4650U CPU @ 1.70GHz, 1600.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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) Core(TM) i7-4650U CPU @ 1.70GHz, 1600.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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,SENSOR,ARAT
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 1, core 0, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i7-4650U CPU @ 1.70GHz, 1600.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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins
acpiec0 at acpi0
acpimcfg0 at acpi0 addr 0xe000, bus 0-155
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (P0P2)
acpiprt2 at acpi0: bus 1 (RP01)
acpiprt3 at acpi0: bus 2 (RP02)
acpiprt4 at acpi0: bus 3 (RP03)
acpiprt5 at acpi0: bus 5 (RP05)
acpiprt6 at acpi0: bus 4 (RP06)
acpicpu0 at acpi0: C3(200@506 mwait.1@0x60), C2(200@148 mwait.1@0x33),
C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: C3(200@506 mwait.1@0x60), C2(200@148 mwait.1@0x33),
C1(1000@1 mwait.1), PSS
acpicpu2 at acpi0: C3(200@506 mwait.1@0x60), C2(200@148 mwait.1@0x33),
C1(1000@1 mwait.1), PSS
acpicpu3 at acpi0: C3(200@506 mwait.1@0x60), C2(200@148 mwait.1@0x33),
C1(1000@1 mwait.1), PSS
acpibat0 at acpi0: BAT0 model "3545797981023400290" type
3545797981528607052 oem "3545797981528673619"
acpiac0 at acpi0: AC unit online
acpibtn0 at acpi0: LID0
acpibtn1 at acpi0: PWRB
acpibtn2 at acpi0: SLPB
acpivideo0 at acpi0: IGPU
acpivout0 at acpivideo0: DD01
cpu0: Enhanced SpeedStep 1600 MHz: speeds: 2301, 2300, 2200, 2100, 2000,
1900, 1800, 1700, 1600, 1500, 1400, 1300, 1200, 1100, 1000, 900, 800,
759 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Core 4G Host" rev 0x09
inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics 5000" rev 0x09
drm0 at inteldrm0
inteldrm0: msi
error: [drm:pid0:inteldrm_attach] *ERROR* failed to init modeset
Memory manager not 

EFI Install on 2013 MacBook Air and Display Corruption

[Bryan Vyhmeister]

I figured I would follow the post by jasper@ about doing a (U)EFI
install and apply it to a 2013 11-inch MacBook Air I have. On
yesterday’s snapshot of amd64, everything boots up with GENERIC.MP right
up to the login screen which is better than I have been able to achieve
with BIOS emulation and a traditional install. The first dmesg is from
my successful boot from yesterday.

http://www.bsdjournal.net/files/macbookair/dmesg.20151028.txt

After that, I asked about inteldrm(4) support on Twitter since I could
only use wsfb(4) initially with X (X couldn’t find a screen with
efifb(4) apparently). Bryan Steele and Chris Cappuccio let me know that
Mark Kettenis was working on allowing inteldrm(4) to attach via pci(4)
rather than vga(4) since vga(4) is typically not available with (U)EFI
booting. In the last twelve hours or so the initial support for
inteldrm(4) to attach to pci(4) has arrived (thank you!) but it didn’t
work smoothly for me and resulted in display corruption after I
installed that snapshot. I am still able to login via ssh. The dmesg
with the errors related to inteldrm(4) is available here:

http://www.bsdjournal.net/files/macbookair/dmesg.20151029.txt

I also have a picture of what the display corruption looks like here:

http://www.bsdjournal.net/files/macbookair/display-corruption.20151029.jpg

I’m happy to do any testing to get this worked out if that might be
helpful. Thanks again to all the developers for OpenBSD!

Bryan

Re: Request for Funding our Electricity

[Bryan Vyhmeister]

On Wed, Jan 15, 2014 at 07:41:03PM +0100, Martin Schröder wrote:
 Him being the leader is the very reason this project still exists.

The thing about OpenBSD is that it has a very clear and strong focus.
This comes from clear and strong leadership. Is Theo right on
everything? Of course not. None of us are. However, he directs things in
a direction that benefits all of us and OpenBSD has an absolutely clear
focus and direction.

Some other operating systems might be entertaining, an academic
exercise, or a just because effort (anyone running Debian/kFreeBSD in
production?) but OpenBSD is extremely powerful and useful. Nothing comes
close in my opinion and there's a reason for that. OpenBSD doesn't have
a huge democratic process that takes months or years to decide anything.
Instead, real work gets done every single release and new and improved
functionality is there every single time without a bunch of binary
blobs.

I'm doing whatever I can to help encourage corporate sponsorship and I
would encourage everyone else to do the same. Now is not the time to
comment on what you think of Theo's leadership. If you don't like it,
use something else. That's the beauty of freedom. No one is forcing you
to use OpenBSD. Let's limit the noise to things that could actually
benefit OpenBSD rather than what we think might be wrong.

Each of us should be looking at ways that *we* can help OpenBSD rather
than pointing out what the developers could do in addition to all the
volunteer coding they're already doing. Don't forget how valuable and
expensive it would be to hire all of these amazing developers to do what
they love doing.

Bryan

Re: low-power/small form factor server (supermicro X9SCL-F w Core i3-3220T)

['Bryan Vyhmeister']

On Wed, Nov 20, 2013 at 12:26:49PM -0800, Paul B. Henson wrote:
 With the 200W power supply in the small form factor chassis,
 supermicro says the max processor TDP supported by the motherboard is
 45w. I guess if you put one in that potentially uses greater power but
 never push it to do so it would still work, but I assume bad things
 would happen if it ever accidentally cranked and tried to suck more
 power than was available 8-/.

From looking at Supermicro's CSE-510-203B page, it says 65W TDP and
every CPU I've mentioned below except for the Xeon E3 1220 (80W) and
Xeon E3 1230v2 (69W) fall below this.

  G860, Core i3 2120, Core i3 3240, Xeon E3 1220, Xeon E3 1260L, and
  Xeon E3 1230v2
 
 The specifications for the motherboard on the supermicro site say
 processors with integrated graphics are not recommended, and since
 so far I've been unable to push them into clarifying why I was a
 little leery. The footnote indicates it's coming from Intel regarding
 the C202 chipset. I've seen a handful of reports of people using
 processors with integrated graphics with this chipset, and then with
 your confirmation I feel better about ordering it. Obviously the
 chipset doesn't support integrated graphics, so the silicon in the CPU
 is going to waste, but I'm guessing the supermicro documentation team
 read doesn't support integrated graphics in the chipset
 documentation and translated that into you shouldn't use one as
 opposed to if you do use one, you can't use the integrated graphics.

I don't think it matters for lower power chips at all and I've been
using chips with integrated graphics for a long time with no issues.
There's only an option on the Xeon E3 chips for no integrated graphics
anyway. That being said, the Xeon E3 1260L and 1265Lv2 chips are ones
that Supermicro reps have recommended to me and both have integrated
graphics although they are low power chips. It's just a waste to use a
Xeon E3 1245v2, for example, which adds heat that shouldn't be there.

  If you don't need IPMI, you could save a few dollars and go with the
  non F versions of the boards. I have found that the IPMI Text
  Console never works right for anything I've tried including
  OpenBSD.
 
 I've used the serial redirection on illumos and linux boxes without
 any trouble. I rarely use the video redirection other than for
 potentially initial bootstrapping and rare diagnostic issues. It's
 nice not ever having to visit the box in person once it's racked :).

It certaily is convenient to avoid connecting a monitor to the system
and to be able to deal with things remotely. I do it all the time.

Bryan

Re: low-power/small form factor server (supermicro X9SCL-F w Core i3-3220T)

['Bryan Vyhmeister']

On Wed, Nov 20, 2013 at 01:31:23PM -0800, Paul B. Henson wrote:
 Hmm, I guess I was actually looking at the SuperServer 5017C-LF page:
 
 http://www.supermicro.com/products/system/1U/5017/SYS-5017C-LF.cfm
 
 It has the X9SCL-F motherboard, a similar chassis with a 200w power supply,
 and indicates max tdp = 45w. I asked supermicro support about the
 510T-203B chassis with the same motherboard, and they told me it only
 supported up to 45w as well. Dunno, better safe than sorry, the T
 version is about the same price as the regular.

Very interesting. There is some ambiguity in the specs. Looking at the
SC510L-200B chassis which is what's included with the SYS-5017C-LF
system you linked to, it also says 65W TDP.

http://www.supermicro.com/products/chassis/1U/510/SC510L-200.cfm

From one of my systems with a Pentium G640 in the SC510T-200B case along
with two Western Digital Scorpio Black 320GB 2.5-inch drives, these are
the hw.sensors values:

hw.sensors.cpu0.temp0=34.00 degC
hw.sensors.cpu1.temp0=34.00 degC
hw.sensors.acpitz0.temp0=27.80 degC (zone temperature)
hw.sensors.acpitz1.temp0=29.80 degC (zone temperature)
hw.sensors.sdtemp0.temp0=29.69 degC
hw.sensors.sdtemp1.temp0=29.62 degC
hw.sensors.lm1.temp0=35.00 degC
hw.sensors.lm1.temp1=33.50 degC
hw.sensors.lm1.temp2=28.00 degC
hw.sensors.lm1.fan0=3013 RPM
hw.sensors.lm1.fan1=164 RPM
hw.sensors.lm1.fan2=3006 RPM
hw.sensors.lm1.fan3=164 RPM
hw.sensors.lm1.fan4=2973 RPM

Also, the SC510T-200B page lists 65W TDP while the SC510T-203B (only
difference is gold rated power supply) doesn't list a TDP value. Also,
be aware that the SC510L-200B case (included with SYS-5017C-LF) is
listed as only having a single fan. I don't have one to verify but I can
verify that the SC510-200B has two fans next to each other as pictured
and the SC510T-200B has three fans, two in the same location as the
others and a third blowing on the two hot swap 2.5-inch hard drive bays.
I think the SC510T-200B/203B is the better choice for hard drives. I use
mostly SSDs in the SC510-200B systems I have.

Bryan

Re: low-power/small form factor server (supermicro X9SCL-F w Core i3-3220T)

['Bryan Vyhmeister']

On Wed, Nov 20, 2013 at 05:38:33PM -0800, Paul B. Henson wrote:
 I managed to escalate the integrated graphics question high enough to
 find somebody who knew what they were talking about, he said, as you
 confirmed, that they work fine with this motherboard other than that
 you cannot use the integrated graphics, it is disabled. Pretty much
 what I thought, they should clarify their footnote on the
 specification page.

Looking at one of the pages, it only says the Xeon E3 12x5 [v2] chips
are not recommended. They really should specify more clearly.

 Out of curiosity, have you tried enabling the ipmi driver? I have an
 older atom server with an X7SPA-HF motherboard (which is actually
 being replaced by this one), and I found that the ipmi sensor provided
 more values than the lm one. The box came as passively cooled, I ended
 up sticking in three fans anyway. It still runs a bit hot, but within
 the acceptable range for that processor:

The ipmi(4) driver only supports IPMI 1.5 although the X7SPA-HF
specifies that it supports IPMI 2.0 just like the X9SCL-F and similar
boards. For whatever reason it doesn't provide any values or load at
all. The kern.watchdog.period option also doesn't appear on this system
(running 5.4, by the way). The ipmi(4) driver shows up in my dmesg but
as:

ipmi at mainbus0 not configured

A few years back I had an X7SPA-HF or similar board in the barebones
system you can buy but I don't have a dmesg from it readily accessible.
In any case, ipmi(4) is not working on my systems.

Bryan

Re: low-power/small form factor server (supermicro X9SCL-F w Core i3-3220T)

['Bryan Vyhmeister']

On Wed, Nov 20, 2013 at 10:16:05PM -0500, Ted Unangst wrote:
 The ipmi driver is disabled by default because it does bad things on
 some systems. If you don't go out of your way to enable it, the not
 configured line is all you'll see.

Thanks for the clarification. I wasn't aware of that. What sort of bad
things happen? I wonder how difficult adding IPMI 2.0 support would be
or if it would matter at all.

Bryan

Re: low-power/small form factor server (supermicro X9SCL-F w Core i3-3220T)

['Bryan Vyhmeister']

On Thu, Nov 21, 2013 at 12:57:06AM -0500, Ted Unangst wrote:
 machine hangs and such. you will figure out if you're affected or not
 pretty quickly. :) cause unknown.

Good to know. I'll try it out and see what happens. Thanks.

Bryan

Re: low-power/small form factor server (supermicro X9SCL-F w Core i3-3220T)

[Bryan Vyhmeister]

On Tue, Nov 19, 2013 at 07:45:46PM -0800, Paul B. Henson wrote:
 I'm looking at the supermicro X9SCL-F motherboard which has an Intel
 C202 PCH chipset and 2 gigabit interfaces (Intel 82579LM and 82574L),
 combined with a Core i3-3220T, stuffed in a 510T-203B chassis.

I have lots of X9SCL-F, X9SCL+-F, X9SCM-F, X9SCI-LN4, X9SCI-LN4F,
X9SCM-iiF boards running OpenBSD in production. Both network interfaces
work flawlessly. I mostly use the CSE-510-200B, CSE-510T-200B, and
CSE-512L-200B chassis options from Supermicro. I use the Kingston
KVR13E9 Unbuffered ECC memory chips in all the various sizes (2GB, 4GB,
and 8GB). Although I'm not using any of the low power chips since I've
found that heat is really not an issue and the non T chips scale down
just the same, I have used lots of chips including the Pentium G620,
G860, Core i3 2120, Core i3 3240, Xeon E3 1220, Xeon E3 1260L, and Xeon
E3 1230v2. You will also want the Supermicro SNK-P0046P heatsink for any
of those 1U cases and an LGA1155 CPU.

If you want to use the IPMI feature, it works fine with the Java
IPMIview software on OS X (presumably Windows and Linux too) with the
KVM Console option with the addition of a couple of
Supermicro-provided Java libraries (do a search to find blog posts about
this on OS X).

If you don't need IPMI, you could save a few dollars and go with the non
F versions of the boards. I have found that the IPMI Text Console
never works right for anything I've tried including OpenBSD.

 I see from the em man page and the list archives that those two Intel
 ethernet chipsets seem reasonably well supported. I couldn't find any
 specific mention of the C202 chipset, but I believe the Intel AHCI SATA
 interface is actually AHCI compliant, so trust it would work fine with the
 standard ahci driver. The i3 processor has a 35w TDP versus the atom's 8.5w,
 but actually working with openbsd is a bit more important than saving a few
 watts :).

The C202, C204, C206, C212, C214, and C216 controllers all work
perfectly with hard drives or SSDs.

 According to the Intel ARK this i3 processor should support ECC memory when
 installed on a board with a server class chipset. I really appreciated the
 heads up I got last week about the unsupported atom, that definitely saved
 me from ordering a box I couldn't use 8-/, so if anybody sees any potential
 issues with this combination for an openBSD server I'd appreciate hearing
 about it :).

You'll have no issues at all. It's a great combination. I tell my
customers and everyone else to just go with an X9SC{L,M} board, an
LGA1155 Pentium, Core i3, or Xeon E3 (if absolutely necessary) and be
done with it. The cheaper Pentium chips and Core i3 support ECC
perfectly and that saves a lot of money that would be wasted on fast
CPUs for minimal workloads.

Bryan

Re: Looking for a laptop in the Toronto area

[Bryan Vyhmeister]

On Wed, Oct 30, 2013 at 05:33:56PM -0700, Dag Richards wrote:
 Theo de Raadt wrote:

 But really, those of you are telling him that are MISSING THE POINT
 ENTIRELY.
 
 Oh time to help is it?
 Where to send the cheque?

I'm sending $500 so we can get this done. Details are here in case
anyone else needs them:

http://www.undeadly.org/cgi?action=articlesid=20131118060855

Bryan

Re: Best OpenBSD cloud hosting?

[Bryan Vyhmeister]

On Mon, Oct 21, 2013 at 05:57:32AM -0400, Jiri B wrote:
 please put info about your testing public. I suppose more people would
 be interested.

I certainly will. I will write everything I find up in an article. Thank
you.

Bryan

Re: Best OpenBSD cloud hosting?

[Bryan Vyhmeister]

On Wed, Oct 09, 2013 at 08:45:37PM +0200, Antoine Jacoutot wrote:
 I personally use SmartOS and while it is an awesome system, OpenBSD
 does not always behave perfectly well under Solaris KVM.  I've had
 several vdisk related issues.  In my experience, Linux KVM is a better
 container for our OS.

Could you elaborate on this? I've run OpenBSD under SmartOS briefly a
few months ago and it seemed to run just fine on my own test box. Were
you using the virtio(4) drivers? I did have network troubles when I
tried them but that was early this year and using the non-virtio network
setup seemed to work fine. I don't remember what I did for disk
settings. I'll have to look at my backups.

Bryan

Re: Best OpenBSD cloud hosting?

[Bryan Vyhmeister]

On Sun, Oct 20, 2013 at 11:13:51PM +0200, Antoine Jacoutot wrote:
 I am often unable to properly shutdown OpenBSD VMs, disks hang.  Using
 virtio or not does not change that.  I did not look into it very
 deeply yet so ... But I never saw this issue in Linux KVM.

Thank you for your response. I'll do testing myself and see if that's
still a problem or what else might be a factor. Thank you.

Bryan

Re: OT: SuperMicro X9SBAA-F with OpenBSD

[Bryan Vyhmeister]

On Fri, Oct 04, 2013 at 03:22:54PM -0700, Chris Cappuccio wrote:
 I accidentally got some supermicro boards with IPMI. Not sure why
 but under OpenBSD the IPMI freaks out crazy all the time. Probably
 wants to use some memory OpenBSD already uses or some shit.  I just ignore
 the blinking light. One of these days

Using Supermicro's IPMIView on OS X, I can use the KVM Console just
fine and is very useful for my datacenter installations. The Text
Console option has never worked right and I gave up on it quite a while
back. This is with OpenBSD 5.3 and later on X9SCL-F, X9SCM-F, and
X9SCI-LN4F boards.

Bryan

Re: Hard Freeze with Snapshots After Aug 19 on ThinkPad X1 Carbon

[Bryan Vyhmeister]

On Thu, Sep 19, 2013 at 01:28:08AM -0400, Gabriel Guzman wrote:
 Ok, been awhile, but I'm definitely still getting some freezes.  I'm
 unable to get a ddb report though as it seems that the kernel hasn't
 actually crashed.   It's a bit of a strange problem, and I'm at a loss
 as to how to provide more detail.   I'll throw in everything I've got.
 Here's the detailed version of what happens: 
 
 Working normally, running programs, checking mail, browsing web, then
 unpredictably the system starts to hang.  Usually the pattern goes like
 this.  No more window updates in X but I'm still able to switch to a
 virtual tty(C1, C2, C3) however, if I attempt to login, I can type my
 username and password, but when I hit enter --- nothing.  I also noticed
 that if I have an ssh session to the machine from another machine, the
 shell is still responsive (i.e. I can hit enter and get a new prompt)
 but if I run anything, even an ls... the program doesn't run and I get
 blocked from doing anything else in that window.  Eventually pings stop
 responding as well, though if I have an open systat window I can see
 the CPU at 100% idle.  It's as if programs that have already been loaded
 into ram continue working, but nothing new can be loaded and executed.
 My only recourse once the pings all stop responding is to hold down the
 power button and restart the machine.
 
 Anyone have any ideas on how to try and get more details?  If I had to
 guess... I'd guess buggy radeon firmware, but... what do I know?

I'm not sure what to tell you. My freezes all totally disappeared and I
haven't had any more since then. I'm wondering if this is related to
radeondrm or something like that. Hopefully someone who knows more can
chime in. Are they still continuing with the latest snapshots?

Bryan

Re: Intel I210 ethernet card support

[Bryan Vyhmeister]

On Aug 10, 2013, at 6:10, Jonathan Gray j...@jsg.id.au wrote:

 The i210/i211 chips aren't supported yet.  The i217/pch_lpt found
 in the Lynx Point/Haswell PCH isn't either.  I don't think any of
 the usual suspects have hardware yet.

Do those that need the hardware have it yet? If not, what's needed? The 
Supermicro X10SLL-S would be a good choice since it has both i217LM  i210AT 
Ethernet. That board along with a Pentium G3220 and 4GB of ECC RAM could get a 
developer the required hardware for Haswell.

Bryan

Re: Hard Freeze with Snapshots After Aug 19 on ThinkPad X1 Carbon

[Bryan Vyhmeister]

On Sat, Sep 07, 2013 at 09:33:07PM -0400, Gabriel Guzman wrote:
 
 Completed a fresh install to the Sept 3rd snapshot and was still having
 the same problem, though much less frequently.  Just upgraded to sept
 7th snap this evening, and so far so good.  

I'm glad it's working for you so far. I only had a single freeze with
the Sep 3rd snapshot myself. I just updated to the Sep 7th snapshot as
well. We'll see how it goes.

Bryan

Re: A suggestion for snapshots

[Bryan Vyhmeister]

On Fri, Sep 06, 2013 at 06:59:29PM +0200, Marc Espie wrote:
 There are also bottlenecks in fanning out from the actual build machines.
 Ports bulk builders are aware of the issues.  These take time to solve.

Would additional fast build machines help? Is that a large part of the
problem?

Bryan

Re: Hard Freeze with Snapshots After Aug 19 on ThinkPad X1 Carbon

[Bryan Vyhmeister]

On Wed, Sep 04, 2013 at 11:46:21AM -0700, Bryan Vyhmeister wrote:
 I installed the 2013/09/03 snapshot first thing this morning and have
 been running all day with it so far. By this point on the previous two
 snapshots I would have at least two to three hard freezes. So far
 everything is good. If that changes I will update this thread.

One freeze after working all day. Whatever it is the situation is
improved but not totally solved apparently.

Bryan

Re: Hard Freeze with Snapshots After Aug 19 on ThinkPad X1 Carbon

[Bryan Vyhmeister]

I installed the 2013/09/03 snapshot first thing this morning and have
been running all day with it so far. By this point on the previous two
snapshots I would have at least two to three hard freezes. So far
everything is good. If that changes I will update this thread.

Bryan

Re: Hard Freeze with Snapshots After Aug 19 on ThinkPad X1 Carbon

[Bryan Vyhmeister]

On Sep 2, 2013, at 3:13, Stefan Sperling s...@openbsd.org wrote:

 If your system locks up over night without being used (which I've seen
 happen once, too, but it's hard to reproduce), or you don't have
 wsmoused running in the first place, then it's probably some other issue.

I'm not running xdm or wsmoused and it happens overnight. It runs perfectly 
with no issues with the Aug 19 snapshot but the following two (Aug 24 and Aug 
29) have the freeze. Must not be that issue then. Thank you.

Bryan

Re: Hard Freeze with Snapshots After Aug 19 on ThinkPad X1 Carbon

[Bryan Vyhmeister]

On Sep 2, 2013, at 9:13, Gabriel Guzman g...@guzman-nunez.com wrote:

 I'm seeing the same thing on my desktop (dmesg below).  Random freezes,
 no debug output that I've seen in any logs, first time I noticed was
 after updating to aug24 snapshot, behavior is the same with aug29th.  

I think this must be the same issue because the behavior surfaced at exactly 
the same time.

 Don't have much more data at the moment, still can't reliably get the
 freeze to happen, sometimes it's when I launch tmux (tmux attach -t0)
 sometimes it's when I have a lot of xterms open... last night it was
 when I was playing warzone2100 (hey, I just got good video support with
 my radeon card!!!) always happens in X
 though, I can use the machine all day long via ssh from work w/out
 an issue.  

It's never reliable for me either. It's only happened in X but I always run X 
so that isn't much help.

 I'll try and track down more data, and run through the disable apmd, etc
 process laster this afternoon.  And if it's useful, I can backtrack
 through snapshots to see where this started happening.

I am also running apmd with either -A or -C. It's interesting that this happens 
on an AMD system which seems to indicate that it's not Intel graphics related 
or something like that.

Bryan

Re: Hard Freeze with Snapshots After Aug 19 on ThinkPad X1 Carbon

[Bryan Vyhmeister]

On Sun, Sep 01, 2013 at 12:31:48PM +0200, Stefan Sperling wrote:
 
 Guys, you need to post dmesg output. Marketing names of laptops
 don't tell us what hardware you're running.
 
 Are any of you using Synaptics or APLS touchpads, per chance?

Yes, I have a Synaptics touchpad and the freeze has only happened under
X as far as I know but I am pretty much always running X. Thank you.

Bryan


OpenBSD 5.4-current (GENERIC.MP) #48: Thu Aug 29 11:22:15 MDT 2013
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8255741952 (7873MB)
avail mem = 8027881472 (7655MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xdae9d000 (70 entries)
bios0: vendor LENOVO version G6ET93WW (2.53 ) date 02/04/2013
bios0: LENOVO 3443CTO
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SLIC TCPA SSDT SSDT SSDT HPET APIC MCFG ECDT FPDT ASF! 
UEFI UEFI MSDM SSDT SSDT DMAR UEFI SSDT DBG2
acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP2(S4) XHCI(S3) EHC1(S3) 
EHC2(S3) HDEF(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) i7-3667U CPU @ 2.00GHz, 1896.04 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,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
cpu0: apic clock running at 99MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i7-3667U CPU @ 2.00GHz, 1895.69 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,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS
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) i7-3667U CPU @ 2.00GHz, 1895.69 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,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS
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) i7-3667U CPU @ 2.00GHz, 1895.69 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,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
acpimcfg0 at acpi0 addr 0xf800, bus 0-63
acpiec0 at acpi0
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG_)
acpiprt2 at acpi0: bus 2 (EXP1)
acpiprt3 at acpi0: bus 3 (EXP2)
acpicpu0 at acpi0: C2, C1, PSS
acpicpu1 at acpi0: C2, C1, PSS
acpicpu2 at acpi0: C2, C1, PSS
acpicpu3 at acpi0: C2, C1, PSS
acpipwrres0 at acpi0: PUBS
acpitz0 at acpi0: critical temperature is 200 degC
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
acpibat0 at acpi0: BAT0 model 45N1071 serial  2531 type LiP oem SMP
acpibat1 at acpi0: BAT1 not present
acpiac0 at acpi0: AC unit online
acpithinkpad0 at acpi0
cpu0: Enhanced SpeedStep 1896 MHz: speeds: 2001, 2000, 1900, 1800, 1700, 1600, 
1500, 1400, 1300, 1200, 1100, 1000, 900, 800 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 Intel Core 3G Host rev 0x09
vga1 at pci0 dev 2 function 0 Intel HD Graphics 4000 rev 0x09
intagp0 at vga1
agp0 at intagp0: aperture at 0xe000, size 0x1000
inteldrm0 at vga1
drm0 at inteldrm0
inteldrm0: 1600x900
wsdisplay0 at vga1 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
Intel 7 Series xHCI rev 0x04 at pci0 dev 20 function 0 not configured
Intel 7 Series MEI rev 0x04 at pci0 dev 22 function 0 not configured
ehci0 at pci0 dev 26 function 0 Intel 7 Series USB rev 0x04: apic 2 int 16
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1
azalia0 at pci0 dev 27 function 0 Intel 7 Series HD Audio rev 0x04: msi
azalia0: codecs: Realtek ALC269, Intel/0x2806, using Realtek ALC269
audio0 at azalia0
ppb0 at pci0 dev 28 function 0 Intel 7 Series PCIE rev 0xc4: msi
pci1 at ppb0 bus 2
sdhc0 at pci1 dev 0 function 0 Ricoh 5U823 SD/MMC rev 0x04: apic 2 int 16
sdmmc0 at sdhc0
ppb1 at pci0 dev 28 function 1 Intel 7 Series PCIE rev 0xc4: msi
pci2 at ppb1 bus 3
iwn0 at pci2 

Hard Freeze with Snapshots After Aug 19 on ThinkPad X1 Carbon

[Bryan Vyhmeister]

I'm running OpenBSD/amd64 5.4-current with GENERIC.MP from 2013/08/19
downloaded from the mirrors on a Levovo ThinkPad X1 Carbon. Both
snapshots I have tried (2013/08/25 and 2013/08/29) after the 19th have
resulted in hard system freezes every few hours. I don't have any logs
or anything else that indicate a hard freeze but everything just hard
freezes. I first noticed because I left the ThinkPad running overnight
on my desk and when I came back to the system the next morning it was
hard frozen. Several times during the day while I'm working I have also
experienced the same thing. Anyone else seeing something similar?

Bryan

Re: Hard Freeze with Snapshots After Aug 19 on ThinkPad X1 Carbon

[Bryan Vyhmeister]

On Aug 30, 2013, at 12:43, Jean Lucas nos...@gmail.com wrote:

 Yes, on an IdeaPad Yoga 13 I also experience hard freezes throughout the
 day. The timing varies from as little as one hour to several. Started
 happening a few snapshots back (around Aug. 19).

Maybe ThinkPad ACPI related or something like that? Anyone have any ideas what 
might be causing the hard freezes? I haven't tried on my ThinkPad X230 but I 
could test on it as well if needed. 

Bryan