Re: objcopy / xv6 question

2015-12-06 Thread d.lowe 

Thanks, but Minix v3 is much more complicated than xv6.

On 12/06/15 14:44, Richard Thornton wrote:

Why not use minix version 3?

Sent from my BlackBerry 10 smartphone on the Verizon Wireless 4G LTE network.
   Original Message
From: d.l...@openmailbox.org
Sent: Sunday, December 6, 2015 8:40 AM
To: misc@openbsd.org
Subject: objcopy / xv6 question

Hello,

I am trying to compile and run xv6 on OpenBSD 5.8, a simple Unix Version
6 clone for educational
usage. I changed the Makefiles, so that it compiles fine on OpenBSD
(mail me if you need a copy).
Sadly enough, I still can't boot the xv6 image in qemu.

I noticed that the 'initcode' target produces a binary that is way too
big, compared to the initcode
binary on other hosts (eg linux). The command that generates such a big
binary is

$(OBJCOPY) -S -O binary initcode.out initcode

I am not sure, why do I get binary 'initcode' with 128MB?

I am not sure if this is the bug why xv6 doesn't boot, but I also do not
understand why I am getting
such a big binary from that command? Is this a bug in objcopy?

Any help is much appreciated.

Thanks,
- dl

Re: retrieving pkg_add messages afterwards?

2015-12-06 Thread lists 
> pkg_add-ing multiple packages, and pkg_add -u, lists out messages such
> as "You should also run rm -fr /var/spool/clamav/*" at the end of a
> batch.

It is likely the message indicates the directory is non empty, so it's
not automatically removed.  This most probably is not part of the
package install or deinstall notices, however.

For interactive use, run pkg tools in tmux(1) and access the scroll
buffer with prefix (C-b) [ or start a script(1) session for recording
the output of the terminal in a file.  Or simply redirect stdout and
stderr to a file for later review for non interactive use.  From the
FAQ:

http://www.openbsd.org/faq/faq15.html#PkgInstall
http://www.openbsd.org/faq/faq15.html#PkgRemove

Some packages have further details in /usr/local/share/doc/pkg-readmes
after installation.  Configuration is not overwritten, non empty dirs
and not removed etc.  In this case the package gets re-installed for
the update (pkg_add -u) so it may not be required to perform the
deinstall suggestions.  Verbosity is controlled by (multiple) -v flags.

For install and deinstall notices, check options -M and -U in the man
page:

$ man pkg_info

In practice this shows both for your installed packages:

$ cd /var/db/pkg; pkg_info -MU * | less

It is a good idea to remove unused dependencies with pkg_delete -a after
updating packages, and to remove partial packages if any (or redo their
installation / fix issues).

$ ls -ld /var/db/pkg/partial*

As a last resort, if you have trouble with packages, read this:

$ man pkg_check

> man pkg_add and pkg.conf shows me that the information is stored in
> ${PKG_DBDIR}, but I'm not seeing how I could retrieve the appropriate
> long information lines just from the last pkg_add .

You can look further into how pkg tools internals work.  This man page
contains a "LIST OF MODULES" section at the end.

$ man OpenBSD::Intro

To display the file name and then view the source of the respective
module you're interested in, e.g. OpenBSD::Add, do this:

$ perldoc -lm OpenBSD::PkgAdd
$ less $(perldoc -lm OpenBSD::PkgAdd)

Re: Suspend on Macbook Pro Retina (MacbookPro 11,1)

2015-12-06 Thread Mike Larkin 
On Fri, Dec 04, 2015 at 03:33:10PM -0500, Bryan C. Everly wrote:
> Hi everyone,
> 
> With the latest snapshot installed, I can confirm that this machine will
> (sort of) suspend.  Unfortunately it won't wake up.
> 
> When it suspends (via 'zzz' from the console), the screen turns off.
> However, the keyboard backlight, the USB network adapter I'm using, and the
> "red cylon eye" in the headphone jack are all still active.
> 
> Any information I can provide to help further the cause here?  Anyone who
> is willing to work with me to help figure out how we can unlock more of the
> potential in this hardware?
> 
> Thanks,
> Bryan
>

Considering that you didn't even give us a dmesg ...

man sendbug

Re: Suspend on Macbook Pro Retina (MacbookPro 11,1)

2015-12-06 Thread Bryan C. Everly 
Hi,

Happy to do so.  Here is an imgur link that has three shots.  I am using
the i3 desktop currently so I can have a little more control over the
fine-grained settings for HiDPI (I had previously been running Gnome 3).
Let me know if there is anything in particular you'd like to see:

https://imgur.com/a/CiQ82

Thanks,
Bryan

On Sun, Dec 6, 2015 at 6:46 AM, Артур Истомин
 wrote:

> On Fri, Dec 04, 2015 at 03:33:10PM -0500, Bryan C. Everly wrote:
> > Hi everyone,
>
> Hi, Bryan!
>
> Sorry for off-top and off-list, but can You please upload two or three
> screenshots of web-pages and any GUI application. I'm interesting how
> OpenBSD's
> fonts look at retina display.
>
> Thank You.

Re: release and patch/errata info in (easily) machine readable format?

2015-12-06 Thread Todd Mortimer 
On Sat, Dec 05, 2015 at 11:20:41AM -0800, openbsd-m...@clark-communications.com 
wrote:
> One approach would be to scrape http://www.openbsd.org/errata.html
> , and figure out the release numbers, and
> then scrape the errata page of a particular release to obtain the patch
> numbers.

If you're just looking for a raw number that will increase for every
patch added, you shouldn't need to scrape the website. There is a
tarball containing all patches for a given release, eg:

http://ftp.openbsd.org/pub/OpenBSD/patches/5.8.tar.gz

It is updated once a day. If you retrieve this, you can get a crude
'patch level' by just counting the number of entries in this tarball:

$ tar -tzf 5.8.tar.gz | wc -l 
  10

If you want to remove the whitespace, you can pipe through tr:

$ tar -tzf 5.8.tar.gz | wc -l | tr -d '[:space:]' 
10$ 

But it sounds like you're using CVS, so I don't think you even need to
bother with the errata page. If you are updating CVS via cron, then 
add the -q flag to your cvs up command. If anything in the stable tree
is updated, then you'll get an email from cron listing the updated files
and then you can go build a new release using your usual method.
Everything that ends up on the errata page is also in CVS, so you won't
miss anything. 

If you do something like this, then the 'patch level' can be reduced to
just the day you did the build, and you can include this in your build
by creating a siteXX file:

http://www.openbsd.org/faq/faq4.html#site

Where your siteXX.tgz contains a file with the date you did the build
(say, /etc/builddate). Then you can easily see if your machines are
running the most recent build by comparing the contents of that file to
the date you did your most recent build. 

Anyway, I know this isn't quite what you were after (machine readable
version / patch level), but if you're just looking to know when to do a
new release build, then you should be able to get there by just tracking
CVS. If you're just looking to track errata, then the tarball can help
you without having to scrape the website, and if you'd prefer to not hit
the website unnecessarily, then tracking the www CVS repo can tell you
when the errata pages have changed, and then you can retrieve the patch
tarball without having to scrape out info about the actual patch
numbers. 

