Re: Alix 2d13 and OpenBSD 6.5 Problems
Hi Sean
Maybe plug in a spare USB drive and format it for swap? Swap on CF is
rarely a good idea, especially if you swap often.
On Thu, Oct 3, 2019 at 2:01 PM Sean Kamath wrote:
>
> Just wanted to say a thank you for everyone’s comments. I’ve combined all my
> replies into one mostly to sum everything up.
>
> > On Oct 2, 2019, at 02:16, Stefan Sperling wrote:
> > Try adding swap space.
> > I have added 2GB of swap space on my alix and it has been running fine ever
> > since.
>
> My “disk” is 2GB. I don’t even have any X sets loaded as they won’t fit.
>
> > On Oct 2, 2019, at 09:03, Olivier Cherrier wrote:
> > On mine (only 32 MB of swap), I had to disable kernel relinking.
> > Otherwise, the system more or less collapses at boot time.
>
>
> Yeah, I believe I only have 32MB of swap (I chose the default disk layout oh
> so long ago).
>
>
> > On Oct 2, 2019, at 08:34, Joe Barnett wrote:
> > I cannot comment on the upgrade process, but I have had zero fatal issues
> > running 6.5 on my alix2d13 boards. That said, memory has been getting
> > tighter with more recent OpenBSD versions, and swap (as someone else
> > suggested) should help. I love these reliable boards, but they are
> > starting to show their age (at least relative to how I use them with
> > OpenBSD).
>
> Yeah, so I’m wondering if I want to get a larger CompactFlash card and
> reinstall, try and be clever and go off the reservation, or just pack in the
> 9 of these things I have and get an APU.
>
> > On Oct 2, 2019, at 09:15, Stuart Henderson wrote:
> > After boot, the kernel is relinked in a random order in the background
> > ("/usr/libexec/reorder_kernel &" in /etc/rc).
>
> Yes, I’m familiar with why it’s done. I was mostly wondering if I broke
> something because I’ve not had this problem since I got these things (I don’t
> even know how long ago), and 6.5 just killed it.
>
> > Unfortunately the Alix doesn't have much RAM and if you have pretty
> > much anything other than a minimal set of daemons running it won't
> > cope well.
>
> I’m running nsd and unbound. I can turn off smtpd. . . What I would be nice
> to do is delay starting daemons until relinking is done. Regardless, I think
> I have my answer about why it’s falling over.
>
> > You can disable the reordering by removing /var/db/kernel.SHA256
> > but be aware that syspatch relies on the reorder_kernel mechanism in
> > order to apply kernel patches.
>
> Good to know. I’m going to do everything I can to avoid turning off
> relinking, because I want to go on the big boy rides! :-)
>
> Sean
>
--
Aaron Mason - Programmer, open source addict
I've taken my software vows - for beta or for worse
Re: Alix 2d13 and OpenBSD 6.5 Problems
Just wanted to say a thank you for everyone’s comments. I’ve combined all my
replies into one mostly to sum everything up.
> On Oct 2, 2019, at 02:16, Stefan Sperling wrote:
> Try adding swap space.
> I have added 2GB of swap space on my alix and it has been running fine ever
> since.
My “disk” is 2GB. I don’t even have any X sets loaded as they won’t fit.
> On Oct 2, 2019, at 09:03, Olivier Cherrier wrote:
> On mine (only 32 MB of swap), I had to disable kernel relinking.
> Otherwise, the system more or less collapses at boot time.
Yeah, I believe I only have 32MB of swap (I chose the default disk layout oh so
long ago).
> On Oct 2, 2019, at 08:34, Joe Barnett wrote:
> I cannot comment on the upgrade process, but I have had zero fatal issues
> running 6.5 on my alix2d13 boards. That said, memory has been getting
> tighter with more recent OpenBSD versions, and swap (as someone else
> suggested) should help. I love these reliable boards, but they are starting
> to show their age (at least relative to how I use them with OpenBSD).
Yeah, so I’m wondering if I want to get a larger CompactFlash card and
reinstall, try and be clever and go off the reservation, or just pack in the 9
of these things I have and get an APU.
> On Oct 2, 2019, at 09:15, Stuart Henderson wrote:
> After boot, the kernel is relinked in a random order in the background
> ("/usr/libexec/reorder_kernel &" in /etc/rc).
Yes, I’m familiar with why it’s done. I was mostly wondering if I broke
something because I’ve not had this problem since I got these things (I don’t
even know how long ago), and 6.5 just killed it.
> Unfortunately the Alix doesn't have much RAM and if you have pretty
> much anything other than a minimal set of daemons running it won't
> cope well.
I’m running nsd and unbound. I can turn off smtpd. . . What I would be nice to
do is delay starting daemons until relinking is done. Regardless, I think I
have my answer about why it’s falling over.
> You can disable the reordering by removing /var/db/kernel.SHA256
> but be aware that syspatch relies on the reorder_kernel mechanism in
> order to apply kernel patches.
Good to know. I’m going to do everything I can to avoid turning off relinking,
because I want to go on the big boy rides! :-)
Sean
Re: New Group for BSD
On Wed, Oct 02, 2019 at 03:42:41PM +0200, Mariusz Zaborski wrote: > 0 > C Poland > P Mazovian > T Warsaw > F Last Thursday each month at 6pm > O Polish BSD User Group > I Mariusz Zaborski > M osho...@freebsd.org > U https://bsd-pl.org/ > N *BSD Added, thanks!
Re: Alix 2d13 and OpenBSD 6.5 Problems
On 2019-10-02, Sean Kamath wrote:
> Hi.
>
> I’m hoping someone either has a cluebat or some helpful suggestions beyond
> “reinstall”.
>
> I had an alix 2d13 running OpenBSD 6.3. I finally got around to upgrading to
> 6.4 (via https://www.openbsd.org/faq/upgrade64.html), and that seemed to go
> just fine (I used the Upgrading Manually section, since I don’t have (easy)
> access to the console).
>
> I let that run for a day, just to make sure all was well, and then attempted
> an upgrade to 6.5 (via https://www.openbsd.org/faq/upgrade65.html), again
> using the “Upgrading Manually” section.
>
> This time, between smtpd and relinking the kernel, it appears my Alix board
> is quickly running out of memory. Within a few seconds the sr rate is in the
> 20K range. I stopped the ld for relinking, and killed SMTPD in order to
> finish the install (the makedev ALL, sysmerge, pkg_update -u bits), and that
> all ran fine. But about 15-20 minutes after a reboot, the box just goes off
> the network, and there’s not much I can do.
>
> I can download and reinstall 6.5, but was hoping to avoid that pain, but I
> just want to make sure 6.5 has no issues on the Alix boards. . .
>
> Thanks! I’d attach dmesg, but the box is dead again. . . If anyone wants to
> dive into what’s going on, just let me know what info you want to see.
>
> Sean
>
>
After boot, the kernel is relinked in a random order in the background
("/usr/libexec/reorder_kernel &" in /etc/rc). This is done so that
there will be a different memory layout on different boots, making
it harder to carry out types of attack that rely on knowing where
things are in the kernel.
Unfortunately the Alix doesn't have much RAM and if you have pretty
much anything other than a minimal set of daemons running it won't
cope well.
You can disable the reordering by removing /var/db/kernel.SHA256
but be aware that syspatch relies on the reorder_kernel mechanism in
order to apply kernel patches. So if you do this and need to apply
such patches, re-enable it temporarily before running syspatch:
"sha256 -h /var/db/kernel.SHA256 /bsd" - stop any unnecessary
processes - then run syspatch. After syspatch has finished
you can remove kernel.SHA256 again before rebooting.
Re: Alix 2d13 and OpenBSD 6.5 Problems
Olivier Cherrier wrote: > On Wed, Oct 02, 2019 at 11:16:21AM +0200, s...@stsp.name wrote: > > Try adding swap space. > > I have added 2GB of swap space on my alix and it has been running fine ever > > since. > > On mine (only 32 MB of swap), I had to disable kernel relinking. > Otherwise, the system more or less collapses at boot time. You must be at least this tall to go onto the big boy rides.
Re: Alix 2d13 and OpenBSD 6.5 Problems
On Wed, Oct 02, 2019 at 11:16:21AM +0200, s...@stsp.name wrote: > Try adding swap space. > I have added 2GB of swap space on my alix and it has been running fine ever > since. On mine (only 32 MB of swap), I had to disable kernel relinking. Otherwise, the system more or less collapses at boot time. -- Olivier Cherrier mailto:o...@symacx.com
Re: Alix 2d13 and OpenBSD 6.5 Problems
On 2019-10-01 22:46, Sean Kamath wrote: Hi. I’m hoping someone either has a cluebat or some helpful suggestions beyond “reinstall”. I had an alix 2d13 running OpenBSD 6.3. I finally got around to upgrading to 6.4 (via https://www.openbsd.org/faq/upgrade64.html), and that seemed to go just fine (I used the Upgrading Manually section, since I don’t have (easy) access to the console). I let that run for a day, just to make sure all was well, and then attempted an upgrade to 6.5 (via https://www.openbsd.org/faq/upgrade65.html), again using the “Upgrading Manually” section. This time, between smtpd and relinking the kernel, it appears my Alix board is quickly running out of memory. Within a few seconds the sr rate is in the 20K range. I stopped the ld for relinking, and killed SMTPD in order to finish the install (the makedev ALL, sysmerge, pkg_update -u bits), and that all ran fine. But about 15-20 minutes after a reboot, the box just goes off the network, and there’s not much I can do. I can download and reinstall 6.5, but was hoping to avoid that pain, but I just want to make sure 6.5 has no issues on the Alix boards. . . I cannot comment on the upgrade process, but I have had zero fatal issues running 6.5 on my alix2d13 boards. That said, memory has been getting tighter with more recent OpenBSD versions, and swap (as someone else suggested) should help. I love these reliable boards, but they are starting to show their age (at least relative to how I use them with OpenBSD). Thanks! I’d attach dmesg, but the box is dead again. . . If anyone wants to dive into what’s going on, just let me know what info you want to see. Sean
New Group for BSD
0 C Poland P Mazovian T Warsaw F Last Thursday each month at 6pm O Polish BSD User Group I Mariusz Zaborski M osho...@freebsd.org U https://bsd-pl.org/ N *BSD -- Mariusz Zaborski oshogbo//vx | http://oshogbo.vexillium.org FreeBSD committer | https://freebsd.org Software developer | http://wheelsystems.com If it's not broken, let's fix it till it is!!1 signature.asc Description: PGP signature
Multi media keys on wired USB keyboard not responding
Hi, I am unable to get the four multimedia keys (Play/Pause, Volume Decrement/Increment, Mute) on my old'ish USB Microsoft Wired Keyboard 600 to respond. I have tried to do my homework by reading man pages, like usbhidaction(1) and usbhidctl(1), and I've been looking at how-tos on the net [1], but to no prevail and I've decided to reach out to misc@ for guidance. dmesg(1) below [2]. This is what I have tried: 1. Identifying key strokes: $ usbhidctl -l -f /dev/uhid0 Consumer_Control.Play/Pause=1 Consumer_Control.No_Event=1 Consumer_Control.0xfe03=0 Consumer_Control.0xfe04=0 Consumer_Control.0xff05=0 Consumer_Control.0xff02=0 Consumer_Control.Unassigned=1 Consumer_Control.No_Event=1 Consumer_Control.0xfe03=0 Consumer_Control.0xfe04=0 Consumer_Control.0xff05=0 Consumer_Control.0xff02=0 [...identical output (except for name) for the other four keys...] 2. usbhidaction(1) configuration file: $ cat ~/.usbhidaction.conf Consumer:Play/Pause 1 mixerctl outputs.master.mute=toggle Consumer:Volume_Decrement 1 mixerctl outputs.master=-8 Consumer:Volume_Increment 1 mixerctl outputs.master=+8 Consumer:Mute 1 mixerctl outputs.master.mute=toggle 3. Executing usbhidaction during xsession or from xterm.. $ usbhidaction -c ~/.usbhidaction.conf -f /dev/uhid0 ..exits without errors but keys are not responding. Bwt: - I used to have a PS/2 keyboard with multi media keys and it was working well with the machine in question. - The current USB keyboard is tested and fully functional on another machine running Windows 7. - None of the multi media keys gets detected by xev(1). Regards, Erling --- [1] https://www.bsdhowto.ch/extrakeys.html [2] $ dmesg OpenBSD 6.6-beta (GENERIC.MP) #314: Mon Sep 16 19:13:24 MDT 2019 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 12867665920 (12271MB) avail mem = 12464992256 (11887MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xfcdf0 (57 entries) bios0: vendor American Megatrends Inc. version "V1.15" date 03/04/2011 bios0: MICRO-STAR INTERNATIONAL CO.,LTD MS-7599 acpi0 at bios0: ACPI 1.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC MCFG OEMB SRAT HPET SSDT acpi0: wakeup devices PCE2(S4) PCE3(S4) PCE4(S4) PCE5(S4) PCE6(S4) PCE7(S4) PCE9(S4) PCEA(S4) PCEB(S4) PCEC(S4) SBAZ(S4) P0PC(S4) UHC1(S4) UHC2(S4) UHC3(S4) USB4(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Athlon(tm) II X4 635 Processor, 2907.73 MHz, 10-05-03 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,MWAIT,CX16,POPCNT,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,ITSC 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, 16 4MB entries fully associative cpu0: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative cpu0: AMD erratum 721 detected and fixed tsc_timecounter_init: TSC skew=0 observed drift=0 cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 200MHz cpu0: mwait min=64, max=64, IBE cpu1 at mainbus0: apid 1 (application processor) TSC skew=3 cpu1: AMD Athlon(tm) II X4 635 Processor, 2907.34 MHz, 10-05-03 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,MWAIT,CX16,POPCNT,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,ITSC 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, 16 4MB entries fully associative cpu1: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative cpu1: AMD erratum 721 detected and fixed tsc_timecounter_init: TSC skew=3 observed drift=0 cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 2 (application processor) TSC skew=4 cpu2: AMD Athlon(tm) II X4 635 Processor, 2907.34 MHz, 10-05-03 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,MWAIT,CX16,POPCNT,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,ITSC cpu2: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache cpu2: ITLB 32 4KB entries fully associative, 16 4MB entries fully associative cpu2: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative cpu2: AMD erratum 721 detected and fixed tsc_timecounter_init: TSC skew=4 observed drift=0 cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 3 (application processor) TSC skew=-18 cpu3: AMD
Re: Alix 2d13 and OpenBSD 6.5 Problems
On Tue, Oct 01, 2019 at 10:46:50PM -0700, Sean Kamath wrote: > Hi. > > I’m hoping someone either has a cluebat or some helpful suggestions beyond > “reinstall”. Try adding swap space. I have added 2GB of swap space on my alix and it has been running fine ever since. I avoided a reinstall by repurposing unused /usr/src and /usr/obj partitions. Snippet from /etc/fstab: #/dev/wd0i /usr/src ffs rw,nodev,nosuid,softdep 1 2 #/dev/wd0j /usr/obj ffs rw,nodev,nosuid,softdep 1 2 /dev/wd0i none swap sw 0 0 /dev/wd0j none swap sw 0 0
OpenBSD 6.6 snapsot and samba's net utility
Hi! net ads is coredumped on last snapshot ORLOV-NB:~$doas net ads testjoin doas (dmitriy.o@ORLOV-NB.sharifa.local) password: net(39600) in free(): bogus pointer (double free?) 0x Abort trap (core dumped) ORLOV-NB:~$ ORLOV-NB:~$uname -a OpenBSD ORLOV-NB.sharifa.local 6.6 GENERIC.MP#342 amd64 Information for inst:samba-4.8.12p1 Comment: SMB and CIFS client and server for UNIX Required by: gvfs-smb-1.40.2 Description: The Samba suite is a set of programs that implement a server for the Windows file- and printer-sharing protocols (SMB/CIFS) and Active Directory compatible Domain Controller. Maintainer: Ian McWilliam , Jeremie Courreges-Anglas < j...@wxcvbn.org> WWW: https://www.samba.org/ Size: 89560080 Signature: samba-4.8.12p1,5,@avahi-0.7p6,@cups-libs-2.3.0,@gamin-0.1.10p24,@gettext-runtime-0.20.1p0,@gnutls-3.6.10,@jansson-2.12,@ldb-1.3.8p0,@libexecinfo-0.3p2v0,@libiconv-1.16p0,@libtalloc-2.1.14,@openldap-client-2.4.48,@openpam-20141014,@popt-1.16p2,@py-dnspython-1.16.0p2,@samba-util-4.8.12,@tdb-1.3.16p0,avahi-client.0.1,avahi-common.0.1,c.95.1,crypto.45.5,cups.7.1,curses.14.0,dbus-1.11.2,execinfo.2.0,fam.1.0,gnutls.46.3,iconv.7.0,intl.6.0,jansson.3.2,lber.12.0,ldap.13.1,ldb.0.8,lib/samba/replace.8.0,lib/samba/util-setid.8.0,m.10.1,pam.5.0,popt.1.0,pthread.26.1,pyldb-util.0.5,pytalloc-util.0.1,python2.7.0.0,readline.4.0,talloc.1.1,tdb.4.3,tevent.0.4,util.13.1,z.5.0 Packing-list: @comment $OpenBSD: PLIST-main,v 1.49 2019/04/12 18:21:17 jca Exp $ @name samba-4.8.12p1 @url http://fastly.cdn.openbsd.org/pub/OpenBSD/snapshots/packages/amd64/samba-4.8.12p1.tgz @version 5 @signer openbsd-66-pkg @digital-signature signify2:2019-10-01T15:30:22Z:external @option manual-installation .. @bin bin/net @sha YF3RPWSyqKMAHnTkHM7Bk9ERUjlVomH7GO5o4DdZlo4= @size 971064 @ts 1569880968 -- Dmitry Orlov
Alix 2d13 and OpenBSD 6.5 Problems
Hi. I’m hoping someone either has a cluebat or some helpful suggestions beyond “reinstall”. I had an alix 2d13 running OpenBSD 6.3. I finally got around to upgrading to 6.4 (via https://www.openbsd.org/faq/upgrade64.html), and that seemed to go just fine (I used the Upgrading Manually section, since I don’t have (easy) access to the console). I let that run for a day, just to make sure all was well, and then attempted an upgrade to 6.5 (via https://www.openbsd.org/faq/upgrade65.html), again using the “Upgrading Manually” section. This time, between smtpd and relinking the kernel, it appears my Alix board is quickly running out of memory. Within a few seconds the sr rate is in the 20K range. I stopped the ld for relinking, and killed SMTPD in order to finish the install (the makedev ALL, sysmerge, pkg_update -u bits), and that all ran fine. But about 15-20 minutes after a reboot, the box just goes off the network, and there’s not much I can do. I can download and reinstall 6.5, but was hoping to avoid that pain, but I just want to make sure 6.5 has no issues on the Alix boards. . . Thanks! I’d attach dmesg, but the box is dead again. . . If anyone wants to dive into what’s going on, just let me know what info you want to see. Sean
