Re: Snapshot crash on boot, "entry point at: 0x1001000" (Intel Gemini Lake)

[Michel von Behr]

@stuart Thank for the suggestion - unfortunately after following the steps
in that link the same error occurred (entry point at: 0x1001000); I
reverted to the obsd kernel (i.e., at boot time, “b obsd”), it’s booting
and the system seems to be working OK, but without dmesg - when I try to
run dmesg, I get:

dmesg: sysctl: KERN_MSGBUF: Cannot allocate memory

$ uname -a
OpenBSD chuwi.mabvb.pro 6.7 GENERIC.MP#6 amd64

Not sure if there’s anything else I can do, if there is I’d be happy try it
out.

Regards

Michel


*Subject:Re: Snapshot crash on boot, "entry point at: 0x1001000"
(Intel Gemini Lake) 
From:   Stuart Henderson 

Date:   2020-10-10 10:51:45

Message-ID: slrnro34i1.2d2i.stu () naiad ! spacehopper ! org

[Download RAW message
 or body
]*

On 2020-10-09, Michel von Behr  wrote:
> I'm trying to run snapshot on a Chuwi Lapbook laptop (Intel Gemini Lake),
> but I get stuck at boot time with the message "entry point at: 0x1001000".
> Based on previous discussions [1] 
>  it looks like the 
> problem is with
> BOOTX64.EFI
> For now I'll be running -stable, but I would like to follow -current. Is
> there a way to run -current with an old version of BOOTX64.EFI for example?

If you upgrade by downloading and untarring sets on the running system,
you can avoid updating the bootloader, the basic method is described
inhttp://www.openbsd.org/faq/upgrade67.html#NoInstKern (obviously skip
the "update the bootloader" step).

Note that newer versions of the bootloader read the seed for early RNG use
in the kernel, I'm not sure when it was added but you might miss out on
that with a 6.7 bootloader.




On Fri, 9 Oct 2020 at 3:37 PM Michel von Behr  wrote:

> Hi all,
> I'm trying to run snapshot on a Chuwi Lapbook laptop (Intel Gemini Lake),
> but I get stuck at boot time with the message "entry point at: 0x1001000".
> Based on previous discussions [1] it looks like the problem is with
> BOOTX64.EFI
> For now I'll be running -stable, but I would like to follow -current. Is
> there a way to run -current with an old version of BOOTX64.EFI for example?
> (i.e., the only alternatives I'm seeing is either 1) compiling a GENERIC
> kernel with the older version of BOOTX64.EFI src, or 2) (try to) compile a
> custom/smaller kernel to avoid the issue).
>
> [1] https://marc.info/?l=openbsd-misc=159147446008114=2
>
> Any pointing to the right direction is welcome.
>
> Regards,
>
> Michel
>

Re: Integrating OpenBSD into Xen/Qubes

[tetrahedra]

On Fri, Oct 16, 2020 at 11:35:40AM +0200, Anders Andersson wrote:

How could any hardening in OpenBSD protect from someone owning the
hardware? Or do you mean that an OpenBSD guest would run with
exclusive access to the NIC and then every other guest is routed
through that guest?


Yes, exactly. The OpenBSD guest would have exclusive access to the NIC, 
and handles all networking for the entire system.


At the moment, Qubes uses a Fedora Linux-based guest system to handle 
networking. This means that if an attacker can compromise the Fedora 
networking drivers, they can compromise the guest, and potentially use 
the guest's PCI access to exploit Xen.


