Quote:
Originally Posted by jggimi
I notice you are running your own GENERIC.MP kernel. Do you have any kernel configuration changes from the default GENERIC?
|
I used Mtiers openup tool to update against security holes.
I don't know why they patched the kernel as no security advisories has been made by OpenBSD.
I didn't update my crapbook wich suffers the same problem though with its 5.4 GENERIC#37 i386 kernel.
Now, I am getting IP conflict as my Internet box decided to give its own Internet adress to any other device instead of a local adress from class C !
A box reboot later, my computer is getting 192.168.0.x.x adress again... And reacts correctly. But I am sure that when it was slow there was no IP conflict at this time.
looking at /var/log/messages I found these memory errors :
Code:
# grep conflict messages
Nov 10 23:04:47 LNBoX /bsd: 0:0:0: mem address conflict 0xe0000000/0x20000000
Nov 10 23:13:41 LNBoX /bsd: 0:0:0: mem address conflict 0xe0000000/0x20000000
Nov 10 23:29:39 LNBoX /bsd: 0:0:0: mem address conflict 0xe0000000/0x20000000
Nov 11 00:01:20 LNBoX /bsd: 0:0:0: mem address conflict 0xe0000000/0x20000000
But again, my netbook reacts the same suglish way and without theses errors and this happened as soon as I plugged the ethernet cable.
To me, it looks like the problem comes from the Internet box, and for some reason, it affects OpenBSD and not FreeBSD