Re: The case of the phantom reboot

2021-03-28 Thread Kristjan Komloši

On 3/27/21 10:27 PM, David Newman wrote:

OpenBSD 6.8 GENERIC#5 i386

One of my systems rebooted at 03:01 local time today. I've seen kernel
panics and bad hardware but I've never seen OpenBSD "just reboot" by
itself, ever.

There's no cron job that would do this. last(1) is no help; it shows the
reboot command but not the shutdown that preceded it:

root@ns ~ 4# last -f /var/log/wtmp.0
reboot~ Sat Mar 27 03:01
root  ttyp0192.168.0.132Wed Mar 24 11:23 - 11:23
(00:00)

wtmp.0 begins Wed Mar 24 11:23 2021
root@ns ~ 5# last -f /var/log/wtmp.1
root  ttyp0192.168.0.132Tue Mar 16 21:30 - 21:30
(00:00)
root  ttyp075.82.86.131 Tue Mar 16 13:14 - 21:30
(08:15)
root  ttyp075.82.86.131 Sun Mar 14 21:20 - 21:29
(00:08)
root  ttyp075.82.86.131 Sat Mar 13 17:42 - 21:13
(03:31)

The date gaps seem odd. I've ssh'd into this system multiple times
between March 16-27. I don't see other signs of trouble in /var/log.

I could use some help in looking for evidence of foul play, or "just" a
hardware or software problem.

Thanks in advance for further troubleshooting clues.

dn

What kind of a machine is it running on? I remember having reboot 
problems on certain HP and Supermicro servers with hardware watchdogs.


--
Kristjan Komloši



Re: Resurrecting the Dead

2021-03-23 Thread Kristjan Komloši

Hi,
thanks for the insightful article, I also really liked the VRF OpenVPN 
guide, I'll try to implement it with my VPN provider some day...

I think you've got some really good content going on on your blog.

Best regards
Kristjan Komlosi

On 3/21/21 6:34 PM, Lari Huttunen wrote:

All,

I wrote a short blog post on how to deal with dead OpenVPN tunnels.
This may be an issue you have encountered as well, when
connecting to a commercial VPN provider's servers on more or less
permanent basis.

The blunt instrument is detailed here:

https://www.huttu.net/posts/openvpn-client-stability/

I would be interested in hearing about other more elegant solutions
as well. :)

Best regards,

Lari Huttunen





Re: news from my (probably not) hacked box

2020-04-02 Thread Kristjan Komloši
Thanks for catching that! Apparently I forgot how pf works... It really is
getting late :/

On Thu, Apr 2, 2020, 23:22 jeanfrancois  wrote:

> It used to be this pf.conf would work (possibly not on latest version):
>
>  block in all
>  pass out all keep state
>
> Pass out keeps states from pass in is not required. Packet filter is
> stateful and gracefully lets expected packets come trough when
> they match a connection initiated.
>
> Jean-François
>
> Le 02/04/2020 à 22:26, Kristjan Komlosi a écrit :
> > [...] but aren't there supposed to be some rules that pass
> > traffic inbound to your interface?
>
>


Re: UEFI Issue

2019-07-19 Thread Kristjan Komloši
On Tue, 2019-07-16 at 18:32 +, Charlie Burnett wrote:
> Hey, I'm looking to get OpenBSD working in UEFI only mode on newer
> Thinkpad
> X1 devices, because for whatever reason it hangs when loading into
> memory
> without CSM enabled, and some of the X1 devices no longer have a CSM
> option. Does anyone have a fix, or advice on where I would start
> looking if
> I was going to patch it myself?
New Lenovo laptops are getting kinda infamous for their comically bad
UEFI implementations. They hardly boot anything but Windows. You may be
on a blind path there.

Try disabling secure boot if you haven't done so already, and try
chainloading OpenBSD through a boot manager like rEFInd (I've been
booting OpenBSD with it for a long time, albeit with CSM support).

-- 
Kristjan Komloši
Mail: kristjan.koml...@gmail.com
Tel:  +386 31 679 339



Re: Qemu Agent assistance needed