As noted in the original Github issue, attacks on networking sub-systems 
are all too common (apparently some Middle Eastern countries are 
building or have built systems to mass exploit anyone who e.g connects 
to a shopping mall's Wi-Fi network).


OpenBSD's hardening and generally higher standard of code quality would 
go a long way to mitigating this attack scenario.

Thinkpad T14s: Sound works through headphones only

[Ashton Fagg]

I've just installed -current on my Thinkpad T14s, and I have a weird
problem with getting sound to work properly.

It seems that sound does work, but only through the headphone jack.
I've made sure everything is unmuted in mixerctl, but nonetheless
there's no output at all from the built in speakers. The audio on my
USB-C dock, while recognized as a device, doesn't seem to work either.

What's interesting is that the machine has a light on the mute key
that glows when the speakers are muted. This seems to be illuminated
all the time (meaning the speakers are muted). Pressing mute does
nothing for the speakers. But, if you are using headphones the mute
button will mute the headphones (but still the light remains
illuminated).

I have included the output of my mixerctl -av, as well as dmesg in
case that is of help. I am not sure whether this is a bug, or, whether
it is something I haven't configured properly. If it's a bug I will
report it as such, but I can't quite tell. Any help appreciated.

Thanks,
Ash

[fagg@moon][~][0] -> doas mixerctl -av
inputs.dac-2:3=104,104
inputs.dac-0:1=104,104
record.adc-0:1_mute=off  [ off on ]
record.adc-0:1=252,252
record.adc-2:3_mute=off  [ off on ]
record.adc-2:3=252,252
outputs.spkr_source=dac-2:3  [ dac-2:3 ]
outputs.spkr_mute=off  [ off on ]
outputs.spkr_eapd=on  [ off on ]
inputs.mic=85,85
outputs.mic_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-2:3_source=mic  { mic }
record.adc-0:1_source=mic  { mic }
outputs.mic_sense=unplugged  [ unplugged plugged ]
outputs.hp_sense=unplugged  [ unplugged plugged ]
outputs.spkr_muters=hp  { hp }
outputs.master=104,104
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=255,255
record.volume.mute=off  [ off on ]
record.volume.slaves=adc-0:1,adc-2:3  { adc-0:1 adc-2:3 mic }
record.enable=sysctl  [ off on sysctl ]

dmesg:

OpenBSD 6.8-current (GENERIC.MP) #115: Fri Oct 16 00:42:26 MDT 2020
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 16332681216 (15576MB)
avail mem = 15822594048 (15089MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.2 @ 0xbf912000 (68 entries)
bios0: vendor LENOVO version "R1CET36W(1.05 )" date 06/11/2020
bios0: LENOVO 20UH000CUS
acpi0 at bios0: ACPI 6.3
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT SSDT SSDT IVRS SSDT SSDT TPM2 SSDT MSDM
BATB HPET APIC MCFG SBST WSMT VFCT SSDT CRAT CDIT FPDT SSDT SSDT SSDT
UEFI SSDT SSDT BGRT
acpi0: wakeup devices GPP0(S3) RESA(S3) GPP4(S4) GPP5(S3) L850(S3)
GPP6(S3) GPP7(S3) GP17(S3) XHC0(S3) XHC1(S3) LID_(S4) SLPB(S3)
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpihpet0 at acpi0: 14318180 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: AMD Ryzen 7 PRO 4750U with Radeon Graphics, 1697.05 MHz, 17-60-01
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,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
cpu0: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB
64b/line 8-way L2 cache, 8MB 64b/line disabled L3 cache
cpu0: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative
cpu0: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=1.1, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: AMD Ryzen 7 PRO 4750U with Radeon Graphics, 1696.82 MHz, 17-60-01
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,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
cpu1: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB
64b/line 8-way L2 cache, 8MB 64b/line disabled L3 cache
cpu1: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative
cpu1: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative
cpu1: disabling user TSC (skew=-392267655)
cpu1: smt 1, core 0, package 0
cpu2 at 

Re: Thinkpad T14/T14s - any experiences?

[Tom Smyth]

Hi Ashton,
I have the T15 and it has more or less the same hardware and it seems
to work good..
Getting OpenBSD and WIndows 10 to play nice and share the same drive
is not as easy as I would like
Both OS are happy until the other OS is there :) ...
I have the Nvida hybrid :( GPU (because of a 4 K screen) but it does work well..


On Fri, 16 Oct 2020 at 22:50, Ashton Fagg  wrote:
>
> On Wed, 14 Oct 2020 at 14:06, Jan Betlach  wrote:
> >
> >
> > I am about to install -current on my new T14s with Ryzen 4750u as well.
> >
> > I have browsed r/openbsd, there are two recent posts related to this. I 
> > have also chatted on Freenode / #openbsd as there are couple of guys 
> > running -current on their AMD Thinkpads.
> >
> > It seems that almost everything works. For suspend you need to switch the 
> > option from "Windows" to "Linux" in Bios (Config/Power/SleepState). Few 
> > people still report occasional problems with suspend.
> > Also, there's no userland clock_gettime on the 4750U (due to reported tsc 
> > skew).
> > Almost everything else works - wifi, acceleration, etc.
> >
> > Will report my own experience as soon as will get to -current installation.
> >
> > Jan
>
> Hey Jan,
>
> I ended up getting some free time today, so I went ahead and installed
> -current on this machine. So far, works great (have a few small
> issues, but these may be down to the fact that I don't know what I'm
> doing :-) I will be interested to hear if you have a similar
> experience (esp. with the small niggles I note below).
>
> I built the install disk from today's snapshot. No issues installing
> (including disk encryption).
>
> Suspend works, haven't tried Hibernate.
>
> WiFi works once you pull in the firmware.
>
> Brightness hotkeys and keyboard backlight hotkeys work fine.
>
> Thus far I have not tested ethernet but the device shows up so I am
> assuming it is fine. X runs fine, haven't noticed any tearing or
> anything. Even without a compositor running it's much
> smoother/performant than on Linux - without something like picom, Arch
> Linux would exhibit large amounts of tearing when playing video.
> OpenBSD does much better here.
>
> The machine doesn't seem to be running hotter than usual or anything either.
>
> A few minor issues (none are deal breakers in the slightest, at least for me):
>
> - Webcam doesn't appear to work
> - Sound works but ONLY through the headphone jack. Even with
> everything in mixerctl unmuted, no dice. The light on the mute hotkey
> stays lit. Oddly though if you are using headphones and press that
> key, the mute works. Thus far I haven't managed to investigate the
> volume keys. I will post separately about this because I suspect maybe
> I am not configuring it right.
> - My Lenovo USB-C dock is recognized - it provides power, USB and is
> also recognized as a sound output device. But the HDMI and
> displayports on it are totally dead. xrandr doesn't pick them up at
> all - I wonder if I need to boot the machine with the dock plugged in.
> That said, if I plug my monitor in via HDMI directly on the laptop, it
> works just fine.
>
> Anyhow, hope that helps anyone Googling for answers on this. :-)
>
> Cheers,
> Ash
>


