FreeBSD › freebsd-current

Waiting for bufdaemon

Classic

List

Threaded

53 messages Options

123

Jakob Alvermark-2

Waiting for bufdaemon

Hi,

When rebooting my thinkpad the 'bufdaemon' times out:

Waiting (max 60 seconds) for system thread 'bufdaemon' to stop ... timed out

Waiting (max 60 seconds) for system thread 'bufspacedaemon-0' to stop
... timed out

Waiting (max 60 seconds) for system thread 'bufspacedaemon-1' to stop
... timed out

Waiting (max 60 seconds) for system thread 'bufspacedaemon-2' to stop
... timed out

Waiting (max 60 seconds) for system thread 'bufspacedaemon-3' to stop
... timed out

Waiting (max 60 seconds) for system thread 'bufspacedaemon-4' to stop
... timed out

Waiting (max 60 seconds) for system thread 'bufspacedaemon-5' to stop
... timed out

This started happening recently (within the last week I think).

Any ideas?

Thanks,

Jakob

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

Konstantin Belousov

Re: Waiting for bufdaemon

On Fri, Jan 15, 2021 at 11:26:47AM +0100, Jakob Alvermark wrote:

> Hi,
>
>
> When rebooting my thinkpad the 'bufdaemon' times out:
>
> Waiting (max 60 seconds) for system thread 'bufdaemon' to stop ... timed out
>
> Waiting (max 60 seconds) for system thread 'bufspacedaemon-0' to stop ...
> timed out
>
> Waiting (max 60 seconds) for system thread 'bufspacedaemon-1' to stop ...
> timed out
>
> Waiting (max 60 seconds) for system thread 'bufspacedaemon-2' to stop ...
> timed out
>
> Waiting (max 60 seconds) for system thread 'bufspacedaemon-3' to stop ...
> timed out
>
> Waiting (max 60 seconds) for system thread 'bufspacedaemon-4' to stop ...
> timed out
>
> Waiting (max 60 seconds) for system thread 'bufspacedaemon-5' to stop ...
> timed out
>
>
> This started happening recently (within the last week I think).
>
>
> Any ideas?

It is bare metal install, right?
Do you see any mis-handling of time or timeouts while the system operates?

Can you bisect it?
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

Yasuhiro KIMURA

Re: Waiting for bufdaemon

In reply to this post by Jakob Alvermark-2

From: Jakob Alvermark <[hidden email]>
Subject: Waiting for bufdaemon
Date: Fri, 15 Jan 2021 11:26:47 +0100

> When rebooting my thinkpad the 'bufdaemon' times out:
>
> Waiting (max 60 seconds) for system thread 'bufdaemon' to stop
> ... timed out
>
> Waiting (max 60 seconds) for system thread 'bufspacedaemon-0' to stop
> ... timed out
>
> Waiting (max 60 seconds) for system thread 'bufspacedaemon-1' to stop
> ... timed out
>
> Waiting (max 60 seconds) for system thread 'bufspacedaemon-2' to stop
> ... timed out
>
> Waiting (max 60 seconds) for system thread 'bufspacedaemon-3' to stop
> ... timed out
>
> Waiting (max 60 seconds) for system thread 'bufspacedaemon-4' to stop
> ... timed out
>
> Waiting (max 60 seconds) for system thread 'bufspacedaemon-5' to stop
> ... timed out
>
>
> This started happening recently (within the last week I think).
>
>
> Any ideas?

I have been experiencing same problem with my 13-CURRENT amd64
VirtualBox VM for about a month. The conditions that the problem
happens are unclear and all what I can say is

* It happens only after I login in the VM and do something for a
while. If I boot the VM and shut it down immediately, it never
happens.
* When the problem happens, one or more unkillable processes seem to
be left.

---
Yasuhiro Kimura
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

Jakob Alvermark-2

Re: Waiting for bufdaemon

In reply to this post by Konstantin Belousov

On 1/15/21 11:53 AM, Konstantin Belousov wrote:

> On Fri, Jan 15, 2021 at 11:26:47AM +0100, Jakob Alvermark wrote:
>> Hi,
>>
>>
>> When rebooting my thinkpad the 'bufdaemon' times out:
>>
>> Waiting (max 60 seconds) for system thread 'bufdaemon' to stop ... timed out
>>
>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-0' to stop ...
>> timed out
>>
>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-1' to stop ...
>> timed out
>>
>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-2' to stop ...
>> timed out
>>
>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-3' to stop ...
>> timed out
>>
>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-4' to stop ...
>> timed out
>>
>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-5' to stop ...
>> timed out
>>
>>
>> This started happening recently (within the last week I think).
>>
>>
>> Any ideas?
> It is bare metal install, right?

Yes, this is a Thinkpad X395 (AMD Ryzen 5 PRO 3500U)
> Do you see any mis-handling of time or timeouts while the system operates?
My webcam (using webcamd) seems to be a little flakey, but that's about
the only thing I have noticed.
>
> Can you bisect it?

I could try, but it will take some time, it seems this only happens when
system has been running for a while. Rebooting right after a boot does
not show this behavior.

Jakob

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

Juraj Lutter-5

Re: Waiting for bufdaemon

In reply to this post by Yasuhiro KIMURA