2019-04-28 Thread Kristjan Komloši
On Sun, 2019-04-28 at 11:10 +, Strahil Nikolov wrote:
> Hi All,
> I am new to openBSD and I really like the idea. Sadly I do not have
> suitable hardware to run on , thus I use KVM and I would be happy if
> anyone hint me of a working solution for Qemu Guest Agent.
> Anything I dig up (via google searches) show up only suggestions ,
> but nothing more.In openBSD 6.4  I successfully installed qemu (and
> thus the agent), but I can't understand how to get the device needed
> for communication with the host up and running.
> As I mainly know linux - I know that we need a kernel module that to
> be loaded and with combination of udev rules - the devices is created
> on the necessary location and with the correct rights.According to
> many google findings - openBSD doesn't support any more loadable
> kernel module support.
> I have tried to figure it out by myself, but I cannot find the
> necessary module needed, nor how to load it in a proper manner.
> Any hint is well appreciated.
> Best Regards,Strahil Nikolov  

Kernel modules don't exist under OpenBSD to ensure security, so don't
go there. Communication with host is probably best done through the
serial console. Take a look at the boot.conf(8) manpage.



Re: Common Lisp and OpenBSD

2018-11-25 Thread Kristjan Komloši
On Sun, 2018-11-25 at 05:17 -0500, Programmer wrote:
> There don't seem to be any Common Lisp libraries available as
> packages.  I'd be interested in packaging the most common and mature
> Common Lisp libraries, but I'm not certain who I'd discuss this with.
> 
> I'd appreciate any help with getting started contributing to OpenBSD.
> 
I found a guide at https://www.openbsd.org/faq/ports/. There is also a
ports mailing list.
-- 
Kristjan Komloši
--
Dobite me lahko preko/you can contact me through:
Mail (šola/school): kristjan.koml...@sg.sckr.si
Mail (privat/private): kristjan.koml...@gmail.com
Tel: +386 31 679 339 (po 14. uri / after 14:00)



uvm_fault on HP T5740

2018-11-12 Thread Kristjan Komloši
Hello,
I've recently performed an install of i386 OpenBSD 6.4 on a HP T5740
thin client (Atom N280, 2GB DDR3, 2GB FLASH, more info on 
parkytowers.me.uk) and I keep running into uvm_fault errors at xenodm
startup when booting. At this point the whole computer freeyes, even
ddb prompt appearing after the error message doesn't work. Single user
boots fine, and doesn't produce any errors whatsoever. I have attached
the single mode dmesg, the disklabel output (I use the install
defaults), and pcidump output with this email.

When booting without any options at boot> prompt, the machine boots
normally until it starts xenodm, at which point the screen flashes
black, as expected at xenodm startup, but then goes back to console,
presenting the following error message:
uvm_fault(0x0d0d55bf0, 0xd2eaf000, 0, 2) -> e
kernel: page fault trap, code=0
Stopped at uvm_pmr_get1page+0x35d: movl %ecx, 0(%edi,%eax,1)
ddb{1}>

When booting bsd.sp kernel, results are very inconclusive. Most often
it results in the same crash as bsd.mp, but in very rare cases it also
crashes at kernel relink time. This didn't want to happen the many
times I have restarted the machine on purpose to trigger the relink, if
anyone can help me force the relink on the bsd.sp kernel, please let me
know. When it reaches the xenodm startup, it fails at the same assembly
line as the bsd.mp kernel.

I have also tested these machines with Alpine Linux, which runs very
stable (I use one of them as my home WiFi access point), so I don't
believe that the machine itself is faulty.

What would be the next step at solving this problem?

-- 
Thanks in advance
Kristjan Komloši
--
Dobite me lahko preko/you can contact me through:
Mail (šola/school): kristjan.koml...@sg.sckr.si
Mail (privat/private): kristjan.koml...@gmail.com
Tel: +386 31 679 339 (po 14. uri / after 14:00 CEST)
# /dev/rwd0c:
type: ESDI
disk: ESDI/IDE disk
label: 2GB ATA Flash Di
duid: 367182f625b2c5e3
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 64
sectors/cylinder: 4032
cylinders: 992
total sectors: 4000752 # total bytes: 1953.5M
boundstart: 64
boundend: 3999744
drivedata: 0 

16 partitions:
#size   offset  fstype [fsize bsize   cpg]
  a:  1889.3M   64  4.2BSD   2048 16384 12958 # /
  b:63.6M  3869440swap# none
  c:  1953.5M0  unused