Todd

vfs_syscalls.c PLEDGE_DPATH undeclared

2015-12-06 Thread 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: 5.8/sparc64 - boot from softraid(4) fails?

2015-12-06 Thread Stefan Sperling 
On Sat, Dec 05, 2015 at 09:34:35PM +0100, Alexander Bochmann wrote:
> I recently tried to install OpenBSD 5.8 on a Sun Fire, 
> using a RAID-1 softraid as boot device. System doesn't 
> boot though, and ends up with this:
> 
>  > Sun Fire V245, No Keyboard
>  > Copyright 2007 Sun Microsystems, Inc.  All rights reserved.
>  > OpenBoot 4.25.10, 4096 MB memory installed, Serial #67141234.
>  > Ethernet address 0:12:33:0:11:aa, Host ID: 8400123a.
>  > 
>  > Rebooting with command: boot
>  > Boot device: disk0  File and args: sr0a:/bsd
>  > OpenBSD IEEE 1275 Bootblock 1.4
>  > >> OpenBSD BOOT 1.7
>  > Unknown device: sr0
>  > Cannot boot from softraid: Unknown error: code 19
>  > Program terminated
> 
> As the documentation for booting from softraid on sparc64 
> feels somewhat sparse, I'm not actually shure I set things up 
> correctly:
> 
> - from the install cd, created disklabels with a RAID 
>   partition on sd0 and sd1
> - assembled softraid with bioctl:
> 
>  > # bioctl -c 1 -l /dev/sd0a,/dev/sd1a softraid0
>  > sd4 at scsibus2 targ 1 lun 0:  SCSI2 0/direct 
> fixed
>  > sd4: 70004MB, 512 bytes/sector, 143369136 sectors
>  > softraid0: RAID 1 volume attached as sd4
> 
> (the system has two other disks)
> 
> - ran ./install to install OpenBSD to sd4
> - rebooted and set boot parameters as per boot_sparc64(8)
> 
> Any steps I am missing? Any hints how to further debug this?
> 
> Thanks,
> 
> Alex.
> 

Can you show the output of 'devalias' at the ok> prompt?
If your disks are more than 4 levels deep inside the device tree
then the diskprobe loop in the boot loader won't see them.

If so, the following (untested) diff might fix the problem (adjusting
to an arbitrarily chosen higher recursion level of 10).

The easiest way to try this diff is to build a new release on another
sparc64 system (see man release(8)) and install that.

Alternatively, the following might work as a shortcut:
(If you're unsure about how to follow those steps, building a full
release will be easier!)
Compile all of /usr/src/sys/arch/sparc64/stand/ and run make install in
/usr/src/sys/arch/sparc64/stand/ofwboot, then copy /usr/mdec/ofwboot
onto a httpd server's webspace where a bsd.rd can fetch it from.
Boot the sun fire into bsd.rd and fetch the patched ofwoot to /tmp/.
Now mount your installed system's root partition at /mnt and its
/usr partition at /mnt/usr, and run:
  /mnt/usr/sbin/installboot sd4 /mnt/usr/mdec/bootblk /tmp/ofwboot