> On 15 Jan 2021, at 12:10, Yasuhiro Kimura <[hidden email]> wrote:
>
> From: Jakob Alvermark <[hidden email]>
> Subject: Waiting for bufdaemon
> Date: Fri, 15 Jan 2021 11:26:47 +0100
>
>> When rebooting my thinkpad the 'bufdaemon' times out:
>>
>> Waiting (max 60 seconds) for system thread 'bufdaemon' to stop
>> ... timed out
>>
>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-0' to stop
>> ... timed out
>>
>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-1' to stop
>> ... timed out
>>
>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-2' to stop
>> ... timed out
>>
>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-3' to stop
>> ... timed out
>>
>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-4' to stop
>> ... timed out
>>
>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-5' to stop
>> ... timed out
>>
>>
>> This started happening recently (within the last week I think).
>>
>>
>> Any ideas?
>
> I have been experiencing same problem with my 13-CURRENT amd64
> VirtualBox VM for about a month. The conditions that the problem
> happens are unclear and all what I can say is
>
> * It happens only after I login in the VM and do something for a
> while. If I boot the VM and shut it down immediately, it never
> happens.
> * When the problem happens, one or more unkillable processes seem to
> be left.

I have been fighting with situations like this for month or two, opened more PRs about it.
My observation was that after putting some load on the machine, mysterious mrsas(4)
timeouts started to happen, processes were unkillable, reboots could not complete in time...

For sake of bisect, main-c255656-gb500c184b656 is known to work OK for me as of now.

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

Santiago Martinez

Re: Waiting for bufdaemon

Hi, there, im having the same issue here ( AMD Ryzen7). i do not use mrsas but in my case even if i try to reboot immediately after a fresh reboot i get the timeouts. Regards Santiago
-------- Original message --------From: Juraj Lutter <[hidden email]> Date: 15/01/2021 12:17 (GMT+01:00) To: [hidden email] Subject: Re: Waiting for bufdaemon > On 15 Jan 2021, at 12:10, Yasuhiro Kimura <[hidden email]> wrote:> > From: Jakob Alvermark <[hidden email]>> Subject: Waiting for bufdaemon> Date: Fri, 15 Jan 2021 11:26:47 +0100> >> When rebooting my thinkpad the 'bufdaemon' times out:>> >> Waiting (max 60 seconds) for system thread 'bufdaemon' to stop>> ... timed out>> >> Waiting (max 60 seconds) for system thread 'bufspacedaemon-0' to stop>> ... timed out>> >> Waiting (max 60 seconds) for system thread 'bufspacedaemon-1' to stop>> ... timed out>> >> Waiting (max 60 seconds) for system thread 'bufspacedaemon-2' to stop>> ... timed out>> >> Waiting (max 60 seconds) for system thread 'bufspacedaemon-3' to stop>> ... timed out>> >> Waiting (max 60 seconds) for system thread 'bufspacedaemon-4' to stop>> ... timed out>> >> Waiting (max 60 seconds) for system thread 'bufspacedaemon-5' to stop>> ... timed out>> >> >> This started happening recently (within the last week I think).>> >> >> Any ideas?> > I have been experiencing same problem with my 13-CURRENT amd64> VirtualBox VM for about a month. The conditions that the problem> happens are unclear and all what I can say is> > * It happens only after I login in the VM and do something for a> while. If I boot the VM and shut it down immediately, it never> happens.> * When the problem happens, one or more unkillable processes seem to> be left.I have been fighting with situations like this for month or two, opened more PRs about it.My observation was that after putting some load on the machine, mysterious mrsas(4)timeouts started to happen, processes were unkillable, reboots could not complete in time...For sake of bisect, main-c255656-gb500c184b656 is known to work OK for me as of [hidden email] mailing listhttps://lists.freebsd.org/mailman/listinfo/freebsd-currentTo unsubscribe, send any mail to "[hidden email]"
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

Mikaël Urankar-2

Re: Waiting for bufdaemon

In reply to this post by Jakob Alvermark-2

On 15/01/2021 11:26, Jakob Alvermark wrote:

> Hi,
>
>
> When rebooting my thinkpad the 'bufdaemon' times out:
>
> Waiting (max 60 seconds) for system thread 'bufdaemon' to stop ...
> timed out
>
> Waiting (max 60 seconds) for system thread 'bufspacedaemon-0' to stop
> ... timed out
>
> Waiting (max 60 seconds) for system thread 'bufspacedaemon-1' to stop
> ... timed out
>
> Waiting (max 60 seconds) for system thread 'bufspacedaemon-2' to stop
> ... timed out
>
> Waiting (max 60 seconds) for system thread 'bufspacedaemon-3' to stop
> ... timed out
>
> Waiting (max 60 seconds) for system thread 'bufspacedaemon-4' to stop
> ... timed out
>
> Waiting (max 60 seconds) for system thread 'bufspacedaemon-5' to stop
> ... timed out
>
>
> This started happening recently (within the last week I think).

Hi,

I'm also affected. I have an AMD Ryzen 9 3900X cpu, running bare metal.

5844bd058aed6f3d0c8cbbddd6aa95993ece0189 (jobc: rework detection of
orphaned groups) "seems" ok

cd240c9cf100bec3def38ceb4a320611b1d02693 (x86 vdso gettc: Add RDTSCP
support), affected by the timeout.

I haven't tried the intermediate commit yet.

My intel machine doesn't seem to be affected

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

Konstantin Belousov

Re: Waiting for bufdaemon

