On 19.02.2022 13:23, Konstantin Belousov wrote:
On Sat, Feb 19, 2022 at 12:14:16PM -0500, Alexander Motin wrote:
On 19.02.2022 12:02, Mike Karels wrote:
On 18 Feb 2022, at 20:55, Tomoaki AOKI wrote:
Just a thought, but can it be the reason with timing (e.g., rendezvous
within (i)threads, hardw
On 02/09/2022 10:08 pm, Larry Rosenman wrote:
Another one today:
❯ more /var/crash/core.txt.1
borg.lerctr.org dumped core - see /var/crash/vmcore.1
Wed Feb 9 19:30:43 CST 2022
core is available, and I can give access and/or send the core and
kernel/debug stuff.
True for this one too.
On Sat, Feb 19, 2022 at 12:14:16PM -0500, Alexander Motin wrote:
> On 19.02.2022 12:02, Mike Karels wrote:
> > On 18 Feb 2022, at 20:55, Tomoaki AOKI wrote:
> > > Just a thought, but can it be the reason with timing (e.g., rendezvous
> > > within (i)threads, hardware controlls without using hardwar
On 19.02.2022 12:02, Mike Karels wrote:
On 18 Feb 2022, at 20:55, Tomoaki AOKI wrote:
Just a thought, but can it be the reason with timing (e.g., rendezvous
within (i)threads, hardware controlls without using hardware timer)
problem?
On FreeBSD, IIUC, multi processor (multi core) implementation
On 18 Feb 2022, at 20:55, Tomoaki AOKI wrote:
> Just a thought, but can it be the reason with timing (e.g., rendezvous
> within (i)threads, hardware controlls without using hardware timer)
> problem?
>
> On FreeBSD, IIUC, multi processor (multi core) implementation assumes
> SMP (differs only cl