-- 
Kindest regards,
Tom Smyth.

Re: Thinkpad T14/T14s - any experiences?

[Ashton Fagg]

On Wed, 14 Oct 2020 at 14:06, Jan Betlach  wrote:
>
>
> I am about to install -current on my new T14s with Ryzen 4750u as well.
>
> I have browsed r/openbsd, there are two recent posts related to this. I have 
> also chatted on Freenode / #openbsd as there are couple of guys running 
> -current on their AMD Thinkpads.
>
> It seems that almost everything works. For suspend you need to switch the 
> option from "Windows" to "Linux" in Bios (Config/Power/SleepState). Few 
> people still report occasional problems with suspend.
> Also, there's no userland clock_gettime on the 4750U (due to reported tsc 
> skew).
> Almost everything else works - wifi, acceleration, etc.
>
> Will report my own experience as soon as will get to -current installation.
>
> Jan

Hey Jan,

I ended up getting some free time today, so I went ahead and installed
-current on this machine. So far, works great (have a few small
issues, but these may be down to the fact that I don't know what I'm
doing :-) I will be interested to hear if you have a similar
experience (esp. with the small niggles I note below).

I built the install disk from today's snapshot. No issues installing
(including disk encryption).

Suspend works, haven't tried Hibernate.

WiFi works once you pull in the firmware.

Brightness hotkeys and keyboard backlight hotkeys work fine.

Thus far I have not tested ethernet but the device shows up so I am
assuming it is fine. X runs fine, haven't noticed any tearing or
anything. Even without a compositor running it's much
smoother/performant than on Linux - without something like picom, Arch
Linux would exhibit large amounts of tearing when playing video.
OpenBSD does much better here.