On Fri, Jan 15, 2021 at 03:56:01PM +0100, Mikaël Urankar wrote:

> On 15/01/2021 11:26, Jakob Alvermark wrote:
> > Hi,
> >
> >
> > When rebooting my thinkpad the 'bufdaemon' times out:
> >
> > Waiting (max 60 seconds) for system thread 'bufdaemon' to stop ... timed
> > out
> >
> > Waiting (max 60 seconds) for system thread 'bufspacedaemon-0' to stop
> > ... timed out
> >
> > Waiting (max 60 seconds) for system thread 'bufspacedaemon-1' to stop
> > ... timed out
> >
> > Waiting (max 60 seconds) for system thread 'bufspacedaemon-2' to stop
> > ... timed out
> >
> > Waiting (max 60 seconds) for system thread 'bufspacedaemon-3' to stop
> > ... timed out
> >
> > Waiting (max 60 seconds) for system thread 'bufspacedaemon-4' to stop
> > ... timed out
> >
> > Waiting (max 60 seconds) for system thread 'bufspacedaemon-5' to stop
> > ... timed out
> >
> >
> > This started happening recently (within the last week I think).
>
> Hi,
>
> I'm also affected. I have an AMD Ryzen 9 3900X cpu, running bare metal.
>
> 5844bd058aed6f3d0c8cbbddd6aa95993ece0189 (jobc: rework detection of orphaned
> groups) "seems" ok
>
> cd240c9cf100bec3def38ceb4a320611b1d02693 (x86 vdso gettc: Add RDTSCP
> support), affected by the timeout.
>
> I haven't tried the intermediate commit yet.
>
> My intel machine doesn't seem to be affected

If you revert only 9e680e4005b7, is it fixed ?
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

Jakob Alvermark-2

Re: Waiting for bufdaemon

In reply to this post by Mikaël Urankar-2

On 1/15/21 3:56 PM, Mikaël Urankar wrote:

> On 15/01/2021 11:26, Jakob Alvermark wrote:
>> Hi,
>>
>>
>> When rebooting my thinkpad the 'bufdaemon' times out:
>>
>> Waiting (max 60 seconds) for system thread 'bufdaemon' to stop ...
>> timed out
>>
>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-0' to stop
>> ... timed out
>>
>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-1' to stop
>> ... timed out
>>
>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-2' to stop
>> ... timed out
>>
>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-3' to stop
>> ... timed out
>>
>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-4' to stop
>> ... timed out
>>
>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-5' to stop
>> ... timed out
>>
>>
>> This started happening recently (within the last week I think).
>
> Hi,
>
> I'm also affected. I have an AMD Ryzen 9 3900X cpu, running bare metal.
>
> 5844bd058aed6f3d0c8cbbddd6aa95993ece0189 (jobc: rework detection of
> orphaned groups) "seems" ok
>
> cd240c9cf100bec3def38ceb4a320611b1d02693 (x86 vdso gettc: Add RDTSCP
> support), affected by the timeout.
>
> I haven't tried the intermediate commit yet.
>
> My intel machine doesn't seem to be affected

I observed the same here. It seems to only happen on my AMD laptop.

I have an Intel laptop which seems fine.

Jakob

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

Mikaël Urankar-2

Re: Waiting for bufdaemon

In reply to this post by Konstantin Belousov

On 15/01/2021 16:02, Konstantin Belousov wrote:

> On Fri, Jan 15, 2021 at 03:56:01PM +0100, Mikaël Urankar wrote:
>> On 15/01/2021 11:26, Jakob Alvermark wrote:
>>> Hi,
>>>
>>>
>>> When rebooting my thinkpad the 'bufdaemon' times out:
>>>
>>> Waiting (max 60 seconds) for system thread 'bufdaemon' to stop ... timed
>>> out
>>>
>>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-0' to stop
>>> ... timed out
>>>
>>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-1' to stop
>>> ... timed out
>>>
>>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-2' to stop
>>> ... timed out
>>>
>>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-3' to stop
>>> ... timed out
>>>
>>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-4' to stop
>>> ... timed out
>>>
>>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-5' to stop
>>> ... timed out
>>>
>>>
>>> This started happening recently (within the last week I think).
>>
>> Hi,
>>
>> I'm also affected. I have an AMD Ryzen 9 3900X cpu, running bare metal.
>>
>> 5844bd058aed6f3d0c8cbbddd6aa95993ece0189 (jobc: rework detection of orphaned
>> groups) "seems" ok
>>
>> cd240c9cf100bec3def38ceb4a320611b1d02693 (x86 vdso gettc: Add RDTSCP
>> support), affected by the timeout.
>>
>> I haven't tried the intermediate commit yet.
>>
>> My intel machine doesn't seem to be affected
>
> If you revert only 9e680e4005b7, is it fixed ?
>

Yes it seems to be fixed with 9e680e4005b7 reverted (I've only done 2
tests, I can do more if you want)
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

Konstantin Belousov

Re: Waiting for bufdaemon

On Fri, Jan 15, 2021 at 04:30:19PM +0100, Mikaël Urankar wrote:

