Re: Lumina-Terminal on OpenBSD

[Martijn Rijkeboer]

On 07/04/18 21:39, rehcla wrote:

Hey Martijn,

Just found a Lumina thread on the OpenBSD Mailinglist and in that one you said 
you are the maintainer of the Lumina port.
Is that still the case?
I did like Lumina on TrueOS, but TrueOS was far too unstable for me... Anyway I 
identifiy much more with OpenBSD and Theo de Raadt:)
If yes, is there any reason wh lumina-terminal is missing?
xterm has no copy paste feature (what is handy if you need to use mpv as 
youtube-player)...
I installed the kde-konsole what dependce on a buch of other kde packages.
It would be great to have lumina-terminal available... How about it?


I'm not the maintainer of the Lumina port, Bryan C. Everly is (according
to the port's Makefile). I use xterm as my terminal emulator and copy
and paste works fine with the middle mouse button.

Kind regards,


Martijn Rijkeboer

Syspatch's SHA256 and SHA256.sig no hash for ipsecout patch

[Martijn Rijkeboer]

Hi,

The SHA256 and SHA256.sig files in /pub/OpenBSD/syspatch/6.3/amd64 don't 
contain the hash for syspatch63-008_ipsecout.tgz. Is this on purpose or 
simply a mistake?


Kind regards,


Martijn Rijkeboer

Re: Lumina enable Shut Down

[Martijn Rijkeboer]

On 23-07-17 23:12, Stefan Sperling wrote:

On Sun, Jul 23, 2017 at 09:10:07PM +0200, Martijn Rijkeboer wrote:

On 22-07-17 02:02, Sha'ul wrote:

In Lumina desktop how do I enable shutdown from GUI menu for point and
click poweroff and reboot?


Try adding yourself to the 'operator' group.


The operator group has read access to raw disk device nodes,
bypassing file system permissions: ls -l /dev/r[ws]d[0-9]*

Allowing shutdown/reboot via doas(1) is a safer option.


I totally agree with you, but if you want to use the shutdown
button from within Lumina you currently need to be member of the
'operator' group [0].

[0] 
https://github.com/trueos/lumina/blob/master/src-qt5/core/libLumina/LuminaOS-OpenBSD.cpp#L157



Kind regards,


Martijn Rijkeboer

Re: Lumina enable Shut Down

[Martijn Rijkeboer]

On 22-07-17 02:02, Sha'ul wrote:

In Lumina desktop how do I enable shutdown from GUI menu for point and
click poweroff and reboot?


Try adding yourself to the 'operator' group.

Kind regards,


Martijn Rijkeboer

Re: Choice of sis(4) versus vr(4) ?

[Martijn Rijkeboer]

Hi Lars,

On 07/18/17 11:11, Stuart Henderson wrote:
> On 2017-07-17, Lars Noodén  wrote:
>> I'm looking to refurbish an old device and will probably add a network
>> card to it.  Are there any reasons based on the current drivers or the
>> hardware itself to choose sis(4) or vr(4) over one or the other on
>> i386 -curren?
>>
>> Regards,
>> Lars
>>
>>
> 
> Staying within these drivers, the VT6105 version of vr(4) is the better
> choice. Can't you find an old intel fxp(4) instead though?

I don't know where you're from, but if you're from The Netherlands, I
still have two PCI fxp(4) cards you can have.

Kind regards,


Martijn

Re: Kernel relinking not working after upgrade to latest snaphot

[Martijn Rijkeboer]

On 06/16/17 16:11, Theo de Raadt wrote:
> This is intentional.  But the script /etc/rc may not be working
> exactly as intended yet.  rpe, tb and I are still iterating this, and
> also attempting to satisfy the unhibernate case which requires booting
> the original kernel.
> 
> The intent of the hash is so that a developer can build their own kernel
> from elsewhere.  Upon the next boot, it will notice that that the hash
> is different.  This means the developer is testing their own kernel,
> and does not want auto relinking to occur.
> 
> However if the hash matches then /bsd is under system management, and
> can be relinked.
> 
> Finally, if there is no hash file, this was an install or an upgrade,
> and it can go into this managed-mode where it auto relinks at boot.
> 
> You can also make it relink on future boots by deleting the hash file.
> 
> As you can tell we're trying to find a happy middle ground between
> automatic safety, and developers being in control of their own
> machines.
> 
> There is also a bootblock change coming, to assist unhibernate.

OK, good to know.


>> After upgrading to the latest snapshot I noticed that the kernel is no
>> longer relinked on boot. The cause seems to be that the SHA256 checksum
>> doesn't match the kernel.
>>
>> # cat /usr/share/compile/GENERIC.MP/SHA256
>> SHA256 (/bsd) =
>> bfcce01e68e62cc5d9666096206492be3f5c310e9711f2a14ac9c75e279585a1
>>
>> # sha256 /bsd
>> SHA256 (/bsd) =
>> 10da3cee5c0bf44ce9182b2603be46b2adfc200222ca74d169691f79750bd05b
>>
>> # sysctl kern.version
>> kern.version=OpenBSD 6.1-current (GENERIC.MP) #13: Thu Jun 15 19:34:58
>> MDT 2017
>> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
>>
>>
>> Is this on purpose or an error on my side?
>>
>> Kind regards,
>>
>>
>> Martijn Rijkeboer

Kernel relinking not working after upgrade to latest snaphot

[Martijn Rijkeboer]

Hi,

After upgrading to the latest snapshot I noticed that the kernel is no
longer relinked on boot. The cause seems to be that the SHA256 checksum
doesn't match the kernel.

# cat /usr/share/compile/GENERIC.MP/SHA256
SHA256 (/bsd) =
bfcce01e68e62cc5d9666096206492be3f5c310e9711f2a14ac9c75e279585a1

# sha256 /bsd
SHA256 (/bsd) =
10da3cee5c0bf44ce9182b2603be46b2adfc200222ca74d169691f79750bd05b

# sysctl kern.version
kern.version=OpenBSD 6.1-current (GENERIC.MP) #13: Thu Jun 15 19:34:58
MDT 2017
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP


Is this on purpose or an error on my side?

Kind regards,


Martijn Rijkeboer

Re: ansible-playbook: Permission denied

[Martijn Rijkeboer]

Hi Predrag,

On 05/24/17 23:20, Predrag Punosevac wrote:
> Hi Martijn,
> 
> Great hints. I was so tired yesterday and unable to think straight.
> 
> # uname -a  
> OpenBSD apollo.autonlab.org 6.1 GENERIC.MP#6 amd64
> # ls -l /usr/local/bin/ansible-playbook
> -rwxr-xr-x  1 root  bin  4800 Apr  1 17:51 /usr/local/bin/ansible-playbook
> # mount | grep '/usr/local'
> /dev/wd0h on /usr/local type ffs (local, nodev)
> 
> 
> So obviously your suggestion at this point would be to add
> 
> wxallowed

That would have been my suggestion indeed.

Kind regards,


Martijn Rijkeboer

Re: ansible-playbook: Permission denied

[Martijn Rijkeboer]

On 05/23/17 23:18, Predrag Punosevac wrote:
> # ansible-playbook update-dns --check 
> ksh: ansible-playbook: Permission denied

Can you show us the output of `ls -l /usr/local/bin/ansible-playbook`
and `mount | grep '/usr/local'`?

Kind regards,


Martijn Rijkeboer

Re: Static binaries on newer releases

[Martijn Rijkeboer]

On 02/24/17 13:07, Juan Francisco Cantero Hurtado wrote:
> On Fri, Feb 24, 2017 at 11:08:21AM +0100, Martijn Rijkeboer wrote:
>> Hi,
>>
>> If I have a static binary compiled on OpenBSD release X, is that binary
>> expected to also run on release X+1, X+2 and X+Y? For example, a static
>> binary that is compiled on OpenBSD 6.0, is it expected to also run on
>> 6.1, 6.2 and 6.3? The reason for asking is a Haskell stack issue [0]
>> that involves GHC bindists.
> 
> In addition to Sebastien's comment, take a look to
> https://github.com/golang/go/issues/15227 . Go has also the same
> problem.

Thanks, I will check that issue.

Kind regards,


Martijn Rijkeboer

Re: Static binaries on newer releases

[Martijn Rijkeboer]

On 02/24/17 12:07, Sebastien Marie wrote:
> On Fri, Feb 24, 2017 at 11:08:21AM +0100, Martijn Rijkeboer wrote:
>> Hi,
>>
>> If I have a static binary compiled on OpenBSD release X, is that binary
>> expected to also run on release X+1, X+2 and X+Y? For example, a static
>> binary that is compiled on OpenBSD 6.0, is it expected to also run on
>> 6.1, 6.2 and 6.3? The reason for asking is a Haskell stack issue [0]
>> that involves GHC bindists.
>>
> 
> The generic answer will be "no".
> 
> The example is the switch from 5.4 to 5.5 release which included time_t
> change (32 to 64 bits) - see https://www.openbsd.org/faq/upgrade55.html#time_t
> 
> But generally, an old binary (from release X) is able to run on a new
> kernel (from release X+1), but nothing more could be expected: old
> things are cleaned, so an old binary could be able to run or not (it
> just depends if relying on old API/ABI with kernel - syscalls, struct
> size...).

Thanks for your answer. This is what I was expecting, but wanted to
make sure before adding the info to the stack issue.

Kind regards,


Martijn Rijkeboer

Static binaries on newer releases

[Martijn Rijkeboer]

Hi,

If I have a static binary compiled on OpenBSD release X, is that binary
expected to also run on release X+1, X+2 and X+Y? For example, a static
binary that is compiled on OpenBSD 6.0, is it expected to also run on
6.1, 6.2 and 6.3? The reason for asking is a Haskell stack issue [0]
that involves GHC bindists.

Kind regards,


Martijn Rijkeboer


[0] https://github.com/commercialhaskell/stack/issues/416

Xfce shutdown and reboot not available on first login

[Martijn Rijkeboer]

Hi,

Since I've switched from SLiM to XDM as login manager I'm not able to
shutdown or reboot from Xfce on the first login (buttons are greyed
out). When I logout and login again, the options are available. Any
suggestions how to fix this?

Kind regards,


Martijn Rijkeboer


$ sysctl kern.version
kern.version=OpenBSD 6.0-current (GENERIC.MP) #158: Mon Jan 30 19:30:12
MST 2017
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP

$ cat /etc/rc.conf.local
xdm_flags=
pkg_scripts=messagebus

$ cat .xsession
/usr/local/bin/startxfce4 --with-ck-launch

$ pkg_info |egrep 'console|polkit|^xfce-'
consolekit2-1.0.2p1 framework for defining and tracking users, sessions
& seats
polkit-0.113p3  framework for granting privileged operations to users
xfce-4.12p6 Xfce desktop meta-package (base installation)

Re: Problem using RFID reader (ucom0 at uslcom0 portno 0)

[Martijn Rijkeboer]

On 08/29/16 18:00, Remco wrote:

Op 08/29/16 om 14:28 schreef Martijn Rijkeboer:

Hi,