to install the patched boot loader.

Index: diskprobe.c
===
RCS file: /cvs/src/sys/arch/sparc64/stand/ofwboot/diskprobe.c,v
retrieving revision 1.3
diff -u -p -r1.3 diskprobe.c
--- diskprobe.c 9 Dec 2014 18:05:16 -   1.3
+++ diskprobe.c 6 Dec 2015 16:47:23 -
@@ -110,12 +110,12 @@ void dump_node(int node)
 
 /*
  * Hunt through the device tree for disks.  There should be no need to
- * go more than four levels deep.
+ * go more than 10 levels deep.
  */
 void
 diskprobe(void)
 {
-   int node, child, stack[4], depth;
+   int node, child, stack[10], depth;
char buf[32];
 
stack[0] = OF_peer(0);
@@ -146,7 +146,7 @@ diskprobe(void)
}
 
child = OF_child(node);
-   if (child != 0 && child != -1 && depth < 3)
+   if (child != 0 && child != -1 && depth < 9)
stack[++depth] = child;
else
stack[depth] = OF_peer(stack[depth]);

Re: vfs_syscalls.c PLEDGE_DPATH undeclared

2015-12-06 Thread 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: vmm uvm_fault in vmware player/workstation when Intel VT/AMD-v not enabled

2015-12-06 Thread Mike Larkin 
On Tue, Nov 24, 2015 at 11:02:30PM +0100, Erwin van Maanen wrote:
> Hello Misc, 
> 
> I was playing around with the new vmm in the bsd snapshot of Nov 23 under 
> VMWare Workstation. 
> And when enabling it, i forget to enabled "Virtualize Intel VT-x/EPT or 
> AMD-V/RVI" option in VMWare workstation an i get an uvm_fault: 
> 
> uvm_fault(0xff007f549f00, 0x60, 0, 1) -> e
> kernel: page fault trap, code=0
> Stopped at   vmmioctl+0x18:  movl   0x60(%rcx),%r8d
> ddb{3}>
> 
> After enabling "Virtualize Intel VT-x/EPT or AMD-V/RVI" all works fine afaik.
> It would be nice to get a little error saying, Intel VT/AMD-V not available 
> or something like that instead of the above.
> 
> Erwin

Following up on old emails - I believe this was already fixed by a later commit,
please let us know if this is not the case.

-ml