> On 15/01/2021 16:02, Konstantin Belousov wrote:
> > On Fri, Jan 15, 2021 at 03:56:01PM +0100, Mikaël Urankar wrote:
> > > On 15/01/2021 11:26, Jakob Alvermark wrote:
> > > > Hi,
> > > >
> > > >
> > > > When rebooting my thinkpad the 'bufdaemon' times out:
> > > >
> > > > Waiting (max 60 seconds) for system thread 'bufdaemon' to stop ... timed
> > > > out
> > > >
> > > > Waiting (max 60 seconds) for system thread 'bufspacedaemon-0' to stop
> > > > ... timed out
> > > >
> > > > Waiting (max 60 seconds) for system thread 'bufspacedaemon-1' to stop
> > > > ... timed out
> > > >
> > > > Waiting (max 60 seconds) for system thread 'bufspacedaemon-2' to stop
> > > > ... timed out
> > > >
> > > > Waiting (max 60 seconds) for system thread 'bufspacedaemon-3' to stop
> > > > ... timed out
> > > >
> > > > Waiting (max 60 seconds) for system thread 'bufspacedaemon-4' to stop
> > > > ... timed out
> > > >
> > > > Waiting (max 60 seconds) for system thread 'bufspacedaemon-5' to stop
> > > > ... timed out
> > > >
> > > >
> > > > This started happening recently (within the last week I think).
> > >
> > > Hi,
> > >
> > > I'm also affected. I have an AMD Ryzen 9 3900X cpu, running bare metal.
> > >
> > > 5844bd058aed6f3d0c8cbbddd6aa95993ece0189 (jobc: rework detection of orphaned
> > > groups) "seems" ok
> > >
> > > cd240c9cf100bec3def38ceb4a320611b1d02693 (x86 vdso gettc: Add RDTSCP
> > > support), affected by the timeout.
> > >
> > > I haven't tried the intermediate commit yet.
> > >
> > > My intel machine doesn't seem to be affected
> >
> > If you revert only 9e680e4005b7, is it fixed ?
> >
> Yes it seems to be fixed with 9e680e4005b7 reverted (I've only done 2 tests,
> I can do more if you want)

Please show me the output from sysctl
kern.timecounter
kern.eventtimer
and first 100 lines of dmesg from the verbose boot (that contains the CPU
ident lines).
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

Mikaël Urankar-2

Re: Waiting for bufdaemon

On 15/01/2021 16:45, Konstantin Belousov wrote:

> On Fri, Jan 15, 2021 at 04:30:19PM +0100, Mikaël Urankar wrote:
>> On 15/01/2021 16:02, Konstantin Belousov wrote:
>>> On Fri, Jan 15, 2021 at 03:56:01PM +0100, Mikaël Urankar wrote:
>>>> On 15/01/2021 11:26, Jakob Alvermark wrote:
>>>>> Hi,
>>>>>
>>>>>
>>>>> When rebooting my thinkpad the 'bufdaemon' times out:
>>>>>
>>>>> Waiting (max 60 seconds) for system thread 'bufdaemon' to stop ... timed
>>>>> out
>>>>>
>>>>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-0' to stop
>>>>> ... timed out
>>>>>
>>>>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-1' to stop
>>>>> ... timed out
>>>>>
>>>>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-2' to stop
>>>>> ... timed out
>>>>>
>>>>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-3' to stop
>>>>> ... timed out
>>>>>
>>>>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-4' to stop
>>>>> ... timed out
>>>>>
>>>>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-5' to stop
>>>>> ... timed out
>>>>>
>>>>>
>>>>> This started happening recently (within the last week I think).
>>>>
>>>> Hi,
>>>>
>>>> I'm also affected. I have an AMD Ryzen 9 3900X cpu, running bare metal.
>>>>
>>>> 5844bd058aed6f3d0c8cbbddd6aa95993ece0189 (jobc: rework detection of orphaned
>>>> groups) "seems" ok
>>>>
>>>> cd240c9cf100bec3def38ceb4a320611b1d02693 (x86 vdso gettc: Add RDTSCP
>>>> support), affected by the timeout.
>>>>
>>>> I haven't tried the intermediate commit yet.
>>>>
>>>> My intel machine doesn't seem to be affected
>>>
>>> If you revert only 9e680e4005b7, is it fixed ?
>>>
>> Yes it seems to be fixed with 9e680e4005b7 reverted (I've only done 2 tests,
>> I can do more if you want)
> Please show me the output from sysctl
> kern.timecounter
> kern.eventtimer
> and first 100 lines of dmesg from the verbose boot (that contains the CPU
> ident lines).
>