The machine doesn't seem to be running hotter than usual or anything either.

A few minor issues (none are deal breakers in the slightest, at least for me):

- Webcam doesn't appear to work
- Sound works but ONLY through the headphone jack. Even with
everything in mixerctl unmuted, no dice. The light on the mute hotkey
stays lit. Oddly though if you are using headphones and press that
key, the mute works. Thus far I haven't managed to investigate the
volume keys. I will post separately about this because I suspect maybe
I am not configuring it right.
- My Lenovo USB-C dock is recognized - it provides power, USB and is
also recognized as a sound output device. But the HDMI and
displayports on it are totally dead. xrandr doesn't pick them up at
all - I wonder if I need to boot the machine with the dock plugged in.
That said, if I plug my monitor in via HDMI directly on the laptop, it
works just fine.

Anyhow, hope that helps anyone Googling for answers on this. :-)

Cheers,
Ash

Problem httpd with https and SNI -current

[ml]

Hello at all,

my httpd.conf
-
prefork 10

logdir "/var/log"

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

server "host1.example.com" {
listen on * tls port 443
no log
root "/htdocs/host1"
tls {
certificate "/etc/httpd/ssl.crt/host1.pem"
key "/etc/httpd/ssl.key/host1.key.pem"
ciphers "secure"
ticket lifetime default
}
}
server "host2.example.com" {
listen on * tls port 443
no log
root "/htdocs/host2"
tls {
certificate "/etc/httpd/ssl.crt/host2.pem"
key "/etc/httpd/ssl.key/host2.key.pem"
ciphers "secure"
ticket lifetime default
}
}
-

cat /etc/hostname.em0   
   
inet 1.2.3.4 255.255.255.0
inet alias 1.2.3.5 255.255.255.0

DNS:
host1.example.com A 1.2.3.4
host2.example.com A 1.2.3.5

=> This works.

But if i change the IP in DNS from host2.example.com to 1.2.3.4
i will get the content of host1

I hope anyone have an idea.

Thanks

Thomas

Re: OpenBSD 6.8 Relase Time

[Erling Westenvik]

On Fri, Oct 16, 2020 at 01:52:14PM +, Valdrin Muja wrote:
> On OpenBSD 6.8 page, `Released Oct XXX` is writing..
> When will it be released?

Octobris 0x1e scilicet!














(Just kidding. No one knows for sure. It just arrives in due time when ready.)

Erling

wait6 ?

[Brennan Vincent]

{Free,Net}BSD have wait6(2), which is even more general than wait4(2), 
and allows one to implement POSIX-mandated waitid(2). See e.g. 
https://man.netbsd.org/wait.2 .


Is the reason this (or something substantially similar) is missing from 
OpenBSD that we don't want it, or just that nobody has done the work to 
implement it?


If it is the latter, I can try to make a patch.

Resume from hibernation failing with amdgpu

[Renato Aguiar]

Hi,

I'd like to report a problem with resuming from hibernation on Thinkpad X13 AMD.

BTW, everything else seems to work just fine :)

System version: OpenBSD 6.8 GENERIC.MP#115 amd64

Relevant logs from /var/log/messages:

Oct 16 08:57:29 orion /bsd: drm0 at amdgpu0
Oct 16 08:57:29 orion /bsd: amdgpu0: msi
Oct 16 08:57:29 orion /bsd: amdgpu0: RENOIR 7 CU rev 0x00
Oct 16 08:57:29 orion /bsd: amdgpu0: 1920x1080, 32bpp
Oct 16 08:59:24 orion apmd: system hibernating
Oct 16 09:02:15 orion /bsd: drm:pid86388:gmc_v9_0_process_interrupt *ERROR* 
[mmhub0] no-retry page fault (src_id:0 ring:128 vmid:0 pasid:0, for process  
pid 0 thread  pid 0)
Oct 16 09:02:15 orion /bsd: drm:pid86388:gmc_v9_0_process_interrupt *ERROR*   
in page starting at address 0x00664000 from client 18
Oct 16 09:02:15 orion /bsd: drm:pid86388:gmc_v9_0_process_interrupt *ERROR* 
VM_L2_PROTECTION_FAULT_STATUS:0x0300
Oct 16 09:02:15 orion /bsd: drm:pid86388:gmc_v9_0_process_interrupt *ERROR* 
 MORE_FAULTS: 0x0