> 
> -- dmesg --
> OpenBSD 5.8-current (GENERIC.MP) #1652: Mon Nov 23 11:46:59 MST 2015
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> real mem = 2130640896 (2031MB)
> avail mem = 2061979648 (1966MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (556 entries)
> bios0: vendor Phoenix Technologies LTD version "6.00" date 05/20/2014
> bios0: VMware, Inc. VMware Virtual Platform
> acpi0 at bios0: rev 2
> acpi0: sleep states S0 S1 S4 S5
> acpi0: tables DSDT FACP BOOT APIC MCFG SRAT HPET WAET
> acpi0: wakeup devices PCI0(S3) USB_(S1) P2P0(S3) S1F0(S3) S2F0(S3) S3F0(S3) 
> S4F0(S3) S5F0(S3) S6F0(S3) S7F0(S3) S8F0(S3) S9F0(S3) S10F(S3) S11F(S3) 
> S12F(S3) S13F(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) i5-4670K CPU @ 3.40GHz, 3391.99 MHz
> cpu0: 
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,MMX,FXSR,SSE,SSE2,SS,HTT,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
> cpu0: 256KB 64b/line 8-way L2 cache
> cpu0: smt 0, core 0, package 0
> mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
> cpu0: apic clock running at 65MHz
> cpu1 at mainbus0: apid 1 (application processor)
> cpu1: Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz, 3391.55 MHz
> cpu1: 
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,MMX,FXSR,SSE,SSE2,SS,HTT,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
> cpu1: 256KB 64b/line 8-way L2 cache
> cpu1: smt 0, core 1, package 0
> cpu2 at mainbus0: apid 2 (application processor)
> cpu2: Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz, 3391.50 MHz
> cpu2: 
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,MMX,FXSR,SSE,SSE2,SS,HTT,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
> cpu2: 256KB 64b/line 8-way L2 cache
> cpu2: smt 0, core 2, package 0
> cpu3 at mainbus0: apid 3 (application processor)
> cpu3: Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz, 3391.45 MHz
> cpu3: 
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,MMX,FXSR,SSE,SSE2,SS,HTT,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
> cpu3: 256KB 64b/line 8-way L2 cache
> cpu3: smt 0, core 3, package 0
> ioapic0 at mainbus0: apid 4 pa 0xfec0, version 11, 24 pins
> acpimcfg0 at acpi0 addr 0xf000, bus 0-127
> acpihpet0 at acpi0: 14318179 Hz
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpicpu0 at acpi0: C1(@1 halt!)
> acpicpu1 at acpi0: C1(@1 halt!)
> acpicpu2 at acpi0: C1(@1 halt!)
> acpicpu3 at acpi0: C1(@1 halt!)
> acpibat0 at acpi0: BAT1 not present
> acpibat1 at acpi0: BAT2 not present
> acpiac0 at acpi0: AC unit online
> acpibtn0 at acpi0: SLPB
> acpibtn1 at acpi0: LID_
> pvbus0 at mainbus0: VMware
> vmt0 at pvbus0
> pci0 at mainbus0 bus 0
> pchb0 at pci0 dev 0 function 0 "Intel 82443BX AGP" rev 0x01
> ppb0 at pci0 dev 1 function 0 "Intel 82443BX AGP" rev 0x01
> pci1 at ppb0 bus 1
> pcib0 at pci0 dev 7 function 0 "Intel 82371AB PIIX4 ISA" rev 0x08
> pciide0 at pci0 dev 7 function 1 "Intel 82371AB IDE" rev 0x01: DMA, channel 0 
> configured to compatibility, channel 1 configured to compatibility
> wd0 at pciide0 channel 0 drive 0: 
> wd0: 64-sector PIO, LBA, 12288MB, 25165824 sectors
> wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
> atapiscsi0 at pciide0 channel 1 drive 0
> scsibus1 at atapiscsi0: 2 targets
> cd0 at scsibus1 targ 0 lun 0:  ATAPI 
> 5/cdrom

Re: vmm uvm_fault in vmware player/workstation when Intel VT/AMD-v not enabled

2015-12-06 Thread Mike Larkin 
On Sun, Dec 06, 2015 at 10:02:50AM -0800, Mike Larkin wrote:
> On Tue, Nov 24, 2015 at 11:02:30PM +0100, Erwin van Maanen wrote:
> > Hello Misc, 
> > 
> > I was playing around with the new vmm in the bsd snapshot of Nov 23 under 
> > VMWare Workstation. 
> > And when enabling it, i forget to enabled "Virtualize Intel VT-x/EPT or 
> > AMD-V/RVI" option in VMWare workstation an i get an uvm_fault: 
> > 
> > uvm_fault(0xff007f549f00, 0x60, 0, 1) -> e
> > kernel: page fault trap, code=0
> > Stopped at   vmmioctl+0x18:  movl   0x60(%rcx),%r8d
> > ddb{3}>
> > 
> > After enabling "Virtualize Intel VT-x/EPT or AMD-V/RVI" all works fine 
> > afaik.
> > It would be nice to get a little error saying, Intel VT/AMD-V not available 
> > or something like that instead of the above.
> > 
> > Erwin
> 
> Following up on old emails - I believe this was already fixed by a later 
> commit,
> please let us know if this is not the case.

Actually after looking a bit, it looks like this wasn't fixed. I'll commit the
fix presently.

-ml

> 
> -ml
> 
> > 
> > -- dmesg --
> > OpenBSD 5.8-current (GENERIC.MP) #1652: Mon Nov 23 11:46:59 MST 2015
> > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> > real mem = 2130640896 (2031MB)
> > avail mem = 2061979648 (1966MB)
> > mpath0 at root
> > scsibus0 at mpath0: 256 targets
> > mainbus0 at root
> > bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (556 entries)
> > bios0: vendor Phoenix Technologies LTD version "6.00" date 05/20/2014
> > bios0: VMware, Inc. VMware Virtual Platform
> > acpi0 at bios0: rev 2
> > acpi0: sleep states S0 S1 S4 S5
> > acpi0: tables DSDT FACP BOOT APIC MCFG SRAT HPET WAET
> > acpi0: wakeup devices PCI0(S3) USB_(S1) P2P0(S3) S1F0(S3) S2F0(S3) S3F0(S3) 
> > S4F0(S3) S5F0(S3) S6F0(S3) S7F0(S3) S8F0(S3) S9F0(S3) S10F(S3) S11F(S3) 
> > S12F(S3) S13F(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) i5-4670K CPU @ 3.40GHz, 3391.99 MHz
> > cpu0: 
> > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,MMX,FXSR,SSE,SSE2,SS,HTT,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
> > cpu0: 256KB 64b/line 8-way L2 cache
> > cpu0: smt 0, core 0, package 0
> > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
> > cpu0: apic clock running at 65MHz
> > cpu1 at mainbus0: apid 1 (application processor)
> > cpu1: Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz, 3391.55 MHz
> > cpu1: 
> > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,MMX,FXSR,SSE,SSE2,SS,HTT,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
> > cpu1: 256KB 64b/line 8-way L2 cache
> > cpu1: smt 0, core 1, package 0
> > cpu2 at mainbus0: apid 2 (application processor)
> > cpu2: Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz, 3391.50 MHz
> > cpu2: 
> > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,MMX,FXSR,SSE,SSE2,SS,HTT,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
> > cpu2: 256KB 64b/line 8-way L2 cache
> > cpu2: smt 0, core 2, package 0
> > cpu3 at mainbus0: apid 3 (application processor)
> > cpu3: Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz, 3391.45 MHz
> > cpu3: 
> > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,MMX,FXSR,SSE,SSE2,SS,HTT,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
> > cpu3: 256KB 64b/line 8-way L2 cache
> > cpu3: smt 0, core 3, package 0
> > ioapic0 at mainbus0: apid 4 pa 0xfec0, version 11, 24 pins
> > acpimcfg0 at acpi0 addr 0xf000, bus 0-127
> > acpihpet0 at acpi0: 14318179 Hz
> > acpiprt0 at acpi0: bus 0 (PCI0)
> > acpicpu0 at acpi0: C1(@1 halt!)
> > acpicpu1 at acpi0: C1(@1 halt!)
> > acpicpu2 at acpi0: C1(@1 halt!)
> > acpicpu3 at acpi0: C1(@1 halt!)
> > acpibat0 at acpi0: BAT1 not present
> > acpibat1 at acpi0: BAT2 not present
> > acpiac0 at acpi0: AC unit online
> > acpibtn0 at acpi0: SLPB
> > acpibtn1 at acpi0: LID_
> > pvbus0 at mainbus0: VMware
> > vmt0 at pvbus0
> > pci0 at mainbus0 bus 0
> > pchb0 at pci0 dev 0 function 0 "Intel 82443BX AGP" rev 0x01
> > ppb0 at pci0 dev 1 function 0 "Intel 82443BX AGP" rev 0x01
> > pci1 at ppb0 bus 1
> > pcib0 at pci0 dev 7 function 0 "Intel 82371AB PIIX4 ISA" rev 0x08
> > pciide0 at pci0 dev 7 function 1 "Intel 82371AB IDE" rev 0x01: DMA, channel 
> > 0 configured to

objcopy / xv6 question

2015-12-06 Thread d . lowe 

Hello,

I am trying to compile and run xv6 on OpenBSD 5.8, a simple Unix Version 
6 clone for educational
usage.  I changed the Makefiles, so that it compiles fine on OpenBSD 
(mail me if you need a copy).

Sadly enough, I still can't boot the xv6 image in qemu.

I noticed that the 'initcode' target produces a binary that is way too 
big, compared to the initcode
binary on other hosts (eg linux).  The command that generates such a big 
binary is


$(OBJCOPY) -S -O binary initcode.out initcode

I am not sure, why do I get binary 'initcode' with 128MB?

I am not sure if this is the bug why xv6 doesn't boot, but I also do not 
understand why I am getting

such a big binary from that command?  Is this a bug in objcopy?

Any help is much appreciated.

Thanks,
 - dl

Re: TXPower

2015-12-06 Thread Stuart Henderson 
On 2015-12-05, bluesun08  wrote:
> Hi,
>
> 1) How can i show the txpower of my wlan-card?
> 2) How can i adjust the txpower?