I put the /var/run/dmesg.boot file on freefall /home/mikael/dmesg.boot
(it seems to be truncated though, I don't know how to retrieve the full log)

sysctl kern.timecounter
kern.timecounter.tsc_shift: 1
kern.timecounter.smp_tsc_adjust: 0
kern.timecounter.smp_tsc: 1
kern.timecounter.invariant_tsc: 1
kern.timecounter.fast_gettime: 1
kern.timecounter.tick: 1
kern.timecounter.choice: ACPI-fast(900) HPET(950) i8254(0) TSC-low(1000)
dummy(-1000000)
kern.timecounter.hardware: TSC-low
kern.timecounter.alloweddeviation: 5
kern.timecounter.timehands_count: 2
kern.timecounter.stepwarnings: 0
kern.timecounter.tc.ACPI-fast.quality: 900
kern.timecounter.tc.ACPI-fast.frequency: 3579545
kern.timecounter.tc.ACPI-fast.counter: 1470549582
kern.timecounter.tc.ACPI-fast.mask: 4294967295
kern.timecounter.tc.HPET.quality: 950
kern.timecounter.tc.HPET.frequency: 14318180
kern.timecounter.tc.HPET.counter: 378058131
kern.timecounter.tc.HPET.mask: 4294967295
kern.timecounter.tc.i8254.quality: 0
kern.timecounter.tc.i8254.frequency: 1193182
kern.timecounter.tc.i8254.counter: 20425
kern.timecounter.tc.i8254.mask: 65535
kern.timecounter.tc.TSC-low.quality: 1000
kern.timecounter.tc.TSC-low.frequency: 1900039387
kern.timecounter.tc.TSC-low.counter: 2386729797
kern.timecounter.tc.TSC-low.mask: 4294967295

sysctl kern.eventtimer
kern.eventtimer.choice: LAPIC(600) HPET(350) HPET1(350) HPET2(350)
i8254(100) RTC(0)
kern.eventtimer.et.HPET2.quality: 350
kern.eventtimer.et.HPET2.frequency: 14318180
kern.eventtimer.et.HPET2.flags: 3
kern.eventtimer.et.HPET1.quality: 350
kern.eventtimer.et.HPET1.frequency: 14318180
kern.eventtimer.et.HPET1.flags: 3
kern.eventtimer.et.HPET.quality: 350
kern.eventtimer.et.HPET.frequency: 14318180
kern.eventtimer.et.HPET.flags: 3
kern.eventtimer.et.RTC.quality: 0
kern.eventtimer.et.RTC.frequency: 32768
kern.eventtimer.et.RTC.flags: 17
kern.eventtimer.et.i8254.quality: 100
kern.eventtimer.et.i8254.frequency: 1193182
kern.eventtimer.et.i8254.flags: 1
kern.eventtimer.et.LAPIC.quality: 600
kern.eventtimer.et.LAPIC.frequency: 50001034
kern.eventtimer.et.LAPIC.flags: 7
kern.eventtimer.periodic: 0
kern.eventtimer.timer: LAPIC
kern.eventtimer.idletick: 0
kern.eventtimer.singlemul: 2
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

Konstantin Belousov

Re: Waiting for bufdaemon

On Fri, Jan 15, 2021 at 05:18:56PM +0100, Mikaël Urankar wrote:

> On 15/01/2021 16:45, Konstantin Belousov wrote:
> > On Fri, Jan 15, 2021 at 04:30:19PM +0100, Mikaël Urankar wrote:
> > > On 15/01/2021 16:02, Konstantin Belousov wrote:
> > > > On Fri, Jan 15, 2021 at 03:56:01PM +0100, Mikaël Urankar wrote:
> > > > > On 15/01/2021 11:26, Jakob Alvermark wrote:
> > > > > > Hi,
> > > > > >
> > > > > >
> > > > > > When rebooting my thinkpad the 'bufdaemon' times out:
> > > > > >
> > > > > > Waiting (max 60 seconds) for system thread 'bufdaemon' to stop ... timed
> > > > > > out
> > > > > >
> > > > > > Waiting (max 60 seconds) for system thread 'bufspacedaemon-0' to stop
> > > > > > ... timed out
> > > > > >
> > > > > > Waiting (max 60 seconds) for system thread 'bufspacedaemon-1' to stop
> > > > > > ... timed out
> > > > > >
> > > > > > Waiting (max 60 seconds) for system thread 'bufspacedaemon-2' to stop
> > > > > > ... timed out
> > > > > >
> > > > > > Waiting (max 60 seconds) for system thread 'bufspacedaemon-3' to stop
> > > > > > ... timed out
> > > > > >
> > > > > > Waiting (max 60 seconds) for system thread 'bufspacedaemon-4' to stop
> > > > > > ... timed out
> > > > > >
> > > > > > Waiting (max 60 seconds) for system thread 'bufspacedaemon-5' to stop
> > > > > > ... timed out
> > > > > >
> > > > > >
> > > > > > This started happening recently (within the last week I think).
> > > > >
> > > > > Hi,
> > > > >
> > > > > I'm also affected. I have an AMD Ryzen 9 3900X cpu, running bare metal.
> > > > >
> > > > > 5844bd058aed6f3d0c8cbbddd6aa95993ece0189 (jobc: rework detection of orphaned
> > > > > groups) "seems" ok
> > > > >
> > > > > cd240c9cf100bec3def38ceb4a320611b1d02693 (x86 vdso gettc: Add RDTSCP
> > > > > support), affected by the timeout.
> > > > >
> > > > > I haven't tried the intermediate commit yet.
> > > > >
> > > > > My intel machine doesn't seem to be affected
> > > >
> > > > If you revert only 9e680e4005b7, is it fixed ?
> > > >
> > > Yes it seems to be fixed with 9e680e4005b7 reverted (I've only done 2 tests,
> > > I can do more if you want)
> > Please show me the output from sysctl
> > kern.timecounter
> > kern.eventtimer
> > and first 100 lines of dmesg from the verbose boot (that contains the CPU
> > ident lines).
> >
>
> I put the /var/run/dmesg.boot file on freefall /home/mikael/dmesg.boot (it
> seems to be truncated though, I don't know how to retrieve the full log)
>
> sysctl kern.timecounter
> kern.timecounter.tsc_shift: 1
> kern.timecounter.smp_tsc_adjust: 0
> kern.timecounter.smp_tsc: 1
> kern.timecounter.invariant_tsc: 1
> kern.timecounter.fast_gettime: 1
> kern.timecounter.tick: 1
> kern.timecounter.choice: ACPI-fast(900) HPET(950) i8254(0) TSC-low(1000)
> dummy(-1000000)
> kern.timecounter.hardware: TSC-low
> kern.timecounter.alloweddeviation: 5
> kern.timecounter.timehands_count: 2
> kern.timecounter.stepwarnings: 0
> kern.timecounter.tc.ACPI-fast.quality: 900
> kern.timecounter.tc.ACPI-fast.frequency: 3579545
> kern.timecounter.tc.ACPI-fast.counter: 1470549582
> kern.timecounter.tc.ACPI-fast.mask: 4294967295
> kern.timecounter.tc.HPET.quality: 950
> kern.timecounter.tc.HPET.frequency: 14318180
> kern.timecounter.tc.HPET.counter: 378058131
> kern.timecounter.tc.HPET.mask: 4294967295
> kern.timecounter.tc.i8254.quality: 0
> kern.timecounter.tc.i8254.frequency: 1193182
> kern.timecounter.tc.i8254.counter: 20425
> kern.timecounter.tc.i8254.mask: 65535
> kern.timecounter.tc.TSC-low.quality: 1000
> kern.timecounter.tc.TSC-low.frequency: 1900039387
> kern.timecounter.tc.TSC-low.counter: 2386729797
> kern.timecounter.tc.TSC-low.mask: 4294967295
>
> sysctl kern.eventtimer
> kern.eventtimer.choice: LAPIC(600) HPET(350) HPET1(350) HPET2(350)
> i8254(100) RTC(0)
> kern.eventtimer.et.HPET2.quality: 350
> kern.eventtimer.et.HPET2.frequency: 14318180
> kern.eventtimer.et.HPET2.flags: 3
> kern.eventtimer.et.HPET1.quality: 350
> kern.eventtimer.et.HPET1.frequency: 14318180
> kern.eventtimer.et.HPET1.flags: 3
> kern.eventtimer.et.HPET.quality: 350
> kern.eventtimer.et.HPET.frequency: 14318180
> kern.eventtimer.et.HPET.flags: 3
> kern.eventtimer.et.RTC.quality: 0
> kern.eventtimer.et.RTC.frequency: 32768
> kern.eventtimer.et.RTC.flags: 17
> kern.eventtimer.et.i8254.quality: 100
> kern.eventtimer.et.i8254.frequency: 1193182
> kern.eventtimer.et.i8254.flags: 1
> kern.eventtimer.et.LAPIC.quality: 600
> kern.eventtimer.et.LAPIC.frequency: 50001034
> kern.eventtimer.et.LAPIC.flags: 7
> kern.eventtimer.periodic: 0
> kern.eventtimer.timer: LAPIC
> kern.eventtimer.idletick: 0
> kern.eventtimer.singlemul: 2

It is clipped at the start, and that was the information which I need.
Add something like
kern.msgbufsize=1048576
to /boot/loader.conf and try again. I need to see the lines starting with

CPU: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (1992.08-MHz K8-class CPU)
Origin="GenuineIntel" Id=0x806ea Family=0x6 Model=0x8e Stepping=10
Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,C
MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
...

(well, this is my w/s, your CPU would be different of course).

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

Mikaël Urankar-2

Re: Waiting for bufdaemon

On 15/01/2021 17:35, Konstantin Belousov wrote:

> On Fri, Jan 15, 2021 at 05:18:56PM +0100, Mikaël Urankar wrote:
>> On 15/01/2021 16:45, Konstantin Belousov wrote:
>>> On Fri, Jan 15, 2021 at 04:30:19PM +0100, Mikaël Urankar wrote:
>>>> On 15/01/2021 16:02, Konstantin Belousov wrote:
>>>>> On Fri, Jan 15, 2021 at 03:56:01PM +0100, Mikaël Urankar wrote:
>>>>>> On 15/01/2021 11:26, Jakob Alvermark wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>>
>>>>>>> When rebooting my thinkpad the 'bufdaemon' times out:
>>>>>>>
>>>>>>> Waiting (max 60 seconds) for system thread 'bufdaemon' to stop ... timed
>>>>>>> out
>>>>>>>
>>>>>>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-0' to stop
>>>>>>> ... timed out
>>>>>>>
>>>>>>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-1' to stop
>>>>>>> ... timed out
>>>>>>>
>>>>>>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-2' to stop
>>>>>>> ... timed out
>>>>>>>
>>>>>>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-3' to stop
>>>>>>> ... timed out
>>>>>>>
>>>>>>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-4' to stop
>>>>>>> ... timed out
>>>>>>>
>>>>>>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-5' to stop
>>>>>>> ... timed out
>>>>>>>
>>>>>>>
>>>>>>> This started happening recently (within the last week I think).
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I'm also affected. I have an AMD Ryzen 9 3900X cpu, running bare metal.
>>>>>>
>>>>>> 5844bd058aed6f3d0c8cbbddd6aa95993ece0189 (jobc: rework detection of orphaned
>>>>>> groups) "seems" ok
>>>>>>
>>>>>> cd240c9cf100bec3def38ceb4a320611b1d02693 (x86 vdso gettc: Add RDTSCP
>>>>>> support), affected by the timeout.
>>>>>>
>>>>>> I haven't tried the intermediate commit yet.
>>>>>>
>>>>>> My intel machine doesn't seem to be affected
>>>>>
>>>>> If you revert only 9e680e4005b7, is it fixed ?
>>>>>
>>>> Yes it seems to be fixed with 9e680e4005b7 reverted (I've only done 2 tests,
>>>> I can do more if you want)
>>> Please show me the output from sysctl
>>> kern.timecounter
>>> kern.eventtimer
>>> and first 100 lines of dmesg from the verbose boot (that contains the CPU
>>> ident lines).
>>>
>>
>> I put the /var/run/dmesg.boot file on freefall /home/mikael/dmesg.boot (it
>> seems to be truncated though, I don't know how to retrieve the full log)
>>
>> sysctl kern.timecounter
>> kern.timecounter.tsc_shift: 1
>> kern.timecounter.smp_tsc_adjust: 0
>> kern.timecounter.smp_tsc: 1
>> kern.timecounter.invariant_tsc: 1
>> kern.timecounter.fast_gettime: 1
>> kern.timecounter.tick: 1
>> kern.timecounter.choice: ACPI-fast(900) HPET(950) i8254(0) TSC-low(1000)
>> dummy(-1000000)
>> kern.timecounter.hardware: TSC-low
>> kern.timecounter.alloweddeviation: 5
>> kern.timecounter.timehands_count: 2
>> kern.timecounter.stepwarnings: 0
>> kern.timecounter.tc.ACPI-fast.quality: 900
>> kern.timecounter.tc.ACPI-fast.frequency: 3579545
>> kern.timecounter.tc.ACPI-fast.counter: 1470549582
>> kern.timecounter.tc.ACPI-fast.mask: 4294967295
>> kern.timecounter.tc.HPET.quality: 950
>> kern.timecounter.tc.HPET.frequency: 14318180
>> kern.timecounter.tc.HPET.counter: 378058131
>> kern.timecounter.tc.HPET.mask: 4294967295
>> kern.timecounter.tc.i8254.quality: 0
>> kern.timecounter.tc.i8254.frequency: 1193182
>> kern.timecounter.tc.i8254.counter: 20425
>> kern.timecounter.tc.i8254.mask: 65535
>> kern.timecounter.tc.TSC-low.quality: 1000
>> kern.timecounter.tc.TSC-low.frequency: 1900039387
>> kern.timecounter.tc.TSC-low.counter: 2386729797
>> kern.timecounter.tc.TSC-low.mask: 4294967295
>>
>> sysctl kern.eventtimer
>> kern.eventtimer.choice: LAPIC(600) HPET(350) HPET1(350) HPET2(350)
>> i8254(100) RTC(0)
>> kern.eventtimer.et.HPET2.quality: 350
>> kern.eventtimer.et.HPET2.frequency: 14318180
>> kern.eventtimer.et.HPET2.flags: 3
>> kern.eventtimer.et.HPET1.quality: 350
>> kern.eventtimer.et.HPET1.frequency: 14318180
>> kern.eventtimer.et.HPET1.flags: 3
>> kern.eventtimer.et.HPET.quality: 350
>> kern.eventtimer.et.HPET.frequency: 14318180
>> kern.eventtimer.et.HPET.flags: 3
>> kern.eventtimer.et.RTC.quality: 0
>> kern.eventtimer.et.RTC.frequency: 32768
>> kern.eventtimer.et.RTC.flags: 17
>> kern.eventtimer.et.i8254.quality: 100
>> kern.eventtimer.et.i8254.frequency: 1193182
>> kern.eventtimer.et.i8254.flags: 1
>> kern.eventtimer.et.LAPIC.quality: 600
>> kern.eventtimer.et.LAPIC.frequency: 50001034
>> kern.eventtimer.et.LAPIC.flags: 7
>> kern.eventtimer.periodic: 0
>> kern.eventtimer.timer: LAPIC
>> kern.eventtimer.idletick: 0
>> kern.eventtimer.singlemul: 2
>
> It is clipped at the start, and that was the information which I need.
> Add something like
> kern.msgbufsize=1048576
> to /boot/loader.conf and try again. I need to see the lines starting with
>
> CPU: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (1992.08-MHz K8-class CPU)
> Origin="GenuineIntel" Id=0x806ea Family=0x6 Model=0x8e Stepping=10
> Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,C
> MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
> ...
>
> (well, this is my w/s, your CPU would be different of course).
>

Thanks, I've updated the file on freefall
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

Freddie Cash-8

Re: Waiting for bufdaemon

On Fri., Jan. 15, 2021, 8:47 a.m. Mikaël Urankar, <[hidden email]>
wrote:

> On 15/01/2021 17:35, Konstantin Belousov wrote:
> > It is clipped at the start, and that was the information which I need.
> > Add something like
> > kern.msgbufsize=1048576
> > to /boot/loader.conf and try again. I need to see the lines starting
> with
> >
> > CPU: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (1992.08-MHz K8-class CPU)
> > Origin="GenuineIntel" Id=0x806ea Family=0x6 Model=0x8e Stepping=10
> >
> Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,C
> > MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
> > ...
> >
> > (well, this is my w/s, your CPU would be different of course).
> >
> Thanks, I've updated the file on freefall.

/var/run/dmesg.boot includes all output from dmesg for the current boot. No
need to manually redirect dmesg output to a file or play with buffer sizes.
:) Just upload that file.

Cheers,
Freddie

Typos due to smartphone keyboard.
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

Juraj Lutter-5

Re: Waiting for bufdaemon

> On 15 Jan 2021, at 18:26, Freddie Cash <[hidden email]> wrote:
>

>
> /var/run/dmesg.boot includes all output from dmesg for the current boot. No
> need to manually redirect dmesg output to a file or play with buffer sizes.
> :) Just upload that file.

On boot, dmesg is saved to dmesg.boot quite lately and start of the circular
buffer can already be rewritten.

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

Freddie Cash-8

Re: Waiting for bufdaemon

On Fri., Jan. 15, 2021, 9:41 a.m. Juraj Lutter, <[hidden email]> wrote:

> > On 15 Jan 2021, at 18:26, Freddie Cash <[hidden email]> wrote:
> >
> > /var/run/dmesg.boot includes all output from dmesg for the current boot.
> No
> > need to manually redirect dmesg output to a file or play with buffer
> sizes.
> > :) Just upload that file.
>
> On boot, dmesg is saved to dmesg.boot quite lately and start of the
> circular
> buffer can already be rewritten.
>

