Re: Firmware
Yes.
Re: Power consumption of Pinebook Pro running OpenBSD
On Sat, May 04, 2024 at 05:56:10PM +1000, Brett Mahar wrote: > Hi misc, > > I am getting a Pinebook Pro soon and just wondering how many hours the > battery tends to last from a full charge with OpenBSD? I ran openbsd on my PBP for a while. To answer your question: a lot less than Linux. The lack of hardware accelerated video *anything* on the PBP (unless this has changed in the last couple of releases) will murder your battery life and make videos rather stuttery. This may be at least partially resolved since I last used it (I don't know if mali drivers would be pulled in during a resync of DRM,) but another thing to be aware of with installing OpenBSD is that (again, unless I'm out of date) there's no tty driver. This means you'll have to do the installation with a 3.5mm to serial adapter. The Pine store sells defective ones, but you can take your chances if you like. You can also repair them if you like. From the factory they're specced to put 5v on the PBP which is expecting 3.3v. It probably won't fry your laptop, but it might. I think it's just swapping one resistor in the cable. Just a heads up. I'd be curious if the experience is much better these days, but given how garbage even support for Linux is when Pine nominally "supports" linux on their products, I'm not holding out too much hope. Best of luck, Danny
Re: OT: SSH3 proposal
On Mon, Feb 05, 2024 at 07:26:27AM +, Carlos Lopez wrote: > Hi all, > > https://blog.apnic.net/2024/02/02/towards-ssh3-how-http-3-improves-secure-shells/ > > Uhmm ... ssh over http/3? What do you think about it? > > Best regards, > C. L. Martinez > I'm not an ssh dev but it seems like it'd technically *work*, it's just cursed as all hell.
Re: Appimage
On Tue, Dec 19, 2023 at 10:31:00PM +0200, Mihai Popescu wrote: > > The point of appimage is to work on any Linux distro. > > But it is not working. Like many other ideas created to work on any distro ... > That's a whole other discussion beyond making it work on OpenBSD ;) As I understand it that's because packagers don't understand that you're supposed to include *every* library in your appimage.
Re: Appimage
On Tue, Dec 19, 2023 at 03:50:26PM +, Kevin Chadwick wrote: > I'm not sure if this is a pipe dream but atleast I imagine the filesystem API > and /proc avoidance is likely possible. > > "https://github.com/AppImage/AppImageKit/issues/98"; > The point of appimage is to work on any Linux distro. There's only one OpenBSD. An AppImage written for Linux with the Linux ABI won't run on OpenBSD even if /proc is implemented.
Re: Unable To Use Headset Microphone
On Thu, May 26, 2022 at 07:48:26AM +, dak wrote: > Hi, > > I wrote a blog post similar to your topic. > I'm also explaining the sndiod settings in use. > > Maybe that helps you. > > https://dkrefft.de/external-usb-speakerphone-on-openbsd/ > > BR > dak > Hi, I think that issue is vaguely similar but not quite right. In my case the only device I'm dealing with is azalia because they're wired headphones; sndiod -confirms that there's only an snd0. The issue (as far as I can tell) is that when I plug my headphones in sndio correctly switches the output to use 0/output1 but it doesn't change the input to use 0/input1 (This is just my best guess, I don't know that the subdevices there actually correspond to speakers/internal mic and speaker/mic through 3.5mm.) Thanks for the suggestion, Danny
Unable To Use Headset Microphone
Hey y'all, I had my headset plugged in on my Thinkpad T480 but when I tried recording audio it only ever went through the awful laptop microphone. Poking around in mixerctl I was able to find audio sources for outputs but I wasn't able to select the headset microphone (mic2 I think) as the normal output. I know that it's possible to tell sndio to use a different device but I wasn't able to find anything in the man page about having sndiod set a different "sub-device" as the default for recording. Can anyone point me in the right direction here? I've attached mixerctl, sndioctl, and dmesg output. ---mixerctl--- inputs.dac-2:3=152,152 inputs.dac-0:1=152,152 record.adc-0:1_mute=on [ off on ] record.adc-0:1=152,152 record.adc-2:3_mute=off [ off on ] record.adc-2:3=152,152 record.adc-4:5_mute=off [ off on ] record.adc-4:5=152,152 inputs.mic=85,85 outputs.spkr_source=dac-2:3 [ dac-2:3 ] outputs.spkr_mute=on [ off on ] outputs.spkr_eapd=on [ off on ] inputs.mic2=85,85 outputs.mic2_dir=input-vr80 [ none input input-vr0 input-vr50 input-vr80 input-vr100 ] outputs.hp_source=dac-0:1 [ dac-2:3 dac-0:1 ] outputs.hp_mute=off [ off on ] outputs.hp_boost=off [ off on ] outputs.hp_eapd=on [ off on ] record.adc-4:5_source=mic2 { mic2 } record.adc-2:3_source=mic2,mic { mic2 mic } record.adc-0:1_source=mic [ mic ] outputs.mic2_sense=plugged [ unplugged plugged ] outputs.hp_sense=plugged [ unplugged plugged ] outputs.spkr_muters=hp { hp } outputs.master=153,153 outputs.master.mute=off [ off on ] outputs.master.slaves=dac-2:3,dac-0:1,spkr,hp { dac-2:3 dac-0:1 spkr hp } record.volume=153,153 record.volume.mute=off [ off on ] record.volume.slaves=adc-0:1,adc-2:3,adc-4:5 { adc-0:1 adc-2:3 adc-4:5 mic mic2 } record.enable=sysctl [ off on sysctl ] ---sndioctl input.level=0.600 input.mute=0 output.level=0.600 output.mute=0 server.device=0 app/firefox0.level=1.000 app/firefox1.level=1.000 dmesg OpenBSD 7.1 (GENERIC.MP) #461: Tue Apr 5 12:11:12 MDT 2022 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 38362574848 (36585MB) avail mem = 37182623744 (35460MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x6ecc4000 (63 entries) bios0: vendor LENOVO version "N24ET49W (1.24 )" date 04/19/2019 bios0: LENOVO 20L50054US acpi0 at bios0: ACPI 5.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT SSDT TPM2 UEFI SSDT SSDT HPET APIC MCFG ECDT SSDT SSDT SSDT BOOT BATB SLIC SSDT SSDT SSDT LPIT WSMT SSDT SSDT SSDT DBGP DBG2 MSDM DMAR ASF! FPDT UEFI acpi0: wakeup devices GLAN(S4) XHC_(S3) XDCI(S4) HDAS(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) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 2399 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz, 1591.24 MHz, 06-8e-0a 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,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 24MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz, 1593.31 MHz, 06-8e-0a 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,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz, 1596.28 MHz, 06-8e-0a cpu2: 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,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SME
Re: No firefox on OpenBSD 7.0 i386?
Crystal Kolipe wrote: * https://sourceforge.net/projects/midori-browser/ (as on Raspbian) Midori might be worth looking at as a light-weight browser replacement for Firefox, although I haven't used it for a number of years. Worth nothing that this version of Midori has been abandoned for the better part of a decade by this point. Modern Midori's a web app (https://astian.org/en/midori-browser/) so it's probably not a viable choice for this case.
Re: 6.9/amd64 runaway acpi process on Thinkpad T580
On Wed, Sep 29, 2021 at 06:29:08PM -0700, Mike Larkin wrote: > On Wed, Sep 29, 2021 at 08:44:54PM -0400, David Anthony wrote: > > After enabling "BIOS Thunderbolt Assist", I experience consistent machine > > slowdown on my T480. Previously, I experienced slowdown after power cycling > > my machine occasionally. Currently, with this BIOS setting enabled, I > > experience slowdown consistently. > > > > I am sorry but I don't know enough technically as to discern why. I am > > simply reporting my user experience. I will re-disable the Thunderbolt > > assist for now. > > > > If someone would build an ACPI_DEBUG kernel and show us what GPE is stuck > then we can make forward progress (we need an acpidump of that machine > also). > > Otherwise, its like throwing darts in the dark. > > -ml I could give it a shot. Do you want all three possible states for the dumps? (disabled, working. Disabled, looped acpi0. Enabled, working.) It probably won't be until tomorrow since it's already pretty late, though. Danny
Re: SOLVED Re: 6.9/amd64 runaway acpi process on Thinkpad T580
On Wed, Sep 29, 2021 at 11:47:34AM -0600, Theo de Raadt wrote: > It would be great if someone figures out why "BIOS Thunderbolt Assist" > disable, causes a pin to get stuck on resume, and/or figures out how we > can recognize to handle/clear the event. The detail in my BIOS options specifically mentions it as a Linux workaround. Obviously patches couldn't be imported but I'll poke around to see if there's any discussion/a description of what exactly is happening. Aside from that is there any data I can send y'all? Jonathan's built up a pretty comprehensive set of dmesgs at this point, it seems like. (No need to cc me, I'm on misc@) Danny
Re: 6.9/amd64 runaway acpi process on Thinkpad T580
On Tue, Sep 28, 2021 at 10:08:47PM -0600, Theo de Raadt wrote: > There are a few people who have experience with this. Maybe one of > them will mail you privately. > I'm glad this thread suddenly got revived, since I tried to find it in my backlog but it got lost. All you have to do is go into your bios' settings and turn on "BIOS Thunderbolt Assist" then everything will work 100% fine. Thanks to jcs on IRC for pointing me at that (dunno what his email is.)
Re: 6.9/amd64 runaway acpi process on Thinkpad T580
I dunno if this is helpful, but I just unplugged my thinkpad and triggered the behavior. ACPI shot right up, and in this case the "charging" LED has stayed on. I've never triggered it by unplugging before, but the symptoms are the same. The system was under some load while doing so (watching a video in Firefox and extracting a backup.) The last line in dmesg also seems weird to me; it might be a firmware thing, from that. Danny OpenBSD 7.0 (GENERIC.MP) #224: Mon Sep 20 11:44:33 MDT 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 38362574848 (36585MB) avail mem = 37183885312 (35461MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x6ecc4000 (63 entries) bios0: vendor LENOVO version "N24ET49W (1.24 )" date 04/19/2019 bios0: LENOVO 20L50054US acpi0 at bios0: ACPI 5.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT SSDT TPM2 UEFI SSDT SSDT HPET APIC MCFG ECDT SSDT SSDT SSDT BOOT BATB SLIC SSDT SSDT SSDT LPIT WSMT SSDT SSDT SSDT DBGP DBG2 MSDM DMAR ASF! FPDT UEFI acpi0: wakeup devices GLAN(S4) XHC_(S3) XDCI(S4) HDAS(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) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 2399 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz, 1591.45 MHz, 06-8e-0a 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,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 24MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz, 1596.28 MHz, 06-8e-0a 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,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz, 1596.28 MHz, 06-8e-0a cpu2: 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,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz, 1596.28 MHz, 06-8e-0a cpu3: 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,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 3, package 0 cpu4 at mainbus0: apid 1 (application processor) cpu4: Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz, 1596.28 MHz, 06-8e-0a cpu4: 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,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTR
Re: New desktop CPU/chipset recommendation
On Mon, Sep 20, 2021 at 02:56:31PM -0400, Andre Smagin wrote: > Good day. > > I am looking for a hardware advice. > I don't upgrade my desktop very often - last one was about ten > years ago (AMD FX-8350 CPU), which I recently made my home server > running -current, no issues. Now I am looking for a new desktop that > will last another ten years, hence the question: if I buy the latest > available AMD chipset (X570 I think) and Ryzen 9 CPU - are there any > current issues with using it for OpenBSD desktop? I would like to > overkill it with the choice of hardware now, so I don't have to worry > about it for a while. > > I am ten years out of touch with hardware development progress, so will > appreciate any input you may have. > > -- > Andre > You got me curious, so I went ahead and installed OpenBSD on the desktop I rebuilt this year. I've got a Ryzen R9 3900X with an MSI MAG B550 TOMAHAWK for the motherboard, and an R9 380 for the graphics card. Works totally fine from my initial impressions. Sound works, USB works, plays full HD videos fine over DP, drives the 1440p display with no issues, etc. The only thing "wrong" is that I don't think Audio-over-HDMI works. Hope this might help a bit, Danny
Re: Determining the number of CPU cores and hyperthreads from userspace
Hyperthreads are easy: they've been disabled for years (unless they got flipped on and I didn't notice.)
Re: 6.9/amd64 runaway acpi process on Thinkpad T580
I've ran into this on my T480, it seems most consistently triggered by power cycles caused by running out of battery. The bug's existed for quite a few years (I think I first noticed it in 2019.) If I recall correctly I've posted it to the list a couple of times but I don't think any concrete answers ever emerged; your report is more thorough than mine were though. I do remember that it never happened on my T430, but that's quite the hardware gap.
Re: .profile not being loaded (ksh) when opening shell in X
On Tue, Apr 27, 2021 at 12:17:55PM +, tetrahe...@danwin1210.me wrote: > On Tue, Apr 27, 2021 at 08:04:32AM +0300, Pierre-Philipp Braun wrote: > > I believe there's no need for neither login-shells nor those X-level > > tricks. To load the interactive environment into xterms or screen, I > > usually to define ENV accordingly in /etc/profile or .profile. Not sure > > it's the right way to also put PATH in (k)shrc, but it would also work. > > > > /etc/profile: export ENV=/etc/shrc > > > > or > > > > ~/.profile: export ENV=/root/.shrc > > That's very interesting. Can someone explain what this does? This is incorrect (see upthread.) ENV is for setting what your interactive rc ought to be. You usually point it at ~/.kshrc. If your session hasn't loaded ~/.profile in order to load $ENV then the kshrc won't necessarily be loaded by your shell no matter what. For ~/.profile to be in your environmnt you definitely need to load it in your xsession. Danny
Re: Remote wipe software
On Tue, Apr 27, 2021 at 08:06:46AM -0400, Nick Holland wrote: > # dd if=/dev/random of=/dev/rsdXc bs=1m I don't know Oliver's specific case but it's worth noting that you probably want to check the output of mount rather than hardcoding a value; if you need remote wipes then you probably need full disk encryption and if I remember correctly your device number isn't always guaranteed there. Root is on sd3 for now, it might be on sd2 next boot, etc. I may be misinformed though.
Re: .profile not being loaded (ksh) when opening shell in X
On Mon, Apr 26, 2021 at 11:31:33PM +0200, Jan Vlach wrote: > > Hi, > > you need: > > xterm*loginShell: true > > in ~/.xresources and something like xrdb ~/.Xresources in ~/.xsession > > JV > > On Mon, Apr 26, 2021 at 09:26:19PM +, tetrahe...@danwin1210.me wrote: > > I have some custom additions to my $PATH. They're defined in ~/.profile and > > they are correctly loaded when I log in from a text console. > > > > When I log in to X (cwm) and open a terminal window, $PATH does not contain > > the entries. > > > > I tried `chmod +x` on my .profile but that didn't help. > > > > Both the text console and the X terminal window are using ksh. > > > > When I call `/bin/ksh -l` then the resulting shell contains the correct > > additions to $PATH. > > > > It looks like the custom $PATH is not being passed from the login shell on > > downwards, since ~/.profile is only read by a login shell. > > > > ~/.kshrc is (according to ksh(1)) read by every spawning shell, but I don't > > see any documentation or examples on the Internet where someone defined > > their $PATH in ~/.kshrc ... > > > > What's the correct way to set $PATH and have it stick no matter where and > > when the shell is spawned? > > > Could also just source your profile in your .xsession. That's what I'm in the habit of doing.
Re: Performance Degradation And acpi0 CPU Usage
I think I've found a correlation: it seems like the system gets stuck in some sort of hard power save mode once the battery hits critical, even after plugging the charger in. Has anyone seen this behavior?
Performance Degradation And acpi0 CPU Usage
Hey all, I'm using snapshots on a Thinkpad T480 and I've noticed that I eventually run into performance issues: videos start lagging, the keyboard starts to repeat inputs, programs take several second to respond to clicks or keypresses, etc. It seems to happen eventually, but at rando with no reliable trigger. Not tied into desktop environment and iirc this has happened to me in previous releases as well. One consistent thing is that if I go into systat, the acpi0 process will be using a lot (80%+) of CPU. As far as I know it can't be fixed except for rebooting, and on rare occasions I've run into this behavior being triggered by the time booting is finished and I'm in gdm. Anyone know what might be going on? Danny OpenBSD 6.9-beta (GENERIC.MP) #428: Wed Mar 24 11:12:16 MDT 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 38362574848 (36585MB) avail mem = 37184536576 (35461MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x6ecc4000 (63 entries) bios0: vendor LENOVO version "N24ET49W (1.24 )" date 04/19/2019 bios0: LENOVO 20L50054US acpi0 at bios0: ACPI 5.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT SSDT TPM2 UEFI SSDT SSDT HPET APIC MCFG ECDT SSDT SSDT SSDT BOOT BATB SLIC SSDT SSDT SSDT LPIT WSMT SSDT SSDT SSDT DBGP DBG2 MSDM DMAR ASF! FPDT BGRT UEFI acpi0: wakeup devices GLAN(S4) XHC_(S3) XDCI(S4) HDAS(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) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 2399 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz, 1591.98 MHz, 06-8e-0a 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,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 24MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz, 1596.29 MHz, 06-8e-0a 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,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz, 1596.29 MHz, 06-8e-0a cpu2: 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,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz, 1596.29 MHz, 06-8e-0a cpu3: 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,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 3, package 0 cpu4 at mainbus0: apid 1 (application processor) cpu4: Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz, 1596.28 MHz, 06-8e-0a cpu4: 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
Re: Programmed wakeup from suspend/hibernate
Ian Darwin wrote: I think you forgot to cc misc@, so the OP won't see your reply. On Thu, Dec 24, 2020 at 10:34:19AM -0500, Daniel Wilkins wrote: Ian Darwin wrote: Otherwise a $10 mechanical timer to cut the power (well after the suspend is finished!) and turn it back on in the morning. You'd want to make sure to *hibernate* for that rather than suspend. Almost all motherboards have wake-on-lan these days. You could get a tiny board that consumes no power whose only job is to send a WoL packet to the server for real suspend if that's viable. I did; my bad. Fixing now.
Re: Good GPU for OpenBSD build?
To save you the search for what the hell northern islands is: the best graphics support you'll have is a Kaby Lake processor without a graphics card. Failing that you want a high end Radeon HD6xxx card (Northern Islands.) Skylake processors may be the better option than those, thinking about it: the 6xxx cards are pushing 10 years old now.
Re: suckless st on OpenBSD62
On Sun, Jan 07, 2018 at 05:14:54PM +0100, Frederic Fichter wrote: > Hello all, > > I recently switched one of my machines from Debian to OpenBSD, Still a few > things left to fix (otherwise it would be no fun) and it looks promising. > > I'm running suckless software, I've installed these packages: > dwm-6.1p0 dynamic window manager > st-0.7p1simple X terminal > > My $HOME/.profile has only one line in it: > export ENV=$HOME/.kshrc > > And I set some variables in my $HOME/.kshrc > > Now, everything's cool in xterm (i.e. variables are set) - but that's not the > case in st, when I launch st from dmenu. > If I launch st from xterm, variables are set as well. > > Where should I look for an explanation? > > Thanks much for your help with this. > > Best, > > Fred > Have you restarted X since you set those variables? dmenu inherits dwm's environment which inherits X's environment which inherits the environment that you logged in with.
Re: Kernel memory leaking on Intel CPUs?
On Thu, Jan 04, 2018 at 10:21:12AM -0500, Allan Streib wrote: > "Alceu R. de Freitas Jr." writes: > > > I guess Intel does not give a shit about non-profit groups. Linux got > > this attention because there are a lot of players making money from > > it, players that surely have some sort of partnership with Intel. > > From what I have read in the past 24 hours, the spectre attacks are not > limited to Intel CPUs, but in theory could affect any that use > speculative execution (including, at least, modern ARM designs and AMD > processors). > > My uninformed take on this is that when you allow anyone in the world to > run programs on your systems (i.e. JavaScript in browsers, "cloud" > hosted virtual machines running on shared hardware, etc.) these sorts of > things occasionally happen. No CPUs or software are perfectly secure. > > Allan > >From what I understand, AMD has come out and explicitly said that their architecture isn't and has never been vulnerable, while Intel's said that it affects every processor in the last 20+ years and that it's "not a big deal for most users" because it's only a kernel memory *read*.
Re: Integrating "safe" languages into OpenBSD?
And on top of what Theo said: rewriting stuff in "safe" languages doesn't reduce the need for mitigations *anyway*. Nobody's rewriting all of the ports tree in memory safe languages.
Re: The "like" factor
Something to consider is that there *are* areas where libreoffice is deficient. It's not uncommon for businesses to have a terrifying amount of embedded visual basic and incredibly elaborate excel macros, I wouldn't be surprised if the (possibly theoretical) suit literally can't get their work done because they don't have access to their scripts and macros that some secretary wrote in 1999. Any migration which messes with office, if you want it to be successful you really need a serious period of testing where you grab up as many business-essential documents as you can and identifying scripts and macros which may become problems, then rewriting them in LO compatible way (LO has scripting, it's just not *literally* vbscript). It has a basic dialect so translation shouldn't necessarily be hard, just time consuming.
Re: What is doas doing??
On Wed, Sep 28, 2016 at 02:45:26PM +0200, Murk Fletcher wrote: > Hi, > > Anybody ever been in a similar situation? > > % su > Password: > you are not in group wheel > Sorry > % groups > wheel > % cat /etc/doas.conf > permit nopass keepenv :wheel > > Thanks! > > Murk > You did remember to relog after adding yourself to wheel, right?
Re: Dual booting - can't boot OpenBSD from Windows 10 bootloader
On Fri, Sep 23, 2016 at 09:56:27PM +0200, Karel Gardas wrote: > On Fri, Sep 23, 2016 at 9:50 PM, Fred wrote: > > > > Or run it all on OpenBSD and run Windows and Linux in qemu from ports. > > > > Works for me ;~) > > How is it looking with performance difference of such combo host > versus guest? OP would like to run Xilinx ISE which is CPU/RAM hog > enough even on the fastest machines so running this in Qemu, hmm... > Given that it's software it'd be pretty abysmal. You'd want a Windows or Linux host with the other two in VMs. Personally I just triple boot using LILO for chainloading and it works fine, even with the OpenBSD partition past 128GB. (Sorry about the direct reply Karel, didn't pay attention to the To field.)
Re: donations
That works very differently as far as taxes go. Theo would have to start reporting it as income if Canada works like the US, and things are interesting from there. On Sun, Aug 21, 2016 at 07:36:40AM -0400, Donald Allen wrote: > But isn't it still better to send the money directly to you, since the > Foundation doesn't support you financially? If I understand the different pots > of money correctly, this gives you maximum flexibility to use what you need > for your own support and if there is any excess, you can send it to the > Foundation. > > > > From: dera...@openbsd.org > > To: ed...@pettijohn-web.com > > CC: misc@openbsd.org > > Subject: Re: donations > > Date: Sat, 20 Aug 2016 19:24:10 -0600 > > > > > It was mentioned in another post that sales of the OpenBSD CD's > > > loses money. > > > > The effort expended vs payout received is probably on par with the > > newspaper route I operated at age 16. > > > > I could be doing far better things than making CDs. > > > > For 20 years I really had no other choice. > > > > > Would it be better to make dontations to the foundation? > > > > Absolutely. Look at the results: > > > > http://www.openbsdfoundation.org/activities.html
Re: Randomish Reboots on Current
On Mon, Jun 20, 2016 at 10:19:36AM +0200, Erling Westenvik wrote: > On Sun, Jun 19, 2016 at 07:54:45PM -0700, Philip Guenther wrote: > > On Sun, Jun 19, 2016 at 1:59 PM, Daniel Wilkins > > wrote: > > > Has anyone else been hvaing random reboots on current? The system freezes > > > up for > > > maybe 30 seconds or so, then reboots. I have a hunch that it's something > > > with my > > > wifi card because occasionally during a reboot it'll error saying > > > something about > > > MIC errors and then reboot, or just freeze+reboot during the netstart > > > portion of boot. > > > The other thing that makes me think it's network is that it tends to > > > happen during > > > relatively network heavy things, like when I'm doing ssh X forwarding > > > while watching > > > streaming video, but this isn't always the case. > > > > > > This is a recent thing that just seems to have randomly appeared; it was > > > working > > > fine before and then it started rebooting one day; I hadn't updated the > > > snapshot > > > although I've tried that since to see if it helped. There's no panic so I > > > don't > > > have any ddb info, but I've attached dmesg and dmesg.boot. > > > > Saying "before" without what that *means* leaves us guessing. What > > was the date of the snapshot or build you had installed *before* this > > occurred? Maybe it's still showing in an old /var/log/message.* file? > > And you should probably try upgrading to the newest snapshot released > yesterday (Jun 19). AFAIK there hasn't been a new snapshot since Jun 2, > which is the date in your dmesg(8), and there seems to have been some > commits on iwn(4) on Jun 3. > > -- > Erling Westenvik > I upgraded to the latest snapshot while I was in class and the reboot happened again within 10 minutes of me getting home; guess there was no fix in there. The fact that I was fine all day when away from home has me convinced that it's an issue in the WPA support at least, since the problem doesn't manifest at all on open networks.
Re: Randomish Reboots on Current
Sorry about that, but the issue appeared separate of an upgrade; I just mentioned that I upgraded to point out that the problem wasn't something that's since been fixed. The messages log (attached anyway) coincides with what I said before; it seem to be a behavior that happens when the network runs into a Michael MIC failure. A bit of googling said that it was a problem which occurs on a network when the router thinks that someone's trying to get around the WPA and that the correct behavior is basically that the network is shut down temporarily; not totally sure where the reboot comes in (doesn't handle something right in the driver, I guess? And it hangs the network card.) On Sun, Jun 19, 2016 at 07:54:45PM -0700, Philip Guenther wrote: > On Sun, Jun 19, 2016 at 1:59 PM, Daniel Wilkins wrote: > > Has anyone else been hvaing random reboots on current? The system freezes > > up for > > maybe 30 seconds or so, then reboots. I have a hunch that it's something > > with my > > wifi card because occasionally during a reboot it'll error saying something > > about > > MIC errors and then reboot, or just freeze+reboot during the netstart > > portion of boot. > > The other thing that makes me think it's network is that it tends to happen > > during > > relatively network heavy things, like when I'm doing ssh X forwarding while > > watching > > streaming video, but this isn't always the case. > > > > This is a recent thing that just seems to have randomly appeared; it was > > working > > fine before and then it started rebooting one day; I hadn't updated the > > snapshot > > although I've tried that since to see if it helped. There's no panic so I > > don't > > have any ddb info, but I've attached dmesg and dmesg.boot. > > Saying "before" without what that *means* leaves us guessing. What > was the date of the snapshot or build you had installed *before* this > occurred? Maybe it's still showing in an old /var/log/message.* file? > > > Philip Guenther Jun 17 00:00:01 Hetalia newsyslog[12898]: logfile turned over Jun 17 00:00:01 Hetalia syslogd: restart Jun 17 00:11:07 Hetalia ntpd[52754]: tls connect failed: 2607:f8b0:4003:c03::69 (www.google.com): connect: No route to host Jun 17 00:15:24 Hetalia apmd: battery status: high. external power status: not connected. estimated battery life 60% (122 minutes) Jun 17 00:26:08 Hetalia ntpd[62489]: tls connect failed: 2607:f8b0:4003:c03::69 (www.google.com): connect: No route to host Jun 17 00:35:25 Hetalia apmd: battery status: low. external power status: not connected. estimated battery life 50% (103 minutes) Jun 17 00:41:08 Hetalia ntpd[25317]: tls connect failed: 2607:f8b0:4003:c03::69 (www.google.com): connect: No route to host Jun 17 00:42:08 Hetalia apmd: battery status: low. external power status: connected. estimated battery life 47% Jun 17 00:44:37 Hetalia Tor[37431]: Tor v0.2.7.6 running on OpenBSD with Libevent 2.0.22-stable, OpenSSL LibreSSL 2.4.0 and Zlib 1.2.3. Jun 17 00:44:37 Hetalia Tor[37431]: Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Jun 17 00:44:37 Hetalia Tor[37431]: Read configuration file "/etc/tor/torrc". Jun 17 00:44:37 Hetalia Tor[37431]: Opening Socks listener on 127.0.0.1:1920 Jun 17 00:44:37 Hetalia Tor[37431]: Parsing GEOIP IPv4 file /usr/local/share/tor/geoip. Jun 17 00:44:38 Hetalia Tor[37431]: Parsing GEOIP IPv6 file /usr/local/share/tor/geoip6. Jun 17 00:44:38 Hetalia Tor[37431]: We were built to run on a 64-bit CPU, with OpenSSL 1.0.1 or later, but with a version of OpenSSL that apparently lacks accelerated support for the NIST P-224 and P-256 groups. Building openssl with such support (using the enable-ec_nistp_64_gcc_128 option when configuring it) would make ECDH much faster. Jun 17 00:44:38 Hetalia Tor[37431]: Bootstrapped 0%: Starting Jun 17 00:44:40 Hetalia Tor[37431]: Bootstrapped 5%: Connecting to directory server Jun 17 00:44:40 Hetalia Tor[37431]: Bootstrapped 80%: Connecting to the Tor network Jun 17 00:44:40 Hetalia Tor[37431]: Bootstrapped 85%: Finishing handshake with first hop Jun 17 00:44:41 Hetalia Tor[37431]: Bootstrapped 90%: Establishing a Tor circuit Jun 17 00:44:48 Hetalia Tor[37431]: Tor has successfully opened a circuit. Looks like client functionality is working. Jun 17 00:44:48 Hetalia Tor[37431]: Bootstrapped 100%: Done Jun 17 00:45:17 Hetalia /bsd: iwn0: Michael MIC failure Jun 17 00:48:28 Hetalia syslogd: start Jun 17 00:48:28 Hetalia /bsd: iwn0: Michael MIC failure Jun 17 00:48:28 Hetalia /bsd: OpenBSD 6.0-beta (GENERIC.MP) #2149: Mon May 30 17:15:14 MDT 2016 Jun 17 00:48:28 Hetalia /bsd: dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/
Randomish Reboots on Current
Has anyone else been hvaing random reboots on current? The system freezes up for maybe 30 seconds or so, then reboots. I have a hunch that it's something with my wifi card because occasionally during a reboot it'll error saying something about MIC errors and then reboot, or just freeze+reboot during the netstart portion of boot. The other thing that makes me think it's network is that it tends to happen during relatively network heavy things, like when I'm doing ssh X forwarding while watching streaming video, but this isn't always the case. This is a recent thing that just seems to have randomly appeared; it was working fine before and then it started rebooting one day; I hadn't updated the snapshot although I've tried that since to see if it helped. There's no panic so I don't have any ddb info, but I've attached dmesg and dmesg.boot. OpenBSD 6.0-beta (GENERIC.MP) #2165: Thu Jun 2 08:37:59 MDT 2016 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8237068288 (7855MB) avail mem = 7982804992 (7612MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xdae9c000 (69 entries) bios0: vendor LENOVO version "G1ETA2WW (2.62 )" date 01/10/2014 bios0: LENOVO 2344BZU acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SLIC TCPA SSDT SSDT SSDT HPET APIC MCFG ECDT FPDT ASF! UEFI UEFI MSDM SSDT SSDT DMAR UEFI DBG2 acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP3(S4) XHCI(S3) EHC1(S3) EHC2(S3) HDEF(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz, 1197.48 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,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz, 1197.28 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,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 1, core 0, package 0 cpu2 at mainbus0: apid 2 (application processor) cpu2: Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz, 1197.28 MHz cpu2: 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,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 1, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz, 1197.28 MHz cpu3: 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,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpiec0 at acpi0 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG_) acpiprt2 at acpi0: bus 2 (EXP1) acpiprt3 at acpi0: bus 3 (EXP2) acpiprt4 at acpi0: bus -1 (EXP3) acpicpu0 at acpi0: C3(200@87 mwait.1@0x30), C2(500@59 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C3(200@87 mwait.1@0x30), C2(500@59 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C3(200@87 mwait.1@0x30), C2(500@59 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C3(200@87 mwait.1@0x30), C2(500@59 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpipwrres0 at acpi0: PUBS, resource for XHCI, EHC1, EHC2 acpitz0 at acpi0: critical temperature is 200 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB "LEN0071" at acpi0 not configured "LEN0015" at acpi0 not configured "SMO1200" at acpi0 not configured acpibat0 at acpi0: BAT0 model "45N1107" serial 24045 type LION oem "LGC" acpiac0 at acpi0: AC unit offline "LEN0078" at acpi0 not configured acpithinkpad0 at acpi0 "PNP0C14" at acpi0 not configured "PNP0C14" at acpi0 not configured acpivideo0 at acpi0: VID_ acpivout at acpivideo0 not configured a
Re: vi vs emacs, which one makes me look more smart in front of my friends?
On Tue, May 17, 2016 at 07:25:45AM +0100, trebol55...@yandex.ru wrote: > mg(1) > > […] It is compatible with emacs because > there shouldn't be any reason to learn more editor types than emacs or > vi(1). > > Where is the troll, where is the silly troll? > Given enough time, a UNIX user's likelihood to use one of the two approaches 1. Why not support both sane configurations out of the box?
Re: How to tune network on Qemu-system-i386
Not as far as I can tell. It'd be via vmm if you can, so your options would be openbsd or netbsd, neither quickly from what I've heard. On Thu Feb 18 01:39:13 2016 GMT-0500, Steve Litt wrote: > Does hardware accelerated Qemu work on OpenBSD now? It didn't at the > end of 2014. > > Thanks, > > SteveT > > On Thu, 18 Feb 2016 10:38:48 +0500 > "dmitry.sensei" wrote: > > > It works :) If i added ifconfig tap0 > > However I have not yet understand how :) > > > > On Thu, Feb 11, 2016 at 4:45 PM, John Long wrote: > > > Dmitry, > > > > > > On Thu, Feb 11, 2016 at 10:06:34AM +0500, dmitry.sensei wrote: > > > > > >> Can you give generic guide to setting up a network in Qemu > > >> (OpenBSD)? I have one physical re0 interface, which looks to the > > >> Internet. > > > > > > #!/bin/ksh > > > ifconfig tun0 create > > > ifconfig tun0 link0 > > > ifconfig tun0 up > > > ifconfig bridge0 create > > > #ifconfig bridge0 fwddelay 4 > > > ifconfig bridge0 add re0 add tun0 > > > ifconfig bridge0 up > > > > > > I can't remember where I found the above but I have been using it > > > with SIMH. It may have been in the example where somebody shows how > > > to run OpenBSD VAX under SIMH. In the SIMH .conf you use > > > > > > at xq tap:tap0 > > > > > > I ASSume you would use a similar syntax in QEMU's config. That is, > > > use tap:tap0 as your network interface name instead of re0. I > > > commented out the fwddelay to see if it affected anything and it > > > doesn't seem to in this application. > > > > > > /jl > > > > > > -- > > > ASCII ribbon campaign ( ) Powered by Lemote Fuloong > > > against HTML e-mail X Loongson MIPS and OpenBSD > > >and proprietary/ \http://www.mutt.org > > > attachments / \ Code Blue or Go Home! > > > Encrypted email preferred PGP Key 2048R/DA65BC04 > > > > > > > > > > > > > -- > SteveT > > Steve Litt > February 2016 featured book: The Key to Everyday Excellence > http://www.troubleshooters.com/key > > -- Sent from my Jolla
Re: Azalia Volume Too Quiet
On Thu, Nov 19, 2015 at 10:13:09PM +, Mike Cond wrote: > There is no direct path to dac in your mixer. I would try to exclude mix from > inputs.mix2_source=dac-0:1,mix > inputs.mix3_source=dac-2:3,mix. > > So your outputs.spkr_source will contain mix3 but without mix components. Did a quick preliminary test, I think I'm still capped at 180. I'm in public though, so it was a bit quick.
Re: Azalia Volume Too Quiet
Sure. You can reply to just the list, by the way; I'm subscribed. inputs.dac-0:1=142,142 inputs.dac-2:3=142,142 record.adc-2:3_mute=off [ off on ] record.adc-2:3=124,124 record.adc-0:1_mute=off [ off on ] record.adc-0:1=124,124 inputs.mix_source=mic2,spkr2,spkr3,beep { mic2 spkr2 spkr3 beep } inputs.mix_mic2=120,120 inputs.mix_spkr2=248,248 inputs.mix_spkr3=248,248 inputs.mix_beep=120,120 inputs.mix2_source=dac-0:1,mix { dac-0:1 mix } inputs.mix3_source=dac-2:3,mix { dac-2:3 mix } inputs.mic=85,85 outputs.spkr_source=mix3 [ mix2 mix3 ] outputs.spkr_mute=off [ off on ] outputs.spkr_eapd=on [ off on ] outputs.hp_source=mix2 [ mix2 mix3 ] outputs.hp_mute=off [ off on ] outputs.hp_boost=on [ off on ] outputs.hp_eapd=on [ off on ] outputs.mic2_source=mix2 [ mix2 mix3 ] outputs.mic2_mute=off [ off on ] inputs.mic2=85,85 outputs.mic2_dir=input-vr80 [ none output input input-vr0 input-vr50 input-vr80 input-vr100 ] outputs.spkr2_source=mix2 [ mix2 mix3 ] outputs.spkr2_mute=off [ off on ] inputs.spkr2=255,255 outputs.spkr2_dir=output [ none output input input-vr0 input-vr50 input-vr80 input-vr100 ] outputs.spkr3_source=mix2 [ mix2 mix3 ] outputs.spkr3_mute=off [ off on ] inputs.spkr3=255,255 outputs.spkr3_dir=output [ none output input input-vr0 input-vr50 input-vr80 input-vr100 ] record.adc-0:1_source=mic2,spkr2,spkr3,beep,mix,mic { mic2 spkr2 spkr3 beep mix mic } record.adc-2:3_source=mic2,spkr2,spkr3,beep,mix { mic2 spkr2 spkr3 beep mix } outputs.hp_sense=unplugged [ unplugged plugged ] outputs.mic2_sense=unplugged [ unplugged plugged ] outputs.spkr_muters=hp,mic2 { hp mic2 } outputs.master=143,143 outputs.master.mute=off [ off on ] outputs.master.slaves=dac-0:1,dac-2:3,spkr,hp,spkr2,spkr3 { dac-0:1 dac-2:3 spkr hp mic2 spkr2 spkr3 } record.volume=124,124 record.volume.mute=off [ off on ] record.volume.slaves=adc-2:3,adc-0:1 { adc-2:3 adc-0:1 mic mic2 spkr2 spkr3 }
Re: Azalia Volume Too Quiet
On Thu, Nov 19, 2015 at 11:34:53AM +0200, Alexey Suslikov wrote: > 2 volume controls in output path (at least). You probably may try > to limit volume control to DACs > > outputs.master.slaves=dac-0:1,dac-2:3 > > and max out everything else in output path. Or > > outputs.master.slaves=spkr,hp > > and max out everything else in output path (including DACs). > I've just tried playing with the dac values. They cap out at 174 and they don't seem to affect the volume at all. I tried to follow Mike's advice as well and make a more direct path, but I ended up with $ mixerctl outputs.spkr_source=dac-2:3 mixerctl: Bad enum value dac-2:3 current mixerctl: inputs.dac-0:1=174,174 inputs.dac-2:3=174,174 record.adc-2:3_mute=off record.adc-2:3=124,124 record.adc-0:1_mute=off record.adc-0:1=124,124 inputs.mix_source=mic2,spkr2,spkr3,beep inputs.mix_mic2=120,120 inputs.mix_spkr2=248,248 inputs.mix_spkr3=248,248 inputs.mix_beep=120,120 inputs.mix2_source=dac-0:1,mix inputs.mix3_source=dac-2:3,mix inputs.mic=85,85 outputs.spkr_source=mix3 outputs.spkr_mute=off outputs.spkr_eapd=on outputs.hp_source=mix2 outputs.hp_mute=off outputs.hp_boost=on outputs.hp_eapd=on outputs.mic2_source=mix2 outputs.mic2_mute=off inputs.mic2=85,85 outputs.mic2_dir=input-vr80 outputs.spkr2_source=mix2 outputs.spkr2_mute=off inputs.spkr2=255,255 outputs.spkr2_dir=output outputs.spkr3_source=mix2 outputs.spkr3_mute=off inputs.spkr3=255,255 outputs.spkr3_dir=output record.adc-0:1_source=mic2,spkr2,spkr3,beep,mix,mic record.adc-2:3_source=mic2,spkr2,spkr3,beep,mix outputs.hp_sense=unplugged outputs.mic2_sense=unplugged outputs.spkr_muters=hp,mic2 outputs.master=255,255 outputs.master.mute=off outputs.master.slaves=dac-0:1,dac-2:3,spkr,hp,spkr2,spkr3 record.volume=124,124 record.volume.mute=off record.volume.slaves=adc-2:3,adc-0:1
Re: Azalia Volume Too Quiet
Oh, a quick self reply: I've noticed that when I look in audioctl, if I have just oss then lowat = hiwat = 25, with sndio running lowat = hiwat = 8. Not sure if this is helpful information.
Re: Azalia Volume Too Quiet
On Wed, Nov 18, 2015 at 08:15:08PM +, Raf Czlonka wrote: > Stefan, the OP already mentioned (see above) that he had already tried > that and it stays constant. > > On my machine, increasing the volume on 'outputs.mixY', where 'Y' is > '2', did the trick. > > Setting 'outputs.hp_boost=on' (for headphones) may increase the volume > further. > > Regards, > > Raf > I haven't got an outputs.mixY on my box, I'm afraid. There are references in other values to a mix2 though, like outputs.spkr2_source=mix2. There *is* an inputs.mix_spkr{2,3}. Changing them gives me an extra 10 units of volume (170 is distinguishable from 255, 180 is not). mixerctl output: inputs.dac-0:1=150,150 inputs.dac-2:3=150,150 record.adc-2:3_mute=off record.adc-2:3=124,124 record.adc-0:1_mute=off record.adc-0:1=124,124 inputs.mix_source=mic2,spkr2,spkr3,beep inputs.mix_mic2=120,120 inputs.mix_spkr2=248,248 inputs.mix_spkr3=248,248 inputs.mix_beep=120,120 inputs.mix2_source=dac-0:1,mix inputs.mix3_source=dac-2:3,mix inputs.mic=85,85 outputs.spkr_source=mix3 outputs.spkr_mute=off outputs.spkr_eapd=on outputs.hp_source=mix2 outputs.hp_mute=off outputs.hp_boost=off outputs.hp_eapd=on outputs.mic2_source=mix2 outputs.mic2_mute=off inputs.mic2=85,85 outputs.mic2_dir=input-vr80 outputs.spkr2_source=mix2 outputs.spkr2_mute=off inputs.spkr2=255,255 outputs.spkr2_dir=output outputs.spkr3_source=mix2 outputs.spkr3_mute=off inputs.spkr3=255,255 outputs.spkr3_dir=output record.adc-0:1_source=mic2,spkr2,spkr3,beep,mix,mic record.adc-2:3_source=mic2,spkr2,spkr3,beep,mix outputs.hp_sense=unplugged outputs.mic2_sense=unplugged outputs.spkr_muters=hp,mic2 outputs.master=151,151 outputs.master.mute=off outputs.master.slaves=dac-0:1,dac-2:3,spkr,hp,spkr2,spkr3 record.volume=124,124 record.volume.mute=off record.volume.slaves=adc-2:3,adc-0:1
Azalia Volume Too Quiet
When I try to play sounds on my Thinkpad T430 I find that the audio's rather quiet, I've experimented a bit and found that at about 170 (mixerctl outputs.master=170) the volume stops increasing. It just stays constant from 170 to 255, or at least the change is so quiet that I can't hear it. I've looked around in the driver a little bit, but I'm no kernel hacker, the only thing I noticed that might help is that for a few widgets outamp (I'm assuming output amplify?) is muted. dmesg (with AZALIA_DEBUG) and audioctl: name=HD-Audio encodings=slinear_le:16:2:1,slinear_le:20:4:1,slinear_le:24:4:1 properties=full_duplex,independent hiwat=25 lowat=25 mode=play play.rate=44100 play.channels=2 play.precision=16 play.bps=2 play.msb=1 play.encoding=slinear_le play.pause=1 vplay.active=0 play.block_size=1792 play.bytes=0 play.errors=0 record.rate=44100 record.channels=2 record.precision=16 record.bps=2 record.msb=1 record.encoding=slinear_le record.pause=1 record.active=0 record.block_size=1792 record.bytes=0 record.errors=0 OpenBSD 5.8-current (GENERIC.MP) #0: Tue Nov 17 19:22:36 EST 2015 da...@hetalia.router5d2448.com:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8237068288 (7855MB) avail mem = 7983288320 (7613MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xdae9c000 (69 entries) bios0: vendor LENOVO version "G1ETA2WW (2.62 )" date 01/10/2014 bios0: LENOVO 2344BZU acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SLIC TCPA SSDT SSDT SSDT HPET APIC MCFG ECDT FPDT ASF! UEFI UEFI MSDM SSDT SSDT DMAR UEFI DBG2 acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP3(S4) XHCI(S3) EHC1(S3) EHC2(S3) HDEF(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz, 1197.51 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,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz, 1197.28 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,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 1, core 0, package 0 cpu2 at mainbus0: apid 2 (application processor) cpu2: Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz, 1197.28 MHz cpu2: 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,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 1, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz, 1197.28 MHz cpu3: 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,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpiec0 at acpi0 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG_) acpiprt2 at acpi0: bus 2 (EXP1) acpiprt3 at acpi0: bus 3 (EXP2) acpiprt4 at acpi0: bus -1 (EXP3) acpicpu0 at acpi0: C3(200@87 mwait.1@0x30), C2(500@59 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C3(200@87 mwait.1@0x30), C2(500@59 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C3(200@87 mwait.1@0x30), C2(500@59 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C3(200@87 mwait.1@0x30), C2(500@59 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpipwrres0 at acpi0: PUBS, resource for XHCI, EHC1, EHC2 acpitz0 at acpi0: critical temperature is 200 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibat0 at acpi0: BAT0 model "45N1107" serial 24045 type LION oem "LGC" acpibat1 at acpi0: BAT1 not present acpiac0 at acpi0: AC unit offline acpithinkpad0 at acpi0 cpu0: Enhanced SpeedStep 1197 MHz: speeds: 2601, 2600
Re: maybe OT 11 year anniversay of Chuck Yerkes death
Either works as an American. Commenting on Chuck would be nice, but I only know him through these yearly emails, so I'll stay silent on that matter. On Wed, Sep 02, 2015 at 09:42:52PM +0300, Mihai Popescu wrote: > I think you should call it a commemoration. I'm not sure, I'm not a > native english speaker (neither british or american).