Oct 16 09:02:15 orion /bsd: drm:pid86388:gmc_v9_0_process_interrupt *ERROR* 
 WALKER_ERROR: 0x0
Oct 16 09:02:15 orion /bsd: drm:pid86388:gmc_v9_0_process_interrupt *ERROR* 
 PERMISSION_FAULTS: 0x0
Oct 16 09:02:15 orion /bsd: drm:pid86388:gmc_v9_0_process_interrupt *ERROR* 
 MAPPING_ERROR: 0x1
Oct 16 09:02:15 orion /bsd: drm:pid86388:gmc_v9_0_process_interrupt *ERROR* 
 RW: 0x0
Oct 16 09:02:15 orion /bsd: [drm] failed to load ucode id (0) [drm] psp command 
(0x6) failed and response status is (0xF)
Oct 16 09:02:15 orion /bsd: drm:pid86388:gmc_v9_0_process_interrupt *ERROR* 
[mmhub0] no-retry page fault (src_id:0 ring:157 vmid:0 pasid:0, for process  
pid 0 thread  pid 0)
Oct 16 09:02:15 orion /bsd: drm:pid86388:gmc_v9_0_process_interrupt *ERROR*   
in page starting at address 0x00669000 from client 18
Oct 16 09:02:15 orion /bsd: drm:pid86388:gmc_v9_0_process_interrupt *ERROR* 
VM_L2_PROTECTION_FAULT_STATUS:0x033A
Oct 16 09:02:15 orion /bsd: drm:pid86388:gmc_v9_0_process_interrupt *ERROR* 
 MORE_FAULTS: 0x0
Oct 16 09:02:15 orion /bsd: drm:pid86388:gmc_v9_0_process_interrupt *ERROR* 
 WALKER_ERROR: 0x5
Oct 16 09:02:15 orion /bsd: drm:pid86388:gmc_v9_0_process_interrupt *ERROR* 
 PERMISSION_FAULTS: 0x3
Oct 16 09:02:15 orion /bsd: drm:pid86388:gmc_v9_0_process_interrupt *ERROR* 
 MAPPING_ERROR: 0x1
Oct 16 09:02:15 orion /bsd: drm:pid86388:gmc_v9_0_process_interrupt *ERROR* 
 RW: 0x0
Oct 16 09:02:15 orion /bsd: [drm] failed to load ucode id (8) [drm] psp command 
(0x6) failed and response status is (0xF)
Oct 16 09:02:15 orion /bsd: drm:pid86388:gmc_v9_0_process_interrupt *ERROR* 
[mmhub0] no-retry page fault (src_id:0 ring:128 vmid:0 pasid:0, for process  
pid 0 thread  pid 0)
Oct 16 09:02:15 orion /bsd: drm:pid86388:gmc_v9_0_process_interrupt *ERROR*   
in page starting at address 0x0066c000 from client 18
Oct 16 09:02:15 orion /bsd: drm:pid86388:gmc_v9_0_process_interrupt *ERROR* 
VM_L2_PROTECTION_FAULT_STATUS:0x0300
Oct 16 09:02:15 orion /bsd: drm:pid86388:gmc_v9_0_process_interrupt *ERROR* 
 MORE_FAULTS: 0x0
Oct 16 09:02:15 orion /bsd: drm:pid86388:gmc_v9_0_process_interrupt *ERROR* 
 WALKER_ERROR: 0x0
Oct 16 09:02:15 orion /bsd: drm:pid86388:gmc_v9_0_process_interrupt *ERROR* 
 PERMISSION_FAULTS: 0x0
Oct 16 09:02:15 orion /bsd: drm:pid86388:gmc_v9_0_process_interrupt *ERROR* 
 MAPPING_ERROR: 0x1