Really? Interesting. Haven't run into that (not saying it can't happen). I
always thought it was essentially streamed to that file once / or /var was
mounted.

Now I'll have to read some RC scripts to see. :)

Thanks for the info.

Cheers,
Freddie

Typos due to smartphone keyboard.

>
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

Mark Millard-4

Re: Waiting for bufdaemon

In reply to this post by Jakob Alvermark-2

In the interest of documenting some variability . . .

While not readily reproducible, on a ThreadRipper 1950X
that I have access to, a recent reboot had one "system
thread" time out: bufspacedaemon-3 . The rest of the
"system thread" list behaved normally.

===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

Rainer Hurling

Re: Waiting for bufdaemon

In reply to this post by Konstantin Belousov

Am 15.01.21 um 16:45 schrieb Konstantin Belousov:

I also have this timeout issue only on AMD, here Ryzen 3950X:

[...]
Waiting for PIDS: 2905
90 seconds watchdog timeout expired. Shutdown terminated.
Fri Jan 15 19:21:01 xxxxxx init[1]: /etc/rc.shutdown terminated
abnormally, going to single user mode
Fri Jan 15 19:21:01 xxxxxx syslogd: exiting on signal 15
wg0: link state changed to DOWN
Waiting (max 69 seconds) for system process `vnlru' to stop... done
Waiting (max 60 seconds) for system process `syncer' to stop...
Syncing disks, vnodes remaining... 22 23 23 1 1 0 0 0 done
Waiting (max 60 seconds) for system thread `bufdaemon' to stop... done
Waiting (max 60 seconds) for system thread `bufspacedaemon-0' to stop...
done
Waiting (max 60 seconds) for system thread `bufspacedaemon-1' to stop...
done
Waiting (max 60 seconds) for system thread `bufspacedaemon-2' to stop...
done
Waiting (max 60 seconds) for system thread `bufspacedaemon-3' to stop...
timeout
Waiting (max 60 seconds) for system thread `bufspacedaemon-4' to stop...
timeout
Waiting (max 60 seconds) for system thread `bufspacedaemon-5' to stop...
done
Waiting (max 60 seconds) for system thread `bufspacedaemon-6' to stop...