OpenBSD 6.4 (GENERIC.MP) #943: Thu Oct 11 13:51:32 MDT 2018
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
real mem  = 2076327936 (1980MB)
avail mem = 2023350272 (1929MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: date 11/12/09, BIOS32 rev. 0 @ 0xf0010, SMBIOS rev. 2.6 @ 
0xfd070 (43 entries)
bios0: vendor American Megatrends Inc. version "786R8 v1.01" date 11/12/2009
bios0: Hewlett-Packard hp t5740
acpi0 at bios0: rev 0
acpi0: sleep states S0 S5
acpi0: tables DSDT FACP APIC MCFG OEMB GSCI SSDT
acpi0: wakeup devices P0P2(S0) P0P1(S0) USB0(S0) USB1(S0) USB2(S0) USB5(S0) 
EUSB(S0) USB3(S0) USB4(S0) USB6(S0) USBE(S0) P0P4(S0) P0P5(S0) P0P6(S0) 
P0P7(S0) P0P8(S0) [...]
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) Atom(TM) CPU N280 @ 1.66GHz ("GenuineIntel" 686-class) 1.67 GHz, 
06-1c-02
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,xTPR,PDCM,MOVBE,NXE,LAHF,PERF,SENSOR,MELTDOWN
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 166MHz
cpu0: mwait min=64, max=64, C-substates=0.2.2.0.2, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Atom(TM) CPU N280 @ 1.66GHz ("GenuineIntel" 686-class) 1.67 GHz, 
06-1c-02
cpu1: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,xTPR,PDCM,MOVBE,NXE,LAHF,PERF,SENSOR,MELTDOWN
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
acpimcfg0 at acpi0
acpimcfg0: addr 0xe000, bus 0-255
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (P0P2)
acpiprt2 at acpi0: bus 1 (P0P1)
acpiprt3 at acpi0: bus 2 (P0P4)
acpiprt4 at acpi0: bus -1 (P0P5)
acpiprt5 at acpi0: bus -1 (P0P6)
acpiprt6 at acpi0: bus -1 (P0P7)
acpiprt7 at acpi0: bus 3 (P0P8)
acpiprt8 at acpi0: bus 4 (P0P9)
acpicpu0 at acpi0: !C2(500@1 mwait.1@0x10), C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: !C2(500@1 mwait.1@0x10), C1(1000@1 mwait.1), PSS
acpicmos0 at acpi0
acpibtn0 at acpi0: PWRB
acpivideo0 at acpi0: GFX0
bios0: ROM list: 0xc/0xfc00! 0xd/0x2000
cpu0: Enhanced SpeedStep 1663 MHz: speeds: 1667, 1333, 1000 MHz
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel GM45 Host" rev 0x09
inteldrm0 at pci0 

Re: Replacing old versions of Android with OpenBSD

2018-10-29 Thread Kristjan Komloši
While the idea seems fantastic upon the first glance, I'm afraid that
OpenBSD's no-blob policy would not be compatible with the humongous amounts
of blobs and proprietary drivers needed to run just about everything on
mobile devices.
Have you already thought of a particular device to do it on?

V V pon., 29. okt. 2018 ob 07:23 je oseba Jyri Hovila [Turvamies.fi] <
jyri.hov...@turvamies.fi> napisala:

> Hi everyone!
>
> There used to be a project called GreenOS, with plans on creating a
> FreeBSD based OS for Android devices:
>
>
> https://www.freebsdnews.com/2012/07/09/greenos-freebsd-based-project-android-devices/
>
> Has anybody here had plans (or tried out?) hacking OpenBSD into some old,
> rootable Android handset?
>
> I'd be interested in setting up a little project around this idea. There's
> no need to worry about any of the 3G/4G stuff at first -- it would be more
> than enough just to see OpenBSD booting on an ex-Android device.
>
> -j.
> --
> +358-404-177133 (24/7)
> jyri.hov...@turvamies.fi
>
>

-- 
Kristjan Komloši


Re: Dell PowerEdge R410 not booting 6.4

2018-10-25 Thread Kristjan Komloši
Does it get to the "entry point at ..." line?

V V čet., 25. okt. 2018 ob 20:02 je oseba diego righi 
napisala:

> did you make only one big a slice?
> try to put the i386 bootloader ;)
>
> On Thu, Oct 25, 2018, 18:20 mabi  wrote:
>
> > Hi,
> >
> > I just installed OpenBSD 6.4 on an older Dell PowerEdge R410 server. The
> > installation went fine but upon reboot I get to the "boot>" prompt then
> the
> > first line of the OpenBSD boot starts with all the numbers displaying but
> > like 2 seconds later the whole server reboots. Any idea what that could
> be?
> >
> > This server is from around 2011 and has two Intel E5620 CPUs. I already
> > tried disabling hyperthreading, booting single user mode (boot -s),
> booting
> > the boot.sp image but so far no luck...
> >
> > Regards,
> > Mabi
> >
> >
> >
> >
> >
> >
>


-- 
Kristjan Komloši