Not really supported on OpenBSD. There are stubs but most drivers don't
actually implement it. (yes this is a bit of a problem if you're using
it with different antennas or very nearby nodes and need to reduce power
to stay legal or to avoid overloading the rx).

Re: 5.8/sparc64 - boot from softraid(4) fails?

2015-12-06 Thread Alexander Bochmann 
Hi,

thanks for your answer.

...on Sun, Dec 06, 2015 at 06:02:35PM +0100, Stefan Sperling wrote:

 > Can you show the output of 'devalias' at the ok> prompt?

Will need a couple of days, as the machine is currently at 
a friend's place. I'll post an update as soon as I have the 
devalias output.

 > The easiest way to try this diff is to build a new release on another
 > sparc64 system (see man release(8)) and install that.

That will need even more time, as I don't currently have 
another sparc64 box on 5.8 :) I can probably try that sometime 
late next week.

Alex.

Re: vmm uvm_fault in vmware player/workstation when Intel VT/AMD-v not enabled

2015-12-06 Thread _rest _rest 
Tried again with "Virtualize Intel VT-x/EPT or AMD-V/RVI" disabled on a freshly 
built current.
Now i get a nice error:

# vmd
fatal in vmd: /dev/vmm: Operation not supported by device

- Oorspronkelijk bericht - 

Van: "Mike Larkin"  
Aan: "Erwin van Maanen"  
Cc: misc@openbsd.org 
Verzonden: Zondag 6 december 2015 19:12:18 
Onderwerp: Re: vmm uvm_fault in vmware player/workstation when Intel VT/AMD-v 
not enabled 

