Re: kernel: page fault trap, code=0 after zzz on amd64 apu1d

2022-02-14 Thread Theo de Raadt
More and more, I am developing the opinion that it is a waste of time to give people source code.

Re: kernel: page fault trap, code=0 after zzz on amd64 apu1d

2022-02-14 Thread Theo de Raadt
Patrick Wildt wrote: > Am Mon, Feb 14, 2022 at 05:57:44PM -0700 schrieb Theo de Raadt: > > your root filesystem is on a detachable device? > > Sure? It seems to use sd0a for root, and that is coming from ahci0. > There is an sd1 though, which seems detachable, but that is not used > as root

Re: kernel: page fault trap, code=0 after zzz on amd64 apu1d

2022-02-14 Thread Patrick Wildt
Am Mon, Feb 14, 2022 at 05:57:44PM -0700 schrieb Theo de Raadt: > your root filesystem is on a detachable device? Sure? It seems to use sd0a for root, and that is coming from ahci0. There is an sd1 though, which seems detachable, but that is not used as root device as far as I can see? > That

Re: kernel: page fault trap, code=0 after zzz on amd64 apu1d

2022-02-14 Thread Theo de Raadt
Oh well. I am only interested in suspend/resume on real machines, and you'll have a hard time finding anyone to help you. You are on your own. You have source. Tilo Stritzky wrote: > On 14/02/22 17:57 Theo de Raadt wrote: > > your root filesystem is on a detachable device? > > No, the root

Re: kernel: page fault trap, code=0 after zzz on amd64 apu1d

2022-02-14 Thread Tilo Stritzky
On 14/02/22 17:57 Theo de Raadt wrote: > your root filesystem is on a detachable device? No, the root disc is SATA: ahci0 at pci0 dev 17 function 0 "ATI SBx00 SATA" rev 0x40: apic 2 int 19, GHC 0x8000 AHCI 1.2 ahci0: capabilities 0xf322ff05, 6 ports, 32 cmds, gen 2 (3.0Gb/s) ahci0: extended

Re: kernel: page fault trap, code=0 after zzz on amd64 apu1d

2022-02-14 Thread Tilo Stritzky
On 15/02/22 01:54 Tilo Stritzky wrote: > > I've got another one with a homebuild from -current as of 2022-02-13, > will put traces in another mail. And here we go. This is from the crash dump, I lost the console log on this one. Dump is still here. tilo $ dmesg -M bsd.0.core -N bsd.0 OpenBSD

Re: kernel: page fault trap, code=0 after zzz on amd64 apu1d

2022-02-14 Thread Theo de Raadt
your root filesystem is on a detachable device? That does not work. Suspend/resume has been written for reasonable laptops which contain a bunch of ACPI tables usually curated by vendors to at least work. What you are trying to do is silly. Tilo Stritzky wrote: > After issuing zzz on a

kernel: page fault trap, code=0 after zzz on amd64 apu1d

2022-02-14 Thread Tilo Stritzky
After issuing zzz on a pcengines apu1d running amd64 I found myself at the ddb prompt (full transcript below): uvm_fault(0x82326b70, 0x0, 0, 1) -> e kernel: page fault trap, code=0 Stopped at bufq_destroy+0x83: movq0(%rcx),%rcx TIDPIDUID PRFLAGS PFLAGS

re0: PHY write failed after zzz on am64 apud1d, ethernet unusable after resume

2022-02-14 Thread Tilo Stritzky
I just discovered my trusted APU1d does suspend/resume. Yai! One fly in the ointment: After a suspend/resume cycle all 3 re ethernet ports are unresponsive. dmesg fills with: re0: reset never completed! re0: PHY write failed re0: PHY write failed re0: PHY write failed re0: PHY write failed re0:

Re: New crash when waking from sleep on Thinkpad T490

2022-02-14 Thread Theo de Raadt
> OpenBSD 7.0-current (GENERIC.MP) #331: Fri Feb 11 22:45:12 MST 2022 3 day old kernel. Already discussed. Today is Feb 14.

Re: New crash when waking from sleep on Thinkpad T490

2022-02-14 Thread Lucas
Am hiting this too, during unhibernate, 100% reproduction. It started after installing a -current snapshot last Saturday. Got 2 different traces. Both times, the lower half of the screen had noise, while the upper half was black. First time: text console, tried to switch right away to X and

Re: smtpd: mta cert-check result="unverified" on smarthost

2022-02-14 Thread Sebastien Marie
On Mon, Feb 14, 2022 at 11:10:01AM -0700, Todd C. Miller wrote: > On Mon, 14 Feb 2022 17:43:47 +0100, Sebastien Marie wrote: > > > It seems I need to explicitly add "tls" on the action line to enforce > > the tls verification now. > > > > - action "relay-free" relay host

Re: pkg_add/delete slow, not informative and other issues

2022-02-14 Thread Stuart Henderson
On 2022/02/14 10:51, bug.ig...@aleeas.com wrote: > As a new OpenBSD user I found some issues with pkg_add and pkg_delete > compared to other package managers I tried. I tried apt, pacman, xbps, > dnf, pkg (freebsd). There are probably other users with far more > experience than mine, but as a new

Re: smtpd: mta cert-check result="unverified" on smarthost

2022-02-14 Thread Todd C . Miller
On Mon, 14 Feb 2022 17:43:47 +0100, Sebastien Marie wrote: > It seems I need to explicitly add "tls" on the action line to enforce > the tls verification now. > > - action "relay-free" relay host "smtps://f...@smtp.free.fr" auth s> > + action "relay-free" relay host

Re: pkg_add/delete slow, not informative and other issues

2022-02-14 Thread Ian Darwin
First, my bias: I find pkg_add superior to many other package management schemes. The fact that you mention having tried so many others is an indication that you have some exposure to many, but also an indication that package management is a continuous evolution, not a once-solved problem. > 2.

Re: smtpd: mta cert-check result="unverified" on smarthost

2022-02-14 Thread Sebastien Marie
Hi, It seems I need to explicitly add "tls" on the action line to enforce the tls verification now. - action "relay-free" relay host "smtps://f...@smtp.free.fr" auth + action "relay-free" relay host "smtps://f...@smtp.free.fr" auth tls I am unsure if the behaviour change was intented

smtpd: mta cert-check result="unverified" on smarthost

2022-02-14 Thread Sebastien Marie
Hi, After upgrading from OpenBSD 7.0-current (GENERIC.MP) #133: Sat Feb 5 12:11:10 CET 2022" toOpenBSD 7.0-current (GENERIC.MP) #335: Sun Feb 13 16:41:43 MST 2022 I am seeing smtpd to report smarthost connection (when my local user is sending a mail) with: Feb 14 16:58:42 quade

Re: [External] : nat-to round-robin without a pool

2022-02-14 Thread Alexandr Nedvedicky
Hello Giovanni, thank you for bug report. diff below should fix the issue. Can you give it a try? I've decided to deal with consequences instead of making pfctl(8) parser bit smarter. As soon as we load rule: match out on em0 from 192.168.1.0/24 to any \ nat-to { 172.16.1.1 }