You will find the wanted output from sysctl and boot -v in the attachment.

HTH,
Rainer Hurling

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

Waiting_for_bufdaemon.txt (12K) Download Attachment

Yasuhiro KIMURA

Re: Waiting for bufdaemon

In reply to this post by Yasuhiro KIMURA

From: Yasuhiro Kimura <[hidden email]>
Subject: Re: Waiting for bufdaemon
Date: Fri, 15 Jan 2021 20:10:30 +0900 (JST)

> I have been experiencing same problem with my 13-CURRENT amd64
> VirtualBox VM for about a month. The conditions that the problem
> happens are unclear and all what I can say is
>
> * It happens only after I login in the VM and do something for a
> while. If I boot the VM and shut it down immediately, it never
> happens.
> * When the problem happens, one or more unkillable processes seem to
> be left.

CPU of my host is not AMD but Intel. According to the
/var/run/dmesg.boot of VM, information of CPU is as following.

CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (3000.09-MHz K8-class CPU)
Origin="GenuineIntel" Id=0x906ed Family=0x6 Model=0x9e Stepping=13
Features=0x1783fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE,SSE2,HTT>
Features2=0x5eda2203<SSE3,PCLMULQDQ,SSSE3,CX16,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,AESNI,XSAVE,OSXSAVE,AVX,RDRAND>
AMD Features=0x28100800<SYSCALL,NX,RDTSCP,LM>
AMD Features2=0x121<LAHF,ABM,Prefetch>
Structured Extended Features=0x842421<FSGSBASE,AVX2,INVPCID,NFPUSG,RDSEED,CLFLUSHOPT>
Structured Extended Features3=0x30000400<MD_CLEAR,L1DFL,ARCH_CAP>
IA32_ARCH_CAPS=0x29<RDCL_NO,SKIP_L1DFL_VME,MDS_NO>
TSC: P-state invariant

Just FYI.

---
Yasuhiro Kimura
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

123