On Sun, Dec 06, 2015 at 10:02:50AM -0800, Mike Larkin wrote: 
> On Tue, Nov 24, 2015 at 11:02:30PM +0100, Erwin van Maanen wrote: 
> > Hello Misc, 
> > 
> > I was playing around with the new vmm in the bsd snapshot of Nov 23 under 
> > VMWare Workstation. 
> > And when enabling it, i forget to enabled "Virtualize Intel VT-x/EPT or 
> > AMD-V/RVI" option in VMWare workstation an i get an uvm_fault: 
> > 
> > uvm_fault(0xff007f549f00, 0x60, 0, 1) -> e 
> > kernel: page fault trap, code=0 
> > Stopped at vmmioctl+0x18: movl 0x60(%rcx),%r8d 
> > ddb{3}> 
> > 
> > After enabling "Virtualize Intel VT-x/EPT or AMD-V/RVI" all works fine 
> > afaik. 
> > It would be nice to get a little error saying, Intel VT/AMD-V not available 
> > or something like that instead of the above. 
> > 
> > Erwin 
> 
> Following up on old emails - I believe this was already fixed by a later 
> commit, 
> please let us know if this is not the case. 

Actually after looking a bit, it looks like this wasn't fixed. I'll commit the 
fix presently. 

-ml 

> 
> -ml 
> 
> > 
> > -- dmesg -- 
> > OpenBSD 5.8-current (GENERIC.MP) #1652: Mon Nov 23 11:46:59 MST 2015 
> > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP 
> > real mem = 2130640896 (2031MB) 
> > avail mem = 2061979648 (1966MB) 
> > mpath0 at root 
> > scsibus0 at mpath0: 256 targets 
> > mainbus0 at root 
> > bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (556 entries) 
> > bios0: vendor Phoenix Technologies LTD version "6.00" date 05/20/2014 
> > bios0: VMware, Inc. VMware Virtual Platform 
> > acpi0 at bios0: rev 2 
> > acpi0: sleep states S0 S1 S4 S5 
> > acpi0: tables DSDT FACP BOOT APIC MCFG SRAT HPET WAET 
> > acpi0: wakeup devices PCI0(S3) USB_(S1) P2P0(S3) S1F0(S3) S2F0(S3) S3F0(S3) 
> > S4F0(S3) S5F0(S3) S6F0(S3) S7F0(S3) S8F0(S3) S9F0(S3) S10F(S3) S11F(S3) 
> > S12F(S3) S13F(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) i5-4670K CPU @ 3.40GHz, 3391.99 MHz 
> > cpu0: 
> > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,MMX,FXSR,SSE,SSE2,SS,HTT,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
> >  
> > cpu0: 256KB 64b/line 8-way L2 cache 
> > cpu0: smt 0, core 0, package 0 
> > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges 
> > cpu0: apic clock running at 65MHz 
> > cpu1 at mainbus0: apid 1 (application processor) 
> > cpu1: Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz, 3391.55 MHz 
> > cpu1: 
> > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,MMX,FXSR,SSE,SSE2,SS,HTT,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
> >  
> > cpu1: 256KB 64b/line 8-way L2 cache 
> > cpu1: smt 0, core 1, package 0 
> > cpu2 at mainbus0: apid 2 (application processor) 
> > cpu2: Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz, 3391.50 MHz 
> > cpu2: 
> > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,MMX,FXSR,SSE,SSE2,SS,HTT,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
> >  
> > cpu2: 256KB 64b/line 8-way L2 cache 
> > cpu2: smt 0, core 2, package 0 
> > cpu3 at mainbus0: apid 3 (application processor) 
> > cpu3: Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz, 3391.45 MHz 
> > cpu3: 
> > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,MMX,FXSR,SSE,SSE2,SS,HTT,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
> >  
> > cpu3: 256KB 64b/line 8-way L2 cache 
> > cpu3: smt 0, core 3, package 0 
> > ioapic0 at mainbus0: apid 4 pa 0xfec0, version 11, 24 pins 
> > acpimcfg0 at acpi0 addr 0xf000, bus 0-127 
> > acpihpet0 at acpi0: 14318179 Hz 
> > acpiprt0 at acpi0: bus 0 (PCI0) 
> > acpicpu0 at acpi0: C1(@1 halt!) 
> > acpicpu1 at acpi0: C1(@1 halt!) 
> > acpicpu2 at acpi0: C1(@1 halt!) 
> > acpicpu3 at acpi0: C1(@1 halt!) 
> > acpibat0 at acpi0: BAT1 not

Re: vmm uvm_fault in vmware player/workstation when Intel VT/AMD-v not enabled

2015-12-06 Thread Mike Larkin 
On Mon, Dec 07, 2015 at 01:05:46AM +0100, _rest _rest wrote:
> Tried again with "Virtualize Intel VT-x/EPT or AMD-V/RVI" disabled on a 
> freshly built current.
> Now i get a nice error:
> 
> # vmd
> fatal in vmd: /dev/vmm: Operation not supported by device
> 

Thanks, that's the expected behavior.

-ml