Oct 16 09:02:15 orion /bsd: drm:pid86388:gmc_v9_0_process_interrupt *ERROR* 
 RW: 0x0
Oct 16 09:02:15 orion /bsd: [drm] failed to load ucode id (9) [drm] psp command 
(0x6) failed and response status is (0xF)
Oct 16 09:02:15 orion /bsd: drm:pid86388:gmc_v9_0_process_interrupt *ERROR* 
[mmhub0] no-retry page fault (src_id:0 ring:24 vmid:0 pasid:0, for process  pid 
0 thread  pid 0)
Oct 16 09:02:15 orion /bsd: drm:pid86388:gmc_v9_0_process_interrupt *ERROR*   
in page starting at address 0x00672000 from client 18
Oct 16 09:02:15 orion /bsd: drm:pid86388:gmc_v9_0_process_interrupt *ERROR* 
VM_L2_PROTECTION_FAULT_STATUS:0x0230
Oct 16 09:02:15 orion /bsd: drm:pid86388:gmc_v9_0_process_interrupt *ERROR* 
 MORE_FAULTS: 0x0
Oct 16 09:02:15 orion /bsd: drm:pid86388:gmc_v9_0_process_interrupt *ERROR* 
 WALKER_ERROR: 0x0
Oct 16 09:02:15 orion /bsd: drm:pid86388:gmc_v9_0_process_interrupt *ERROR* 
 PERMISSION_FAULTS: 0x3
Oct 16 09:02:15 orion /bsd: drm:pid86388:gmc_v9_0_process_interrupt *ERROR* 
 MAPPING_ERROR: 0x0
Oct 16 09:02:15 orion /bsd: drm:pid86388:gmc_v9_0_process_interrupt *ERROR* 
 RW: 0x0
Oct 16 09:02:15 orion /bsd: [drm] failed to load ucode id (10) [drm] psp 
command (0x6) failed and response status is (0xF)
Oct 16 09:02:15 orion /bsd: drm:pid86388:gmc_v9_0_process_interrupt *ERROR* 
[mmhub0] no-retry page fault (src_id:0 ring:157 vmid:0 pasid:0, for process  
pid 0 thread  pid 0)
Oct 16 09:02:15 orion /bsd: drm:pid86388:gmc_v9_0_process_interrupt *ERROR*   
in page starting at address 0x00677000 from client 18

OpenBSD 6.8 Relase Time

[Valdrin Muja]

Hi Misc,

I'm looking forward to OpenBSD 6.8 release.

On OpenBSD 6.8 page, `Released Oct XXX` is writing..

https://www.openbsd.org/68.html

When will it be released?

