Re: system freeze on 14.0-CURRENT

2021-03-30 Thread Masachika ISHIZUKA
main-8223717ce is working fine on vostro 3267, but isn't working on XPS 12. -- Masachika ISHIZUKA ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to

update to RC4 from RC3 shutdown regression

2021-03-30 Thread Antonio Olivares
Dear all, after updating to RC4 with # freebsd-update -r upgrade 13.0RC4 When I shutdown, I get error messages AE_??? PCI Press any key to reboot It shutdown before from 13.0-BETA4 updated all the way to RC3. I can save a screenshot if needed. Thanks.

Re: 13.0-RC3 bison causes tputs SIGSEGV

2021-03-30 Thread Thomas Dickey
On Tue, Mar 30, 2021 at 08:37:22AM +0200, Juraj Lutter wrote: > Hi, > > very similar behavior is observed in editors/poke, on recent 13.0-STABLE > (stable/13-85ad493677a2): > > (lldb) bt > * thread #1, name = 'poke', stop reason = signal SIGSEGV: invalid address > (fault address: 0x0) > *

Re: 13.0 RC4 might be delayed

2021-03-30 Thread Guido Falsi via freebsd-current
On 29/03/21 16:28, Mario Lobo wrote: [snip] Good point. Now the question is, what the default should be. Since the correct aio configuration is in the pkg-message and easy to setup I'd go for default to AIO turned on. -- Guido Falsi +1 The way it is, is running smooth here on STABLE/13

Re: 13.0-RC3 bison causes tputs SIGSEGV

2021-03-30 Thread Juraj Lutter
Hi, very similar behavior is observed in editors/poke, on recent 13.0-STABLE (stable/13-85ad493677a2): (lldb) bt * thread #1, name = 'poke', stop reason = signal SIGSEGV: invalid address (fault address: 0x0) * frame #0: 0x frame #1: 0x0008009ed30a