Re: Sparc64 livelock/system freeze w/cpu traces

On Sep 2, 2023, at 7:35 AM, Martin Pieuchot wrote: > > On 28/06/23(Wed) 20:07, Kurt Miller wrote: >> On Jun 28, 2023, at 7:16 AM, Martin Pieuchot wrote: >>> >>> On 28/06/23(Wed) 08:58, Claudio Jeker wrote: I doubt this is a missing wakeup. It is more the system is thrashing and

Re: Sparc64 livelock/system freeze w/cpu traces

On 28/06/23(Wed) 20:07, Kurt Miller wrote: > On Jun 28, 2023, at 7:16 AM, Martin Pieuchot wrote: > > > > On 28/06/23(Wed) 08:58, Claudio Jeker wrote: > >> > >> I doubt this is a missing wakeup. It is more the system is thrashing and > >> not making progress. The SIGSTOP causes all threads to par

Re: Sparc64 livelock/system freeze w/cpu traces

On Wed, Jun 28, 2023 at 01:16:42PM +0200, Martin Pieuchot wrote: > On 28/06/23(Wed) 08:58, Claudio Jeker wrote: > > On Tue, Jun 27, 2023 at 08:18:15PM -0400, Kurt Miller wrote: > > > On Jun 27, 2023, at 1:52 PM, Kurt Miller > > > wrote: > > > > > > > > On Jun 14, 2023, at 12:51 PM, Vitaliy Makko

Re: Sparc64 livelock/system freeze w/cpu traces

On 28/06/23(Wed) 08:58, Claudio Jeker wrote: > On Tue, Jun 27, 2023 at 08:18:15PM -0400, Kurt Miller wrote: > > On Jun 27, 2023, at 1:52 PM, Kurt Miller wrote: > > > > > > On Jun 14, 2023, at 12:51 PM, Vitaliy Makkoveev wrote: > > >> > > >> On Tue, May 30, 2023 at 01:31:08PM +0200, Martin Pieuc

Re: Sparc64 livelock/system freeze w/cpu traces

On Tue, Jun 27, 2023 at 08:18:15PM -0400, Kurt Miller wrote: > On Jun 27, 2023, at 1:52 PM, Kurt Miller wrote: > > > > On Jun 14, 2023, at 12:51 PM, Vitaliy Makkoveev wrote: > >> > >> On Tue, May 30, 2023 at 01:31:08PM +0200, Martin Pieuchot wrote: > >>> So it seems the java process is holding

Re: Sparc64 livelock/system freeze w/cpu traces

On Jun 27, 2023, at 1:52 PM, Kurt Miller wrote: > > On Jun 14, 2023, at 12:51 PM, Vitaliy Makkoveev wrote: >> >> On Tue, May 30, 2023 at 01:31:08PM +0200, Martin Pieuchot wrote: >>> So it seems the java process is holding the `sysctl_lock' for too long >>> and block all other sysctl(2). This s

Re: Sparc64 livelock/system freeze w/cpu traces

On Jun 14, 2023, at 12:51 PM, Vitaliy Makkoveev wrote: > > On Tue, May 30, 2023 at 01:31:08PM +0200, Martin Pieuchot wrote: >> So it seems the java process is holding the `sysctl_lock' for too long >> and block all other sysctl(2). This seems wrong to me. We should come >> up with a clever way

Re: Sparc64 livelock/system freeze w/cpu traces

On Tue, May 30, 2023 at 01:31:08PM +0200, Martin Pieuchot wrote: > On 25/05/23(Thu) 16:33, Kurt Miller wrote: > > On May 22, 2023, at 2:27 AM, Claudio Jeker wrote: > > > I have seen these WITNESS warnings on other systems as well. I doubt this > > > is the problem. IIRC this warning is because sys

Re: Sparc64 livelock/system freeze w/cpu traces

On 25/05/23(Thu) 16:33, Kurt Miller wrote: > On May 22, 2023, at 2:27 AM, Claudio Jeker wrote: > > I have seen these WITNESS warnings on other systems as well. I doubt this > > is the problem. IIRC this warning is because sys_mount() is doing it wrong > > but it is not really an issue since sys_mo

Re: Sparc64 livelock/system freeze w/cpu traces

On May 22, 2023, at 2:27 AM, Claudio Jeker wrote: > I have seen these WITNESS warnings on other systems as well. I doubt this > is the problem. IIRC this warning is because sys_mount() is doing it wrong > but it is not really an issue since sys_mount is not called often. Yup. I see that now that

Re: Sparc64 livelock/system freeze w/cpu traces

On Sun, May 21, 2023 at 06:11:42PM -0400, Kurt Miller wrote: > > > > On May 17, 2023, at 2:39 PM, Kurt Miller wrote: > > > > On May 13, 2023, at 3:07 PM, Kurt Miller > > wrote: > >> > >> On May 13, 2023, at 9:16 AM, Kurt Miller > >> wrote: > >>> > >>> On

Re: Sparc64 livelock/system freeze w/cpu traces

> On May 17, 2023, at 2:39 PM, Kurt Miller wrote: > > On May 13, 2023, at 3:07 PM, Kurt Miller > wrote: >> >> On May 13, 2023, at 9:16 AM, Kurt Miller wrote: >>> >>> On May 12, 2023, at 10:26 AM, Martin Pieuchot wrote: On 09/05/23(Tue) 20:02,

Re: Sparc64 livelock/system freeze w/cpu traces

On May 13, 2023, at 3:07 PM, Kurt Miller wrote: > > On May 13, 2023, at 9:16 AM, Kurt Miller wrote: >> >> On May 12, 2023, at 10:26 AM, Martin Pieuchot wrote: >>> >>> On 09/05/23(Tue) 20:02, Kurt Miller wrote: While building devel/jdk/1.8 on May 3rd snapshot I noticed the build fre

Re: Sparc64 livelock/system freeze w/cpu traces

On May 13, 2023, at 9:16 AM, Kurt Miller wrote: > > On May 12, 2023, at 10:26 AM, Martin Pieuchot wrote: >> >> On 09/05/23(Tue) 20:02, Kurt Miller wrote: >>> While building devel/jdk/1.8 on May 3rd snapshot I noticed the build >>> freezing >>> and processes getting stuck like ps. After enablin

Re: Sparc64 livelock/system freeze w/cpu traces

On May 13, 2023, at 9:16 AM, Kurt Miller wrote: > > On May 12, 2023, at 10:26 AM, Martin Pieuchot wrote: >> >> On 09/05/23(Tue) 20:02, Kurt Miller wrote: >>> While building devel/jdk/1.8 on May 3rd snapshot I noticed the build >>> freezing >>> and processes getting stuck like ps. After enablin

Re: Sparc64 livelock/system freeze w/cpu traces

On May 12, 2023, at 10:26 AM, Martin Pieuchot wrote: > > On 09/05/23(Tue) 20:02, Kurt Miller wrote: >> While building devel/jdk/1.8 on May 3rd snapshot I noticed the build freezing >> and processes getting stuck like ps. After enabling ddb.console I was able to >> reproduce the livelock and captu

Re: Sparc64 livelock/system freeze w/cpu traces

On 09/05/23(Tue) 20:02, Kurt Miller wrote: > While building devel/jdk/1.8 on May 3rd snapshot I noticed the build freezing > and processes getting stuck like ps. After enabling ddb.console I was able to > reproduce the livelock and capture cpu traces. Dmesg at the end. > Let me know if more informa