I'm having trouble using the Stronglink SL500 RFID reader with OpenBSD.
The SL500 is a USB based RFID reader that attaches to ucom. When I
write data to it and try to read the response, I'm often getting
wrong results. Sometimes the program even lock and unplugging the
device is the only option. I'm using the test program attached below.
This program should produce the following output (as it always does on
Linux):

$ ./test
received: 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 0x05
received: 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 0x05


When I run the program on OpenBSD-current (AMD64) I get the following:

$ ./test
received: 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 0x05
received: 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 0x05
$ ./test
received: 0x0a 0xbb 0x06 0x00 0x00 0x00 0x07 0x01 0x02 0x04
received: 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 0x05
$ ./test
received: 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 0x05
received: 0x0a 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00
$ ./test
received: 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 0x05
received: 0x0a 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00


In the output above the first run is correct. In the second run the
first response is incorrect. In the third and fourth run the second
response is incorrect. Any suggestions what is wrong? To me it looks
like a bug in ucom or uslcom, but I could also be doing something
wrong...

I've included the test program, lsusb output and dmesg output below.


Kind regards,


Martijn Rijkeboer



Test program




O_NONBLOCK: not sure this is necessary.


The O_NONBLOCK is indeed not necessary.



Check return values, at least of read and write (EAGAIN, partial
read/write ?),
they will probably tell you what's wrong.