> - Oorspronkelijk bericht - 
> 
> Van: "Mike Larkin"  
> Aan: "Erwin van Maanen"  
> Cc: misc@openbsd.org 
> Verzonden: Zondag 6 december 2015 19:12:18 
> Onderwerp: Re: vmm uvm_fault in vmware player/workstation when Intel VT/AMD-v 
> not enabled 
> 
> On Sun, Dec 06, 2015 at 10:02:50AM -0800, Mike Larkin wrote: 
> > On Tue, Nov 24, 2015 at 11:02:30PM +0100, Erwin van Maanen wrote: 
> > > Hello Misc, 
> > > 
> > > I was playing around with the new vmm in the bsd snapshot of Nov 23 under 
> > > VMWare Workstation. 
> > > And when enabling it, i forget to enabled "Virtualize Intel VT-x/EPT or 
> > > AMD-V/RVI" option in VMWare workstation an i get an uvm_fault: 
> > > 
> > > uvm_fault(0xff007f549f00, 0x60, 0, 1) -> e 
> > > kernel: page fault trap, code=0 
> > > Stopped at vmmioctl+0x18: movl 0x60(%rcx),%r8d 
> > > ddb{3}> 
> > > 
> > > After enabling "Virtualize Intel VT-x/EPT or AMD-V/RVI" all works fine 
> > > afaik. 
> > > It would be nice to get a little error saying, Intel VT/AMD-V not 
> > > available or something like that instead of the above. 
> > > 
> > > Erwin 
> > 
> > Following up on old emails - I believe this was already fixed by a later 
> > commit, 
> > please let us know if this is not the case. 
> 
> Actually after looking a bit, it looks like this wasn't fixed. I'll commit 
> the 
> fix presently. 
> 
> -ml 
> 
> > 
> > -ml 
> > 
> > > 
> > > -- dmesg -- 
> > > OpenBSD 5.8-current (GENERIC.MP) #1652: Mon Nov 23 11:46:59 MST 2015 
> > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP 
> > > real mem = 2130640896 (2031MB) 
> > > avail mem = 2061979648 (1966MB) 
> > > mpath0 at root 
> > > scsibus0 at mpath0: 256 targets 
> > > mainbus0 at root 
> > > bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (556 entries) 
> > > bios0: vendor Phoenix Technologies LTD version "6.00" date 05/20/2014 
> > > bios0: VMware, Inc. VMware Virtual Platform 
> > > acpi0 at bios0: rev 2 
> > > acpi0: sleep states S0 S1 S4 S5 
> > > acpi0: tables DSDT FACP BOOT APIC MCFG SRAT HPET WAET 
> > > acpi0: wakeup devices PCI0(S3) USB_(S1) P2P0(S3) S1F0(S3) S2F0(S3) 
> > > S3F0(S3) S4F0(S3) S5F0(S3) S6F0(S3) S7F0(S3) S8F0(S3) S9F0(S3) S10F(S3) 
> > > S11F(S3) S12F(S3) S13F(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) i5-4670K CPU @ 3.40GHz, 3391.99 MHz 
> > > cpu0: 
> > > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,MMX,FXSR,SSE,SSE2,SS,HTT,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
> > >  
> > > cpu0: 256KB 64b/line 8-way L2 cache 
> > > cpu0: smt 0, core 0, package 0 
> > > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges 
> > > cpu0: apic clock running at 65MHz 
> > > cpu1 at mainbus0: apid 1 (application processor) 
> > > cpu1: Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz, 3391.55 MHz 
> > > cpu1: 
> > > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,MMX,FXSR,SSE,SSE2,SS,HTT,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
> > >  
> > > cpu1: 256KB 64b/line 8-way L2 cache 
> > > cpu1: smt 0, core 1, package 0 
> > > cpu2 at mainbus0: apid 2 (application processor) 
> > > cpu2: Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz, 3391.50 MHz 
> > > cpu2: 
> > > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,MMX,FXSR,SSE,SSE2,SS,HTT,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
> > >  
> > > cpu2: 256KB 64b/line 8-way L2 cache 
> > > cpu2: smt 0, core 2, package 0 
> > > cpu3 at mainbus0: apid 3 (application processor) 
> > > cpu3: Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz, 3391.45 MHz 
> > > cpu3: 
> > > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,MMX,FXSR,SSE,SSE2,SS,HTT,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
> > >  
> > > cpu3: 256KB 64b/line 8-way L2 cache 
> > > cpu3: smt 0, core 3, package 0 
> > > ioapic0 at mainbus0: apid 4 pa 0xfec0, version 11, 24 pins

Add Bay Trail EHCI controller to pcidevs

2015-12-06 Thread Callum Davies 
Doesn't work, but at least it makes the dmesg look better.

Index: sys/dev/pci/pcidevs
===
RCS file: /cvs/src/sys/dev/pci/pcidevs,v
retrieving revision 1.1780
diff -u -p -u -r1.1780 pcidevs
--- sys/dev/pci/pcidevs 28 Nov 2015 14:11:33 -  1.1780
+++ sys/dev/pci/pcidevs 6 Dec 2015 20:38:06 -
@@ -3102,6 +3102,7 @@ product INTEL BAYTRAIL_LPA0x0f28  Bay Tr
 product INTEL BAYTRAIL_IGD_1   0x0f31  Bay Trail Video
 product INTEL BAYTRAIL_IGD_2   0x0f32  Bay Trail Video
 product INTEL BAYTRAIL_IGD_3   0x0f33  Bay Trail Video