Sent with [ProtonMail](https://protonmail.com) Secure Email.

Re: Integrating OpenBSD into Xen/Qubes

[Anders Andersson]

On Wed, Oct 14, 2020 at 8:24 PM  wrote:
>
> A number of people are working on integrating OpenBSD into Qubes.
>
> In particular, OpenBSD's hardening and mitigations are potentially very
> useful in talking to the NIC: Xen vulnerabilities have been repeatedly
> found that would allow a guest with PCI access to compromise the entire
> system, and on most machines the network card is a PCI device.

How could any hardening in OpenBSD protect from someone owning the
hardware? Or do you mean that an OpenBSD guest would run with
exclusive access to the NIC and then every other guest is routed
through that guest?

Re: reposync to JP mirror silently fails

[rgc]

Suzuki-sama

otsukaresamadesu
(sorry i could type kana, my macppc is not setup good enough)


First of all, I am very thankful that I (we) could use your server
for CVS reposysnc. It is great service to the community.

Personally, I was not inconvenienced so please don't apologize.

Thank you very much for the quick reply. I can verify that reposync
is running fine again.

yorosikuonegaiitashimasu



On Fri, Oct 16, 2020 at 09:57:54AM +0900, SUZUKI Hitoshi wrote:
> RGC,
> thank you for letting me know the situation.
> And sorry for the inconvinience.
> 
> The service was not usabele after Sept. 14th
> because I could not catch the update of reposync package,
> 
> Now I've added the info. to /var/db/reposync/known_hosts,
> so everything back is back to normal.
> 
> 
> On 20/10/16 05:44, rgc wrote:
> > misc@
> > 
> > just a heads up
> > 
> > 
> > i usually reposync to 'rsync://anoncvs.au.openbsd.org/cvs/' but the past 
> > few months
> > i noticed reposync is not pulling any changes from this mirror.
> > 
> > maybe it is not syncing correctly to the main server.
> > 
> > i temporarily moved to a different mirror.
> > 
> 
> -- 
> SUZUKI Hitoshi s...@nagasaki-u.ac.jp
> Faculty of Economics, Nagasaki Univ.

Re: bgpd path selection seems broken at now

[Bars Bars]

Thanks for your response.

# dmesg
OpenBSD 6.6-stable (VPN) #5: Fri Sep  4 18:52:23 CEST 2020
root@VPN:/usr/src/sys/arch/amd64/compile/VPN
real mem = 34297917440 (32709MB)
avail mem = 33245429760 (31705MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.5 @ 0x7f6bd000 (85 entries)
bios0: vendor IBM Corp. version "-[D6E148BUS-1.08]-" date 06/25/2010
bios0: IBM 69Y5698
acpi0 at bios0: ACPI 4.0
acpi0: sleep states S0 S1 S5
acpi0: tables DSDT FACP TCPA APIC MCFG SLIC HPET SRAT SLIT SSDT SSDT ERST
DMAR
acpi0: wakeup devices UHC1(S4) UHC2(S4) UHC3(S4) UHC4(S4) UHC5(S4) EHC1(S4)
EHC2(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) Xeon(R) CPU E5630 @ 2.53GHz, 2666.94 MHz, 06-2c-02
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,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT,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 133MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Xeon(R) CPU E5630 @ 2.53GHz, 2666.77 MHz, 06-2c-02
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,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT,MELTDOWN
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 18 (application processor)
cpu2: Intel(R) Xeon(R) CPU E5630 @ 2.53GHz, 2666.77 MHz, 06-2c-02
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,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT,MELTDOWN
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 9, package 0
cpu3 at mainbus0: apid 20 (application processor)
cpu3: Intel(R) Xeon(R) CPU E5630 @ 2.53GHz, 2666.77 MHz, 06-2c-02
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,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT,MELTDOWN
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 0, core 10, package 0
cpu4 at mainbus0: apid 32 (application processor)
cpu4: Intel(R) Xeon(R) CPU E5630 @ 2.53GHz, 2666.77 MHz, 06-2c-02
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,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT,MELTDOWN
cpu4: 256KB 64b/line 8-way L2 cache
cpu4: smt 0, core 0, package 1
cpu5 at mainbus0: apid 34 (application processor)
cpu5: Intel(R) Xeon(R) CPU E5630 @ 2.53GHz, 2666.77 MHz, 06-2c-02
cpu5:
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,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT,MELTDOWN
cpu5: 256KB 64b/line 8-way L2 cache
cpu5: smt 0, core 1, package 1
cpu6 at mainbus0: apid 50 (application processor)
cpu6: Intel(R) Xeon(R) CPU E5630 @ 2.53GHz, 2666.77 MHz, 06-2c-02
cpu6:
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,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT,MELTDOWN
cpu6: 256KB 64b/line 8-way L2 cache
cpu6: smt 0, core 9, package 1
cpu7 at mainbus0: apid 52 (application processor)
cpu7: Intel(R) Xeon(R) CPU E5630 @ 2.53GHz, 2666.77 MHz, 06-2c-02
cpu7:
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,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT,MELTDOWN
cpu7: 256KB 64b/line 8-way L2 cache
cpu7: smt 0, core 10, package 1
cpu8 at mainbus0: apid 1 (application processor)
cpu8: Intel(R) Xeon(R) CPU E5630 @ 2.53GHz, 2666.77 MHz, 06-2c-02
cpu8:
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,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT,MELTDOWN
cpu8: 256KB 64b/line 8-way L2 cache
cpu8: smt 1,