None of the calls returned -1, but issuing a `tcflush(fd, TCIOFLUSH)'
before sending the first data fixed the problem. Thanks for your time.

Kind regards,


Martijn Rijkeboer

Problem using RFID reader (ucom0 at uslcom0 portno 0)

[Martijn Rijkeboer]

Hi,

I'm having trouble using the Stronglink SL500 RFID reader with OpenBSD.
The SL500 is a USB based RFID reader that attaches to ucom. When I
write data to it and try to read the response, I'm often getting
wrong results. Sometimes the program even lock and unplugging the
device is the only option. I'm using the test program attached below.
This program should produce the following output (as it always does on
Linux):

$ ./test
received: 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 0x05
received: 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 0x05


When I run the program on OpenBSD-current (AMD64) I get the following:

$ ./test
received: 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 0x05
received: 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 0x05
$ ./test
received: 0x0a 0xbb 0x06 0x00 0x00 0x00 0x07 0x01 0x02 0x04
received: 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 0x05
$ ./test
received: 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 0x05
received: 0x0a 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00
$ ./test
received: 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 0x05
received: 0x0a 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00


In the output above the first run is correct. In the second run the
first response is incorrect. In the third and fourth run the second
response is incorrect. Any suggestions what is wrong? To me it looks
like a bug in ucom or uslcom, but I could also be doing something
wrong...

I've included the test program, lsusb output and dmesg output below.


Kind regards,


Martijn Rijkeboer



Test program


#include 
#include 
#include 
#include 

int open_port(void) {
int fd = open("/dev/cuaU0", O_RDWR | O_NONBLOCK);  // OpenBSD
//int fd = open("/dev/ttyUSB0", O_RDWR | O_NONBLOCK);  // Linux
if (fd == -1) {
perror("can't open port");
} else {
fcntl(fd, F_SETFL, 0);
}

struct termios options;
tcgetattr(fd, );
cfsetispeed(, B19200);
cfsetospeed(, B19200);
options.c_cflag |= (CLOCAL | CREAD);
options.c_cflag &= ~CSTOPB;
cfmakeraw();
tcsetattr(fd, TCSANOW, );
return fd;
}

void send_led_green(int fd) {
unsigned char data[] = 
{0xaa,0xbb,0x06,0x00,0x00,0x00,0x07,0x01,0x02,0x04};

write(fd, data, sizeof(data));
}

void send_led_red(int fd) {
unsigned char data[] = 
{0xaa,0xbb,0x06,0x00,0x00,0x00,0x07,0x01,0x01,0x07};

write(fd, data, sizeof(data));
}

void recv_led(int fd) {
unsigned char actual[10];
read(fd, , sizeof(actual));
printf("received: ");
printf("0x%02x ", actual[0]);
printf("0x%02x ", actual[1]);
printf("0x%02x ", actual[2]);
printf("0x%02x ", actual[3]);
printf("0x%02x ", actual[4]);
printf("0x%02x ", actual[5]);
printf("0x%02x ", actual[6]);
printf("0x%02x ", actual[7]);
printf("0x%02x ", actual[8]);
printf("0x%02x ", actual[9]);
printf("\n");
}

int main() {
int fd = open_port();

send_led_green(fd);
recv_led(fd);

send_led_red(fd);
recv_led(fd);

close(fd);
}



$ lsusb
===
Bus 000 Device 001: ID 1b6f:
Bus 001 Device 001: ID 1b6f:
Bus 002 Device 001: ID 1002:
Bus 003 Device 001: ID 1002:
Bus 004 Device 001: ID 1002:
Bus 004 Device 002: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard
Bus 004 Device 003: ID 046d:c069 Logitech, Inc. M500 Laser Mouse
Bus 004 Device 004: ID 05ac:0221 Apple, Inc. Aluminum Keyboard (ISO)
Bus 005 Device 001: ID 1002:
Bus 006 Device 001: ID 1002:
Bus 006 Device 002: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x 
UART Bridge / myAVR mySmartUSB light

Bus 007 Device 001: ID 1002:



$ lsusb -v -s 6:2
=
Bus 006 Device 002: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x 
UART Bridge / myAVR mySmartUSB light

Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   1.10
  bDeviceClass0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize064
  idVendor   0x10c4 Cygnal Integrated Products, Inc.
  idProduct  0xea60 CP210x UART Bridge / myAVR mySmartUSB light
  bcdDevice1.00
  iManufacturer   1 Silicon Labs
  iProduct2 CP2102 USB to UART Bridge Controller
  iSerial 3 0001
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   32
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  0
bmAttributes 0x80
  (Bus Powered)
MaxPower  100mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   2
  bInterfaceClass

Re: WAPBL?

[Martijn Rijkeboer]

> I have more up to date versions of these patches around here.
>
> The problem with them is that fundamentally, the WAPBL implementation
> as it is assumes that it may infinitely steal
> buffers from the buffer cache and hold onto them indefinitely - and it
> assumes it can always get buffers from it. While the patch as it sits
> may "work" in the "happy case" on many people's machines, as it sits
> today it is dangerous and can lock up your machine and corrupt things
> in low memory situations.
>
> Basically in order to progres WAPBL (renamed "FFS Journalling" here)
> needs to have a mechanism added to allow
> it be told "no it can't have a buffer" and let it deal with it
> correctly.  The first part is done, the latter part is complex.

Thanks for the update. I completely understand that you are holding
back these patches. This attitude to correctness is one of the pillars
that make OpenBSD great.

Kind regards,


Martijn Rijkeboer

Re: WAPBL?

[Martijn Rijkeboer]

Hi,

> I'm not working on it for a while. Sadly I am with no time, but trying
> to escape to return. :(

Thanks for the update.

Kind regards,


Martijn Rijkeboer

WAPBL?

[Martijn Rijkeboer]

Hi,

Just out of curiosity, what has happend with WAPBL? There were some patches
floating around on tech@ in the last months of 2015, but then it became
quiet. I'm not complaining just curious.

Kind regards,


Martijn Rijkeboer

Re: current snap fails on gigabyte brix at uhub0

[Martijn Rijkeboer]

> FYI -- the current snapshot fails on a Gigabyte Brix.
>
> The boot process blows up at:uhub0
>
> --
> uhub0: device problem, disabling port 1
> uhub0: device problem, disabling port 2
> ehci_sync_hc: tsleep() = 35
> ehci_sync_hc: tsleep() = 35
> ehci_sync_hc: tsleep() = 35
> ehci_sync_hc: tsleep() = 35
> ehci_sync_hc: tsleep() = 35
> ehci_sync_hc: tsleep() = 35
> ehci_sync_hc: tsleep() = 35
> ehci_sync_hc: tsleep() = 35

I had the same problem with a Gigabyte GA-970A-UD3 based computer, but the
latest snapshot (#1846: Sun Jan 17 02:34:54 MST 2016) fixed it for me.

Kind regards,


Martijn Rijkeboer

Re: Vipw / pwd_mkdb not working

[Martijn Rijkeboer]

>> When I try to edit the master.passwd (as root) with vipw I get the
>> following error when saving:
>>
>>   pwd_mkdb: /etc/spwd.db.tmp to /etc/spwd.db: Operation not permitted

> For now, and as quick-fix, I have disabled the pledge call from
> usr.sbin/pwd_mkdb/pwd_mkdb.c
>
> So you can rebuild an reinstall usr.sbin/pwd_mkdb.

Thanks, that fixes it.

Kind regards,


Martijn Rijkeboer

Vipw / pwd_mkdb not working

[Martijn Rijkeboer]

Hi,

When I try to edit the master.passwd (as root) with vipw I get the
following error when saving:

  pwd_mkdb: /etc/spwd.db.tmp to /etc/spwd.db: Operation not permitted

Any suggestions on how to fix this?

OS: OpenBSD 5.8-current (GENERIC.MP) #1568: Wed Nov  4 20:48:36 MST 2015
Arch: AMD64


Kind regards,


Martijn Rijkeboer

Re: Unbound root.key in insecurity output

[Martijn Rijkeboer]

>> I'm running a DNS resolver using Unbound (OpenBSD 5.8-stable AMD64) with
>> the auto-trust-anchor-file option set. This results in daily updates of
the
>> /var/unbound/db/root.key file (only comments are changed). Unfortunately
>> this file is also checked via the security(8) script, which results in
>> getting an insecurity output mail every day (Cry Wolf problem). Is there a
>> way to exclude the comments in the checks or the complete root.key file?

> The security script checks the files listed in /etc/changelist.
> See changelist(5) for details.
>
> I don't think there's a way of checking 'everything but comments', but
> it shouldn't be hard to do that with a custom daily.local script,
> see daily(8).

As Martijn van Duren suggested I will comment out the entry in
/etc/changelist.

Kind regards,


Martijn Rijkeboer

Re: Unbound root.key in insecurity output

[Martijn Rijkeboer]

> I solved this by commenting out the file in /etc/changelist.

Thanks, I will do that.


>> I'm running a DNS resolver using Unbound (OpenBSD 5.8-stable AMD64) with
>> the auto-trust-anchor-file option set. This results in daily updates of
the
>> /var/unbound/db/root.key file (only comments are changed). Unfortunately
>> this file is also checked via the security(8) script, which results in
>> getting an insecurity output mail every day (Cry Wolf problem). Is there a
>> way to exclude the comments in the checks or the complete root.key file?

Kind regards,


Martijn Rijkeboer

Unbound root.key in insecurity output

[Martijn Rijkeboer]

Hi,

I'm running a DNS resolver using Unbound (OpenBSD 5.8-stable AMD64) with the
auto-trust-anchor-file option set. This results in daily updates of the
/var/unbound/db/root.key file (only comments are changed). Unfortunately this
file is also checked via the security(8) script, which results in getting an
insecurity output mail every day (Cry Wolf problem). Is there a way to
exclude
the comments in the checks or the complete root.key file?

Kind regards,


Martijn Rijkeboer

Httpd perfect forward secrecy

[Martijn Rijkeboer]

Hi,

I've just switched my webserver from 5.6/nginx to 5.7/httpd and was
testing my TLS setup using SSL Labs[1]. The SSL Labs test indicates that
my setup doesn't support forward secrecy. Is this not implemented in
the 5.7 version of httpd or is my configuration wrong (included below)?

OS: OpenBSD 5.7-stable AMD64

Kind regards,


Martijn Rijkeboer


--- /etc/httpd.conf ---

ext_addr=*

server www.bunix.org {
listen on $ext_addr tls port 443
tls certificate /etc/ssl/www.bunix.org.crt.pem
tls key /etc/ssl/private/www.bunix.org.key.pem

connection {
max requests 500
timeout 3600
}

root /htdocs/www.bunix.org
}

types {
include /usr/share/misc/mime.types
}


-

[1] https://www.ssllabs.com/ssltest/

Re: Httpd perfect forward secrecy

[Martijn Rijkeboer]

 I've just switched my webserver from 5.6/nginx to 5.7/httpd and was
 testing my TLS setup using SSL Labs[1]. The SSL Labs test indicates
 that my setup doesn't support forward secrecy. Is this not implemented
 in the 5.7 version of httpd or is my configuration wrong (included
 below)?

In my previous message I have forgotten to mention that I also tried
setting tls dhe to auto, but that didn't help either.

Kind regards,


Martijn Rijkeboer

Re: Httpd perfect forward secrecy

[Martijn Rijkeboer]

 On Mon, May 18, 2015 at 07:43:26PM +0200, Martijn Rijkeboer wrote:
 Hi,

 I've just switched my webserver from 5.6/nginx to 5.7/httpd and was
 testing my TLS setup using SSL Labs[1]. The SSL Labs test indicates
 that my setup doesn't support forward secrecy. Is this not implemented
 in the 5.7 version of httpd or is my configuration wrong (included
 below)?

 We disabled older cipher suites and protocols by default.  Any new-ish
 browser should prefer ECDHE over DHE.

Thank you very much for your explanation. SSL labs flags this webserver
as not supporting Forward Secrecy with the reference browsers, because
one of the reference browsers doesn't work (IE 8-10 / Win 7). Since none
of my users uses that browser I will stick to the sane defaults.


 So if your really want to enable legacy DHE modes, set the following
 in the server section:

   tls dhe legacy

This doesn't help either, but as explained above that's no problem for
me.

Kind regards,


Martijn Rijkeboer

Re: acpi0: PM1 stuck (en 0x121 st 0x1), clearing

[Martijn Rijkeboer]

Hello,

 I'm running 5.5 on amd64 and am seeing the following message a few seconds
 after the system has booted to the login prompt:

 acpi0: PM1 stuck (en 0x121 st 0x1), clearing

 Does this matter? Can anybody suggest a resolution? AHCI is enabled in the
 BIOS and apmd seems to be throttling the CPU correctly.

I have the same problem [1]. I don't know whether this matters nor do I
have a
resolution.


Kind regards,


Martijn Rijkeboer

[1] http://marc.info/?l=openbsd-miscm=138645003103589w=2

etc56.tgz missing in SHA256[.sig]

[Martijn Rijkeboer]

Hi,

The files http://ftp.openbsd.org/pub/OpenBSD/snapshots/amd64/SHA256[.sig]
don't have a hash for etc56.tgz and the etc56.tgz file is also older that
the other base files. Is this an error or did I miss something?

Kind regards,


Martijn Rijkeboer

Re: etc56.tgz missing in SHA256[.sig]

[Martijn Rijkeboer]

 The files
 http://ftp.openbsd.org/pub/OpenBSD/snapshots/amd64/SHA256[.sig]
 don't have a hash for etc56.tgz and the etc56.tgz file is also older
 that
 the other base files. Is this an error or did I miss something?

 the etc set goes away.

Thanks, that explains...

Kind regards,


Martijn Rijkeboer

Re: etc56.tgz missing in SHA256[.sig]

[Martijn Rijkeboer]

 The files
 http://ftp.openbsd.org/pub/OpenBSD/snapshots/amd64/SHA256[.sig] don't
 have a hash for etc56.tgz and the etc56.tgz file is also older that
 the other base files. Is this an error or did I miss something?

 http://marc.info/?l=openbsd-cvsm=140908438211799w=2

Thanks, apparently I wasn't paying attention when reading the CVS log mails.

Kind regards,


Martijn Rijkeboer

Bochs QEMU Virtual CPU: SP or MP

[Martijn Rijkeboer]

Hi,

I've got a VPS at transip.nl that runs OpenBSD 5.5 AMD64. When I install
the machine the installer only selects the GENERIC (SP) kernel, although
the system has two CPU's. The system can also boot the GENERIC.MP kernel
without problems. What is the recommended way? Staying on SP or manually
add the MP kernel and override the installer? The system is going to act
as a webserver with static content. I've added the sysctl hw and dmesg
output for both the SP and MP kernels below.

Kind regards,


Martijn Rijkeboer


GENERIC (SP)


$ sysctl hw
hw.machine=amd64
hw.model=QEMU Virtual CPU version 1.7.1
hw.ncpu=1
hw.byteorder=1234
hw.pagesize=4096
hw.disknames=wd0:ff833b66cc728bb6,cd0:,fd0:
hw.diskcount=3
hw.cpuspeed=2200
hw.vendor=Bochs
hw.product=Bochs
hw.uuid=611bc3c6-3dc2-b8a8-8a09-27d4d448
hw.physmem=4278181888
hw.usermem=4278169600
hw.ncpufound=2
hw.allowpowerdown=1

$ dmesg
OpenBSD 5.5 (GENERIC) #271: Wed Mar  5 09:31:16 MST 2014
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
real mem = 4278181888 (4079MB)
avail mem = 4155727872 (3963MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf15d0 (13 entries)
bios0: vendor Bochs version Bochs date 01/01/2011
bios0: Bochs Bochs
acpi0 at bios0: rev 0
acpi0: sleep states S3 S4 S5
acpi0: tables DSDT FACP SSDT APIC HPET
acpi0: wakeup devices
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
acpihpet0 at acpi0: 1 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpicpu0 at acpi0
mpbios0 at bios0: Intel MP Specification 1.4
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: QEMU Virtual CPU version 1.7.1, 2200.32 MHz
cpu0:
FPU,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,CX16,POPCNT,NXE,LONG,LAHF
cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB
64b/line
16-way L2 cache
cpu0: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
cpu0: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 999MHz
cpu at mainbus0: not configured
mpbios0: bus 0 is type PCI
mpbios0: bus 1 is type ISA
ioapic0 at mainbus0: apid 0 pa 0xfec0, version 11, 24 pins
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 Intel 82441FX rev 0x02
pcib0 at pci0 dev 1 function 0 Intel 82371SB ISA rev 0x00
pciide0 at pci0 dev 1 function 1 Intel 82371SB IDE rev 0x00: DMA, channel 0
wired to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 0: QEMU HARDDISK
wd0: 16-sector PIO, LBA48, 153600MB, 314572800 sectors
wd0(pciide0:0:0): using PIO mode 4, DMA mode 2
atapiscsi0 at pciide0 channel 1 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: QEMU, QEMU DVD-ROM, 1.7. ATAPI 5/cdrom
removable
cd0(pciide0:1:0): using PIO mode 4, DMA mode 2
uhci0 at pci0 dev 1 function 2 Intel 82371SB USB rev 0x01: apic 0 int 11
piixpm0 at pci0 dev 1 function 3 Intel 82371AB Power rev 0x03: apic 0 int 9
iic0 at piixpm0
vga1 at pci0 dev 2 function 0 unknown vendor 0x1234 product 0x rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
em0 at pci0 dev 3 function 0 Intel 82540EM rev 0x03: apic 0 int 11, address
52:54:00:aa:0d:ab
eap0 at pci0 dev 4 function 0 Ensoniq AudioPCI rev 0x00: apic 0 int 11
audio0 at eap0
midi0 at eap0: AudioPCI MIDI UART
virtio0 at pci0 dev 5 function 0 Qumranet Virtio Memory rev 0x00: Virtio
Memory Balloon Device
viomb0 at virtio0
virtio0: apic 0 int 10
isa0 at pcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pms0 mux 0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
fd0 at fdc0 drive 1: density unknown
usb0 at uhci0: USB revision 1.0
uhub0 at usb0 Intel UHCI root hub rev 1.00/1.00 addr 1
nvram: invalid checksum
uhidev0 at uhub0 port 1 configuration 1 interface 0 QEMU QEMU USB Tablet
rev
1.00/0.00 addr 2
uhidev0: iclass 3/0
uhid0 at uhidev0: input=6, output=0, feature=0
vscsi0 at root
scsibus1 at vscsi0: 256 targets
softraid0 at root
scsibus2 at softraid0: 256 targets
root on wd0a (ff833b66cc728bb6.a) swap on wd0b dump on wd0b
clock: unknown CMOS layout


GENERIC.MP
==

$ sysctl hw
hw.machine=amd64
hw.model=QEMU Virtual CPU version 1.7.1
hw.ncpu=2
hw.byteorder=1234
hw.pagesize=4096
hw.disknames=wd0:ff833b66cc728bb6,cd0:,fd0:
hw.diskcount=3
hw.cpuspeed=2200
hw.vendor=Bochs
hw.product=Bochs
hw.uuid=611bc3c6-3dc2-b8a8-8a09-27d4d448
hw.physmem=4278181888
hw.usermem=4278165504
hw.ncpufound=2
hw.allowpowerdown=1

$ dmesg
OpenBSD 5.5 (GENERIC.MP) #315: Wed Mar  5 09:37:46 MST 2014
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 4278181888

OpenSMTPD routing incoming mail

[Martijn Rijkeboer]

Hi,

I'm trying to migrate our Postfix setup to OpenSMTPD. The setup consists of
two MX servers that run Spamd and that forward the incoming mail to a
internal mail server that contains the mailboxes. In Postfix a transport
map is used to accomplish this. Is it possible to create the same setup with
OpenSMTPD? The servers are running OpenBSD 5.5 AMD64.

Kind regards,


Martijn Rijkeboer

Re: OpenSMTPD routing incoming mail

[Martijn Rijkeboer]

Hi,

 # incoming mail for our domains is relayed to i-mail server
 accept from any for domain domains relay hostname i-mail

But this will also relay non existing mailboxes. Any suggestions for that?

Kind regards,


Martijn Rijkeboer

Re: OpenSMTPD routing incoming mail

[Martijn Rijkeboer]

 my solution would be:
 accept from any for domain d1.com virtual d1users relay hostname i-mail

I've tried something similar but I'm getting:
  aliases/virtual may not be used with a relay rule

Kind regards,


Martijn Rijkeboer

Re: OpenSMTPD routing incoming mail

[Martijn Rijkeboer]

 use recipient instead:
 accept from any for domain domains recipient addresses relay

Nice. The following is even simpler:
accept from any for any recipient addresses relay

Kind regards,


Martijn Rijkeboer

OpenSMTPD recipient table with db file

[Martijn Rijkeboer]

Hi,

When I try to use a db file for my recipient table I get invalid use of
table recipients as RECIPIENT parameter. When I use a plain file it
works. I've created the db file with makemap -t set recipients. Is this
on purpose or is it a bug?

Using a plain file:
  table recipients file:/etc/mail/recipients
  accept from any for any recipient recipients relay via ...

Using a db file:
  table recipients db:/etc/mail/recipients.db
  accept from any for any recipient recipients relay via ...

OS: OpenBSD 5.5 AMD64.

Kind regards,


Martijn Rijkeboer

Re: Weird disklabel problem

[Martijn Rijkeboer]

 OK, I got it booting. In a fairly useless config, but ...

 Booting from a -current amd64 cd55.iso cd-rom, I (E)dited the MBR so
 that the OpenBSD 'A6' partition started on sector 2048, and was 500MB
 in size.

 I accepted the auto configured disklabel (i.e. all space in 'a') and
 installed w/o X, Compiler or games sets.

 Removing the CD and rebooting got me to the usual login prompt.

 I'm going to experiment some more, but I'm now suspicious that the old
 '512MB' limit is coming into play somehow.

 So for those following along, try a tiny OpenBSD MBR partition
 starting at sector 2048 and see what happens. And of course if it
 works, how big can your partition be before it stops working.

 I've tried this and the system boots with 500MB, 1000MB, 2000MB but
 doesn't with 4000MB. Since 2GB is way too small, I'm going to buying a
 pci - sata card to avoid the Intel SATA chip.

 I'm thinking of buying a HighPoint Rocket 620 card. Anybody using this
 card with OpenBSD? Or recommendations for a different pci - sata card?

Unfortunately the pci - sata card didn't work either. However there
was a bios upgrade released by Gigabyte a few days after my initial
mail and with that bios version it works (using the Intel SATA chip). So
I would like to thank everybody that has spent time diagnosing this
problem.

Kind regards,


Martijn Rijkeboer

Postfix to OpenSMTPD - virtual domains transport map

[Martijn Rijkeboer]

Hi,

I'm trying to migrate our Postfix setup to OpenSMTPD (OpenBSD 5.5). The
current setup contains two mx servers that run spamd and forward the mail
to the mailbox server using a transport map. On the mailbox server we use
virtual domains so mail for i...@domain1.com and i...@domain2.com go
to different mailboxes.

On the mx servers we use the following (Postfix) options:
- virtual_mailbox_domains = hash:/etc/postfix/virtual-domains
- virtual_alias_maps  = hash:/etc/postfix/virtual-aliases
- virtual_mailbox_maps= hash:/etc/postfix/virtual-mailboxes
- virtual_transport   = smtp:[mail.example.com]

The virtual_mailbox_domains can be replaced with a domain table:
  accept for domain mydomains 

The virtual_alias_maps can be replaced with a aliasing table:
  accept for domain mydomains virual myaliases ...

But how do I replace the virtual_mailbox_maps and virtual_transport so that
only mail for known users gets forwarded to the mailbox server?

And is it possible to configure OpenSMTPD - on the mailbox server - so that
i...@domain1.com and i...@domain2.com go to different mailboxes? If I use
a userinfo table I can only specify the user part and not the complete
domain and the mail would end up in the same mailbox.

Kind regards,


Martijn Rijkeboer

Re: Weird disklabel problem

[Martijn Rijkeboer]

 Indeed. Experiments here show that plugging in a pci - sata card to
 avoid the Intel SATA chip makes the disk work fine.

 Disks smaller than 1TB also work. So I'm guessing it's something
 magical about 4K-sector disks presenting themselves as 512-byte sector
 disks that is the source of problems. I'm still a bit fogged as to how
 a disklabel triggers the problem.


 I also saw these problems with a Chronos MKNSSDCR120GB SSD drive. I
 don't know which sector size these drives use internally...

 Actually, I didn't get any of my drives to work with OpenBSD on this
 mainboard. I don't know if it helps -- I've also unsuccessfully tested a
 320GB WD3200AAKS from 08/2010.

 Best Regards
 Andreas

 OK, I got it booting. In a fairly useless config, but ...

 Booting from a -current amd64 cd55.iso cd-rom, I (E)dited the MBR so
 that the OpenBSD 'A6' partition started on sector 2048, and was 500MB
 in size.

 I accepted the auto configured disklabel (i.e. all space in 'a') and
 installed w/o X, Compiler or games sets.

 Removing the CD and rebooting got me to the usual login prompt.

 I'm going to experiment some more, but I'm now suspicious that the old
 '512MB' limit is coming into play somehow.

 So for those following along, try a tiny OpenBSD MBR partition
 starting at sector 2048 and see what happens. And of course if it
 works, how big can your partition be before it stops working.

I've tried this and the system boots with 500MB, 1000MB, 2000MB but doesn't
with 4000MB. Since 2GB is way too small, I'm going to buying a pci - sata
card to avoid the Intel SATA chip.

I'm thinking of buying a HighPoint Rocket 620 card. Anybody using this
card with OpenBSD? Or recommendations for a different pci - sata card?

Kind regards,


Martijn Rijkeboer

Re: Weird disklabel problem

[Martijn Rijkeboer]

 So marking a partition as 'Active/Bootable', (the 00 - 80 change)
 causes your system to hang. Apparently Linux does this when you
 'Label' it. The OpenBSD installer does it for you when you
 select 'Whole disk'. Nothing obviously to do with the disklabel. You
 could test this by manually
 setting the 'Active' flag on the working Linux MBR. Or, conversely
 unsetting the flag with fdisk
 after the OpenBSD install but before rebooting. In either case does it
 get further before noticing that it can't boot?


I did some testing with the following results:

1. Partition disk with Linux gparted and use cfdisk to set partition
type to A6 and OpenBSD disklabel to set disklabel.
(partition: 0; start: 2048; size: 1953519616)
- Bootflag off, no disklabel   - boot
- Bootflag on,  no disklabel   - boot
- Bootflag off, with disklabel - freeze
- Bootflag on,  with disklabel - freeze

2. Partition disk with OpenBSD fdisk + disklabel (installer start + size).
(partition: 3, start: 64; size: 1953520001)
- Bootflag off, no disklabel   - freeze
- Bootflag on,  no disklabel   - freeze
- Bootflag off, with disklabel - freeze
- Bootflag on,  with diskalbel - freeze

3. Partition disk with OpenBSD fdisk + disklabel (linux start + size).
(partition: 3: start: 2048; size: 1953519616)
- Bootflag off, no disklabel   - boot
- Bootflag on,  no disklabel   - boot
- Bootflag off, with disklabel - freeze
- Bootflag on,  with disklabel - freeze

4. Partition disk with OpenBSD fdisk with type 83 (installer start + size).
(partition: 3, start: 64; size: 1953520001)
- Bootflag off - freeze
- Bootflag on  - freeze

It looks like the motherboard doesn't like the partition to start at 64 and
it also doesn't like disklabels.

Any suggestions on what to try next or should I just buy a different
motherboard?

Kind regards,


Martijn Rijkeboer

Re: Weird disklabel problem

[Martijn Rijkeboer]

 Can you provide a hex dump of the MBR Linux produces? The evidence would
 seem to point at the boot code stored in the MBR. To which I made a
 recent minor tweak. So you might also try a 5.4 install to see if it
 works.

Below are the hexdumps of the MBR. The before was created with Linux and
before labeling. The after was created with Linux and after labeling. The
obsd-55 was created with the OpenBSD 5.5 installer with the whole disk
option. The obsd-54 was created with the OpenBSD 5.4 installer with the
whole disk option.

The before and after differ only on line 1b0. The obsd-55 and
obsd-54 are identical. The problem occurs with all except before.

Kind regards,


Martijn Rijkeboer



before
==
000 05ea c000 8c07 8ec8 bcd0 fffc d88e a0b8
010 8e07 31c0 31f6 b9ff 0200 f3fc eaa4 0022
020 07a0 071e 1f0e 02b4 16cd 03a8 0a74 07b0
030 cbe8 8000 b40e 0101 c2f6 7580 be08 0136
040 afe8 b200 be80 01be 04b9 8a00 3c04 7480
050 830f 10c6 f5e2 6abe e801 0096 f4fb fceb
060 d088 0f24 3004 27a2 b001 2834 a2c8 0134
070 be56 011a 06f6 01b4 7501 4601 73e8 5e00
080 c726 fe06 0001 f600 b406 0101 3175 1488
090 aabb b455 cd41 8a13 7214 8124 55fb 75aa
0a0 f61e 01c1 1974 2eb0 53e8 6600 4c8b 6608
0b0 0e89 0112 b456 be42 010a 13cd 735e b019
0c0 e83b 003a 748a 8b01 024c 01b8 3102 cddb
0d0 7313 be05 0152 81eb 7dbe e801 0014 8126
0e0 fe3e 5501 75aa ea05 7c00  61be e901
0f0 ff67 fc50 84ac 74c0 e80f 0002 f6eb 5350
100 0eb4 01bb cd00 5b10 c358 0010 0001 
110 07c0     5521 6973 676e
120 6420 6972 6576 5820 202c 6170 7472 7469
130 6f69 206e 0059 424d 2052 6e6f 6620 6f6c
140 7070 2079 726f 6f20 646c 4220 4f49 0d53
150 000a 0a0d 6552 6461 6520 7272 726f 0a0d
160 4e00 206f 2f4f 0d53 000a 6f4e 6120 7463
170 7669 2065 6170 7472 7469 6f69 0d6e 000a
180 0090       
190        
*
1b0    784f b8e7 0009  2000
1c0 0021 fea6  0800  5800 7470 
1d0        
*
1f0        aa55
200


after
=
000 05ea c000 8c07 8ec8 bcd0 fffc d88e a0b8
010 8e07 31c0 31f6 b9ff 0200 f3fc eaa4 0022
020 07a0 071e 1f0e 02b4 16cd 03a8 0a74 07b0
030 cbe8 8000 b40e 0101 c2f6 7580 be08 0136
040 afe8 b200 be80 01be 04b9 8a00 3c04 7480
050 830f 10c6 f5e2 6abe e801 0096 f4fb fceb
060 d088 0f24 3004 27a2 b001 2834 a2c8 0134
070 be56 011a 06f6 01b4 7501 4601 73e8 5e00
080 c726 fe06 0001 f600 b406 0101 3175 1488
090 aabb b455 cd41 8a13 7214 8124 55fb 75aa
0a0 f61e 01c1 1974 2eb0 53e8 6600 4c8b 6608
0b0 0e89 0112 b456 be42 010a 13cd 735e b019
0c0 e83b 003a 748a 8b01 024c 01b8 3102 cddb
0d0 7313 be05 0152 81eb 7dbe e801 0014 8126
0e0 fe3e 5501 75aa ea05 7c00  61be e901
0f0 ff67 fc50 84ac 74c0 e80f 0002 f6eb 5350
100 0eb4 01bb cd00 5b10 c358 0010 0001 
110 07c0     5521 6973 676e
120 6420 6972 6576 5820 202c 6170 7472 7469
130 6f69 206e 0059 424d 2052 6e6f 6620 6f6c
140 7070 2079 726f 6f20 646c 4220 4f49 0d53
150 000a 0a0d 6552 6461 6520 7272 726f 0a0d
160 4e00 206f 2f4f 0d53 000a 6f4e 6120 7463
170 7669 2065 6170 7472 7469 6f69 0d6e 000a
180 0090       
190        
*
1b0    784f b8e7 0009  2080
1c0 0021 fea6  0800  5800 7470 
1d0        
*
1f0        aa55
200


obsd-55
===
000 05ea c000 8c07 8ec8 bcd0 fffc d88e a0b8
010 8e07 31c0 31f6 b9ff 0200 f3fc eaa4 0022
020 07a0 071e 1f0e 02b4 16cd 03a8 0a74 07b0
030 cbe8 8000 b40e 0101 c2f6 7580 be08 0136
040 afe8 b200 be80 01be 04b9 8a00 3c04 7480
050 830f 10c6 f5e2 6abe e801 0096 f4fb fceb
060 d088 0f24 3004 27a2 b001 2834 a2c8 0134
070 be56 011a 06f6 01b4 7501 4601 73e8 5e00
080 c726 fe06 0001 f600 b406 0101 3175 1488
090 aabb b455 cd41 8a13 7214 8124 55fb 75aa
0a0 f61e 01c1 1974 2eb0 53e8 6600 4c8b 6608
0b0 0e89 0112 b456 be42 010a 13cd 735e b019
0c0 e83b 003a 748a 8b01 024c 01b8 3102 cddb
0d0 7313 be05 0152 81eb 7dbe e801 0014 8126
0e0 fe3e 5501 75aa ea05 7c00  61be e901
0f0 ff67 fc50 84ac 74c0 e80f 0002 f6eb 5350
100 0eb4 01bb cd00 5b10 c358 0010 0001 
110 07c0     5521 6973 676e
120 6420 6972 6576 5820 202c 6170 7472 7469
130 6f69 206e 0059 424d 2052 6e6f 6620 6f6c
140 7070 2079 726f 6f20 646c 4220 4f49 0d53
150 000a 0a0d 6552 6461 6520 7272 726f 0a0d
160 4e00 206f 2f4f 0d53 000a 6f4e 6120 7463
170 7669 2065 6170 7472 7469 6f69 0d6e 000a
180 0090       
190        
*
1b0    784f    
1c0        

Re: Weird disklabel problem

[Martijn Rijkeboer]

 Your MBR OpenBSD partition is not flagged as active.

Yes I know, but that doesn't matter for this problem..

Kind regards,


Martijn Rijkeboer

Re: Weird disklabel problem

[Martijn Rijkeboer]

 Did you guys see my mail yesterday ? (albeit responding to the Problem
 booting OpenBSD-current AMD64 thread)

Yes I did. Sorry for the late response.


 First of all I'd expect OpenBSD to create its fdisk partition on the
 partition with id 3, starting at LBA offset 64. (don't know if this
 changed)
 Is the partition 0 starting at offset 2048 a Linux left-over ?

No I did that on purpose, because when I partition the harddisk with the
OpenBSD installer the system won't boot.


 Anyway, my Gigabyte board used to work fine with a fdisk partition
 starting at either offset 63 or 64, respectively. Not so much after
 installing Linux the other day, which put the starting offset at 2048.

Unfortunately this board won't start with the offset of either 63 or 64.


 This happens using the on-board Intel AHCI controller. Fortunately my
 board also has a non-Intel controller which does work, so being able to
 use that I didn't put more time into investigating this.

Unfortunately this board doesn't have a non-Intel controller.

Kind regards,


Martijn Rijkeboer

Weird disklabel problem

[Martijn Rijkeboer]

Hello,

I've got a weird disklabel related problem (or so it seems). When I
partition my harddisk with fdisk and add an OpenBSD (A6) primary
partition the system can still boot, but once I place a disklabel
on the partition (disklabel -E sd0) I can't boot the system anymore
(it freezes during the post).

System Info:
- OS: OpenBSD-current AMD64
- CPU: Intel Core i3 4130T
- Motherboard: Gigabyte GA-B85M-DS3H
- Harddisk: WD Green 1TB (SATA)

It is possible that it's a Gigabyte specific problem since Karl
Karlsson has the same problem with his Gigabyte GA-Z87MX-DH3
motherboard.

The other strange thing is that if I use an USB-stick instead
of the harddisk I can install and boot OpenBSD without problems.
Even with the harddisk present, but without a disklabel, I can
still boot from the USB stick, but as soon as I place a disklabel
on the harddisk (although it isn't used, nor in the boot sequence)
the system freezes during the post again.

Any suggestions on how to fix this or should I just buy a different
motherboard?

Kind regards,


Martijn Rijkeboer

Re: Weird disklabel problem

[Martijn Rijkeboer]

 Please post at least a dmesg with the disk attached but no disklabel
 plus fdisk and disklabel output after setting the label but before the
 (failing) reboot.

Below you will find the dmesg and output from fdisk and disklabel before
and after labeling. I used Linux to partition the harddisk, because if I
use the Whole option from the OpenBSD installer in can't boot...

Kind regards,


Martijn Rijkeboer

dmesg
=

OpenBSD 5.5-current (GENERIC.MP) #86: Tue Apr 29 03:35:46 MDT 2014
t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8443088896 (8051MB)
avail mem = 8209612800 (7829MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb5f0 (76 entries)
bios0: vendor American Megatrends Inc. version F2 date 01/18/2014
bios0: Gigabyte Technology Co., Ltd. B85M-DS3H
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT SSDT SSDT MCFG HPET SSDT SSDT DMAR
acpi0: wakeup devices PS2K(S3) PS2M(S3) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) 
PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) PXSX(S4) RP06(S4) 
PXSX(S4) RP07(S4) [...]
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) i3-4130T CPU @ 2.90GHz, 2893.72 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,LONG,LAHF,ABM,PERF,ITSC
cpu0: 256KB 64b/line 8-way L2 cache
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=25345, max=46847 (bogus)
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Core(TM) i3-4130T CPU @ 2.90GHz, 2893.30 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,LONG,LAHF,ABM,PERF,ITSC
cpu1: 256KB 64b/line 8-way L2 cache
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
acpimcfg0 at acpi0 addr 0xf800, bus 0-63
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (RP01)
acpiprt2 at acpi0: bus 2 (RP03)
acpiprt3 at acpi0: bus -1 (P0P2)
acpiprt4 at acpi0: bus -1 (P0PA)
acpiprt5 at acpi0: bus -1 (P0PB)
acpiprt6 at acpi0: bus -1 (PEG0)
acpiprt7 at acpi0: bus -1 (PEG1)
acpiprt8 at acpi0: bus -1 (PEG2)
acpiec0 at acpi0: Failed to read resource settings
acpicpu0 at acpi0: C2, C1, PSS
acpicpu1 at acpi0: C2, C1, PSS
acpipwrres0 at acpi0: FN00, resource for FAN0
acpipwrres1 at acpi0: FN01, resource for FAN1
acpipwrres2 at acpi0: FN02, resource for FAN2
acpipwrres3 at acpi0: FN03, resource for FAN3
acpipwrres4 at acpi0: FN04, resource for FAN4
acpitz0 at acpi0: critical temperature is 90 degC
acpitz1 at acpi0: critical temperature is 90 degC
acpibat0 at acpi0: BAT0 not present
acpibat1 at acpi0: BAT1 not present
acpibat2 at acpi0: BAT2 not present
acpibtn0 at acpi0: PWRB
acpibtn1 at acpi0: LID0
acpivideo0 at acpi0: GFX0
acpivout0 at acpivideo0: DD1F
cpu0: Enhanced SpeedStep 2893 MHz: speeds: 2900, 2800, 2600, 2500, 2300, 2200, 
2100, 1900, 1800, 1600, 1500, 1400, 1200, 1100, 900, 800 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 Intel Core 4G Host rev 0x06
vga1 at pci0 dev 2 function 0 Intel HD Graphics 4600 rev 0x06
intagp0 at vga1
agp0 at intagp0: aperture at 0xe000, size 0x1000
inteldrm0 at vga1
drm0 at inteldrm0
error: [drm:pid0:i915_write32] *ERROR* Unknown unclaimed register before 
writing to 10
inteldrm0: 1920x1200
wsdisplay0 at vga1 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 0x06: msi
azalia0: No codecs found
Intel 8 Series xHCI rev 0x05 at pci0 dev 20 function 0 not configured
Intel 8 Series MEI rev 0x04 at pci0 dev 22 function 0 not configured
puc0 at pci0 dev 22 function 3 Intel 8 Series KT rev 0x04: ports: 1 com
com4 at puc0 port 0 apic 2 int 19: ns16550a, 16 byte fifo
com4: probed fifo depth: 0 bytes
ehci0 at pci0 dev 26 function 0 Intel 8 Series USB rev 0x05: 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
azalia1 at pci0 dev 27 function 0 Intel 8 Series HD Audio rev 0x05: msi
azalia1: codecs: Realtek/0x0887
audio0 at azalia1
ppb0 at pci0 dev 28 function 0 Intel 8 Series PCIE rev 0xd5: msi
pci1 at ppb0 bus 1
ppb1 at pci0 dev 28 function 2 Intel 8 Series PCIE rev 0xd5: msi
pci2 at ppb1 bus 2
re0 at pci2 dev 0 function 0 Realtek 8168 rev 0x06: RTL8168E/8111E-VL 
(0x2c80), msi, address 74:d4:35:04:aa:86
rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 5
ehci1 at pci0 dev 29 function 0 Intel 8

Re: Problem booting OpenBSD-current AMD64

[Martijn Rijkeboer]

 Ubuntu (server) 14.04 supports UEFI so it's hard to tell what you are
 seeing here.

 Perhaps you could explain what happens when you try and boot OpenBSD?
 Let's start with 1. what medium are you using and 2. what does it
 display when it tries to boot?

When I power on the machine I see the GigaByte logo and at the bottom
the options to enter the bios, Q-flash and boot selection. As soon
as this is shown the system freezes. I can't enter the bios by pressing
Del or select the boot media by pressing F12 nor does OpenBSD start.

I've installed the system using the install55.iso onto the SATA
harddisk (WD Green 1TB).

Once I have installed OpenBSD onto the harddisk I can't get into
the bios or boot from a CDROM althrough the CDROM is specified as
the first boot device. To be able to enter the bios again I have
to remove the harddisk or whipe the first few megabytes of the harddisk
with dd on another computer.

Hope this helps.


Kind regards,


Martijn Rijkeboer

Re: Problem booting OpenBSD-current AMD64

[Martijn Rijkeboer]

 I've installed OpenBSD-current AMD64 on my new computer without problems,
 but as soon as I reboot the system, it freezes in the post. The only way to
 go past the post is wiping the first few megabytes of the harddisk using
 another computer and than start again. After installing I can't even
 enter the bios setup.
 
 The system contains the following components:
 - Motherboard: Gigabyte GA-B85M-DS3H
 - CPU: Intel Core i3 4130T
 - Memory: Kingston ValueRAM 8 GB DDR3-1600 Kit
 
 I've configured the bios the following way:
 - Windows 8 Features: Other OS
 - Boot Mode Selection: Legacy Only
 - VGA Support: Auto (Enables legacy option)

 I'm not familiar with the particular motherboard, but I had success
 with other Gigabyte models.

 Find the option CSM Support in the bios and set it to Always, leave
 Boot Mode Selection and Storage Boot Option Control to Legacy
 Only, power down the system and then try booting OpenBSD.

Unfortunately that doesn't work either. The strange thing is that if I remove
the harddisk and use an USB stick I can install OpenBSD on it and boot it
without problems.

When I place the harddisk back with only an OpenBSD fdisk partition (A6) I can
still boot from the USB stick, but once I place a disklabel on the harddisk I
can't boot anymore (the system freezes on reboot). Apparently the bios can't
handle the disklabel...

Kind regards,


Martijn Rijkeboer

Problem booting OpenBSD-current AMD64

[Martijn Rijkeboer]

I've installed OpenBSD-current AMD64 on my new computer without problems,
but as soon as I reboot the system, it freezes in the post. The only way to
go past the post is wiping the first few megabytes of the harddisk using
another computer and than start again. After installing I can't even
enter the bios setup.

The system contains the following components:
- Motherboard: Gigabyte GA-B85M-DS3H
- CPU: Intel Core i3 4130T
- Memory: Kingston ValueRAM 8 GB DDR3-1600 Kit

I've configured the bios the following way:
- Windows 8 Features: Other OS
- Boot Mode Selection: Legacy Only
- VGA Support: Auto (Enables legacy option)

The system is working since I can install and run Ubuntu 14.04 AMD64
without problems.

Any suggestions on how to fix this?

Kind regards,


Martijn Rijkeboer

Re: PPPoE ip unnumbered

[Martijn Rijkeboer]

 Is it possible to create an IP unnumbered setup with PPPoE on OpenBSD?

 And what the heck you mean by unnumbered? If it is wildcard address,
 and by it, that the pppoe access concentrator provides the ip addres,
 then yes, it works. For us to help you we need a little more than this.

Sorry for not providing enough information. IP unnumbered seems to mean
that both the pppoe physical device and the pppoe device don't have an
IP-address. Only the internal interface has an IP-address. The following
is a Cisco configuration that shows such a configuration.

  interface FastEthernet0/0
   description LAN klant
   ip address 123.123.123.1 255.255.255.128
   duplex auto
   speed auto
   no keepalive
  !
  interface FastEthernet0/1
   description WAN
   no ip address
   duplex full
   speed 100
   pppoe enable
   pppoe-client dial-pool-number 1
  !
  interface Dialer0
   ip unnumbered FastEthernet0/0
   encapsulation ppp
   ip tcp adjust-mss 1452
   dialer pool 1
   dialer idle-time
   dialer-group 1
   no cdp enable
   ppp authentication pap callin
   ppp pap sent-username username@solcon.net password password
  !
  ip route 0.0.0.0 0.0.0.0 Dialer0 permanent


Kind regards,


Martijn Rijkeboer

Re: PPPoE ip unnumbered

[Martijn Rijkeboer]

 Is it possible to create an IP unnumbered setup with PPPoE on OpenBSD?

 Untested but I think you should be able to put an address from your lan
 interface on the pppoe interface which might do what you want..
 Worth a try anyway.

Unfortunately that doesn't work.

Kind regards,


Martijn Rijkeboer

Re: PPPoE ip unnumbered

[Martijn Rijkeboer]

 My setup is exactly like this. The physical interface do not have an ip
 address and the pppoe also do not have an ip address until the
 concentrator provides one:

 inet 0.0.0.0 255.255.255.255 NONE \
  pppoedev physical_dev authproto pap \
  authname 'user' authkey 'pass' up
  dest 0.0.0.1
  !/sbin/route add default -ifp pppoe0 0.0.0.1

The difference is that in the setup that I needed the concentrator doesn't
provide an IP. The ISP will route the traffic to the IP on the internal
interface, so both the PPPoE physical device and the PPPoE device don't
have an IP and won't get one either (that's probably why it is called
unnumbered).

Anyway my ISP has changed the setup so now I've got a static route without
PPPoE and that works just fine.

Kind regards,


Martijn Rijkeboer

Re: PPPoE ip unnumbered

[Martijn Rijkeboer]

 Can you show what you tried (e.g. ifconfig -A output)?

Unfortunately I can't since my ISP has changed the setup to a static route
and that is now operational (no PPPoE anymore).

Kind regards,


Martijn Rijkeboer

Re: PPPoE ip unnumbered

[Martijn Rijkeboer]

 The point behind unnumbered is that the ppp interface *doesn't* have an
 IP, usually this is when the WAN address is inside a routed subnet.
 Since PPP is layer2, IP addresses aren't actually needed.

Indeed.

Kind regards,


Martijn Rijkeboer

Re: PPPoE problem

[Martijn Rijkeboer]

 Does it work with a configuration such as this?

 inet 123.123.123.1 255.255.255.128 NONE \
 pppoedev em2 authproto pap \
 authname 'username@solcon.net' authkey 'password' up
 dest 0.0.0.1
 ! /sbin/route add default 123.123.123.1

 I'm using a configuration like that with static IP over pppoe
 from a german ISP and it works fine.

 You might see some hints logged to /var/log/messages if you
 run 'ifconfig pppoe0 debug'.

Unfortunately I can't try this setup anymore, since my ISP has changed
the setup to a static route without PPPoE which is currently operational.


Kind regards,


Martijn Rijkeboer

PPPoE problem

[Martijn Rijkeboer]

Hi,

I'm trying to setup a PPPoE connection to my ISP (solcon.nl). I've read
pppoe(4) and pppoe(8) and got the following configuration:

cat /etc/hostname.pppoe0
  inet 0.0.0.0 255.255.255.255 NONE \
pppoedev em2 authproto pap \
authname 'username@solcon.net' authkey 'password' up
  dest 0.0.0.1
  !/sbin/route add default -ifp pppoe0 0.0.0.1


cat /etc/hostname.em2
  up


According to my ISP I should specify my IP-address and netmask which makes
the following:

cat /etc/hostname.pppoe0
  inet 123.123.123.1 255.255.255.128 NONE \
pppoedev em2 authproto pap \
authname 'username@solcon.net' authkey 'password' up
  dest 0.0.0.1
  !/sbin/route add default -ifp pppoe0 0.0.0.1


In both cases I'm getting pppoe0: pap failure. This seems to indicate
that the authentications is wrong, but according to my ISP they don't see
any traffic from me to their radius server and we double checked the
username and password.

Since they don't support OpenBSD they gave me a sample config for Cisco:

  interface FastEthernet0/0
   description LAN klant
   ip address 123.123.123.1 255.255.255.128
   duplex auto
   speed auto
   no keepalive
  !
  interface FastEthernet0/1
   description WAN
   no ip address
   duplex full
   speed 100
   pppoe enable
   pppoe-client dial-pool-number 1
  !
  interface Dialer0
   ip unnumbered FastEthernet0/0
   encapsulation ppp
   ip tcp adjust-mss 1452
   dialer pool 1
   dialer idle-time
   dialer-group 1
   no cdp enable
   ppp authentication pap callin
   ppp pap sent-username username@solcon.net password password
  !
  ip route 0.0.0.0 0.0.0.0 Dialer0 permanent


Any suggestions on what I'm doing wrong or how to configure this?

Kind regards,


Martijn Rijkeboer

PPPoE ip unnumbered

[Martijn Rijkeboer]

Hi,

Is it possible to create an IP unnumbered setup with PPPoE on OpenBSD?

Kind regards,


Martijn Rijkeboer

acpi0: PM1 stuck (en 0x121 st 0x1), clearing

[Martijn Rijkeboer]

Hi,

Every time I boot OpenBSD (5.4-current AMD64) I get the following
message/error after a while:
  acpi0: PM1 stuck (en 0x121 st 0x1), clearing

Any suggestions what the problem could be? The system runs openbox, chrome,
vim, terminator and ghc and feels much slower than when running Xubuntu
12.04 LTS (dual booting). Dmesg is below.

Kind regards,


Martijn Rijkeboer


OpenBSD 5.4-current (GENERIC.MP) #171: Sat Nov 30 00:30:47 MST 2013
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8553889792 (8157MB)
avail mem = 8318050304 (7932MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf0100 (59 entries)
bios0: vendor Award Software International, Inc. version F4 date 10/13/2011
bios0: Gigabyte Technology Co., Ltd. GA-970A-UD3
acpi0 at bios0: rev 0
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP MSDM HPET MCFG MATS TAMG APIC MATS SSDT
acpi0: wakeup devices USB0(S3) USB1(S3) USB2(S3) USB3(S3) USB4(S3)
USB5(S3) USB6(S3) SBAZ(S4) PEX0(S5) PEX1(S5) PEX2(S5) PEX3(S5) P2P_(S5)
PCE2(S4) PCE3(S4) PCE4(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpihpet0 at acpi0: 14318180 Hz
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: AMD FX(tm)-4100 Quad-Core Processor , 20295.75 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,NXE,MMXX,FFXSR,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TOPEXT,ITSC
cpu0: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB
64b/line 16-way L2 cache, 8MB 64b/line 64-way L3 cache
cpu0: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative
cpu0: DTLB 32 4KB entries fully associative, 32 4MB entries fully associative
cpu0: smt 0, core 0, package 0
cpu0: apic clock running at 201MHz
cpu0: mwait min=64, max=64, C-substates=0.0.0.0.0, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: AMD FX(tm)-4100 Quad-Core Processor , 3624.11 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,NXE,MMXX,FFXSR,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TOPEXT,ITSC
cpu1: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB
64b/line 16-way L2 cache, 8MB 64b/line 64-way L3 cache
cpu1: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative
cpu1: DTLB 32 4KB entries fully associative, 32 4MB entries fully associative
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: AMD FX(tm)-4100 Quad-Core Processor , 3624.11 MHz
cpu2:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,NXE,MMXX,FFXSR,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TOPEXT,ITSC
cpu2: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB
64b/line 16-way L2 cache, 8MB 64b/line 64-way L3 cache
cpu2: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative
cpu2: DTLB 32 4KB entries fully associative, 32 4MB entries fully associative
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: AMD FX(tm)-4100 Quad-Core Processor , 3624.11 MHz
cpu3:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,NXE,MMXX,FFXSR,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TOPEXT,ITSC
cpu3: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB
64b/line 16-way L2 cache, 8MB 64b/line 64-way L3 cache
cpu3: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative
cpu3: DTLB 32 4KB entries fully associative, 32 4MB entries fully associative
cpu3: smt 0, core 3, package 0
ioapic0 at mainbus0: apid 8 pa 0xfec0, version 21, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 8
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 6 (PEX0)
acpiprt2 at acpi0: bus -1 (PEX1)
acpiprt3 at acpi0: bus -1 (PEX2)
acpiprt4 at acpi0: bus -1 (PEX3)
acpiprt5 at acpi0: bus 5 (P2P_)
acpiprt6 at acpi0: bus 1 (PCE2)
acpiprt7 at acpi0: bus -1 (PCE3)
acpiprt8 at acpi0: bus 2 (PCE4)
acpiprt9 at acpi0: bus -1 (PCE5)
acpiprt10 at acpi0: bus -1 (PCE6)
acpiprt11 at acpi0: bus 3 (PCE7)
acpiprt12 at acpi0: bus -1 (PCE9)
acpiprt13 at acpi0: bus 4 (PCEA)
acpiprt14 at acpi0: bus -1 (PCEB)
acpiprt15 at acpi0: bus -1 (PCEC)
acpiprt16 at acpi0: bus -1 (PCED)
acpicpu0 at acpi0: C2, PSS
acpicpu1 at acpi0: C2, PSS
acpicpu2 at acpi0: C2, PSS
acpicpu3 at acpi0: C2, PSS
acpibtn0 at acpi0: PWRB
cpu0: 20295 MHz: speeds: 3600 3300 2500

Re: Unbound in base

[Martijn Rijkeboer]

 The primary cause of this is unbound is not a drop-in replacement for
 bind, they use different utilities, like unbound use drill, and bind use
 dig and friends.

Maybe I'm overlooking something, but that could be a problem with replacing
bind by unbound but not with linking unbound to the build. Currently we have
bind/nsd and apache/nginx all linked to the build.

Anyway I'm just curious, so no complaining intended.

Kind regards,


Martijn Rijkeboer

Unbound in base

[Martijn Rijkeboer]

Hi,

Just out of curiosity, what is holding the linking of Unbound to the build
back? I'm not complaining since I'm using Unbound from ports without issues.

Kind regards,


Martijn Rijkeboer

Re: uaudio0: audio descriptors make no sense, with Schiit Bifrost USB DAC

[Martijn Rijkeboer]

 If I'm interpreting this correctly your device is an USB Audio 2.0
 device.
 AFAICT there's currently no support for such a device in OpenBSD.

I didn't know it wasn't supported, so thanks for the info.


 But it shouldn't be too hard to port the FreeBSD changes in our tree, if
 anybody is motivated ;)

Well I guess that anybody should be me, but I don't have the needed
kernel / device skills nor the time to learn them, which will probably mean
nothing will change in this area.

Kind regards,


Martijn Rijkeboer

Re: uaudio0: audio descriptors make no sense, with Schiit Bifrost USB DAC

[Martijn Rijkeboer]

)
bTerminalLink   1
bmControls   0x05
  Active Alternate Setting Control (read-only)
  Valid Alternate Setting Control (read-only)
bFormatType 1
bmFormats   1
  PCM
bNrChannels 2
bmChannelConfig   0x0003
  Front Left (FL)
  Front Right (FR)
iChannelNames   0
  AudioStreaming Interface Descriptor:
bLength 6
bDescriptorType36
bDescriptorSubtype  2 (FORMAT_TYPE)
bFormatType 1 (FORMAT_TYPE_I)
bSubslotSize4
bBitResolution 32
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x05  EP 5 OUT
bmAttributes5
  Transfer TypeIsochronous
  Synch Type   Asynchronous
  Usage Type   Data
wMaxPacketSize 0x00d0  1x 208 bytes
bInterval   1
AudioControl Endpoint Descriptor:
  bLength 8
  bDescriptorType37
  bDescriptorSubtype  1 (EP_GENERAL)
  bmAttributes 0x00
  bmControls   0x00
  bLockDelayUnits 0 Undefined
  wLockDelay  0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x85  EP 5 IN
bmAttributes   17
  Transfer TypeIsochronous
  Synch Type   None
  Usage Type   Feedback
wMaxPacketSize 0x0004  1x 4 bytes
bInterval   4
Interface Association:
  bLength 8
  bDescriptorType11
  bFirstInterface 2
  bInterfaceCount 1
  bFunctionClass  3 Human Interface Device
  bFunctionSubClass   0 No Subclass
  bFunctionProtocol   0 None
  iFunction   0
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber2
  bAlternateSetting   0
  bNumEndpoints   1
  bInterfaceClass 3 Human Interface Device
  bInterfaceSubClass  0 No Subclass
  bInterfaceProtocol  0 None
  iInterface  0
HID Device Descriptor:
  bLength 9
  bDescriptorType33
  bcdHID   1.00
  bCountryCode0 Not supported
  bNumDescriptors 1
  bDescriptorType34 Report
  wDescriptorLength  24
  Report Descriptor: (length is 24)
Item(Global): Usage Page, data= [ 0x0c ] 12
Consumer
Item(Local ): Usage, data= [ 0x01 ] 1
Consumer Control
Item(Main  ): Collection, data= [ 0x01 ] 1
Application
Item(Global): Logical Minimum, data= [ 0x00 ] 0
Item(Global): Logical Maximum, data= [ 0xff 0x00 ] 255
Item(Global): Report Size, data= [ 0x08 ] 8
Item(Global): Report Count, data= [ 0x10 ] 16
Item(Local ): Usage, data= [ 0x00 ] 0
Unassigned
Item(Main  ): Input, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile
Bitfield
Item(Local ): Usage, data= [ 0x00 ] 0
Unassigned
Item(Main  ): Output, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile
Bitfield
Item(Main  ): End Collection, data=none
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84  EP 4 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0010  1x 16 bytes
bInterval   4
Device Qualifier (for other device speed):
  bLength10
  bDescriptorType 6
  bcdUSB   2.00
  bDeviceClass  239 Miscellaneous Device
  bDeviceSubClass 2 ?
  bDeviceProtocol 1 Interface Association
  bMaxPacketSize064
  bNumConfigurations  1
Device Status: 0x
  (Bus Powered)


Kind regards,


Martijn Rijkeboer

uaudio0: audio descriptors make no sense, with Schiit Bifrost USB DAC

[Martijn Rijkeboer]

Hi,

I have a Schiit Bifrost USB DAC that includes an uaudio device for audio
playback. When I plug the device in I'm getting uaudio0: audio
descriptors make no sense, error=4. Any suggestions on how to make this
work?

Here are the relevant lines from usbdevs -v (debugging enabled for uaudio):

Controller /dev/usb0:
addr 1: high speed, self powered, config 1, EHCI root hub(0x),
Intel(0x8086), rev 1.00
 port 1 addr 2: high speed, power 100 mA, config 1, Schiit USB Audio
Device(0x0319), Schiit(0x0d8c), rev 1.02
 port 2 powered
 port 3 powered
 port 4 powered
 port 5 powered
 port 6 powered


Here are the relevant lines from dmesg:

uaudio0 at uhub0 port 1 configuration 1 interface 0 Schiit Schiit USB Audio
Device rev 2.00/1.02 addr 2
uaudio_identify_ac: AC interface is 0
uaudio0: audio descriptors make no sense, error=4
uhidev0 at uhub0 port 1 configuration 1 interface 2 Schiit Schiit USB Audio
Device rev 2.00/1.02 addr 2
uhidev0: iclass 3/0
uhid0 at uhidev0: input=16, output=16, feature=0
ugen0 at uhub0 port 1 configuration 1 Schiit Schiit USB Audio Device rev
2.00/1.02 addr 2


Here is the uname -a output:

OpenBSD goofy.bunix.org 5.3 GENERIC#0 i386


Kind regards,


Martijn Rijkeboer

Re: ESI Julia XTe soundcard

[Martijn Rijkeboer]

 ESI Julia XTe places Envy24HT-S on PCIe via TENOR TE7009 PCI-to-PCIe
 bridge, which is transparent bridge. so, it should work right away,
 because PCIe-to-PCI conversion is entirely transparent from audio
 driver point of view - it will be recognized by the driver as ESI
 Julia on PCI, i.e. exactly like the old card. however, one potential
 problem (but it's very unlikely) is issues with PCIe-to-PCI chip in
 use in OpenBSD - i have such in the past, even though that was on
 different favor of *BSD, as well it was many years ago and it could be
 already fixed, but here is the old case for reference:

Thanks for the info. If I buy this card -- I'm still in doubt whether to use
this card or the onboard S/PDIF with external DAC -- I will let the list
know the results.

Kind regards,


Martijn Rijkeboer

ESI Julia XTe soundcard

[Martijn Rijkeboer]

Hi,

According to the envy(4) manpage the ESI Julia is supported. Is the
ESI Julia XTe [1], which is the PCIe version of the Julia, known or expected
to work?

Kind regards,


Martijn Rijkeboer


[1] http://www.esi-audio.com/products/juliaxte/

Re: 3k machines

[Martijn Rijkeboer]

Hi Friedrich,

 i am managing some openbsd machines. There are a company, here, in the
 city a live that holds about 3k machines and i not including servers
 hardware; only desktop.

 I was wondering: How do you manage such a volume of nodes, i mean, in an
 efficient manner.
 Any experience with that ?

I would recommend Cfengine [1]. Unfortunately the latest version segfaults
on OpenBSD, but version 3.4.0b1 still works fine. I've opened a bug
report [2] with Cfengine, but no solution yet. If you want, I can provide
you with the package for 5.2 (AMD64) or the updated port.

Kind regards,


Martijn Rijkeboer

1. http://cfengine.com/
2. https://cfengine.com/dev/issues/1701

Re: Shellscript escaping problem

[Martijn Rijkeboer]

 If you're doing complex rsync setups, you might also consider using
 rsnapshot as a wrapper. I just joined the maintainer list on that,
 it's a very useful old perl tool, well organized for frequent and well
 managed backups.

Rsnapshot is a nice tool, but for my current usage rsync suffices.

Kind regards,


Martijn Rijkeboer

Re: Shellscript escaping problem

[Martijn Rijkeboer]

 RSYNC_CMD=/usr/local/bin/rsync -v -n \
  --rsync-path='rsync sudo' \

 This doesn't do what you think it does.  The single quotes are getting
 literally passed to rsync, they're not reinterpreted after $RSYNC_CMD
 is interpolated.

 Yep. $RSYNC_CMD will be splitted by space, tab or newline by default, or
 by the contents of $IFS, if set.

 if you need it to be reusable, I'd suggest making it a function or so:

 synchronize() {
   /usr/local/bin/rsync -v -n \
   --rsync-path='/usr/bin/sudo /usr/local/bin/rsync' \
   --archive --one-file-system --compress --hard-links \
   --numeric-ids --human-readable --delete-after \
   --backup --backup-dir=deleted/$TODAY \
   --exclude=deleted \
   $@
 }

 synchronize backup@fqdn:$DATADIR/dir/ $DATADIR/dir

Using a function works without problems. Thanks to all who gave input.

Kind regards,


Martijn Rijkeboer

Shellscript escaping problem

[Martijn Rijkeboer]

Hi,

I'm using the script below and it keeps giving me the following error:

  Unexpected remote arg: backup@fqdn:/data/dir/
  rsync error: syntax or usage error (code 1) at main.c(1214) [sender=3.0.9]

It looks like something is going wrong with my escaping, because when I
remove the --rsync-path line everything works fine. It also works fine
if I echo the last line of the script and copy and paste it in my shell
(KSH). I've tried all kinds of different escaping and nothing seems to
work. Any ideas on what I'm doing wrong?

Kind regards,


Martijn Rijkeboer


#!/bin/sh

DATADIR=/data
TODAY=`/bin/date +%Y%m%d`

RSYNC_CMD=/usr/local/bin/rsync -v -n \
--rsync-path='rsync sudo' \
--rsh=ssh \
--archive --one-file-system --compress --hard-links --numeric-ids \
--human-readable --delete-after --backup --backup-dir=deleted/$TODAY \
--exclude=deleted

$RSYNC_CMD backup@fqdn:$DATADIR/dir/ $DATADIR/dir

Re: Page fault trap when booting GENERIC.MP on Xen

[Martijn Rijkeboer]

 Like http://marc.info/?l=openbsd-miscm=133612760603867w=2 ?

 He is using OpenBSD as a guest in Xen, not as a host.

Indeed.

Kind regards,


Martijn Rijkeboer

Re: Page fault trap when booting GENERIC.MP on Xen

[Martijn Rijkeboer]

 Xen is basically its own platform.  If you take a look at the NetBSD
 or FreeBSD trees, you'll see that there are scads of #ifdef XEN
 lines throughout the kernel, including additional MMU flushing from
 the core context switch routine...and completely different startup
 routines for additional CPUs.

 OpenBSD has not been ported this new platform.

Clear. I guess that this will not happen anytime soon, so better bet
on KVM?

Kind regards,


Martijn Rijkeboer

Page fault trap when booting GENERIC.MP on Xen

[Martijn Rijkeboer]

 targets
root on wd0a (6412ffe6504713d5.a) swap on wd0b dump on wd0b
clock: unknown CMOS layout


Kind regards,


Martijn Rijkeboer

Re: Crash with uvm_fault after upgrade to latest snapshot

[Martijn Rijkeboer]

Hi,

 After upgrading my AMD64-current installation to the latest snapshot it
 crashes on boot with an uvm_fault.

With the latest snapshot the problem has vanished.

Kind regards,


Martijn Rijkeboer

Re: Crash with uvm_fault after upgrade to latest snapshot

[Martijn Rijkeboer]

Hi Ariane,

 dmesg from an older kernel that does work :)

Below is the dmesg from the kernel with fxp disabled (thanks Otto).

OpenBSD 5.1-current (GENERIC.MP) #248: Wed Mar 28 21:46:36 MDT 2012
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 2146369536 (2046MB)
avail mem = 2066944000 (1971MB)
User Kernel Config
UKC disable fxp
105 fxp* disabled
106 fxp* disabled
UKC exit
Continuing...
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.3 @ 0xf0100 (41 entries)
bios0: vendor Award Software International, Inc. version FB date 01/10/2007
bios0: Gigabyte Technology Co., Ltd. M55S-S3
acpi0 at bios0: rev 0
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT HPET MCFG APIC
acpi0: wakeup devices HUB0(S5) XVR0(S5) XVR1(S5) XVR2(S5) XVR3(S5)
XVR4(S5) XVR5(S5) USB0(S3) USB2(S3) AZAD(S5) MMAC(S5) UAR1(S5)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: counter not incrementing
acpimcfg0 at acpi0 addr 0xe000, bus 0-127
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: AMD Athlon(tm) 64 X2 Dual Core Processor 4800+, 2513.19 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,3DNOWP
cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB
64b/line 16-way L2 cache
cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative
cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative
cpu0: apic clock running at 201MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: AMD Athlon(tm) 64 X2 Dual Core Processor 4800+, 2512.88 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,3DNOWP
cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB
64b/line 16-way L2 cache
cpu1: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative
cpu1: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 11, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 2
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (HUB0)
acpicpu0 at acpi0: PSS
acpicpu1 at acpi0: PSS
acpibtn0 at acpi0: PWRB
cpu0: PowerNow! K8 2513 MHz: speeds: 2500 2400 2200 2000 1800 1000 MHz
pci0 at mainbus0 bus 0
NVIDIA MCP55 Memory rev 0xa1 at pci0 dev 0 function 0 not configured
pcib0 at pci0 dev 1 function 0 NVIDIA MCP55 ISA rev 0xa2
nviic0 at pci0 dev 1 function 1 NVIDIA MCP55 SMBus rev 0xa2
iic0 at nviic0
spdmem0 at iic0 addr 0x50: 1GB DDR2 SDRAM non-parity PC2-5300CL5
spdmem1 at iic0 addr 0x51: 1GB DDR2 SDRAM non-parity PC2-5300CL5
iic1 at nviic0
NVIDIA MCP55 Memory rev 0xa2 at pci0 dev 1 function 2 not configured
ohci0 at pci0 dev 2 function 0 NVIDIA MCP55 USB rev 0xa1: apic 2 int 11,
version 1.0, legacy support
ehci0 at pci0 dev 2 function 1 NVIDIA MCP55 USB rev 0xa2: apic 2 int 15
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 NVIDIA EHCI root hub rev 2.00/1.00 addr 1
pciide0 at pci0 dev 4 function 0 NVIDIA MCP55 IDE rev 0xa1: DMA, channel
0 configured to compatibility, channel 1 configured to compatibility
pciide0: channel 0 ignored (disabled)
pciide0: channel 1 ignored (disabled)
pciide1 at pci0 dev 5 function 0 NVIDIA MCP55 SATA rev 0xa2: DMA
pciide1: using apic 2 int 11 for native-PCI interrupt
wd0 at pciide1 channel 0 drive 0: ST3320620AS
wd0: 16-sector PIO, LBA48, 305244MB, 625140335 sectors
wd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 6
pciide2 at pci0 dev 5 function 1 NVIDIA MCP55 SATA rev 0xa2: DMA
pciide2: using apic 2 int 15 for native-PCI interrupt
atapiscsi0 at pciide2 channel 0 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: TSSTcorp, CD/DVDW SH-S183L, SB01 ATAPI
5/cdrom removable
cd0(pciide2:0:0): using PIO mode 4, Ultra-DMA mode 2
ppb0 at pci0 dev 6 function 0 NVIDIA MCP55 PCI-PCI rev 0xa2
pci1 at ppb0 bus 1
Intel 8255x rev 0x05 at pci1 dev 7 function 0 not configured
TI TSB43AB23 FireWire rev 0x00 at pci1 dev 10 function 0 not configured
azalia0 at pci0 dev 6 function 1 NVIDIA MCP55 HD Audio rev 0xa2: apic 2
int 10
azalia0: codecs: Realtek ALC888
audio0 at azalia0
nfe0 at pci0 dev 8 function 0 NVIDIA MCP55 LAN rev 0xa2: apic 2 int 10,
address 00:16:e6:9d:9c:05
eephy0 at nfe0 phy 1: 88E1116 Gigabit PHY, rev. 1
ppb1 at pci0 dev 15 function 0 NVIDIA MCP55 PCIE rev 0xa2
pci2 at ppb1 bus 2
vga1 at pci2 dev 0 function 0 ATI Radeon HD 4350 rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
radeondrm0 at vga1: apic 2 int 15
drm0 at radeondrm0
azalia1 at pci2 dev 0 function 1 ATI Radeon HD 4000 HD Audio rev 0x00:
apic 2 int 11
azalia1: no supported codecs
pchb0 at pci0 dev 24 function 0 AMD AMD64 0Fh HyperTransport rev 0x00
pchb1 at pci0 dev 

Re: Crash with uvm_fault after upgrade to latest snapshot

[Martijn Rijkeboer]

Hi Otto,

 dmesg from an older kernel that does work :)
 Or boot with -c, and disable fxp
Thanks, that worked.

Kind regards,


Martijn Rijkeboer

Crash with uvm_fault after upgrade to latest snapshot

[Martijn Rijkeboer]

Hi,

After upgrading my AMD64-current installation to the latest snapshot it
crashes on boot with an uvm_fault.

Message:

  starting network
  uvm_fault(0xfe807f4032a0, 0x0, 0, 1) - e
  kernel: page fault trap, code=0
  stopped atfxp_load_ucode+0x8a:movzwl0x2(%rbx),eax
  ddb{0}


Kernel:

  OpenBSD 5.1-current (GENERIC.MP) #248: Wed Mar 28 21:46:36 MDT 2012


The system also crashes when I boot the GENERIC (non MP) kernel with the
same message, but only a different memory address. Any suggestions?

Kind regards,


Martijn Rijkeboer

Re: Crash with uvm_fault after upgrade to latest snapshot

[Martijn Rijkeboer]

Hi Ariane,

 Please supply a trace, dmesg and the output of ps (on ddb, type
 'trace' for the trace, and 'ps' for the ps output.

 The uvm_fault is a null-pointer exception.  We need the trace and ps to
 diagnose where the fault occured.

Below are the trace and the ps. I've typed them, because I couldn't copy
and paste them. How do I get a dmesg if I can't start the machine? Boot
from an installation CD?

ddb{0} trace
fxp_load_ucode() at fxp_load_ucode+0x8a
fxp_init() at fxp_init+0x9b
fxp_ioctl() at fxp_ioctl+0xeb
in6_addmulti() at in6_addmulti+0x1ed
in6_joingroup() at in6_joingroup+0x4e
in6_update_ifa() at in6_update_ifa+0x5c1
in6_ifattach_linklocal() at in6_ifattach_linklocal+0x113
in6_ifattach() at in6_ifattach+0x104
in6_if_up() at in6_if_up+0x15
if_up() at if_up+0x78
ifioctl() at ifioctl+0xb98
sys_ioctl() at sys_ioctl+0x146
syscall() at syscall+0x248
--- syscall (number 54) ---
end trace frame: 0x0, count: -13
acpi_pdirpa+0x405402:

ddb{0} ps
   PIDPPIDPGRP UID   S   FLAGS   WAITCOMMAND
*2039973277327   0   7   0   dhclient
  7327   17327   0   30x88   pause   sh
14   0   0   0   30x100200   aiodonedaiodoned
13   0   0   0   30x100200   syncer  update
12   0   0   0   30x100200   cleaner cleaner
11   0   0   0   30x100200   reaper  reaper
10   0   0   0   30x100200   pgdaemonpagedaemon
 9   0   0   0   30x100200   bored   crypto
 8   0   0   0   30x100200   pftmpfpurge
 7   0   0   0   30x100200   usbtsk  usbtask
 6   0   0   0   30x100200   usbatsk usbatsk
 5   0   0   0   30x100200   acpi0   acpi0
 4   0   0   0   7  0x40100200   idle1
 3   0   0   0   30x100200   bored   syswq
 2   0   0   0   3  0x40100200   idle0
 1   0   1   0   30x80   waitinit
 0  -1   0   0   3   0x200   scheduler   swapper


Kind regards,


Martijn Rijkeboer