+product INTEL BAYTRAIL_EHCI0x0f34  Bay Trail EHCI
 product INTEL BAYTRAIL_XHCI0x0f35  Bay Trail xHCI
 product INTEL BAYTRAIL_82370x0f40  Bay Trail I2C DMA
 product INTEL BAYTRAIL_I2C_1   0x0f41  Bay Trail I2C

Re: Suspend on Macbook Pro Retina (MacbookPro 11,1)

2015-12-06 Thread Bryan C. Everly 
Sorry Mike.  Feeling like a real dork here.  Here's my dmesg (I also read
the manpage for sendbug and used it to send one):

OpenBSD 5.8-current (GENERIC.MP) #1708: Fri Dec  4 10:41:02 MST 2015
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
RTC BIOS diagnostic error
ff
real mem = 17065656320 (16275MB)
avail mem = 16544325632 (15777MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0x8ad14000 (43 entries)
bios0: vendor Apple Inc. version "MBP111.88Z.0138.B16.1509081438" date
09/08/2015
bios0: Apple Inc. MacBookPro11,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 SSDT MCFG DMAR
acpi0: wakeup devices P0P2(S3) EC__(S3) HDEF(S3) RP01(S3) RP02(S3) RP03(S4)
ARPT(S4) RP05(S3) RP06(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-4558U CPU @ 2.80GHz, 2700.37 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX
,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEA
DLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,
BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,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-4558U CPU @ 2.80GHz, 2700.01 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX
,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEA
DLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,
BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,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-4558U CPU @ 2.80GHz, 2700.01 MHz
cpu2:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX
,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEA
DLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,
BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,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-4558U CPU @ 2.80GHz, 2700.01 MHz
cpu3:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX
,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEA
DLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,
BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,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 offline
acpibtn0 at acpi0: LID0
acpibtn1 at acpi0: PWRB
acpibtn2 at acpi0: SLPB
acpivideo0 at acpi0: IGPU
acpivout0 at acpivideo0: DD01
cpu0: Enhanced SpeedStep 2700 MHz: speeds: 2801, 2800, 2700, 2400, 2200,
2000, 1700, 1500, 1300, 1100, 900, 756 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 Iris Graphics 5100" rev 0x09
drm0 at inteldrm0
inteldrm0: msi
inteldrm0: 2560x1600
wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
azalia0 at pci0 dev 3 function 0 "Intel Core 4G HD Audio" rev 0x09: msi
xhci0 at pci0 dev 20 function 0 "Intel 8 Series xHCI" rev 0x04: msi
usb0 at xhci0: USB revision 3.0

Re: Suspend on Macbook Pro Retina (MacbookPro 11,1)

2015-12-06 Thread Bryan Everly 
Performance is great from my perspective. No noticeable lag, etc.

The wifi will probably never get a driver in OpenBSD though (only a
closed source driver in Linux) and power management is flakey (even in
Linux). Just keep that in mind.

Thanks,
Bryan

> On Dec 6, 2015, at 5:06 PM, Артур Истомин 
wrote:
>
>> On Sun, Dec 06, 2015 at 09:28:05AM -0500, Bryan C. Everly wrote:
>> Hi,
>>
>> Happy to do so.  Here is an imgur link that has three shots.  I am using
>> the i3 desktop currently so I can have a little more control over the
>> fine-grained settings for HiDPI (I had previously been running Gnome 3).
>> Let me know if there is anything in particular you'd like to see:
>>
>> https://imgur.com/a/CiQ82
>
> Bryan, what about performance 2D, 3D? Are there any difference between
> "retina" and "standard" dpi on Intel video on OpenBSD? I'm about
performance
> issues, not about aesthetics (yes, fonts are realy awesome, that is why I
want
> to buy laptop with hidpi display).

Re: Suspend on Macbook Pro Retina (MacbookPro 11,1)

2015-12-06 Thread Артур Истомин 
On Sun, Dec 06, 2015 at 09:28:05AM -0500, Bryan C. Everly wrote:
> Hi,
> 
> Happy to do so.  Here is an imgur link that has three shots.  I am using
> the i3 desktop currently so I can have a little more control over the
> fine-grained settings for HiDPI (I had previously been running Gnome 3).
> Let me know if there is anything in particular you'd like to see:
> 
> https://imgur.com/a/CiQ82

Bryan, what about performance 2D, 3D? Are there any difference between
"retina" and "standard" dpi on Intel video on OpenBSD? I'm about performance
issues, not about aesthetics (yes, fonts are realy awesome, that is why I want
to buy laptop with hidpi display).

Re: Hitting the bootable cylinder limit?

2015-12-06 Thread Alan Corey 
Another possibility is that something like a bootloader was looking
for a file at a particular location (sector, inode) on the disk.  In
installing Grub under Arch Linux there's mention of that.  Linux has
an immutable flag on files, with a utility chattr for setting and
unsetting it, when it's set supposedly the file can't be moved.

-- 
Credit is the root of all evil.  - AB1JX