On Mon, Jul 22, 2024 at 10:52:19PM GMT, Mark Kettenis wrote:
> However, it is entirely plausible that the breakage is caused by either:
>
> dev/acpi/acpipwrres.c rev. 1.14
this is the one I tried backing out with no success.
> or
>
> dev/acpi/acpi.c rev. 1.434
backing only this one out
On Mon, Jul 22, 2024 at 12:50:03PM GMT, Mike Larkin wrote:
> does zzz (suspend, lowercase z) work properly?
It does, regarding USB. (the "wakeup event: GPE 0x0" is still present.)
On Sun, Mar 03, 2024 at 11:58:51AM +, Stuart Henderson wrote:
> On 2024/03/02 14:46, Theo de Raadt wrote:
> > Is this a situation where two libc's are being loaded into the address
> > space? And the 2nd one is refused for pinsyscalls & msyscall, etc etc.
>
> It seems the most likely cause.
On Sat, Mar 02, 2024 at 08:32:04PM +, Lucas Gabriel Vuotto wrote:
> Hello,
>
> gajim is reporting a msyscall error on launch since today's snapshot.
>
> OpenBSD 7.5 (GENERIC.MP) #46: Fri Mar 1 19:36:05 MST 2024
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/
Hello,
gajim is reporting a msyscall error on launch since today's snapshot.
OpenBSD 7.5 (GENERIC.MP) #46: Fri Mar 1 19:36:05 MST 2024
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
99921 python3.10 CALL munmap(0xfbdb9aea778,0x6e8)
99921 python3.10 RET munmap 0
Hi bugs,
As the topic says. Seen as of a couple of minutes ago in
- http://ftp.openbsd.org/pub/OpenBSD/snapshots/amd64/SHA256{,.sig}
- http://cdn.openbsd.org/pub/OpenBSD/snapshots/amd64/SHA256{,.sig}
SHA256.sig:
untrusted comment: verify with openbsd-74-base.pub
